On Wed, 10 May 2000, Chris Blazie wrote:
>
> I've become kind of stuck in the boot process somewhere after the
> ramdisk apparently gets mounted. In fixup_sa1100 I have:
>
> 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?
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).
> But it stops as shown below. I'm using Nicolas's ramdisk_img.gz.
> I tried setting init->bash but it's apparently not getting that far.
Be sure you have /dev/console as a chrdev with major 5 minor 1, not a
symlink to /dev/ttyS0. If for example your ttyS0 isn't the serial port on
which boot messages are sent, you might well be running a shell in the
air.
> Also, I want to make the ramdisk live in flash when everything
> else comes up okay. What is required to make a ramdisk in flash get
> mounted properly?
Either you make your bootloader copy the ramdisk from flash to ram before
booting the kernel, or you modify the kernel to grab the initrd data
directly from Flash (no bootmem allocation, no page freeing at the end,
etc.)
Alternately you could use my flash block driver (if you use Intel flashes)
and boot directly on the Flash.
Nicolas
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++ Please use [EMAIL PROTECTED] for ++
++ kernel-related discussions. ++
