wow. 2.4 sure did start to grow, but I'd still like a copy of that .config
Indeed. Attached is my kernel .config and my toplevel configuration file for the Dauphin Orasis model 1.
Ah, yes, the options. On the todo list: build a web page with all the options and what they mean. And fix all those option names that are config dependent with a CONFIG_ prefix so you can tell. Sorry.
heh, no problem. In the meantime, is it possible for me to pick through NLBConfig and glean the easier ones? I haven't looked at the source for NLBConfig yet, so I may be asking a dumb question here. :-)
Config files are in directories in the src tree and describe how to use and build the .c files in that directory. Config files can pull in Config files from other places.
Ok so am I correct in assuming that since there are on Config files in any of the superio/SMC/ directories that the superio.c file is not used at all? I based my fdc37n958fr configuration off of the fdc37c67x's configuration, but did not bother with the superio.c since it went off on an entirely different tangent. (enable PNP?)
The config.example etc. are top-level files which are handed to the NLBConfig tool (New Linux Bios Config) and which start the process of building a build directory.
Alright, I think I have some semblance of a clue. :-) Is there any documentation on the general boot process that LinuxBIOS uses? i.e. very basic init, superio init (so we have a serial port), chipset init (enable sdram, ide, whatever, test RAM if enabled), decompress to RAM address 0xwhatever (why/how 0xwhatever was chosen), other init, jump to payload? Or did I just pretty much describe it? :-)
Regards, Andrew