From: James A S. <jsi...@ac...> - 2000-03-02 15:30:01
|
> Well, I don't think that I can help with this too much - my web > design skills are pretty bad. Looka t http://libggi3d.sourceforge.net to > see what I am capable of |->. I see. Mine such too! > I think that we have three major areas of concern which will drive > the design of this project: > > 1: What do we need? > * Better multiheading, > * Cleaner and more abstract [virtual] console representation, > * fbcon backwards compatibility, > * /dev/gfx integration, > * Abstract input devices and event flow graphing, > * ...others... I think this shoudl go on the web page. The accel handling issues is the only point I don't agree. I will post the reason why in another post. > 2: What does Linus want? Something that works. Show me the code is his mato. Once coding begins I suggest we send him some patches to look at. He will then add his comments. Some good, some bad. > 3: What will Linus accept into 2.5.x? > > EvStacks was a _really_ good design, but I guss it was too complex > and ambitious for Linus. Therefore, we really need to know where Linus > stands on the issues before we do any significant amount of design work > this time around. One thing I can guarantee is his position on what a console is. I had the discussion with him on private mappings and bending the rules for the linux-SGI GFX port. We wouldn't go for it. The reason why is the concept. To him a thread process is and will always be a lightweight process. As he stated it is what it is. If not then rules don't mean much and you might as well allow people to break the basic definations that define UNIX for their own gain. To him a tty will always be a keyboard and a display. Thats it. Breaking what the meaning of a tty is will not go over with him. Codito, ergo sum - "I code, therefore I am" James Simmons (o_ fbdev/gfx developer (o_ (o_ //\ http://www.linux-fbdev.org (/)_ (/)_ V_/_ http://linuxgfx.sourceforge.net |