Re: Fwd: memory probing

Quoting alfred hitch ([EMAIL PROTECTED]): > Hi Doug, > > thanks a lot for your explanation, it explains quite well now to me > the x86 arch. It is not just the x86, but the same is true of other architectures such as the PPC (PREP/CHRP or not), 68K, VAX or any other CPU architecture. You have a

Re: Fwd: memory probing

Hi Doug, thanks a lot for your explanation, it explains quite well now to me the x86 arch. Ok coming back to the discussion, sau bios reads this info from north bridge, north bridge gets this across reboots from memory module using i2c. so, basically the info is coming from the memory chip ? We

Re: [ppc] [patch] set environment from commandline

Hollis Blanchard <[EMAIL PROTECTED]> writes: > Yeah, I consider it absolutely required, so that when users say "it > crashed before I could do anything" we can just ask them to boot with > "debug=all". What I want to use it for is setting the prefix. Usually I have grub.cfg stored on the HD and

Re: [ppc] [patch] more cleanups

Hollis Blanchard <[EMAIL PROTECTED]> writes: >>> /* Where grub-mkimage places the core modules in memory. */ >>> -#define GRUB_IEEE1275_MODULE_BASE 0x030 >>> +#define GRUB_IEEE1275_MODULE_BASE 0x0030 >> >> Huh? Can you explain this? I would even prefer: >> >> #define GRUB_IEEE1275_MODUL