Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Ilya A. Volynets-Evenbakh" <ilya@total-knowledge.com>
To: ppopov@embeddedalley.com
Cc: "'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
Subject: Re: Au1000 PCMCIA I/O space?
Date: Mon, 01 Aug 2005 12:08:51 -0700	[thread overview]
Message-ID: <42EE7343.9020209@total-knowledge.com> (raw)
In-Reply-To: <1122877889.5014.319.camel@localhost.localdomain>

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

      reply	other threads:[~2005-08-01 19:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-01  6:16 Au1000 PCMCIA I/O space? Ilya A. Volynets-Evenbakh
2005-08-01  6:31 ` Pete Popov
2005-08-01 19:08   ` Ilya A. Volynets-Evenbakh [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42EE7343.9020209@total-knowledge.com \
    --to=ilya@total-knowledge.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ppopov@embeddedalley.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox