On Wed, 27 Jun 2001, peckerwood wrote: > I think besides the name, the seperation of the stages would be very good > idea. I would also seperate the first stage making a stage that should work > on all platforms, then another stage for spacific chipsets or motherboards. > Then the 3rd stage could contain the kernel with drivers it needs or a > bootloader. I think I'm missing something. What is non-modular? You pick what pieces you get via the config file.The modularity is done at rom build time. That's the modularity. I find that word 'modular' is over-used in too many contexts. For example in the context of classes, libraries, and linux it means quite different things than it does in the context of linuxbios. Maybe someone can explain what is 'modular' in this context. Another interesting thing: on the Dell 350 we're finding that due to the way things work we probably won't even be doing raminit. LinuxBIOS will start up some time after raminit is done. So the "phase 1" won't even exist. How do you fit that in? I'm finding that things are too variable on these machines to use hard and fast names like phase 1, phase 2, phase 3 categories. In many ways that is an inappropriate classification. For every categorization you can name I can name an excepton. And, modular to most people conjures up pictures of .o's, opaque interfaces, blah blah blah. None of that makes any sense in this context. ron
