From: Jun Sun <jsun@mvista.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Ralf Baechle <ralf@oss.sgi.com>, linux-mips@oss.sgi.com
Subject: Re: lift the ioport_resource limit ...
Date: Thu, 10 May 2001 11:11:53 -0700 [thread overview]
Message-ID: <3AFAD9E8.EC4D6D80@mvista.com> (raw)
In-Reply-To: Pine.GSO.3.96.1010510111734.10485A-100000@delta.ds2.pg.gda.pl
"Maciej W. Rozycki" wrote:
>
> On Wed, 9 May 2001, Jun Sun wrote:
>
> > The PCI IO space essentially extends the ISA bus, which effectively removes
> > the 0xffff limits.
>
> Note that while there is usually no problem with using addresses beyond
> 64kB in the PCI I/O space, certain PCI-to-PCI bridges may not pass such
> accesses across. So it's best to avoid assigning and using them. That's
> why Linux remaps "high" I/O space resources on Alpha, which get set up for
> some systems by the SRM console (firmware), e.g. in the system I was using
> a few years ago, SRM used to assign addresses around 0x11000 and 0x12000
> for the onboard network and SCSI devices, IIRC.
>
I would not normally assign IO space above 0xffff either. But recently I
found multiple PCI buses, especially dual PCI buses, are getting popular, as
examplified by two Gallelio chips and the new NEC Vrc5477 chips.
Since all drivers share the same mips_io_port_base, - even though the devices
may be on different PCI buses - we need to assign the PCI IO windows
contiguously so that drivers can share the same base address. In most such
setups, you will get more than 0xffff IO ranges.
Jun
next prev parent reply other threads:[~2001-05-10 18:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-09 17:35 lift the ioport_resource limit Jun Sun
2001-05-09 19:26 ` Ralf Baechle
2001-05-09 21:06 ` Jun Sun
2001-05-10 9:43 ` Maciej W. Rozycki
2001-05-10 9:58 ` Geert Uytterhoeven
2001-05-10 11:08 ` Maciej W. Rozycki
2001-05-10 18:11 ` Jun Sun [this message]
2001-05-10 20:20 ` Ralf Baechle
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=3AFAD9E8.EC4D6D80@mvista.com \
--to=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
--cc=ralf@oss.sgi.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