linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Darren Stevens <darren@stevens-zone.net>
To: linuxppc-dev@lists.ozlabs.org
Cc: olof@lixom.net, Christian Zigotzky <chzigotzky@xenosoft.de>
Subject: [ RFC PATCH 3/3] powerpc:pasemi: Fix device_type of Nemo SB600 node.
Date: Wed, 31 Aug 2016 13:24:45 +0100 (BST)	[thread overview]
Message-ID: <48ba9b708e2.6395f2f3@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: 262 bytes --]

    The of_node for the SB600 (io-bridge) has its device_type set to
    'io-bridge' Set it to 'isa' so that it can be found by
    isa_bridge_find_early() instead of using patches in the kernel.

    Signed-off-by: Darren Stevens <darren@stevens-zone.net>

---

[-- Attachment #3: nemo_2.patch --]
[-- Type: text/plain, Size: 833 bytes --]

diff --git a/arch/powerpc/kernel/prom_init.c b/arch/powerpc/kernel/prom_init.c
index 8269093..d75937a 100644
--- a/arch/powerpc/kernel/prom_init.c
+++ b/arch/powerpc/kernel/prom_init.c
@@ -2697,6 +2697,24 @@ static void __init fixup_device_tree_pasemi(void)
 			}
 		}
 	}
+
+	/*
+	 * The io-bridge has device_type set to 'io-bridge'
+	 * change it to 'isa' so that generic isa-bridge code can add the SB600 and
+	 * its on-board peripherals.
+	 */
+
+	name = "/pxp@0,e0000000/io-bridge@0";
+        iob = call_prom("finddevice", 1, 1, ADDR(name));
+        if (!PHANDLE_VALID(iob))
+                return;
+
+	/* device_type is already set, just change it. */
+
+	prom_printf("Changing device_type of SB600 node...\n");
+
+	prom_setprop(iob, name, "device_type", "isa", sizeof("isa"));
+
 #endif //CONFIG_PPC_PASEMI_NEMO
 }
 #else

                 reply	other threads:[~2016-08-31 14:10 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=48ba9b708e2.6395f2f3@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).