From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Testing todays u-boot-fdt
Date: Thu, 19 Apr 2007 10:24:20 -0500 [thread overview]
Message-ID: <462789A4.6080206@freescale.com> (raw)
In-Reply-To: <46275BC2.6080506@smiths-aerospace.com>
Jerry Van Baren wrote:
> The bad version error is because you are running a version 16 blob and
> you need a version 17 blob to allow modifications. David Gibson has an
> intention of upconverting a v16 to v17 as part of libfdt, but neither of
> us has gotten around to doing it yet.
In that case, "libfdt: FDT_ERR_BADVERSION" is a really useless error message. Please
change it to something like, "Cannot modify this version (v16) of the device tree".
Now that we support multiple version of the device tree, it is very important that error
message are clear. On a working system, it's unlikely people will update their device
tree. They'll just update the kernel and U-Boot, and so people using older versions of
the device tree need to be told very clearly what they can and can't do.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-04-19 15:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 8:58 [U-Boot-Users] Testing todays u-boot-fdt Wolfgang Grandegger
2007-04-19 12:08 ` Jerry Van Baren
2007-04-19 13:10 ` Wolfgang Grandegger
2007-04-19 13:19 ` Jerry Van Baren
2007-04-19 15:24 ` Timur Tabi [this message]
2007-04-22 20:38 ` Timur Tabi
2007-04-23 0:05 ` Jerry Van Baren
2007-04-19 13:28 ` Jerry Van Baren
2007-04-19 13:42 ` Wolfgang Grandegger
2007-04-19 15:51 ` Wolfgang Denk
2007-04-19 23:11 ` Jerry Van Baren
2007-04-19 23:19 ` Wolfgang Denk
2007-04-20 16:36 ` Wolfgang Grandegger
2007-04-20 17:11 ` Jerry Van Baren
2007-04-20 20:40 ` Wolfgang Denk
2007-04-20 22:02 ` Jerry Van Baren
2007-04-20 3:38 ` Jerry Van Baren
2007-04-20 13:32 ` Wolfgang Denk
2007-04-20 3:40 ` Jerry Van Baren
[not found] <4629358C.5050401@cideas.com>
2007-04-20 23:01 ` Wolfgang Denk
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=462789A4.6080206@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