From: Wolfgang Grandegger <wg@grandegger.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] fdt_find_compatible_node() and friends
Date: Thu, 03 May 2007 16:47:59 +0200 [thread overview]
Message-ID: <4639F61F.2050506@grandegger.com> (raw)
Hi Jerry,
before re-coding fdt_find_compatible_node(), some more comments.
After browsing more carefully the FDT related code of "arch/powerpc"
I think we also need, apart from fdt_find_compatible_node() and
fdt_path_offset(), fdt_find_node_by_type() and maybe
fdt_find_node_by_name(). These functions do a sequential scan of all
devices starting at the beginning or after a specified node. They
actually ignore the hierarchy. Do you agree?
BTW: any reason why not using the more compatible name
fdt_find_node_by_path() for fdt_path_offset()?
Wolfgang.
next reply other threads:[~2007-05-03 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 14:47 Wolfgang Grandegger [this message]
2007-05-03 15:14 ` [U-Boot-Users] fdt_find_compatible_node() and friends Jerry Van Baren
2007-05-05 13:03 ` Wolfgang Grandegger
2007-05-16 10:40 ` Wolfgang Grandegger
2007-05-16 13:33 ` Jerry Van Baren
2007-05-17 10:38 ` Jerry Van Baren
2007-05-17 11:32 ` Wolfgang Grandegger
2007-05-17 12:04 ` Jerry Van Baren
2007-05-17 12:31 ` Wolfgang Grandegger
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=4639F61F.2050506@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox