From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Marian Balakowicz <m8@semihalf.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: PCI IO range limitation
Date: Tue, 03 Jul 2007 21:13:30 +1000 [thread overview]
Message-ID: <1183461210.10386.104.camel@localhost.localdomain> (raw)
In-Reply-To: <468A15D9.7010003@semihalf.com>
On Tue, 2007-07-03 at 11:24 +0200, Marian Balakowicz wrote:
> Benjamin Herrenschmidt wrote:
> > On Thu, 2007-06-28 at 12:20 +0200, Marian Balakowicz wrote:
> >> I guess that with the above dropping of non-zero based PCI IO ranges
> >> this is not supposed to be working. But does anyone know why?
> >
> > We just fixed that for 64 bits but 32 bits still has the limitation.
> > Note that it's not a very good idea to have your IO range at !0 if
> > you're going to use anything ISA-like, such as a VGA video card or other
> > legacy devices behind a PCI southbridge or SuperIO.
>
> Agree with the zero-based IO range for ISA devices. But, knowing we don't
> have any ISA stuff on board it should be possible to change the IO base.
And you don't plan to ever have a VGA video card ?
> Are you planning on modifications for 32 bits as well?
Not right now, but you are welcome to send a patch :-) Though I fail to
see why you want to do it.
Ben
next prev parent reply other threads:[~2007-07-03 11:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 10:20 PCI IO range limitation Marian Balakowicz
2007-06-28 17:43 ` Benjamin Herrenschmidt
2007-06-28 23:38 ` Matt Sealey
2007-06-29 0:13 ` Benjamin Herrenschmidt
2007-06-29 17:08 ` Matt Sealey
2007-06-29 23:14 ` Benjamin Herrenschmidt
2007-07-03 9:24 ` Marian Balakowicz
2007-07-03 11:13 ` Benjamin Herrenschmidt [this message]
2007-07-06 13:37 ` Marian Balakowicz
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=1183461210.10386.104.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=m8@semihalf.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;
as well as URLs for NNTP newsgroup(s).