Re: FBdev remains in unusable state

From: David Woodhouse (dwmw2@infradead.org)
Date: Thu Dec 13 2001 - 06:35:21 EST

Next message: Andreas Steinmetz: "Re: Kernel-2.4.17pre8 & invalidate: busy buffer"
Previous message: Markus Hetzmannseder: "Re: VT82C686 && APM deadlock bug?"
In reply to: Petr Vandrovec: "Re: FBdev remains in unusable state"
Next in thread: Pozsar Balazs: "Re: FBdev remains in unusable state"
Reply: Pozsar Balazs: "Re: FBdev remains in unusable state"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

VANDROVE@vc.cvut.cz said:
> Documentation/fb/vesafb.txt, X11 paragraph, last sentence:
> -------8<-----
> The X-Server must restore the video mode correctly, else you end up
> with a broken console (and vesafb cannot do anything about this).
> -------8<-----

This isn't strictly true. We could just call the VESA BIOS to set it up
again for us. The 'vesa' XFree86 driver manages to do this perfectly well
from userspace, even.

-- dwmw2

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Next message: Andreas Steinmetz: "Re: Kernel-2.4.17pre8 & invalidate: busy buffer"
Previous message: Markus Hetzmannseder: "Re: VT82C686 && APM deadlock bug?"
In reply to: Petr Vandrovec: "Re: FBdev remains in unusable state"
Next in thread: Pozsar Balazs: "Re: FBdev remains in unusable state"
Reply: Pozsar Balazs: "Re: FBdev remains in unusable state"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:25 EST