[PATCH] Imply --no-mem-option for Linux 2.4.18 and newer

[Pavel Roskin]

Hello!

I believe the issue with adding the "mem" option for the Linux kernels
should be revisited.  There have been several bug reports in the Linux
PCMCIA list (http://lists.infradead.org/pipermail/linux-pcmcia) that
turned out to be caused by that option.  Some PCMCIA bridges prefer their
memory resource 0 to be allocate at the end of the first gigabyte of
memory, and BIOS does it.  It the system has 1 Gb of memory, GNU GRUB
instructs to treat that area as system memory.  Using --no-mem-option
fixes the problem.  It's going to become a FAQ.

In fact, it would be very strange if any bootloader was doing better job
and determining memory layout than the Linux kernel on its most supported
architecture.

I believe that adding the "mem" option was intended to prevent breakage in
old Linux kernels.  It was also meant to protect GNU GRUB developers from
complaints about Linux bugs.  I believe the situation has changed and the
issue should be revisited.

Linux boot protocol 2.03, which appeared in Linux 2.4.18 and is present in
2.6 kernels, provides a pointer to the kernel version.  We could parse it
to see if the kernel can be trusted to do its own memory detection.  But
for simplicity we could assume that any Linux kernel with boot protocol
2.03 should be trusted.

The attached patch makes --no-mem-option implied for Linux kernels with
boot protocol 2.03, i.e. kernel versions 2.4.18 and newer.

-- 
Regards,
Pavel Roskin

nomem_new_linux.diff
Description: Text document