On Fri, Jul 19, 2013 at 5:49 PM, Geert Uytterhoeven
<geert@xxxxxxxxxxxxxx> wrote:
On Fri, Jul 19, 2013 at 4:31 PM, Thorsten Glaser <tg@xxxxxxxxx> wrote:
does the limit apply to just the kernel image
(plus some margin) or is the initrd also subject
to that restriction?
That's a very good question ;-)
The 4 MiB limit only applies to early startup, in arch/m68k/kernel/head.S.
Initrd is accessed later, in arch/m68k/kernel/setup_mm.c, so I'd expect it to
not fall under the limit.
Of course, better try it to be sure ;-)
On ARAnyM, I could boot a 4 MiB initrd (note that ARAnyM doesn't seem to
support gzipped ramdisks!), created by appending zeroes to the good old
filesys-ELF-2.0.x-1400K-2, and running resize2fs.
It even worked with a 32 MiB initrd, after increasing xx to 32768.
Haven't tried with the Amiga yet.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
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 from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
