Re: Mapping Video BIOS?

From: M. Warner Losh <imp_at_bsdimp.com>
Date: Sun, 27 Jul 2003 22:32:42 -0600 (MDT)
In message: <20030728043155.GV45069_at_wantadilla.lemis.com>
            "Greg 'groggy' Lehey" <grog_at_lemis.com> writes:
: On Sunday, 27 July 2003 at 22:17:32 -0600, M. Warner Losh wrote:
: > In message: <20030728041557.GU45069_at_wantadilla.lemis.com>
: >             "Greg 'groggy' Lehey" <grog_at_freebsd.org> writes:
: >> On Sunday, 27 July 2003 at 22:11:29 -0600, M. Warner Losh wrote:
: >>> Where are you getting the data?  A windows tool?
: >>
: >> If you're talking about the BIOS contents I'm printing, yes, I'm using
: >> a Microsoft tool called DEBUG (which has been around since before
: >> Microsoft bought DOS :-).
: >
: > I don't suppose that you could use FreeBSD's /dev/mem + od?
: 
: Yup, can do.
: 
:   # dd if=/dev/mem bs=64k skip=12 count=1 | hd | less
: 
:   00000000  55 aa 78 e9 44 06 00 00  00 00 00 00 00 00 00 00  |U.x.D...........|
:   00000010  00 00 00 00 00 00 00 00  68 01 00 00 00 00 49 42  |........h.....IB|
:   ...
:   0000bff0  04 03 80 00 0c 00 00 00  20 00 10 0b 3e 00 02 40  |........ ...>.._at_|
:   0000c000  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
:   *
:   00010000
: 
: That's pretty much what I expected.  Up to offset bff0, it's identical
: with the Microsoft dump.

Shouldn't you be looking at 0x000c0000 instead of 0x0000c000?

Warner
Received on Sun Jul 27 2003 - 19:35:02 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:16 UTC