All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: jim@jtan.com, linux-mips@oss.sgi.com
Subject: Re: ISA
Date: Tue, 18 Dec 2001 18:09:52 -0800	[thread overview]
Message-ID: <3C1FF6F0.B8834B75@mvista.com> (raw)
In-Reply-To: Pine.GSO.3.96.1011219023325.16267B-100000@delta.ds2.pg.gda.pl

"Maciej W. Rozycki" wrote:

>  Hmm, I believe there should be no such problem.  For systems equipped
> with the PCI bus we may just assume the low 16MB of PCI memory address
> space is reserved for ISA memory addresses (it's hardwired for many
> platforms, so there should be no problem with it), i.e. avoid programming
> BARs to point to that space and make ioremap() (or __ioremap(), actually)
> act accordingly, i.e. assume a 1:1 mapping for addresses above 16MB and
> perform an ISA mapping for ones below 16MB.

I see.  I missed that part where you have a pivoting point at 16MB.

That sounds like a working solution to me.

Overall, I still feel using isa_xxx() macros in the driver seems like a
cleaner solution.  That essentially treats ISA memory space as a separate
space.  The ioremap/readb/writeb approach tries to lump ISA memory and PCI
memory space together but in fact we still have treat them differently (based
on whether the address is greater than 16MB, which is a little hackish.)

Jun

  parent reply	other threads:[~2001-12-19  3:10 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-18 20:04 ISA Jim Paris
2001-12-18 20:27 ` ISA Bradley D. LaRonde
2001-12-18 20:27   ` ISA Bradley D. LaRonde
2001-12-18 21:44   ` ISA Jim Paris
2001-12-18 22:01     ` ISA Maciej W. Rozycki
2001-12-18 22:24       ` ISA Jim Paris
2001-12-19  1:17         ` ISA Jun Sun
2001-12-19  1:50           ` ISA Maciej W. Rozycki
2001-12-19  2:05             ` ISA Bradley D. LaRonde
2001-12-19  2:05               ` ISA Bradley D. LaRonde
2001-12-19  2:09             ` Jun Sun [this message]
2001-12-19  2:30               ` ISA Maciej W. Rozycki
2001-12-19  9:52                 ` ISA Geert Uytterhoeven
2001-12-19 13:59                   ` ISA Alan Cox
2001-12-19 13:59                     ` ISA Alan Cox
2001-12-19 14:06                     ` ISA Geert Uytterhoeven
2001-12-20 13:09                       ` ISA Maciej W. Rozycki
2001-12-20 13:14                         ` ISA Geert Uytterhoeven
2001-12-20 13:39                           ` ISA Maciej W. Rozycki
2001-12-20 13:45                             ` ISA Geert Uytterhoeven
2001-12-20 14:06                               ` ISA Maciej W. Rozycki
2001-12-21 16:12                       ` ISA Alan Cox
2001-12-21 16:12                         ` ISA Alan Cox
2001-12-21 18:44                         ` ISA Jim Paris
2002-01-01 19:22                           ` ISA Jun Sun
2002-01-01 19:34                             ` ISA Bradley D. LaRonde
2002-01-02  1:03                               ` ISA M. Warner Losh
2002-01-02  9:41                               ` ISA Geert Uytterhoeven
2002-01-02 14:36                                 ` ISA Bradley D. LaRonde
2002-01-01 20:13                             ` ISA Alan Cox
2002-01-01 20:13                               ` ISA Alan Cox
2001-12-19  1:28         ` ISA Maciej W. Rozycki

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=3C1FF6F0.B8834B75@mvista.com \
    --to=jsun@mvista.com \
    --cc=jim@jtan.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    /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.