From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kevin Hao <haokexin@gmail.com>
Cc: Scott Wood <scottwood@freescale.com>,
linuxppc <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 1/3] powerpc/mpc85xx: remove the unneeded pci init functions for corenet ds board
Date: Fri, 31 May 2013 20:11:20 +1000 [thread overview]
Message-ID: <1369995080.3928.140.camel@pasglop> (raw)
In-Reply-To: <20130531064102.GB16514@pek-khao-d1.corp.ad.wrs.com>
On Fri, 2013-05-31 at 14:41 +0800, Kevin Hao wrote:
> Hi Ben,
>
> Could you shed some light on this issue? Do we really has the restriction
> that we have to pick one bus controller as primary even there is no
> ISA bus on the board? I did check the current code and found no code
> has a requirement for this. I also searched the archives and but found
> nothing useful. :-(
You can just pick the first one as primary... The reason we somewhat need
a primary is related to how we handle IO space.
We ioremap the IO space of all busses and assign the base of the primary
one to a global "_IO_BASE". Then any "port" access is an offset from that
which means that non-primary can end up having negative offsets. We fix
up all resources, which works fine ... unless drivers do stupid casts
and the wrap-around fails.
The main reason we did that originally is because we still had a slew of
x86 originated HW that would access hard wired IO ports, especially on things
like CHRP machines, looking for things like 8259 PIC, legacy kbd controllers,
UARTs, etc... at fixed IO port numbers.
We still support some of these boxes (though I do wonder how long since
somebody last booted a Pegasos) so I'm not quite yet keen on getting rid
of that stuff...
Cheers,
Ben.
next prev parent reply other threads:[~2013-05-31 10:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 12:04 [PATCH 0/3] several cleanup patches for fsl pci Kevin Hao
2013-05-21 12:04 ` [PATCH 1/3] powerpc/mpc85xx: remove the unneeded pci init functions for corenet ds board Kevin Hao
2013-05-28 22:52 ` Scott Wood
2013-05-30 10:20 ` Kevin Hao
2013-05-30 18:54 ` Scott Wood
2013-05-31 6:41 ` Kevin Hao
2013-05-31 10:11 ` Benjamin Herrenschmidt [this message]
2013-06-01 10:59 ` Kevin Hao
2013-06-01 11:47 ` Benjamin Herrenschmidt
2013-06-02 0:07 ` Kevin Hao
2013-06-03 16:42 ` Scott Wood
2013-06-07 2:00 ` Kevin Hao
2013-06-08 0:00 ` Scott Wood
2013-07-23 22:31 ` Scott Wood
2013-07-25 12:54 ` Kevin Hao
2013-07-26 22:43 ` Scott Wood
2013-07-28 0:32 ` Kevin Hao
2013-05-31 6:43 ` Kevin Hao
2013-05-31 23:27 ` Scott Wood
2013-06-01 11:13 ` Kevin Hao
2013-05-21 12:04 ` [PATCH 2/3] powerpc/fsl-pci: fix the unreachable warning message Kevin Hao
2013-05-21 12:05 ` [PATCH 3/3] powerpc/fsl-pci: enable SWIOTLB in function setup_pci_atmu Kevin Hao
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=1369995080.3928.140.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=haokexin@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.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).