Andreas Beck wrote:
 
> > I mean, is there any schedule on when a new release of GGI/KGI is going
> > to happen?
> 
> Hmm - Marcus: How is your current schedule ? We should probably finally whip
> up a new LibGGI release.
> 
> > * Is going KGI to be integrated in the new 2.4x kernel series?
> 
> No.
> 
> > If not, why?
> 
> Hmm - Steffen what is your status ?

Current status is that I returned from a badly needed holiday, finding that the
important threads always happen when I am away. 

> Still working, or did you quit ?

Still working. I am currently getting a light-weight X server running with
KGI-0.9, which is currently initializing the graphics card and displaying
the windows. I am right now implementing the event delivery in KGI-0.9 and
getting the X server to respond to my input. Then there will be another
snapshot release.

> > and should the GGI team develop a branch of the kernel?
> 
> If someone wants to do this, it might make sense. We maintained patches for
> a long time a long while ago, but as noone seemed to be too interested,
> we started lagging behind kernel changes and finally stopped updating stuff.

KGI-0.9 will follow 

> > Why doesn't Linus want KGI inside the kernel sources?.
> 
> The data about this topic is very dated. I wouldn't count on that still
> being the case, with stuff like DRI also getting its helper modules in.

That's a question Linus has to answer, not I.

> > And DRI? Is DRI possible under GGI?
> 
> Noone has tried yet. According to Steffen DRI is something one shouldn't
> really try ...

You could try it, it might work, but I cannot recommend it for everyday use, as 
any user running a DRI program can accidentally freeze the machine, just
by halting the program in question at a bad time. See the security analysis
at PI's website.

> > Is GGI/KGI ending as a curiosity - another kind of graphics library - ,
> 
> I am afraid it will - regarding Linux.

Which is my feeling too. However, as long as there is no solution to the
problems I intend to solve with KGI, I will continue with it. Maybe someone
can use it too.


Jon M. Taylor wrote:

>         *BSD has been ascendant recently.  There have been discussions in
> the past about using *BSD instead of Linux as the primary KGI development
> OS, but nothing ever happened.  HURD was also mentioned at one point, as
> was Win32(!).

This is still on my list of cool things to do, and recent developments have
only made me more certain about that. There is, however, one point that keeps
me from immediately jumping at HURD/Mach, or other OSes: I want to have the
concepts for the driver model _working_ and fleshed out before ports to another
platform start. As a beginning, I would love to see the current KGI-0.9 running
on PPC or Alpha, but I have no hardware to test it, nor are there developers
having the hardware and wanting to do the port.

Once the KGI-0.9 acceleration concept is proved, we can focus on taking the
world,
doing it before will cause a bigger mess than worth the hassle.

> * I never got the 2.3/2.4 port working.  Close (it wasn't _that_
> difficult), but no cigar.  The 2.2 kernel series is still being actively
> maintained by Alan Cox, but 2.4 will have several new features (most
> notably kiobufs and devfs) which if used by KGI would make the KGI kernel
> patches quite a bit smaller and simpler.

Intentionally I do not put work into a 2.4 port before 2.4-final is out.
Mainly because then is clear what parts of the new console system
are in. For the current stuff I am working on, 2.4 is not a requirement,
so its not on the priority list.

>        In sum, while KGI does require a decent bit of work, it is already
> quite far along.

Oh yes, it is. Though it needs work. Fortunately I will find the
time to give it another push during the next two weeks.

>  Don't give up on it.

It's hard some times, but I've quite a high frustration level...
But even that gets exceeded sometimes.

> If you don't already know about
> how kick-ass Steffen's design for the new KGI is, or haven't read
> Steffen's excellent architectural descriptions of KGI, please head over to
> SourceForge and do some KGI browsing.  You'll be amazed.

Thanks for the credits :-) 



                        Steffen

_______________________________________________________________________________
Steffen Seeger                              mailto:[EMAIL PROTECTED]
TU-Chemnitz                                      http://www.tu-chemnitz.de/~sse

Reply via email to