On Monday, May 21, 2007, Jesse Barnes wrote:
> > There is more to fbdev than mode setting. It is also how non-x86
> > platforms achieve their boot display. How will boot display be handled
> > with the your design? What about console display on non-x86 platforms?
> > Loading both fbdev and the new code puts us right back into the
> > multiple driver fight we have today.
>
> Maybe you should take a look at the patches. :) The code I posted
> actually creates an fb device as a slave of the DRM device, and uses
> that for the boot console. Once you've booted, you can use the new
> interfaces to do whatever you want with the graphics device... though it
> doesn't create /dev/fb* devices per-CRTC like you seem to want, it's
> really easy to do the equivalent with a small userspace program (though
> I haven't actually tested sharing of buffer objects, it should work).
Actually, scratch that last bit. I forgot about a recent change alanh
committed that did just that: per-CRTC FB devices. So please take a
close look (modesetting-101 of mesa/drm git at freedesktop.org) and let me
know if you see any gaping holes.
Thanks,
Jesse
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
