Messages in this thread | | | Date | Sun, 24 Jan 1999 15:47:44 -0800 | From | Ian Eure <> | Subject | Re: why is vesafb not a module? |
| |
On Fri, Jan 22, 1999 at 08:40:30PM +0000, 91b59e21456b337c213e7290c93f43a8@interlinx.bc.ca wrote: > Wow, my second posting in two days. As I have not yet subscribed to the > list can I as that you CC me (yup to that horrifyingly ugly from > address) on any responses. > > I am wondering why the vesafb (VESA Frame Buffer device) is not a > module? I like building stripped down kernels (even to the point of > putting my load time devices into an initrd ramdisk) that I can run on a > variety of machines. I have some machines that use the Matro frame > buffer framebuffer device but others that use the standard VESA frame > buffer. > > I would like to decide at run time which frame buffer to run, depending > on of course the hardware in the box. Compiling one kernel with the > vesa frame buffer in (for video cards without a specific frame buffer > driver) and then one without (to run a specific frame buffer) to satisfy > this kinda sucks. :-) > > As a side note, anyone know of a source for the frame buffer version of > the Xserver? Vesafb is not a module because it needs to make a real-mode VESA 2.0 call to setup the video mode. This can't be done once the kernel is booted.
The source for Xfb should be available at www.xfree86.org, though I have not checked.
-- ______________________________________________________________ | ian eure, network admin, freelance security consultant, and | | manically depressed paranoid schizophrenic, at your service. | ; <ieure@minion.org> - http://minion.org ; : raw speed = 105.6 wpm with 4.5% errors : . . . . . . . . . . . . . . . . . . . . . .
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |