slides from my talk at DDC

[Alan Hourihane]

On Thu, 2005-07-28 at 12:21 +0200, Waldo Bastian wrote:
> On Thursday 28 July 2005 03:48, Jon Smirl wrote:
> > On 7/27/05, Dave Airlie <airlied at gmail.com> wrote:
> > > Some issues I don't mention that need thinking about are going to be
> > > how mode setting interacts with virtual screens, and
> > > merged-framebuffer type things... (i.e. you want to set two different
> > > modes on the CRTCs but only have a single framebuffer, the mode
> > > setting APIs I've looked at don't seem to cover this too well... but
> > > maybe they don't need to.
> >
> > In my original scheme if you owned both heads the valid merged fbmodes
> > would be added to the mode list. You can generate the valid list by
> > knowing the chip capability and the DDC from both of the monitors. If
> > you then set a mergefb mode both monitor would change mode if needed
> > and the CRTC would be adjusted for the new resolution. Set either
> > monitor back to a non-merged mode to cancel.
> 
> Just to make sure I understand where this fits in: lack of this is one of the 
> reasons it's so difficult to get laptops working correctly with projectors at 
> the moment, right?

No. Projectors aren't treated any differently than a CRT (if it's
attached to the analogue port) or a real DVI flat panel (if it's
attached via the DVI port).

If you are thinking of the Intel driver Waldo, then I can fill you in on
a few things offline on why people have problems.

Alan.