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

[Dave Airlie]

On Fri, May 7, 2010 at 12:40 AM, Adam Jackson <ajax at nwnk.net> wrote:
> 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).

I only do it for canGrow drivers, others keep the old behaviour, I
assume if you canGrow then you can do something interesting when a
display shows up later like resize the framebuffer within any
constraints.

I've tested with radeon, I can try and do Intel/nouveau today, no
other drivers will be exposing canGrow.

Dave.