On Wed, 10 May 2000, Chris Blazie wrote:
>
> > > SET_BANK( 0, 0xc0000000, 64*1024*1024 );
> > > SET_BANK( 1, 0xc8000000, 64*1024*1024 );
> > > mi->nr_banks = 2;
> >
> > Do you really have that amount of ram?
>
> On this daughterboard, yes. But it's possible that not all of it
> is properly enabled; I am only cautiously optimistic that all of our SDRAM
> problems are solved.
Better try to be absolutely sure you solved them... otherwise anything
can happen.
> > You might try with:
> >
> > SET_BANK( 0, 0xc0000000, 16*1024*1024 );
> > mi->nr_banks = 1;
> >
> > just to see if it makes a difference (besides the amount of ram of
> > course).
>
> Good idea, but no luck when I tried it. Can you tell me where
> (roughly) in the source I'm getting stuck? I think I can track down the
> problem if I can figure out where it's supposed to be going at that point.
Place some printk()'s through the kernel until you find something. For a
starter, look in linux/init/main.c at the very bottom and see if execution
reaches the call to execve() and so on.
Nicolas
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++ Please use [EMAIL PROTECTED] for ++
++ kernel-related discussions. ++
