[PATCH] xf86: allow for no outputs connected at startup operation.

Adam Jackson ajax at nwnk.net
Thu May 6 07:40:34 PDT 2010


On Thu, 2010-05-06 at 13:18 +1000, Dave Airlie wrote:
> From: Dave Airlie <airlied at redhat.com>
> 
> When nothing is connected at startup and we canGrow, allow the server
> to start with a 1024x768 framebuffer, and when the drivers send
> hotplug events this will expand to the correct size dynamically.

It keeps the logic out of the drivers, which I strongly approve of.
Where does this leave you after startup?  Framebuffer with no CRTCs
connected seems logical enough, but it might not be something the
drivers are prepared to deal with (if they have constraints on how the
fb is allocated, for example).

- ajax
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.x.org/archives/xorg-devel/attachments/20100506/45fe2901/attachment-0001.pgp>


More information about the xorg-devel mailing list