I agree this can be a straight and safe way of building a 'universal' desktop system which recognizes the platform it runs and tunes up all the drivers correspondingly.
But we have no chance to develop 1000s of drivers needed. And even porting open-source Linux drivers will be a problem unless we accept the entire Linux driver model.
Just look svn/drivers/ddk
to see what I mean. What we get on this way is a small asm-
kernel surrounded with hundreds of alien C-
But there is another way to move: we stay with or current driver model, and leave reasonable freedom of resouce access/sharing for application.
In this case, very accurate code alignment needed to communicate with the given hardware, and the user has to do such an alignment during automatic, semi-automatic or manual OS installation.
We cannot guaranty this will work for any PC platform, and therefore I put forward
the idea of "selected platforms" the System supports.
AMD RS780+ and Fusion/Hudson are such platforms: my Kolibri-A
manages this hardware with some new tricks unavailable with the trunk kernel.yogev_ezra
bravely builds his own flavour of KolibriOS on eBox platform despite many problems and objectives.
He has a TARGET, and a WILL to go, and he doesn't care about compatibility etc.