lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 26 Jun 2019 08:50:47 +0200
From:   Andrzej Pietrasiewicz <>
To:     Russell King - ARM Linux admin <>,
        Emil Velikov <>,,,
        Joonyoung Shim <>,
        Maxime Ripard <>,
        Maarten Lankhorst <>,
        Seung-Woo Kim <>,
        Krzysztof Kozlowski <>,
        Inki Dae <>,
        David Airlie <>,
        Kyungmin Park <>,
        Kukjin Kim <>,,, Sean Paul <>,,
Subject: Re: [PATCH 0/2] Associate ddc adapters with connectors

W dniu 25.06.2019 o 16:20, Daniel Vetter pisze:
> On Tue, Jun 25, 2019 at 03:10:32PM +0100, Russell King - ARM Linux admin wrote:
>> On Tue, Jun 25, 2019 at 04:07:55PM +0200, Daniel Vetter wrote:
>>> Otherwise I like this. Biggest problem I'm seeing here is rolling this out
>>> everywhere, this is a lot of work. And without widespread adoptions it's
>>> not terribly useful for userspace.
>> There will be cases where it's not possible, because the I2C bus is
>> hidden behind a chip that doesn't give you direct access to the DDC
>> bus.
> Oh sure, plus lots of connectors where there's just not ddc bus at all.
> But if we only roll this out for a handful of drivers it's also not great,
> that's what I meant. Looking at
> $ git grep drm_do_get_edid
> there's only very few drivers where the ddc bus is hidden. There's a lot
> more where it's not, and I think a big series to tackle those would serve
> extremely well to make a case for this sysfs link.
> -Daniel

I will respond with a v3 then, including as many drivers as possible.
Those will be compile-tested only, though.


Powered by blists - more mailing lists