Skip to contentSkip to conversation

MVME5100 and bugboot fails

DISCUSSION Brian Waite 1 participant 1 message Sep 6, 2001 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Tom,
I was in the process of writing the same message you wrote. I would be more than willing to test the patch. Right now here is what I do in misc-simple.c

/*

         * Find a place to stick the zimage and initrd and
         * relocate them if we have to. -- Cort
         */
        avail_ram = (char *)PAGE_ALIGN((unsigned long)_end);
        puts("zimage at:     "); puthex((unsigned long)zimage_start);
        puts(" "); puthex((unsigned long)(zimage_size+zimage_start));
puts("\n");
        if ( ((unsigned long)zimage_start  >= 0xf0000000) ||
              ((unsigned long)zimage_start <= 0x00800000) )

Is there a better way than testing against 0xf0000000 to tell if you are in FLASH memory. I'd like something more generic or at least less hardcoded. Anyway, send me any code you want tested and Ill let you know how it behaves.

Quoted 15 lines · you
Quoted 1 line · Brian Waite

I am playing with the MVME5100 and I am having a bit of trouble with

booting

Quoted 1 line

using bugboot and an initrd. I get a message at bootup saying initrd > 16

MB

Quoted 1 line

and then as it is booting it gets an oops in mem_init.

[snip]

Quoted 1 line

My question is is the failure due to the bootloader not relocating the

Quoted 8 lines

initrd

Quoted 2 lines

or is it that ClearPageReserved() is being called when the initrd is in FLASH? Any ideas?

Right now, we only see if we need to relocate the initrd if we need to relocate
the kernel. I'll go and fix this (I think gemini has the right idea).

--
Thanks

Brian

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/