Re: split biosfs.c into several XDD's?

[Thomas Schulze <ts@uni-paderborn.de>]

Hi,

you wrote: (with lots of stuff deleted)

>  This would result in having the following device drivers (not all of them
> for every type of computer, but that should be a job of the initialization
> code then), with some notes about possible changes I've been thinking of:
> 
> console.xdd
> midi.xdd - shouldn't forget that :-)
> modem1.xdd - switch to new (unix-style) names?
> modem2.xdd - dito?
> serial1.xdd - dito?
> serial2.xdd - dito?
> centr.xdd - switch to a proper name, say, lp.xdd? would make it easier to
> 		*replace* it with Thierry Bousch's one
> fasttext.xdd - perhaps merge this with console.xdd and use some fcntl to
> 		switch between them?
> null.xdd
> mouse.xdd - add an absolute mode? the small buffering of relative steps
> 		makes - for example - MGR crawl like a snake when the system
> 		is under heavy load, making the buffer bigger wouldn't do,
> 		but adding an absolute mode (errr, not SUN compatible)


Ok, but I think we should have a core set of drivers inside the kernel.
console.xdd is one of them, the (to be written) acsi/scsi xdd another one.
How about writing a keyboard.xdd, too? 

Otherwise, how could MiNT inform Joe User about non existing path for loading
xdd's? Or about serious problems while starting? 

In fact each of these xdd should be a possible part of the kernel to build
a version of MiNT which boots from the network. This will result in a 
configurable kernel... 

And another one: How about integrating Juergen Lock's vcon (Virtual Console)
into the kernel?

Just my two cents, Thomas.
ts@uni-paderborn.de