[pull] tilcdc-next for 3.9

Rob Clark robdclark at gmail.com
Mon Feb 18 06:46:34 PST 2013


On Mon, Feb 18, 2013 at 7:40 AM, Tomi Valkeinen <tomba at iki.fi> wrote:
> On 2013-02-18 14:35, Rob Clark wrote:
>> On Mon, Feb 18, 2013 at 7:32 AM, Tomi Valkeinen <tomba at iki.fi> wrote:
>>> On 2013-02-18 14:26, Rob Clark wrote:
>>>
>>>> So I'm not going to get too hung up on supporting current DT bindings
>>>> in the future when we have something better.  But I needed something
>>>
>>> I may be mistaken, but my understanding is that DT bindings are like
>>> kernel's userspace APIs. After they have been merged, they have to work
>>> in the future kernels also.
>>
>> and that probably *eventually* makes sense when dts files are kicked
>> out of the kernel.  For now, it doesn't really seem useful, unlike
>> maintaining compatibility for userspace ABI's.
>
> Why does that matter? Afaik, the dts files are in the kernel for
> convenience, and as examples. You can as well have the DT data in your
> bootloader.
>
> Or has there been a clear decision that while the dts files are in the
> kernel, they are considered unstable?

I'm not sure.. I'm just going by what I've seen people actually using
for the boards which this driver works on currently.  I haven't seen
anyone embed DT data in bootloader.. either they are appending it to
the kernel image or keeping it as a separate file generated from
kernel tree.

BR,
-R

>  Tomi
>


More information about the dri-devel mailing list