Re: actual kernel not compiling

[Paul M. <le...@li...>]

On Sun, Nov 11, 2007 at 12:22:13PM +0100, Heiko Schocher wrote:
> Paul Mundt schrieb:
> >Feel free to complain if you think the wiki page should be updated with
> >some more information that might be helpful, this should be a fairly
> >painless process, so we'd like to have all of the ambiguities addressed.
> >  
> 
> Hmm.. I am using git, because I think thats the "standard" todays, 
> right? Couldnt find some informations about git on this page, maybe
> this should be updated?
> 
Well, the git trees aren't directly linked primarily because they're just
a staging ground for the stuff that goes to Linus. I generally prefer
people to use Linus's git tree directly, as I only bother syncing up if
there's changing that need to be merged.

I suppose the entry could use some more clarity though, I'll see about
reworking it a bit.

> If I make a while (1); at the end of the function sh_cpu_init()  in
> arch/sh/kernel/cpu/init.c the cpu dont restart, the next function
> called is start_kernel (). If I make there as first a while (1), the
> cpu restarts ... dont see an SH7750R specific thing in
> arch/sh/kernel/head.S on this place:
> 
[snip]

> Any ideas?
> (damned, dont have a debugger ...)
> 
Sounds like something could be falling out as a result of the initial
cache flush in cache_init(), possibly due to things left over from your
boot loader. You might try playing with that a bit.

Also, if you don't have a debugger, early printk should still be usable.
If you're using sh-ipl+g then you don't have to do anything special for
it, but if you want to use the SCIF directly and are using an alternate
loader, you will have to plug in the I/O port and some various fixups for
SH7750R (most of which you can just glean from sh-sci.[ch]).

If you want to start debugging from sh_cpu_init() already and have
sh-ipl+g, you can #include <asm/sh_bios.h> directly and use the write
routine there. This causes a trap directly, and can be handled regardless
of whether the MMU is enabled or not. Barring that, find an LED and start
toggling.. this is how I do most of my debugging :-)