On Tue, 2007-05-22 at 10:09 +1000, Benjamin Herrenschmidt wrote: > I do stongly beleive that the decision of what mode to choose should not > be made in the kernel. That's the plan; the kernel just provides mechanism. The architecture used in the X server splits precisely at this point with the mechanism in the driver and the configuration and policy up in the X server proper. Quite a bit of that code could be broken out into a shared library for fbdev-based apps and the X server to share, but that's down the road a bit after the kernel APIs look a lot more solid. With the goal of getting to a single-mode-set boot to avoid screen flashing before login, the key here is to make any early user-mode graphics apps share the same kernel graphics infrastructure as the X server to identify the common cases where the startup and X modes are the same and avoid resetting the configuration. -- [email protected]
Attachment:
signature.asc
Description: This is a digitally signed message part
- Follow-Ups:
- Re: [RFC] enhancing the kernel's graphics subsystem
- From: Benjamin Herrenschmidt <[email protected]>
- Re: [RFC] enhancing the kernel's graphics subsystem
- References:
- [RFC] enhancing the kernel's graphics subsystem
- From: Jesse Barnes <[email protected]>
- Re: [RFC] enhancing the kernel's graphics subsystem
- From: Benjamin Herrenschmidt <[email protected]>
- [RFC] enhancing the kernel's graphics subsystem
- Prev by Date: Re: [RFC] enhancing the kernel's graphics subsystem
- Next by Date: Re: [rfc] increase struct page size?!
- Previous by thread: Re: [RFC] enhancing the kernel's graphics subsystem
- Next by thread: Re: [RFC] enhancing the kernel's graphics subsystem
- Index(es):
 |