Re: KGI ... KGIcon ... GGI Console ???

1999-12-21 Thread Brian S. Julin

On Sun, 19 Dec 1999, Firstname Lastname wrote:
> hmm, is the resason that I haven't been able to get KGI to work because it 
> only has the driver for permedia, and all the others are in KGIcon?

Yeah, probably :).  The older, obselete KGI 0.8 had more drivers, including 
a few that didn't make it into KGIcon.  The KGIcon driverswere ported from 
KGI 0.8, and work has been done on them to start making them look more like 
KGI 0.9 drivers, so they can then be easily ported to KGI 0.9.  I expect, not 
to put words into his mouth, but given Steffen's blistering pace lately, that 
he'll announce a pretty fully functional KGI within the next few months and 
that the drivers will be ported faster than you would think possible as soon 
as that happens :).

--
Brian




Re: KGI ... KGIcon ... GGI Console ???

1999-12-18 Thread Firstname Lastname

> > What is the difference between KGIcon and KGI, if there is one?
>
>The KGI driver system itself is designed to be portable across platforms
>(both hardware- and OS-wise). KGIcon is a wrapper around the KGI drivers
>that will let them look like normal fbcon drivers for the Linux kernel
>(hence the name).
>
>KGI 0.0.9 - which is maintained by Steffen Seeger - is a massive intrusion
>into the Linux console subsystem which sets quite some things right and 
>thus
>allows to use more features of modern graphics cards.
>
>It will need some updating of the drivers, but we will try to merge kgicon
>and KGI 0.0.9, so that you can use KGI drivers on both stock and patched
>Linux kernels.

hmm, is the resason that I haven't been able to get KGI to work because it 
only has the driver for permedia, and all the others are in KGIcon?


__
Get Your Private, Free Email at http://www.hotmail.com



Re: KGI ... KGIcon ... GGI Console ???

1999-12-17 Thread Marcus Sundberg

Andreas Beck <[EMAIL PROTECTED]> writes:

> KGI 0.0.9 - which is maintained by Steffen Seeger - is a massive intrusion
> into the Linux console subsystem which sets quite some things right and thus
> allows to use more features of modern graphics cards.
> 
> It will need some updating of the drivers, but we will try to merge kgicon
> and KGI 0.0.9, so that you can use KGI drivers on both stock and patched
> Linux kernels.

You do mean KGI 0.9, right?

//Marcus
-- 
---+
Marcus Sundberg| http://www.stacken.kth.se/~mackan
 Royal Institute of Technology |   Phone: +46 707 295404
   Stockholm, Sweden   |   E-Mail: [EMAIL PROTECTED]



Re: KGI ... KGIcon ... GGI Console ???

1999-12-17 Thread Andreas Beck

> What is the difference between KGIcon and KGI, if there is one? 

The KGI driver system itself is designed to be portable across platforms
(both hardware- and OS-wise). KGIcon is a wrapper around the KGI drivers 
that will let them look like normal fbcon drivers for the Linux kernel
(hence the name).

KGI 0.0.9 - which is maintained by Steffen Seeger - is a massive intrusion
into the Linux console subsystem which sets quite some things right and thus
allows to use more features of modern graphics cards.

It will need some updating of the drivers, but we will try to merge kgicon
and KGI 0.0.9, so that you can use KGI drivers on both stock and patched
Linux kernels.

> How fits GGI Console (J.McMullan's EvStack?) in the architecture?

It was an alternate design for the Linux Console Input/Output subsystem which
relies heavily on a special form of message passing.

It is a very flexible approach designed for advanced needs like
multihead/multikeyboard/multi-whatever support and advanced input methods
like gesture recognition programs that kind of "translate" the events
produces by other inputs.

Unfortunately Jason doesn't have time to spend on it currently.

> I'm working at my theses at the University of Dresden and my task is 
> to design a console system for the DROPS project 
> (http://os.inf.tu-dresden.de/drops/).

Feel free to take from the EvStack code. IMHO it's one of the simplest and
most transparent implementations for a Unix style console subsystem.

As it separates all components (input drivers, remapping [keyboard layout],
terminal-emulation [Key-ESC-Sequences], userspace-IO, terminal-emulation 
[terminal control ESC sequences], virtual scroller, graphics subsystem), it
is very easy to write modules and maintain them.
Just start out with a naive implementation of all subsystems and then
enhance them.

> I'm just wondering if I could use the 'GGI Console' in a Linux-emulating
> (Microkernel-) Server. I think that is similar to the thing the HURD people
> want to do. 

Sure. Feel free to take.

CU, Andy

-- 
= Andreas Beck|  Email :  <[EMAIL PROTECTED]> =



KGI ... KGIcon ... GGI Console ???

1999-12-17 Thread Christian Helmuth


Hello,

I spent the last 3 days reading papers, websites and mailing lists about the
GGI-Project. There is still something confusing for me:

What is the difference between KGIcon and KGI, if there is one? 
How fits GGI Console (J.McMullan's EvStack?) in the architecture?

I'm working at my theses at the University of Dresden and my task is to design
a console system for the DROPS project (http://os.inf.tu-dresden.de/drops/).
This a Multiserver-Architecture based on the DROPS-Microkernel. At this point
I'm just wondering if I could use the 'GGI Console' in a Linux-emulating
(Microkernel-) Server. I think that is similar to the thing the HURD people
want to do. 

Christian.