Re: ARM topic: Is DT on ARM the solution, or is there something better?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Mon, Oct 21, 2013 at 5:27 AM, Sascha Hauer <s.hauer@xxxxxxxxxxxxxx> wrote:
>> If a subsystem doesn't work well with DT, then the choices are either:
>>
>> (a) don't use DT with the subsystem
>
> The underlying problem has nothing to do with DT. Multi component
> hardware does exist and won't vanish when we stop using DT.
>
>> (b) fix the subsystem
>
> I'd love to do that. Step one to this seems to be to increase the
> awareness that there's something wrong with DRM.


Note that I suspect your idea of "fixing drm" is going to break some
userspace assumptions about the hw (ie. userspace isn't expecting
crtcs/encoders/connectors to suddenly appear/disappear.  And the funny
thing is, on all of this hw, that isn't going to happen anyways.

In whatever is done, we need some way to know all the devices in hw
that comprise the "graphics card", so that we can -EPROBE_DEFER until
we have all the bits and pieces.

BR,
-R
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]
  Powered by Linux