From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx.com>
Cc: "Koss, Mike \(Mission Systems\)" <mike.koss@ngc.com>,
"David H. Lynch Jr." <dhlii@dlasystems.com>,
linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: Xilinx devicetrees
Date: Mon, 26 Nov 2007 15:09:06 -0700 [thread overview]
Message-ID: <fa686aa40711261409s1535d2b8m3a58e90bcc2206a7@mail.gmail.com> (raw)
In-Reply-To: <20071126215615.73F4B1138066@mail175-dub.bigfish.com>
On 11/26/07, Stephen Neuendorffer <stephen.neuendorffer@xilinx.com> wrote:
>
>
> > -----Original Message-----
> > From: David H. Lynch Jr. [mailto:dhlii@dlasystems.com]
> > Sent: Monday, November 26, 2007 1:17 PM
> > To: Koss, Mike (Mission Systems)
> > Cc: Stephen Neuendorffer; Grant Likely; linuxppc-embedded
> > Subject: Re: Xilinx devicetrees
> >
> > My objective is to get alot of software - linux, GHS, and
> > standalone apps, to all load - from a single executables, accross
> > multiple different bit images on several different (though
> > deliberately
> > similar) products. My Linux kernel needs to work regardless
> > of the Pico
> > card and regardless of the bit image, as done my GHS kernel, and ....
> > And I need to do that in a severly resource constrained environment.
> > I would hope that should make sense of my harping about
> > version/capabilities registers. If I have maybe 10 possible
> > peices of IP
> > that may/maynot be present in a given FPGA and I am trying to
> > dynamically configure - Linux/GHS/... to adapt to whatever it
> > encounters
> > and work as long as it is a viable combination. At best
> > devicetrees are
> > an extremly complex way of solving that - while version
> > registers are a
> > trivial way.
I disagree. I'm not disputing that version registers are valuable.
But I *am* disputing their value for device detection. It may work in
your specific case of devices always in certain locations, but it does
not help the general case where devices can be instantiated anywhere
in the 4GB address space.
>
> It sounds like the real problem that you have is that even if you get
> device trees working for Linux, you still have the same problem for GHS,
> so from your perspective "device trees don't help"
In embedded power.org land, device trees are becoming the recommended
method for describing platform configuration for all embedded powerpc
software. Not just Linux. So from that perspective device trees
might help.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-11-26 22:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 11:37 Xilinx devicetrees David H. Lynch Jr.
2007-11-24 17:12 ` Grant Likely
2007-11-25 5:24 ` Stephen Neuendorffer
2007-11-25 9:37 ` David H. Lynch Jr.
2007-11-25 18:15 ` Stephen Neuendorffer
2007-11-27 23:55 ` John Williams
2007-11-28 0:27 ` Grant Likely
2007-11-28 0:28 ` Stephen Neuendorffer
2007-11-28 0:52 ` John Williams
2007-11-28 14:33 ` Jon Loeliger
2007-11-28 17:28 ` Stephen Neuendorffer
2007-11-28 18:12 ` Grant Likely
2007-11-29 10:56 ` David H. Lynch Jr.
2007-11-25 9:15 ` David H. Lynch Jr.
2007-11-25 22:21 ` Grant Likely
2007-11-25 22:55 ` David H. Lynch Jr.
2007-11-25 23:58 ` Stephen Neuendorffer
2007-11-26 21:36 ` David H. Lynch Jr.
2007-12-13 2:40 ` Koss, Mike (Mission Systems)
2007-11-26 16:30 ` Grant Likely
2007-11-26 20:28 ` David H. Lynch Jr.
2007-11-26 21:16 ` David H. Lynch Jr.
2007-11-26 21:55 ` Stephen Neuendorffer
2007-11-26 22:09 ` Grant Likely [this message]
2007-11-26 22:19 ` Koss, Mike (Mission Systems)
2007-12-13 4:52 ` Stephen Neuendorffer
2007-12-13 13:49 ` Koss, Mike (Mission Systems)
2007-12-13 17:36 ` Stephen Neuendorffer
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=fa686aa40711261409s1535d2b8m3a58e90bcc2206a7@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=dhlii@dlasystems.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mike.koss@ngc.com \
--cc=stephen.neuendorffer@xilinx.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;
as well as URLs for NNTP newsgroup(s).