Re: 16 MB -> 32 MB, a memory problem resolved!

Andrew E. Mileski (aem@nic.ott.hookup.net)
Wed, 17 Apr 1996 16:45:11 -0400 (EDT)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Milton W. Thomas Jr.: "Re: floppy problem & Award BIOS floppy swap"
Previous message: Albert Cahalan: "Re: SEGFAULTS???"
In reply to: Hemment_Mark/HEMEL_IOPS_INTERNATIONAL-SALES@uniplex.co.uk: "Re: 16 MB -> 32 MB, a memory problem resolved!"

> Andrew E. Mileski wrote:
> > Some motherboards can relocate the 384k RAM that is leftover
> > from making the I/O hole at 0xa0000-0xfffff, but most can't.
> > What is worse, this feature _ONLY_ works with 16Mb or _LESS_
> > installed memory (on most mobos).
> > ...
> > Linux can't read your mobo manual for you (or the mind of the
> > mobo designer). For that matter, no OS can (especially not Windows).
>
> Isn't it possible to look for BIOS signatures between 0xa0000-0xfffff
> (check every 2k?) to determine what memory is left for the OS?
> Other reserved areas (such as floppy track buffer, VGA fonts) are at
> well know addresses. The interesting problem is detecting the onboard
> memory in other cards...

Yes it is possible. In fact the PnP patch does this :-)
see http://www.redhat.com/pnp/ for details.

All ROMs + memory are listed in /proc/addresses

-- Andrew E. Mileski --
mailto:aem@ott.hookup.net
http://www.redhat.com/~aem/

Next message: Milton W. Thomas Jr.: "Re: floppy problem & Award BIOS floppy swap"
Previous message: Albert Cahalan: "Re: SEGFAULTS???"
In reply to: Hemment_Mark/HEMEL_IOPS_INTERNATIONAL-SALES@uniplex.co.uk: "Re: 16 MB -> 32 MB, a memory problem resolved!"