All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Sealey <matt@genesi-usa.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Marian Balakowicz <m8@semihalf.com>
Subject: Re: PCI IO range limitation
Date: Fri, 29 Jun 2007 18:08:50 +0100	[thread overview]
Message-ID: <46853CA2.2040203@genesi-usa.com> (raw)
In-Reply-To: <1183075997.5521.292.camel@localhost.localdomain>

Benjamin Herrenschmidt wrote:

> On Fri, 2007-06-29 at 00:38 +0100, Matt Sealey wrote:
>> Benjamin Herrenschmidt wrote:
>>> On Thu, 2007-06-28 at 12:20 +0200, Marian Balakowicz wrote:
>>>> Hi,
>>>>
>>>> Trying to change PCI IO window base for 52xx target I found that
>>>> we are pretty much limited to a "0" offset only.
>>> 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.
>> The chances of that on an MPC52xx platform are practically zero, aren't
>> they?
> 
> Euh... don't you use VGA video cards on Efika ? :-)

Define "legacy device"? What should that entail? You mean like mapping
most of those registers to the first couple of kilobytes of "IO"?

If they're just left as their own on their own as PCI devices, why would
it matter what the window was?

-- 
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations

  reply	other threads:[~2007-06-29 17:08 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 [this message]
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

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=46853CA2.2040203@genesi-usa.com \
    --to=matt@genesi-usa.com \
    --cc=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 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.