[vortex] iomem allocation by network driver

[Michael Wisse]

>
>
>The card is using the I/O address 0xcc000
>
O.k., I found it in /proc/ioports.

But what is with this entry in /proc/iomem?

000d0000-000d07ff : Extension ROM

It is definitivly from the tornado  card. If I unplug the card, this 
range is empty.

>I believe that your problem is that the BIOS is not assigning the "high
>memory" region to the ISA bus. 
>
What do you mean with "high memory "? I can plug jumpers on the ISA card 
to set the memory range below 1 MByte (a good choice is d0000,because it 
is normally free)  or above 1 Mbyte, what is not recommended.  Therefore 
I try to use the adress range from d0000.

>
>ISA "high memory" cards use a different address space: "memory mapped",
>instead of "I/O mapped" space.
>
The ISA driver uses  ioports and iomem in the above mentioned range for 
configuration of the card and implements mmap() for some fast access 
functions, which are not used by the driver access library.  I am new in 
driver programming, but I just try to port the ISA driver to kernel 2.4.

I know, here is no driver programming maillist, but I am really 
interested in the question, if I can use the memory range from 
000d0000-000d07ff or if the tornado card prevents this.

Regards
Michael

Donald Becker wrote:

>On Tue, 29 Apr 2003, Michael Wisse wrote:
>
>  
>
>>We have bought new computers with 3c905C  cards. The 3c59x driver 
>>detects the card as Tornado:  "PCI 3c905C Tornado at 0xcc00. Vers LK1.1.16"
>>    
>>
>
>This looks normal.  The card is using the I/O address 0xcc000
>
>  
>
>>In this computers plugs an ISA card, which needs ISA memory in the range 
>>of 0xd0000 to 0xdffff.
>>    
>>
>
>That's fine...
>
>  
>
>>We found out in /proc/iomem, that unfortunatly 
>>the 3c905C network driver allocates iomemory in the range from 
>>000d0000-000d07ff,  which is marked as "Extension ROM" , so that the ISA 
>>cards don't work.
>>    
>>
>
>ISA "high memory" cards use a different address space: "memory mapped",
>instead of "I/O mapped" space.
>
>I believe that your problem is that the BIOS is not assigning the "high
>memory" region to the ISA bus.  There is typically a BIOS setup field
>that controls this.
>
>Mucking about with the BIOS might seem ugly and complex: manual resource
>control is one of the reasons the ISA bus was an unsuitable design for
>deployed use.
>
>  
>