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

2010-05-23 Thread Dave Airlie
From: Dave Airlie airl...@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. Reviewed-by: Keith Packard kei...@keithp.com

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

2010-05-08 Thread Dave Airlie
On Sat, May 8, 2010 at 3:02 PM, Keith Packard kei...@keithp.com wrote: On Fri, 7 May 2010 06:18:45 +1000, Dave Airlie airl...@gmail.com wrote: 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

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

2010-05-07 Thread Keith Packard
On Thu, 6 May 2010 13:18:20 +1000, Dave Airlie airl...@gmail.com wrote: From: Dave Airlie airl...@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

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

2010-05-07 Thread Keith Packard
On Fri, 7 May 2010 06:18:45 +1000, Dave Airlie airl...@gmail.com wrote: 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. Ajax: I

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

2010-05-06 Thread Adam Jackson
On Thu, 2010-05-06 at 13:18 +1000, Dave Airlie wrote: From: Dave Airlie airl...@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.

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

2010-05-06 Thread Keith Packard
On Thu, 06 May 2010 10:40:34 -0400, Adam Jackson a...@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

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

2010-05-06 Thread Dave Airlie
On Fri, May 7, 2010 at 12:40 AM, Adam Jackson a...@nwnk.net wrote: On Thu, 2010-05-06 at 13:18 +1000, Dave Airlie wrote: From: Dave Airlie airl...@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

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

2010-05-05 Thread Dave Airlie
From: Dave Airlie airl...@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. Signed-off-by: Dave Airlie airl...@redhat.com ---

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

2010-05-05 Thread Keith Packard
On Thu, 6 May 2010 13:18:20 +1000, Dave Airlie airl...@gmail.com wrote: From: Dave Airlie airl...@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