From: Michael Ellerman <michael@ellerman.id.au>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org, dhlii@dlasys.net
Subject: Re: device trees.
Date: Mon, 11 May 2009 12:00:03 +1000 [thread overview]
Message-ID: <1242007203.7767.28.camel@concordia> (raw)
In-Reply-To: <fa686aa40905091351k140c64a0w27eb44908218814@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 766 bytes --]
On Sat, 2009-05-09 at 14:51 -0600, Grant Likely wrote:
> On Fri, May 8, 2009 at 10:03 AM, David H. Lynch Jr. <dhlii@dlasys.net> wrote:
> > Is there an example somewhere that shows building a device tree on
> > the fly ?
> >
> > As our products move forward it becomes increasingly clear that
> > static configurations are not going to work.
> To use device tree with partial reconfiguration would require rework
> to the device tree infrastructure to prune and graft portions of the
> device tree. I think it is possible, but it is non-trivial to get
> working.
arch/powerpc/platforms/pseries/reconfig.c
Not pretty, but it does more or less what you're talking about. Would
need some work to get it going on !pseries obviously.
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-05-11 2:00 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 16:03 device trees David H. Lynch Jr.
2009-05-08 17:15 ` Timur Tabi
2009-05-08 18:43 ` Kumar Gala
2009-05-09 20:51 ` Grant Likely
2009-05-11 2:00 ` Michael Ellerman [this message]
2009-05-11 4:08 ` Grant Likely
2009-05-11 6:32 ` David H. Lynch Jr.
2009-05-11 13:51 ` Grant Likely
2009-05-11 15:52 ` Stephen Neuendorffer
2009-05-11 16:58 ` David H. Lynch Jr.
[not found] ` <20090511183638.F07C01438054@mail184-wa4.bigfish.com>
[not found] ` <4A08C599.2030100@dlasys.net>
[not found] ` <20090512005554.EEE1019D009B@mail129-dub.bigfish.com>
2009-05-12 2:34 ` David H. Lynch Jr.
2009-05-12 4:27 ` Stephen Neuendorffer
2009-05-12 5:30 ` Grant Likely
2009-05-13 0:10 ` Stephen Neuendorffer
2009-05-13 2:36 ` David Gibson
2009-05-13 4:03 ` Grant Likely
2009-05-13 6:11 ` David H. Lynch Jr.
2009-05-13 6:21 ` David Gibson
2009-05-13 18:11 ` David H. Lynch Jr.
2009-05-14 3:08 ` David Gibson
2009-05-14 12:51 ` David H. Lynch Jr.
2009-05-13 6:58 ` Stephen Neuendorffer
2009-05-11 16:45 ` David H. Lynch Jr.
2009-05-11 17:47 ` Grant Likely
2009-05-11 21:38 ` David H. Lynch Jr.
2009-05-11 22:29 ` Benjamin Herrenschmidt
2009-05-11 22:56 ` David Gibson
2009-05-12 2:37 ` Michael Ellerman
2009-05-11 23:09 ` Grant Likely
2009-05-12 1:12 ` David Gibson
2009-05-12 5:22 ` Grant Likely
2009-05-12 23:24 ` David Gibson
2009-05-13 0:01 ` Grant Likely
2009-05-13 0:13 ` David H. Lynch Jr.
2009-05-13 1:15 ` Grant Likely
2009-05-13 2:32 ` David Gibson
2009-05-11 23:19 ` Stephen Neuendorffer
2009-05-12 0:04 ` Grant Likely
2009-05-12 7:38 ` Wolfram Sang
2009-05-11 14:58 ` Timur Tabi
2009-05-11 16:54 ` David H. Lynch Jr.
2009-05-11 23:27 ` David Gibson
2009-05-11 22:25 ` Benjamin Herrenschmidt
[not found] <20110703222042.19386c7wy7zfn4g8@webmail.huji.ac.il>
[not found] ` <20110703222042.19386c7wy7zfn4g8-2RFepEojUI0+8gVPFGsyePqBs+8SCbDb@public.gmane.org>
2011-07-03 21:01 ` Device Trees 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=1242007203.7767.28.camel@concordia \
--to=michael@ellerman.id.au \
--cc=dhlii@dlasys.net \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.