Re: mem= option for broken bioses

From: Pavel Machek (pavel@suse.cz)
Date: Tue Mar 04 2003 - 08:18:55 EST


Hi!

> > > I've seen broken bios that did not mark acpi tables in e820
> > > tables. This allows user to override it. Please apply,
> >
> > OK, looks reasonable. Can you also gen up a patch documenting this in
> > kernel-parameters.txt?
> >
>
> This is very much *NOT* reasonable. In fact, screwing around with the
> syntax of the mem= parameter is poison. I know it has already
> happened, and those changes need to be reverted and the new stuff
> moved to a different option.
>
> The mem= option is unique in that it is an option that affects both
> the boot loader and the kernel. Therefore, ITS SYNTAX MUST NOT
> CHANGE.

This should be commented, somewhere.
Why is mem= option used by boot loader?
Does your bootloader really parse stuff
like mem=exactmap?

-- 
				Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Fri Mar 07 2003 - 22:00:24 EST