On 5/22/07, Alan Cox <[email protected]> wrote:
> you display text in graphics mode entirely in kernel context. The
> driver should also attempt to stop the GPU to try and make sure it
> doesn't erase the OOPS display.
If we know how yes. Probably the X server needs to provide us with a
simple list of operations to perform or failing that write 128K of null
to the display then print the characters (the 128K should ensure any
running FIFO for commands is stuffed and we get back to the framebuffer)
> Another simple thing that needs to be built is a mechanism to run the
> VBIOS in x86 mode when the driver is first loaded. This can be
We don't want to touch the video bios for most cards, its not as good as
the X mode switcher code, nor for that matter does it work in a lot of
cases as they use IRQ and DMA functions sometimes.
The only reason the VBIOS is run is to initially reset the card. Once
we get the card reset it isn't used any more. For almost all cards
this is the only way to reset them, we have insufficient information
to write this ourselves.
Alan
--
Jon Smirl
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
