From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] idea: fdt_checkboard
Date: Fri, 18 May 2007 09:17:28 -0500 [thread overview]
Message-ID: <464DB578.3080508@freescale.com> (raw)
In-Reply-To: <464D0F0F.8070901@gmail.com>
Jerry Van Baren wrote:
> I would rather give hush the ability to read fdt properties so that the
> logic could be scripted rather than being "hardcoded" in a C function.
> This would give some interesting capabilities, like selecting the proper
> fdt out of several in memory.
The two really aren't mutually exclusive. Besides, fdt_checkboard() would not work in a
hush script. The C function would scan the device tree *and* read data from the hardware
and compare the two. For instance, if it says that there's a PCI device at address X, it
should check if CFG_PCI1_MEM_PHYS is set to the same value. These are the kinds of things
that can only be done in C code.
--
Timur Tabi
Linux Kernel Developer @ Freescale
prev parent reply other threads:[~2007-05-18 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 19:11 [U-Boot-Users] idea: fdt_checkboard Timur Tabi
2007-05-18 2:27 ` Jerry Van Baren
2007-05-18 6:48 ` Wolfgang Grandegger
2007-05-18 14:17 ` Timur Tabi [this message]
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=464DB578.3080508@freescale.com \
--to=timur@freescale.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