From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org
Subject: Re: is there any continuing value in node "chosen@0"?
Date: Mon, 6 Aug 2018 12:55:10 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.1808061253130.27570@localhost.localdomain> (raw)
In-Reply-To: <CAL_JsqJnzYoKP-3PN_5g1rFTotMBDx5N-KecbQYAus+mspbBmw@mail.gmail.com>
On Mon, 6 Aug 2018, Rob Herring wrote:
> On Mon, Aug 6, 2018 at 6:34 AM Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> >
> >
> > while the current DTSpec says nothing about the chosen node
> > possibly having a unit-address, if i search the current linux
> > kernel code base, there are a few examples of just that:
> >
> > $ git grep chosen@
> > arch/mips/generic/yamon-dt.c: chosen_off = fdt_path_offset(fdt, "/chosen@0");
> > arch/mips/generic/yamon-dt.c: chosen_off = fdt_path_offset(fdt, "/chosen@0");
>
> Nothing MIPS based should need this I think.
i just submitted a patch to the MIPS list, and they're applying it
to mips-next for 4.19, so i just need to browbeat the PPC folks into
dropping it, and all references to "/chosen@0" can be tossed entirely.
i love deleting stuff.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2018-08-06 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 12:32 is there any continuing value in node "chosen@0"? Robert P. J. Day
2018-08-06 15:57 ` Rob Herring
2018-08-06 16:55 ` Robert P. J. Day [this message]
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=alpine.LFD.2.21.1808061253130.27570@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.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).