On Thu, Mar 01, 2012 at 10:41:32PM +0100, Paul Menzel wrote: > Am Donnerstag, den 01.03.2012, 20:38 +0100 schrieb Daniel Vetter: > > On Thu, Mar 01, 2012 at 06:44:35AM +0100, Mathias.Froehlich@xxxxxxx wrote: > > > From: Mathias Fröhlich <Mathias.Froehlich@xxxxxx> > > > > > > Add an option to skip reading the mode entries from > > > the vbt bios tables. > > > This change enables the use of displays where the vbt table just > > > contains inappropriate values, but either the vesa defaults or > > > the video=... modes do something sensible with the attached display. > > > > > > Reviewed-by: Paul Menzel <paulepanter@xxxxxxxxxxxxxxxxxxxxx> > > > Signed-off-by: Mathias Froehlich <Mathias.Froehlich@xxxxxx> > > > > Can you elaborate a bit on why this is required? Is this for a machine > > (like the chrome machines) that just lack a vbios? Or do we fail to parse > > the vbt in some way? > > Pasted from Mathias’ message with the first patch iteration. Ah, that explains things. I've added this to the commit message and queued it for -next, thanks. -Daniel > > Am Mittwoch, den 29.02.2012, 20:34 +0100 schrieb Mathias Fröhlich: > > Attached is a small change to i915 that fixes a customer case that I had in my > > day job. > > > > The problem happens with an embedded board that contains vbt bios tables that > > do not match the attached display. > > Using this change and the appropriate kernel boot command line they are able to > > use an otherwise completely unusable secondary display on that embedded board. > > > > Please review. > > > Thanks, > > Paul -- Daniel Vetter Mail: daniel@xxxxxxxx Mobile: +41 (0)79 365 57 48 _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
