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:   Sun, 26 Feb 2017 12:14:46 +0000
From:   Emil Velikov <>
To:     Maxime Ripard <>
Cc:     Tobias Jakobi <>,
        ML dri-devel <>,
        Mark Rutland <>,
        Thomas Petazzoni <>,
        devicetree <>,
        Greg Kroah-Hartman <>,
        linux-kernel <>,,
        Chen-Yu Tsai <>, Rob Herring <>,
        LAKML <>
Subject: Re: [PATCH 0/8] ARM: sun8i: a33: Mali improvements

Hi Maxime,

Thanks for the links.

On 24 February 2017 at 00:19, Maxime Ripard
<> wrote:
> Hi,
> On Fri, Feb 17, 2017 at 08:39:33PM +0000, Emil Velikov wrote:
>> As I feared things have taken a turn for the bitter end :-]
>> It seems that this is a heated topic, so I'l kindly ask that we try
>> the following:
>>  - For people such as myself/Tobias/others who feel that driver and DT
>> bindings should go hand in hand, prove them wrong.
>> But please, do so by pointing to the documentation (conclusion of a
>> previous discussion). This way you don't have to repeat yourself and
>> get [too] annoyed over silly suggestions.
> "The "Open Firmware Device Tree", or simply Device Tree (DT), is a
> data structure and language for describing hardware. More
> specifically, it is a description of hardware that is readable by an
> operating system so that the operating system doesn't need to hard
> code details of the machine"
> "What it does do is provide a language for decoupling the hardware
> configuration from the board and device driver support in the Linux
> kernel (or any other operating system for that matter)."
The above seems to imply that there is (merged) device driver support
in the Linux kernel (or other) that uses the bindings.

It's not my call to make any of the policy, so I'll just kindly
suggest improving the existing documentation:
 - Reword/elaborate if out of tree [Linux or in general?] drivers are
suitable counterpart.
 - Patches could/should reference the "other OS" driver, or the "other
OS" name at least ?

Rather than clumping the above in 2.1 a separate section would be better ?

> And like I said, we already had bindings for out of tree bindings,
> like this one:
> Which triggered no discussion at the time (but the technical one,
> hence a v2, that should always be done).
Needless to say, there's many of us waiting to see a Mali driver land
- hence the noise. It's not meant to belittle/sway the work you and
others do.

>> - The series has code changes which [seemingly] cater for out of tree
>> module(s).
> That patch was dropped, only DT changes remains now, and do not depend
> of that missing patch anyway.
>> Clearly state in the commit message who is the user, why it's save to
>> do so and get an Ack from more prominent [DRM] developers.
> DRM is really not important here. We could implement a driver using
> i2c as far as the DT is concerned.
What I meant to say is:

Please, provide clear expectations from the start - "Linux driver is
OOT with no ETA on landing" or "driver for $FOO OS is at $LINK".
Afaict Hans did the former in the patch mentioned. Perhaps you already
did - in which case pardon for missing it.

> FreeBSD for example uses a different, !DRM framework to support our
> display stack, and still uses the DT.
Interesting - do you have a link handy ? Does it use open-source usespace ?


Powered by blists - more mailing lists