Messages in this thread |  | | Date | Tue, 29 Aug 2000 07:18:13 +0200 (CEST) | From | Mike Galbraith <> | Subject | Re: Possible PATCH?? RAMSIZE detect changes in 2.4 |
| |
On Mon, 28 Aug 2000, Michael Peddemors wrote:
> in the 2.2 series, memory_end is taken from (1<<20)+EXT_MEM_K, and this > worked.... Now looking at 2.4 it seems that it ignores all the data > discovered by the boot loader, and just looks at the memory_map provided by > the BIOS. So why is it getting the wrong information when a simple bootloader > can get the right information??
Because there is more than one way to obtain memory information. That's why I suggested trying defining STANDARD_MEMORY_BIOS_CALL.
-Mike
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |