All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Paul Mackerras <paulus@samba.org>
Cc: Steven Scholz <steven.scholz@imc-berlin.de>,
	Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: [PATCH] m8xx_setup.c and PCMCIA
Date: Sun, 26 Jan 2003 23:09:53 -0500	[thread overview]
Message-ID: <3E34B111.6050203@embeddededge.com> (raw)
In-Reply-To: 15924.24396.105367.383171@argo.ozlabs.ibm.com


Paul Mackerras wrote:

> I'm not really here, I'm on vacation, but anyway...

Me, too :-)


> What it boils down to is that we have little choice (unless you want
> to rewrite the pcmcia layer :) but to make inb/outb etc. do what the
> pcmcia layer is expecting.  That's the reason for the _IO_BASE mapping
> hacks.

I understand that, I was just concerned about why it was needed and the
way it was done in this patch.  The PCMCIA has been working quite well
for many people on the 8xx, so I'm hoping someone that has experience with
that can take a look at these changes and discuss them.

On processors like the 8xx where you have multiple, separate address
spaces that can be the targets of inb/outb, you have to be very careful
how you use the IO_BASE addresses and map those spaces.  Anyone making a
change that uses this raises a big red flag, because it usually "fixes"
one configuration and breaks everything else.

Thanks.


	-- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2003-01-27  4:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3E30F363.1020501@imc-berlin.de>
2003-01-24 15:11 ` [PATCH] m8xx_setup.c and PCMCIA Dan Malek
2003-01-24 15:42   ` Steven Scholz
2003-01-26 22:21   ` Paul Mackerras
2003-01-27  4:09     ` Dan Malek [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=3E34B111.6050203@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=paulus@samba.org \
    --cc=steven.scholz@imc-berlin.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.