From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] dtb in env sector - was: (Try 2) Please pull ...
Date: Tue, 03 Apr 2007 10:21:01 -0400 [thread overview]
Message-ID: <461262CD.7000309@smiths-aerospace.com> (raw)
In-Reply-To: <1175609051.12080.41.camel@gentoo-jocke.transmode.se>
Joakim Tjernlund wrote:
> On Tue, 2007-04-03 at 14:59 +0200, Wolfgang Denk wrote:
>> In message <1175600261.12080.24.camel@gentoo-jocke.transmode.se> you wrote:
>>> I think to start with one would just need an install dtb command that
>>> places the dtb at the end of the env. sector to allow either one
>>> to grow without trashing eachother. Also rendundant env needs to be
>> Umm... The environment will not grow beyond it's defined size. Then
>> just use "cp" to copy the dtb to the next free address.
>
> And later you need some more space for env. so you increase CFG_ENV_SIZE
> a little and now you have destroyed your dtb as well.
Actually, it is much worse than that: currently when you do a "saveenv"
it will wipe out the fdt blob because it doesn't know that the blob is
in the same sector.
I'm thinking that we want to store the blob immediately after the env
variable storage _reserved area_ as a #define option (as a new #define
option? part of the CONFIG_OF_LIBFDT define?) and enhance the env
save/restore to do the blob too. This would get us the redundancy and
we can cover it with a new (preferred?) or existing env CRC (not good?).
>>> Secondly one needs someway of telling bootm where to find the dtb.
>> You pass the address as an argument...
>
> yes, but it would be handy to just say "use the dtb in my spare
> env space", especially if you use rendundant env. so the right
> one is selected.
>
> Regards
> Jocke
Best regards,
gvb
next prev parent reply other threads:[~2007-04-03 14:21 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-31 17:43 [U-Boot-Users] (Try 2) Please pull branch fdt-cmd from u-boot-fdt.git Jerry Van Baren
2007-03-31 18:20 ` Wolfgang Denk
2007-03-31 18:48 ` Jerry Van Baren
2007-04-03 23:50 ` Wolfgang Denk
2007-04-04 10:16 ` Jerry Van Baren
2007-04-04 12:22 ` [U-Boot-Users] Warning for mpc8360emds users: " Jerry Van Baren
2007-04-04 15:46 ` Timur Tabi
2007-04-04 16:17 ` Jerry Van Baren
2007-04-04 22:46 ` Wolfgang Denk
2007-04-05 3:08 ` Jerry Van Baren
2007-04-05 8:06 ` Wolfgang Denk
2007-04-05 11:00 ` Jerry Van Baren
2007-04-05 18:02 ` Bruce_Leonard at selinc.com
2007-04-05 18:12 ` Jerry Van Baren
2007-04-05 18:40 ` Bruce_Leonard at selinc.com
2007-04-06 21:57 ` Timur Tabi
2007-04-06 22:39 ` Jerry Van Baren
2007-04-07 0:15 ` Wolfgang Denk
2007-04-07 1:29 ` Jerry Van Baren
2007-03-31 18:27 ` [U-Boot-Users] (Try 2) Please pull branch " Jerry Van Baren
2007-04-04 0:21 ` Wolfgang Denk
2007-04-03 9:39 ` Joakim Tjernlund
2007-04-03 10:34 ` Jerry Van Baren
2007-04-03 11:37 ` Joakim Tjernlund
2007-04-03 12:06 ` Jerry Van Baren
2007-04-03 12:59 ` [U-Boot-Users] dtb in env sector - was: (Try 2) Please pull Wolfgang Denk
2007-04-03 14:04 ` Joakim Tjernlund
2007-04-03 14:21 ` Jerry Van Baren [this message]
2007-04-03 14:36 ` Martin Krause
2007-04-03 15:14 ` Joakim Tjernlund
2007-04-03 15:17 ` Jerry Van Baren
2007-04-03 15:24 ` Wolfgang Denk
2007-04-03 18:53 ` Joakim Tjernlund
2007-04-03 12:53 ` Wolfgang Denk
2007-04-03 12:49 ` Wolfgang Denk
2007-04-03 13:58 ` Joakim Tjernlund
2007-04-03 15:18 ` 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=461262CD.7000309@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.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