Date: Mon, 28 Jul 2003 13:39:29 +0930 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-mobile@FreeBSD.org Subject: Re: Mapping Video BIOS? Message-ID: <20030728040929.GS45069@wantadilla.lemis.com> In-Reply-To: <20030727.220357.65159779.imp@bsdimp.com> References: <20030728032653.GA37499@wantadilla.lemis.com> <20030727.214235.20045695.imp@bsdimp.com> <20030728040157.GP45069@wantadilla.lemis.com> <20030727.220357.65159779.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--nk27jClX7wGPY2hW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Sunday, 27 July 2003 at 22:03:57 -0600, M. Warner Losh wrote:
> In message: <20030728040157.GP45069@wantadilla.lemis.com>
> "Greg 'groggy' Lehey" <grog@FreeBSD.org> writes:
>> Sure. The data at offset 0xc0000 are:
>>
>> C000:0000 55 AA 78 E9 44 06 00 00-00 00 00 00 00 00 00 00 U.x.D...........
>>
>> The 0xaa55 is the BIOS signature ("Here be a BIOS"), and the 0x78 is
>> the length byte (120 sectors, or 60 kB). That's how orm0 knows the
>> end address.
>>
>>> I don't think that it suggests that things are 'unmapped'...
>>
>> If the area between 0xcc000 and 0xcffff had been mapped, orm0 would
>> have found this too:
>>
>> C000:F000 55 AA 08 E8 6D 0B CB 11-FE 02 00 00 00 00 00 00 U...m...........
>
> 08 -> 4k
Correct. It should have shown a BIOS from 0xcf000 to 0xcffff
> It could also be that there's a bug in orm that's missing it...
Sure, but given the other indications, that's not so likely.
Greg
--
See complete headers for address and phone numbers
--nk27jClX7wGPY2hW
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (FreeBSD)
iD8DBQE/JKH5IubykFB6QiMRAjbFAJ9Pszbb8t0qo6qYS9SbG9gj7YD6kQCgn/5o
GSpP5Hcd4BUa021v4rBlmg4=
=h94r
-----END PGP SIGNATURE-----
--nk27jClX7wGPY2hW--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030728040929.GS45069>