From: Rodolphe Ortalo <ortalo@laas.fr>
  To  : ggi-develop@eskimo.com
  Date: Tue, 11 Aug 1998 11:18:55 +0200

Re: kgicon problems...

Brian answered:
>> In my case, mode->fb is filled with the "baseptr" field of the
>> memory region containing the framebuffer. (I think it's a virtual
>> address ?)
>
>If it's i386 and it is of form 0xc####### then it is already
>a virtual address.
>
>> baseptr is initialized by mem_claim_region (kgicon/include/system.h)
>> as ioremap(region->base, r->size).
>
>I think your driver is written correctly then.  VGA is not, it
>sets mode.fb to 0xa0000 explicitly.

Okay, but, well, I also get an oops (on the 0xc###### adress) when
I 'insert' my kgicon driver. So, what's the real problem ? A bug in
ioremap ?

(BTW: In VGA-compatible text mode, my card was always returning 0xa0000
for mode->fb, even through the baseptr field.)

You know, I always wondered what the right thing to was on this
topic (and... that unable to handle paging request Oops has a long
story on my computer, initially related to 2.1.x kernels).

Then, what, any hint on what to do ?


Rodolphe