How about running X on top of something else?

> > Bah.  We don't relocate resources unless we need to.  So that ball's as
> > much in your court as it is in ours.
> 
> Any X reassignment of PCI resources is unsafe in Linux 2.4, and going to
> get more so. The DGA comemnt applies here the other way around - you don't
> currently have a way to get the kernel to do the work for you. We need to
> address that. X doesn't know enough hw issues or locking

That's the point where KGI comes into the place. Most of you, I guess,
remember
on the heating discussion on the linux kernel ml in 1997/1998.

In the meantime, it has been redesigned and rewritten from scratch. So, all
what you (still) believe to know about KGI is very likely out of date.

KGI is splitted in two parts. The kernel driver knows all stuff to access
the
hardware and to map the graphic resources (i.e. accelerator) safely to the
userspace - BTW: ioctls are only used for setting up video modes and other
initialisation stuff and nothing else.

The userspace part uses the graphic resources and is able to send commands
(i.e. drawing operations) to the graphic board.

So much I can explain you so far. My area is GGI not KGI. KGI is a separate
sister
project of GGI nowadays, btw.

Thus, I point you to the KGI site http://www.kgi-project.org/ for more
information.
And you all are invited to join the KGI ML
(http://lists.sourceforge.net/lists/listinfo/kgi-develop)
and the IRC channel (irc.freenode.net:6667 #kgi) to discuss any sort of
questions you have about KGI with the KGI developers.



[...]
> The kernel also has the framework to report new PCI devies to XFree86
> as well as device removal.

Nothing more? What about IRQ's and other resources such as the accelerator
and video memory addresses, so far as possible?

-- 
CU,

Christoph Egger


+++ GMX - Mail, Messaging & more  http://www.gmx.net +++
Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!