linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: Marcus Sundberg <erammsu@kieraypc01.p.y.ki.era.ericsson.se>
Cc: Ruedi.Hofer@ascom.ch, linuxppc-embedded@lists.linuxppc.org
Subject: Re: PCMCIA support for 860
Date: Mon, 03 Apr 2000 15:55:12 -0400	[thread overview]
Message-ID: <38E8F720.40E7C0DB@embeddededge.com> (raw)
In-Reply-To: kfypus7w23t.fsf@kieraypc01.p.y.ki.era.ericsson.se


Marcus Sundberg wrote:

> -#define _IO_BASE        0
> +#define _IO_BASE       0xf4000000
> +#define _IO_BASE_SIZE  0x10000
>  #define _ISA_MEM_BASE   0


You have to be very careful with this.  These definitions won't work
on any 8xx with a PCI bridge.  I get too many patches from people that
hack these around to suit their configuration and it breaks everything
else.

The correct (as best I have found :-) approach is to continue to make
IO_BASE represent the PCI/ISA space for which it is intended.  Then
separately map the PCMCIA and adjust the addresses for those drivers
based upon the IO_BASE (so in/out, and so on work).  You can also map
the PCMCIA into the PCI/ISA space as it has address decode priority
over the memory controller.


	-- Dan

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

  reply	other threads:[~2000-04-03 19:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-03  7:55 PCMCIA support for 860 Ruedi.Hofer
2000-04-03 17:01 ` Marcus Sundberg
2000-04-03 19:55   ` Dan Malek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-04-04  9:49 Ruedi Hofer
2000-04-04 11:54 ` Marcus Sundberg
2000-04-04 23:33   ` Dan Malek
2000-04-04 11:52 Ruedi Hofer
2000-04-04 13:23 ` Marcus Sundberg
2000-04-05 16:21 Ruedi.Hofer
2000-04-06  9:07 ` Marcus Sundberg
2000-04-06 10:39 Ruedi.Hofer
2000-04-06 12:23 ` Marcus Sundberg
2000-05-19  8:35 Shuangjun Zhu
2000-05-22  9:24 Shuangjun Zhu
2000-05-23  9:58 Shuangjun Zhu

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=38E8F720.40E7C0DB@embeddededge.com \
    --to=dan@netx4.com \
    --cc=Ruedi.Hofer@ascom.ch \
    --cc=erammsu@kieraypc01.p.y.ki.era.ericsson.se \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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;
as well as URLs for NNTP newsgroup(s).