On Tue, Aug 26, 2014 at 03:22:07PM +0200, Maxime Ripard wrote: > On Tue, Aug 26, 2014 at 10:40:27AM +0200, Thierry Reding wrote: > > On Mon, Aug 25, 2014 at 05:18:22PM +0200, Luc Verhaegen wrote: > > > On Mon, Aug 25, 2014 at 05:12:58PM +0200, Thierry Reding wrote: > > > > > > > > Out of curiosity, how does this work in practice? How does the > > > > bootloader create this entry? Does it scan the DT to see which clocks > > > > the real hardware device references and then simply copies them to the > > > > simplefb node? > > > > > > > > Thierry > > > > > > https://www.mail-archive.com/linux-sunxi@xxxxxxxxxxxxxxxx/msg06619.html > > > > That looks like a royal pain. Again, I think it'd be much simpler (but > > not less code, unfortunately) to do this on a per-resource basis. That > > way these low-level firmware drivers in the kernel can stay trivial, > > keeping the real complexity where they belong: in hardware-specific > > drivers such as DRM/KMS. > > So we have to write a DRM/KMS driver in order to have display working > while waiting for a DRM/KMS driver to be worked on? Come on... Perhaps you should go and read this thread again. That's not at all what I've been saying. Thierry
Attachment:
pgpYbeqVOtUXy.pgp
Description: PGP signature
