On Wed, Apr 26, 2006 at 11:40:33AM -0700, Mike Taht wrote:
> My preliminary builds from 2.6-git have failed to boot though, and I'm
> thinking that perhaps it's because my bootloader isn't passing the correct
> machine identification up to the kernel? (I seem to remember that TS had
> arbitrarily chosen one at the time I'd got the board in the first place)
> Either that or my entry point is wrong (?) or the patchset bogus...
One thing you could try is sticking a call to printascii() in the
vprintk function in kernel/printk.c, i.e. something a la (copy-paste,
so whitespace-damaged) -- that should give you a bit more info on
what's going on.
Index: linux-2.6.17-rc1/kernel/printk.c
===================================================================
--- linux-2.6.17-rc1.orig/kernel/printk.c
+++ linux-2.6.17-rc1/kernel/printk.c
@@ -508,6 +508,8 @@ asmlinkage int vprintk(const char *fmt,
/* Emit the output into the temporary buffer */
printed_len = vscnprintf(printk_buf, sizeof(printk_buf), fmt, args);
+// printascii(printk_buf);
+
/*
* Copy the output into log_buf. If the caller didn't provide
* appropriate log level tags, we insert them here
cheers,
Lennert
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|