[coreboot] CONFIG_DEBUG_RAM_SETUP breaks build on i82810, i440bx and maybe more

Keith Hui buurin at gmail.com
Mon Dec 20 03:56:58 CET 2010

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.

I have seen i440bx build break similarly. You don't see it in this log
because I am developing a fix for it. (Working mainly on a P2B-LS, I'm
directly affected :-) )
i440lx uses a similar debugging facility and theoretically is also
broken, but apparently there is no 440LX mainboards in the tree.

abuild is modified as below, just to get CONFIG_DEBUG_RAM_SETUP set
when doing all-targets abuild:

Index: util/abuild/abuild
--- util/abuild/abuild  (revision 6204)
+++ util/abuild/abuild  (working copy)
@@ -58,6 +58,9 @@
 # use ccache

+# RAM debug messages
 # stackprotect mode enabled by -ns option.

@@ -197,6 +200,11 @@
                        echo "CONFIG_CCACHE=y" >> ${build_dir}/config.build

+               if [ "$debugramsetup" = "true" ]; then
+                       printf "(debugramsetup enabled) "
+                       echo "CONFIG_DEBUG_RAM_SETUP=y" >>
+               fi
                if [ "$scanbuild" = "true" ]; then
                        printf "(scan-build enabled) "
                        echo "CONFIG_SCANBUILD_ENABLE=y" >>


Above is not meant to be committed, but just in case, it is
Signed-off-by: Keith Hui <buurin at gmail.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: abuild.config_debug_ram_setup.log
Type: application/octet-stream
Size: 31843 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20101219/33f4c5fe/attachment.obj>

More information about the coreboot mailing list