From: Jun Sun <jsun@mvista.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: lift the ioport_resource limit ...
Date: Wed, 09 May 2001 14:06:59 -0700 [thread overview]
Message-ID: <3AF9B173.5E13AD2@mvista.com> (raw)
In-Reply-To: 20010509162608.C2466@bacchus.dhis.org
Ralf Baechle wrote:
>
> On Wed, May 09, 2001 at 10:35:12AM -0700, Jun Sun wrote:
>
> > Currently IO_SPACE_LIMIT is 0xffff, which is probably borrowed from the legacy
> > i386 code. Let us remove that limit, so that each machine does not have to
> > laboriously reset it.
>
> ISA?
>
> Ralf
ISA bus?
The PCI IO space essentially extends the ISA bus, which effectively removes
the 0xffff limits.
If you are really paranoid, we can do something like this:
#if defined(CONFIG_ISA) && !defined(CONFIG_PCI)
#define IO_SPACE_LIMIT 0xffff
#else
#define IO_SPACE_LIMIT 0xffffffff
#endif
Jun
next prev parent reply other threads:[~2001-05-09 21:06 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 [this message]
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
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=3AF9B173.5E13AD2@mvista.com \
--to=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
--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