Re: KGI portability

[Tomasz W. <ma...@be...>]

On Tue, Apr 25, 2000 at 08:02:51AM +0200, Steffen Seeger wrote:
> 
> 1)	KGI environment (console management, boot display drivers,
> 	/dev/graphic special file mapper etc.)
> 
> 	This is quite Linux specific in terms of the TTY driver
> 	and /dev/graphic special file driver interface used to
> 	actually link these driver into Linux.
> 	However, I tried to keep OS dependencies out of
> 	all KGI internal stuff where that seemed to make sense
> 	An exception is that it assumes a monolithic
> 	kernel design, which is that we assume we are running
> 	non-preemptive when executing this code.

Does it mean
1) it has to be run in kernel space
2) it may be run in kernel space or as real-time process
3) only some marked parts of code must be run non-preemptive

> 	The boot display and input device drivers are i386 and
> 	PC architecture specific. They are just there to ge a machine
> 	running, until we have a file system and can get the real
> 	display drivers loaded. Thus porting KGI to another
> 	(Linux-)architecture will require implementation of proper
> 	boot drivers too.

Is it possible to leave original boot driver and run KGI later,
when system is in more usual state ?

> 2)	KGI display drivers (in the drv/display directory, formerly
> 	referenced as driver/graphics)
> 
> 	These drivers require only a working KGI environment, so
> 	once you have the environment ported, you should have all the
> 	drivers. Actually not even that, the drivers themselves only
> 	need the hardware resource allocation and handling to work
> 	properly. (e.g. as long as the stuff in
> 	http://kgi.sourceforge.net/source/kgi-0.9/kgi/include/kgi/io.h
> 	is supplied by the 'other POSIX OS'
> 
> If you intend porting KGI to another OS, starting to look over 
> system.h, io.h and creating <cpu-type>-compiler.h, <cpu-type>-types.h
> should make definitions of most KGI basic types and the basic
> I/O operations operational. Done this the drivers should already
> compile. (Re-)implementing the OS environment will take some more work,
> depending on how much the 'other POSIX OS' will differ from Linux.

i386-* should work, I'm on i386
system.h and io.h won't work w/o modifications

> I hope that answers your question, if not, don't hesiate to ask further
> questions.

and before I will try to do any real work :
why does make make so many warnings (about overwriting commands) ?