Messages in this thread |  | | | Subject | Re: GGI, EGCS/PGCC, Kernel source | | From | Jes Degn Soerensen <> | | Date | 23 Feb 1998 14:13:01 +0100 |
| |
>>>>> "Pavel" == Pavel Machek <pavel@atrey.karlin.mff.cuni.cz> writes:
>> There is also the question whether GGI is the right approach or >> not! On the m68k we need to use framebuffers and thus framebuffer >> consoles, however I have not seen a lot of evidence that it will >> actually buy us a lot to tale the GGI approach rather than the nice >> and fairly simple `fbcon' style we use now. Bascially fbcon (and >> the abstract console system) allows for framebuffer consoles, >> VGA-like text mode consoles, consoles on weird devices such as TIGA >> boards and it allows for screen-mode switching in the kernel, which >> is necessary for the framebuffer devices. I can't see a lot of >> other graphics related issues that needs to go into the kernel.
Pavel> Hmm, how do you handle accelerated graphics? Userland may need Pavel> to call video's accelerated graphics functions (some of them Pavel> may require dma and interrupts...)
You map the video registers to the user space application and let the X server do the work, similar to how the PC-style X servers works today. We may need some ioctl (if its not already there) to tell the console code not to perform any operation that involves the blitter when a user space application is controlling the display.
DMA and interrupts is a different issue, if we want it we may need a more sophisticated kernel interface, as far as I can see it is a matter of specifying some simple API for that.
Jes
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
|  |