From: Warner Losh <imp@bsdimp.com>
To: grant.likely@secretlab.ca
Cc: ddaney@caviumnetworks.com, prasun.kapoor@caviumnetworks.com,
linux-mips@linux-mips.org, devicetree-discuss@lists.ozlabs.org
Subject: Re: Device Tree questions WRT MIPS/Octeon SOCs.
Date: Thu, 14 Oct 2010 19:13:09 -0600 (MDT) [thread overview]
Message-ID: <20101014.191309.515504596.imp@bsdimp.com> (raw)
In-Reply-To: <AANLkTi=UM2p26JJMqv-cNh8xACS_KPf_dCst5cgmh5VR@mail.gmail.com>
In message: <AANLkTi=UM2p26JJMqv-cNh8xACS_KPf_dCst5cgmh5VR@mail.gmail.com>
Grant Likely <grant.likely@secretlab.ca> writes:
: Overall the plan makes sense, however I would suggest the following.
: instead of 'live' modifying the tree, another option is to carry a set
: of 'stock' device trees in the kernel; one per board. Of course this
: assumes that your current ad-hoc code is keying on the specific board.
: If it is interpreting data provided by the firmware, then your
: suggestion of modifying a single stock tree probably makes more sense,
: or possibly a combination of the too. In general you should avoid
: live modification as much as possible.
The one draw back on this is that there's lots of different "stock"
boards that the Cavium Octeon SDK supports. These will be difficult
to drag along for every kernel. And they'd be mostly the same to,
which is why I think that David is suggesting the live modification
thing...
I know that FreeBSD will have exactly the same problem as we move to
using the FDT for FreeBSD/mips' configuration.
Warner
next prev parent reply other threads:[~2010-10-15 1:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 0:17 Device Tree questions WRT MIPS/Octeon SOCs David Daney
2010-10-15 0:32 ` Grant Likely
2010-10-15 1:13 ` Warner Losh [this message]
2010-10-15 1:29 ` Grant Likely
2010-10-15 17:30 ` David VomLehn (dvomlehn)
2010-10-15 17:30 ` David VomLehn (dvomlehn)
2010-10-15 17:42 ` David Daney
2010-10-15 17:48 ` David VomLehn (dvomlehn)
2010-10-15 17:48 ` David VomLehn (dvomlehn)
2010-10-16 3:45 ` Grant Likely
2010-10-16 6:24 ` David Gibson
2010-10-16 6:20 ` David Gibson
2010-10-16 3:48 ` Grant Likely
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=20101014.191309.515504596.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=ddaney@caviumnetworks.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-mips@linux-mips.org \
--cc=prasun.kapoor@caviumnetworks.com \
/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