As promised. Attached is my fix: Fully convert 440BX RAM init debugging to use printk(). Fixes build breakage with CONFIG_DEBUG_RAM_SETUP enabled.
A number of debugging messages have been tweaked to take advantage of the "new found" ability to output decimal numbers. :-D I also need to make a small change to the dimm_size struct to fix another breakage. Build tested with the modified abuild I used to report this bug. Boot tested on P2B-LS. Joseph, now go fix i810. ;-) Happy holidays Keith Signed-off-by: Keith Hui <[email protected]> On Mon, Dec 20, 2010 at 11:12 AM, Joseph Smith <[email protected]> wrote: > > > On Sun, 19 Dec 2010 21:56:58 -0500, Keith Hui <[email protected]> wrote: >> As title. Log from a locally modified abuild attached. >> >> I think this is something we did some time ago with simplifying >> debugging facility - trying to use printk() everywhere. >> > Well, that is not good. Not good at all... > > -- > Thanks, > Joseph Smith > Set-Top-Linux > www.settoplinux.org > >
440bx.config-debug-ram-setup.patch
Description: Binary data
-- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
