On Tue, Apr 14, 2009 at 09:22, Michael Schmitz
<[email protected]> wrote:
>> > Anyway: do you have a section like this in your log?
>> >
>> > Ignoring memory chunk at 0x0:0xe00000 before the first chunk
>> > Fix your bootloader or use a memfile to make use of this area!
>>
>> Yes, I have this message in my log. Full log attached (seems minicom
>> cut it at 80 cols).
>
> Must be a minicom setting problem - mine doesn't (at least not what's copied
> to
> the log after ^A L).
>
> Geert, Roman: does paging_init rely on part of the first memory chunk being
> mapped in head.S, or just part of the chunk the kernel resides in? Could I
> reorder the m68k_memory[] elements in setup.c to fix the ordering problems?
Should work. config_amiga() removes Zorro II memory chunks, and that's
just before
paging_init() is called. of course you cannot reorder the first chunk,
as that one is
already in use.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
