All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] arm: versatile: enable PCI I/O space
Date: Tue, 20 Jul 2010 23:12:17 +0200	[thread overview]
Message-ID: <201007202312.18353.arnd@arndb.de> (raw)
In-Reply-To: <AANLkTikiim-a8zM0PRDVVN078xBWeZt7ElwbC4oZsfXy@mail.gmail.com>

On Tuesday 20 July 2010, Eric Miao wrote:

> > -
> > -/* CIK guesswork */
> > -#define PCIBIOS_MIN_IO                 0x44000000
> > +#define PCIBIOS_MIN_IO                 0x00001000
> 
> I guess this is true for other sub-architectures. Currently no idea
> why they are all using different values. But 0x1000 seems to be
> good value and maybe we should default all of them to this and
> move it into some common place instead of defining them every
> where.

Yes. The 0x1000 is really the only sensible way to avoid the
legacy ISA ranges. Most platforms currently set this to zero,
which only works as long as you never try to load things like
an PC keyboard driver (including KDB) or an nvram driver that
probes the well-known ISA ports. The only reason I can see for
using less than 0x1000 is if you have a really small
IO_SPACE_LIMIT, but most platforms seem to set that to
0xffffffff, which is rather unrealistic if you use a memory
mapped IO region.

We also have two platforms (integrator and shark) that use a
higher value of 0x6000 but do not document why they do so.
iop13xx defines it as variable but never sets it to anything
else than zero.

	Arnd

  reply	other threads:[~2010-07-20 21:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 13:07 [RFC] arm: versatile: enable PCI I/O space Eric Miao
2010-07-20 21:12 ` Arnd Bergmann [this message]
2010-07-20 21:19   ` Russell King - ARM Linux
  -- strict thread matches above, loose matches on Subject: below --
2010-07-20  9:23 Arnd Bergmann
2010-07-20  9:55 ` Colin Tuckley
2010-07-20  9:59 ` Russell King - ARM Linux
2010-07-20 11:09   ` Arnd Bergmann

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=201007202312.18353.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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.