[lkml]   [1999]   [Dec]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: memory detection problems: 2.0.x vs. 2.2.x
From wrote:

> Okay, this looks like the problem we are having with some Athlon boards. My
> guess is that the board supports ACPI, which includes SMAP (int 15/e820) for
> memory reporting. Depending on the configuration, SMAP compliance may
> require that int 15/e801 memory reporting change. At least one bios vendor
> has decided to remove int 15/e801 memory reporting instead, which is
> permitted. 2.2.x does not support SMAP (although it may, if I can get
> things together), so we end up with int 15/88 reporting.
> POSSIBLE FIX: It may be that if ACPI is turned off, int 15/e801 reporting
> is restored. Since 2.2.x does not support ACPI, this should not result in
> any performance degredation. If this does not work, you are stuck with
> using mem=XXX.

You might want to look at the code in the GRUB bootloader (look at
"". It does all this automatically...
AND has been tested on a bunch of systems (in particular, the SMAP feature
didn't always return contiguous memory as such in the table, so you have
to loop through the table and coalesce the entries, or just add them to
your page available pool and assume there can be multiple separate
sections of available memory).

It turned out to not take that much code, and if you absolutely want to
put the code into the Linux kernel, you can just steal/adapt the code
I wrote.

Erich Stefan Boleyn \_ <>
Mad but Happy Scientist \__
Motto: "I'll live forever or die trying" ---------------------------

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:55    [W:0.029 / U:9.516 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site