linux-mips
[Top] [All Lists]

Re: Au1000 PCMCIA I/O space?

To: ppopov@embeddedalley.com
Subject: Re: Au1000 PCMCIA I/O space?
From: "Ilya A. Volynets-Evenbakh" <ilya@total-knowledge.com>
Date: Mon, 01 Aug 2005 12:08:51 -0700
Cc: "'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
In-reply-to: <1122877889.5014.319.camel@localhost.localdomain>
Organization: Total Knowledge
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <42EDBE3B.3010503@total-knowledge.com> <1122877889.5014.319.camel@localhost.localdomain>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla Thunderbird 1.0.6 (X11/20050723)
Hmm, I see. I'm not really using PCMCIA driver - I just have
IDE interface hanging off of PCMCIA controller of Au1000, so
I had to do something similar to drivers/ide/mips/swarm.c.
Thus since I can pass addresses directly to ioremap, I'm OK
anyways.


Pete Popov wrote:

On Sun, 2005-07-31 at 23:16 -0700, Ilya A. Volynets-Evenbakh wrote:
Is there any particular reason why Au1000 PCMCIA IO space is not included in 36-bit address fixup? Attached patch fixes it for me, but I'm wondering if there is valid reason not to do that.

Because it's ioremapped by the au1x pcmcia driver and the driver passes the virt address to the pcmcia stack. If this isn't working for you, something else is broken. You only need the fixup when you can't call ioremap with the entire 36 bit phys address. For example, the attribute and
common memory space are ioremapped by the "pcmcia stack" in the kernel,
not the low level socket driver over which we have control. Thus, to
work around the fact that you can't easily change the entire pcmcia
stack, you do the fixup thing.
Unless the pcmcia stack changed, the driver should work as is.

Pete


--
Ilya A. Volynets-Evenbakh
Total Knowledge. CTO
http://www.total-knowledge.com


<Prev in Thread] Current Thread [Next in Thread>