From: Wolfgang Grandegger <wg@grandegger.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] libfdt release?
Date: Mon, 15 Oct 2007 21:21:54 +0200 [thread overview]
Message-ID: <4713BDD2.7070608@grandegger.com> (raw)
In-Reply-To: <477B32C9-EC0F-4DB7-A1A1-C5E3041C9CDE@freescale.com>
Kumar Gala wrote:
> Guys,
>
> Can you tell me where we stand on changes/additions to libfdt vs u-
> boot. I'd really like to see an updated libfdt imported into u-boot
> for the next window and am happy to work on the u-boot modifications
> as long as I understand what exactly they are.
>
> Having fdt_get_name() and fdt_get_path() will be really useful for
> some fixup of device node code I've got and will allow us to drop the
> hard coded/explicit PATHs to nodes from <config.h>.
>
> I'd rather see us take a clean libfdt drop rather than pulling in
> bits and pieces.
Yes, that would be nice but the libfdt for U-Boot may still need to be
extended, especially for dynamic configuration. Therefore I would
appreciate a discussion on what else we need for that purpose and how we
handle (separate) common and extended libfdt functions for U-Boot. For
the dynamic configuration, I'm clearly in favor of function names
similar to the one commonly used in Linux (with the prefix fdt:):
of_find_node_by_path
of_find_node_by_type
of_find_node_by_phandle
of_find_compatible_node
of_device_is_compatible
of_get_property
Wolfgang.
next prev parent reply other threads:[~2007-10-15 19:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <006E3CAD-11CB-4892-8BDB-9866677F371D@freescale.com>
[not found] ` <20071010061458.GA6135@localhost.localdomain>
[not found] ` <912BB32E-FD7D-4CBC-AE3D-3D358E97DECB@freescale.com>
[not found] ` <20071011041239.GF14873@localhost.localdomain>
[not found] ` <9917D225-2082-4900-BFD4-96490EA88C42@freescale.com>
2007-10-11 23:35 ` [U-Boot-Users] libfdt release? Jerry Van Baren
2007-10-11 23:56 ` Detlev Zundel
2007-10-12 4:28 ` David Gibson
2007-10-12 7:16 ` Wolfgang Grandegger
2007-10-15 3:20 ` David Gibson
2007-10-12 11:58 ` Jerry Van Baren
2007-10-15 4:12 ` David Gibson
2007-10-15 18:30 ` Kumar Gala
2007-10-15 18:51 ` Jerry Van Baren
2007-10-15 19:03 ` Kumar Gala
2007-10-15 19:23 ` Jerry Van Baren
2007-10-15 21:50 ` Kumar Gala
2007-10-15 19:21 ` Wolfgang Grandegger [this message]
2007-10-16 2:44 ` David Gibson
2007-10-16 7:03 ` Wolfgang Grandegger
2007-10-16 7:19 ` David Gibson
2007-10-23 14:39 ` Kumar Gala
2007-10-23 23:51 ` David Gibson
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=4713BDD2.7070608@grandegger.com \
--to=wg@grandegger.com \
--cc=u-boot@lists.denx.de \
/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.