Skip to contentSkip to conversation

pci io remapping and ide_ioreg_t

DISCUSSION Liam Davies 3 participants 3 messages Feb 20, 2001 MIPS

lore
Share & tools
lore
#0 lore raw

I have an old (2.0.x) ide driver that used to hard code the hwif->io_ports up to the 0x100001f0-0x100001f7 range. This is now broken in the 2.4 kernel since ide_ioreg_t has changed from unsigned long to unsigned short.

What is the mechanism for reaching these ports now?

Thanks
Liam

#1 lore raw
Quoted 6 lines · Liam Davies

I have an old (2.0.x) ide driver that used to hard code the hwif->io_ports up to the 0x100001f0-0x100001f7 range. This is now broken in the 2.4 kernel since ide_ioreg_t has changed from unsigned long to unsigned short.

What is the mechanism for reaching these ports now?

Change ide_ioreg_t back to unsigned long? ide_ioreg_t is arch specific.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven ------------- Sony Software Development Center Europe (SDCE) [email protected] ------------------- Sint-Stevens-Woluwestraat 55 Voice +32-2-7248626 Fax +32-2-7262686 ---------------- B-1130 Brussels, Belgium

#2 lore raw
In reply to Liam Davies
Quoted 6 lines · Liam Davies

I have an old (2.0.x) ide driver that used to hard code the hwif->io_ports up to the 0x100001f0-0x100001f7 range. This is now broken in the 2.4 kernel since ide_ioreg_t has changed from unsigned long to unsigned short.

What is the mechanism for reaching these ports now?

Consider this size of ide_ioreg_t a glitch; most current MIPS designs have their IDE ports in outer space. It shouldn't break anything, so until somebody is going to cry I'll change it to unsigned long.

Ralf