Re: [PATCH} 2.5.5-pre1 VESA fb

[Martin Dalecki <dalecki@evision-ventures.com>]

Alan Cox wrote:

>>This adjusts the VESA fb driver to the new bus mapping API.
>>I think that this time this is providing the right replacement.... but 
>>who knows
>>
>
>The VESA fb window will be higher than the ISA window as its a linear
>frame buffer
>
>>-		pmi_base  = (unsigned short*)bus_to_virt(((unsigned long)screen_info.vesapm_seg << 4) + screen_info.vesapm_off);
>>+		pmi_base  = (unsigned short*)isa_bus_to_virt(((unsigned long)screen_info.vesapm_seg << 4) + screen_info.vesapm_off);
>>
>
>I don't think it actually matters on x86 but phys_to_virt() is probably
>more correct
>

Well I think this is only the BIOS register gateway which we deal with 
here and I was therefore assuming
(without reading the doc's about the *isa*pci*bus*phys*virt* ) that this 
can be expected to reside in
the low memmory area < 1M of the physical address space. And then there 
are no pci references in the vesa driver
at all. Perhaps becouse they ignore the actual frame-buffer mapping 
games for non intel archs entierly.
Anyway I think that the isa_variant is correct. But please feel free to 
consider me a bit
arrogant for not reading the doc's about the address mapping functions. 
If I'm mistaken here, you could
alternatively consider it as a test for the fact that the API isn't 
"obvious" in first place, becouse it's not
easy to figure out what to do without sudying the docu for something 
such trivial like IO address range mapping ;-).

Regards