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

Keith Packard keithp at keithp.com
Thu May 6 10:36:52 PDT 2010


On Thu, 06 May 2010 10:40:34 -0400, Adam Jackson <ajax at nwnk.net> wrote:

> 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).

Yeah, they may fail, but that's what the server was about to do
anyway...

-- 
keith.packard at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg-devel/attachments/20100506/bd45a85e/attachment.pgp>


More information about the xorg-devel mailing list