----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: "arm" <[EMAIL PROTECTED]>
Sent: Thursday, February 28, 2002 10:49 PM
Subject: strange io mapping problem


> Hello-- I am _still_ working on the pcmcia driver for the inhand Elf. I
> have run into a really bizzare problem. I am useing a SANDisk ATA card to
> debug the driver. PCMCIA works fine, as long as I do not try to read from
> the IO portions that should map to the card, aka when the ide driver tries
> to do an identify on the card. This means I am able to read all of the
> attribute memory fine to determine which card I have inserted.
>
> I am using 0xf700|0000 as the base address, as inhand has mapped the
> pd6722 to 0x3000|0000. The IO space for the sockets has been mapped to
> 0x3000|0000, and 0x3000|8000 by inhand directly. When I am in the ide
> driver and do a loop to print the values from 0xf700|0000 to 0xf700|0007,
> the ide registers that should be on the cards, I get the value 0xa1 for
> ALL of them. When I use dev2mem to print the values, I get what appear to
> be different values. Are there any ideas as to why this might be
> happening? I would be much appreciative to anyone who can help as I have
> to have this working in the next 2 weeks.!!!
>
> Thanks
> [...]

Are you sure you are performing the proper byte access in the driver? If you
try a word access you'll get back garbage.

Also check in which mode the driver programs the CF card (typically the
control register is in attribute space at 0x200). After reset a CF card will
be in memory mapped mode but it also supports 3 other modes: port 0x1f0+,
port 0x170+, every 16-byte boundary address port. If the driver changes the
card mode you may access the wrong locations.

--
 Paul Chitescu
 [EMAIL PROTECTED]   http://pchitescu.myip.org/   ICQ:22641673
 Any spammers will be painfully squeezed into /dev/null




_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
http://www.arm.linux.org.uk/armlinux/mailinglists.php
Please visit the above addresses for information on this list.

Reply via email to