Intel 2.0.0 driver not seeing laptop screen resolutions properly

[Eric Anholt]

On Tue, 2007-05-08 at 17:40 -0700, Keith Packard wrote:
> On Tue, 2007-05-08 at 16:52 -0700, Eric Anholt wrote:
> 
> > Here's a proposed hack to detect your situation and plug in better
> > values for the detected panel timings.  If it works, I'll add it.  Note
> > that in your case the BIOS gets the right answer (it looks like).
> > However, since the BIOS sometimes likes to disappear on us, it's
> > probably better to have this hack in place.
> 
> That's gross. Reading the BIOS at X server startup time and recording
> that seems far more reliable; so far, I don't think we haven't found a
> machine that has the BIOS unmapped after boot, just machines that have
> it unmapped on resume from S3.
> 
> We do need more accurate BIOS table locating code; that seems like a
> more tractable problem than quirking the driver to support every weird
> machine like this.

So, we lose out on starting X after a resume from S3 has happened, on
that hardware (which, as I understand, is not uncommon)?  That seems
like a recipe for even more pain than the current situation.

-- 
Eric Anholt                             anholt at FreeBSD.org
eric at anholt.net                         eric.anholt at intel.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
URL: <http://lists.x.org/archives/xorg/attachments/20070508/b4262fb8/attachment.pgp>