From: Marian Balakowicz <m8@semihalf.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: PCI IO range limitation
Date: Fri, 06 Jul 2007 15:37:03 +0200 [thread overview]
Message-ID: <468E457F.4030402@semihalf.com> (raw)
In-Reply-To: <1183461210.10386.104.camel@localhost.localdomain>
Benjamin Herrenschmidt wrote:
> 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 ?
You definitely got a point, but still, I tend to think that if someone wants to shoot himself in a foot he should be free to do it.
>> 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.
I don't necessarily need that, I was rather wondering what were the reasons for such modification. This used to be allowed in 2.4, while 2.6 kernel with the legacy setup will silently reset. Kernel booting and issuing a big warning instead would be much nicer if we are to stick to the 0 based IO ranges.
Marian
prev parent reply other threads:[~2007-07-06 13:37 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
2007-07-06 13:37 ` Marian Balakowicz [this message]
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=468E457F.4030402@semihalf.com \
--to=m8@semihalf.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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 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.