All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Integrator PCI base dilemma
Date: Fri, 22 Mar 2013 12:34:59 +0000	[thread overview]
Message-ID: <201303221234.59289.arnd@arndb.de> (raw)
In-Reply-To: <20130322121218.GD4977@n2100.arm.linux.org.uk>

On Friday 22 March 2013, Russell King - ARM Linux wrote:
> > Also, in many cases, you don't even have the choice in the kernel between
> > the two options, either PCI is identity mapped or mapped starting at
> > address zero based on whatever the soc or board designer thought, and the
> > only thing we can do is tell the kernel what the hardware does.
> 
> Exactly which is why you're wrong. :)  If the hardware enforces a
> separation of the physical address space from the PCI address space
> by way of an offset translation, then you have no option but to have
> a non-zero mem_offset.

I still think we are in complete agreement about the facts here, at least
I was trying to say the same thing above that you replied with.

> > It looks like cns3xxx, tegra, versatile and ks8695 are all hardwired to a
> > zero mem_offset, while dc21285, integrator, it8152 and sa1100/pci-nanoengine
> > map the PCI bus starting at bus address 0.
> 
> Don't read too much into the versatile stuff.  All that is very very much
> untested and fragile.  It's fairly buggered at the moment as it stands,
> and as far as I can tell there's absolutely no way to know what the right
> solution is - because the ARM documentation is extremely poor and all the
> real hardware has been stuffed through the mincer.
> 
> So that leaves cns3xxx, tegra and ks8695 being the non-plat ones which
> are "different" from the majority on ARM.

Well, those and all the ones that chose to set up their windows in the
same way like the plat-orion based ones.

	Arnd

  reply	other threads:[~2013-03-22 12:34 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20 23:15 Integrator PCI base dilemma Linus Walleij
2013-03-20 23:54 ` Rob Herring
2013-03-21  9:16   ` Linus Walleij
2013-03-21 13:22     ` Rob Herring
2013-03-21 16:17       ` Arnd Bergmann
2013-03-22 11:05       ` Russell King - ARM Linux
2013-03-21 13:02 ` Arnd Bergmann
2013-03-21 23:40   ` Russell King - ARM Linux
2013-03-22  9:48     ` Arnd Bergmann
2013-03-22 10:37       ` Russell King - ARM Linux
2013-03-22 11:52         ` Arnd Bergmann
2013-03-22 12:12           ` Russell King - ARM Linux
2013-03-22 12:34             ` Arnd Bergmann [this message]
2013-03-22 18:33               ` Jason Gunthorpe
2013-03-22 18:35                 ` Russell King - ARM Linux
2013-03-22 19:22         ` Linus Walleij
2013-03-22 19:22           ` [U-Boot] " Linus Walleij
2013-03-22 20:05           ` Arnd Bergmann
2013-03-22 20:05             ` [U-Boot] " Arnd Bergmann
2013-03-22 21:13           ` Wolfgang Denk
2013-03-22 21:13             ` [U-Boot] " Wolfgang Denk
2013-03-22 22:35             ` Linus Walleij
2013-03-22 22:35               ` [U-Boot] " Linus Walleij
2013-03-22 23:48               ` Russell King - ARM Linux
2013-03-22 23:48                 ` [U-Boot] " Russell King - ARM Linux
2013-03-23  0:19               ` Wolfgang Denk
2013-03-23  0:19                 ` [U-Boot] " Wolfgang Denk

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=201303221234.59289.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.