From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Darren Stevens <darren@stevens-zone.net>, linuxppc-dev@lists.ozlabs.org
Cc: Pat Wall <pjwall@mac.com>,
matthew@a-eon.com, aperez@alexperez.com,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
Christian Zigotzky <chzigotzky@xenosoft.de>
Subject: Re: Proposed: Patch to fix boot on PA6T
Date: Mon, 27 Jun 2016 08:50:01 +1000 [thread overview]
Message-ID: <1466981401.20278.29.camel@kernel.crashing.org> (raw)
In-Reply-To: <4863e2f8235.599ebfcf@auth.smtp.1and1.co.uk>
On Sun, 2016-06-26 at 18:42 +0100, Darren Stevens wrote:
>
> commit d6a9996e84ac4beb7713e9485f4563e100a9b03e
> powerpc/mm: vmalloc abstraction in preparation for radix
>
> This commit introduced variables for some linux kernel addresses that had
> before been constants, unfortunately this stopped PaSemi PA6T systems(*) from
> booting as they call ioremap to map SoC registers before the mmu is initialised. The
> attached patch adds a hard-coded init of pci_io_base to the pas_init_early()
> function which which allows the kernel to boot normally.
Tell me more, when is that mapping done ? I'm changing things so that
platform probe is called much later so that might have an impact.
What consumes pci_io_base before it's been initialized ?
> The value will be harmlessly set again once pci starts up.
>
> (*) At the moment this has only been tested on an AmigaOneX1000, but I
> expect PaSemi
> reference systems to have been affected in the same way.
next prev parent reply other threads:[~2016-06-26 22:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-26 17:42 Proposed: Patch to fix boot on PA6T Darren Stevens
2016-06-26 20:08 ` Christian Zigotzky
2016-06-26 22:50 ` Benjamin Herrenschmidt [this message]
2016-06-29 19:52 ` Darren Stevens
2016-06-28 10:51 ` Michael Ellerman
2016-06-29 19:54 ` Darren Stevens
2016-06-28 14:18 ` Aneesh Kumar K.V
2016-06-29 19:56 ` Darren Stevens
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=1466981401.20278.29.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=aperez@alexperez.com \
--cc=chzigotzky@xenosoft.de \
--cc=darren@stevens-zone.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matthew@a-eon.com \
--cc=pjwall@mac.com \
--cc=rtd2@xtra.co.nz \
/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).