From: Mike Ditto <mditto@consentry.com>
To: linuxppc-embedded@ozlabs.org
Subject: unit name for /soc in device tree
Date: Fri, 03 Oct 2008 13:13:17 -0700 [thread overview]
Message-ID: <48E67CDD.8080002@consentry.com> (raw)
Hi,
I'm starting a scratch port of Linux 2.6 to an MPC8272 board that currently
runs 2.4 (MontaVista).
Documentation/powerpc/booting-without-of.txt says:
The name of an soc
node should start with "soc", and the remainder of the name should
represent the part number for the soc. For example, the MPC8540's
soc node would be called "soc8540".
So I used the unit name "soc8272@f0000000" in my .dts file.
But arch/powerpc/boot/cpm-serial.c does:
muram = finddevice("/soc/cpm/muram/data");
And that doesn't work if I follow the naming convention suggested.
I changed the .dts file to use the name "soc" instead of "soc8272" and
now the boot serial driver works. Is that the right way to go? Or
will this lead to problems in the kernel later (I'm not that far yet)?
-=] Mike [=-
next reply other threads:[~2008-10-03 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 20:13 Mike Ditto [this message]
2008-10-03 20:25 ` unit name for /soc in device tree Scott Wood
2008-10-03 20:41 ` Mike Ditto
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=48E67CDD.8080002@consentry.com \
--to=mditto@consentry.com \
--cc=linuxppc-embedded@ozlabs.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 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).