From: "David H. Lynch Jr." <dhlii@dlasys•net>
To: Timur Tabi <timur@freescale•com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: device trees.
Date: Mon, 11 May 2009 12:54:58 -0400 [thread overview]
Message-ID: <4A085862.5070303@dlasys.net> (raw)
In-Reply-To: <ed82fe3e0905110758l59ee1c94nffbfa50280851613@mail.gmail.com>
Timur Tabi wrote:
> On Mon, May 11, 2009 at 1:32 AM, David H. Lynch Jr. <dhlii@dlasys•net> wrote:
>
> So all you need to do is have your boot loader create a device tree
> from scratch. If you're using U-Boot, then you can already do this by
> making the appropriate libfdt calls. Otherwise, you should probably
> add libfdt to your boot loader.
>
As I mentioned before, we do nto use u-boot. I am not looking to
start a debate on it either, but it does not meet a number of our needs,
and would require significant architectural changes to do so. The
difference between it and devicetrees is that u-boot is avaiable to us
if we want, I did port u-boot to our hardware at one point and it did
everything it promised, but u-boot is optional, device trees are not.
I do not have to re-architect u-boot to fit into 16k of bram, or
load bit files or .....
If I want to move past 2.6.26 I have to not only use device trees
but actually make them work in a way that will function as we need with
our systems.
It is likely I will use libdft as a starting point, but I can not
see it as more than a short term solution. libdft is orders of magnitude
large than our entire monitor, and it is a toolkit rather than the whole
solution.
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii@dlasys•net http://www.dlasys.net
fax: 1.253.369.9244 Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.
"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein
next prev parent reply other threads:[~2009-05-11 17:01 UTC|newest]
Thread overview: 43+ 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
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. [this message]
2009-05-11 23:27 ` David Gibson
2009-05-11 22:25 ` Benjamin Herrenschmidt
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=4A085862.5070303@dlasys.net \
--to=dhlii@dlasys$(echo .)net \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=timur@freescale$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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