A lot of small differences have accumulated between my tree and the main LinuxBIOS tree. Some of them are hacks that I need to generalize before putting them in the public tree. So I am taking this in small manageable chunks.
Holler if anything looks to nasty.
src/arch/i386/boot/boot.c - Tone down the severity of error messages src/arch/i386/lib/console.inc - Preserve morre registers in __CONSOLE_INLINE_TX_HEX8 src/arch/i386/lib/hardwaremain.c - Fixup the cmos option to handle multiple cpus - Move pci setup before ramsize initialization - Renable keyboard_on src/arch/i386/smp/Config Add secondary.S src/arch/i386/smp/secondary.S - add src/arch/i386/smp/secondary.inc - remove src/arch/i386/smp/start_stop.c - Remove unused variables src/config/Config - Cleanup the cross compiling options - Rename cmos.conf cmos.layout as the previous name was too confusing src/cpu/p6/mtrr.c - Create subroutines to enable/disable caching - Call them in all of the appropriate places - Add an extra argument to range_to_mtrr to allow for future optimizations
Eric
- Move pci setup before ramsize initialization
I originally put this after with the idea that we would know where to start PCI memory space instead of the current assumptions that it starts at 0x80000000. I realize that we have stuck with the current blind placement of pci space but if you put pci setup before ramsize you won't have a way to fix this -- ever.
Question is, how do you pick a place to start pci space now?
Or does it not matter?
ron
Ronald G Minnich rminnich@lanl.gov writes:
- Move pci setup before ramsize initialization
I originally put this after with the idea that we would know where to start PCI memory space instead of the current assumptions that it starts at 0x80000000. I realize that we have stuck with the current blind placement of pci space but if you put pci setup before ramsize you won't have a way to fix this -- ever.
Question is, how do you pick a place to start pci space now?
I start pci memory space at 0xFFFFFFFF and work backwards. And then I remove the ram I cannot use do to having too many pci devices. I should probably put a limit like ensuring I have at least 64M of ram or something. But currently it is much more common to have Gigabytes of ram then gigabytes of pci memory space consumed.
Check out my src.rpm if you want to see how I am actually acheiving this in my tree.
But basically you really need to know how large each region is potentially before you make those decisions. So at least assign_pci_resources needs to happen before getting the ram size.
Eric
On 10 Oct 2002, Eric W Biederman wrote:
I start pci memory space at 0xFFFFFFFF and work backwards.
that sounds good.
ron
-
Eric W Biederman -
Ronald G Minnich