From: Darren Stevens <darren@stevens-zone.net>
To: linuxppc-dev@lists.ozlabs.org
Cc: Olof Johansson <olof@lixom.net>,
Christian Zigotzky <chzigotzky@xenosoft.de>
Subject: [PATCH 1/1] pasemi: Add fixup_device_tree function to prom_init
Date: Sun, 17 Jul 2016 19:46:41 +0100 (BST) [thread overview]
Message-ID: <487fa17881e.5524720d@auth.smtp.1and1.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 178 bytes --]
AmigaOS...........: http://yam.ch/
Unix/MacOS/Windows: http://www.mozilla.com/thunderbird/
General information about MIME can be found at:
http://en.wikipedia.org/wiki/MIME
[-- Attachment #2: Type: text/plain, Size: 271 bytes --]
Add a pasmei platform specific entry in the fixup_device_tree() call
in prom_init.c.
This call will be used to fix the broken device tree passed by CFE
on AmigaOneX1000 machines.
Signed-off-by: Darren Stevens<darren@stevens-zone.net>
---
[-- Attachment #3: prom.patch --]
[-- Type: text/plain, Size: 720 bytes --]
diff --git a/arch/powerpc/kernel/prom_init.c b/arch/powerpc/kernel/prom_init.c
index 6ee4b72..287ce4b 100644
--- a/arch/powerpc/kernel/prom_init.c
+++ b/arch/powerpc/kernel/prom_init.c
@@ -2639,6 +2639,13 @@ static void __init fixup_device_tree_efika(void)
#else
#define fixup_device_tree_efika()
#endif
+#ifdef CONFIG_PPC_PASEMI
+static void __init fixup_device_tree_pasemi(void)
+{
+}
+#else
+#define fixup_device_tree_pasemi()
+#endif
static void __init fixup_device_tree(void)
{
@@ -2647,6 +2654,7 @@ static void __init fixup_device_tree(void)
fixup_device_tree_chrp();
fixup_device_tree_pmac();
fixup_device_tree_efika();
+ fixup_device_tree_pasemi();
}
static void __init prom_find_boot_cpu(void)
reply other threads:[~2016-07-17 19:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=487fa17881e.5524720d@auth.smtp.1and1.co.uk \
--to=darren@stevens-zone.net \
--cc=chzigotzky@xenosoft.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=olof@lixom.net \
/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).