Message-ID: <8D53104ECD0CD211AF4000A0C9D60AE32300AD@probe-2.Acclaim-Euro.net>
From: Shawn Hargreaves <ShawnH AT Probe DOT co DOT uk>
To: djgpp AT delorie DOT com
Subject: Re: VESA
Date: Mon, 26 Oct 1998 10:45:51 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1460.8)
Content-Type: text/plain
Reply-To: djgpp AT delorie DOT com

snadrel AT atlas DOT uvigo DOT es writes:
> I know that the LFB starts in 0xE0000000, but I made a program 
> that read the VESA information and it tells me that the LFB 
> starts in 0xFC000000.

How do you know that the real LFB is at 0xE0000000? If VESA is 
reporting some other value, isn't there a chance that you could 
be wrong about where you think it is?

Try running some other program that print out information from the
VESA driver, to check that you are doing this correctly. There is
a utility like this in the GRX source distribution, or you can use
the Allegro VESAINFO program.

If these utilities agree that the address is 0xFC000000, I think 
you must be mistaken about 0xE0000000. If they do print 0xE0000000 
(which I do think is likely, because that is a very common address 
for a framebuffer), you are obviously doing something wrong, in 
which case you can look at the sources to these other programs to
see where they differ from your code...


	Shawn Hargreaves.