From: David Andrey <David.Andrey@netmodule.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Updating YAFFS2 RootFS
Date: Mon, 28 Jun 2010 14:13:47 +0200 [thread overview]
Message-ID: <1OTDDq-0001LY-6O@wolf.netmodule.com> (raw)
In-Reply-To: <20100628073204.F34D614EBF7@gemini.denx.de>
Dear Wolfgang,
>>
>> he NAND is formatted as follow:
>> * U-Boot Partition
>> * Images Partition (YAFFS2) (Kernel, RootFS as tgz, FPGA / DSP
>> Firmwares).
>> * Linux RootFS (YAFFS2)
>
>> To update "Linux", the way we imagine is this one:
>> 1. write a new kernel and rootFS in the "Images" partition (get the
>> files through TFTP)
>> 2. u-boot erase the old rootFS and "install" the newer
>> 3. Boot Linux with the newer kernel
>If you have a network connection an can download the images through
>TFTP, then why do you need the "Images Partition" at all? You
>coulinstall the downloaded images directly.
For restore purposes.
> So, I'm looking to clarify the step 2. What is missing ? Ideally,
> something like this:
> yrdm /images/my_newer_rootfs.tgz my_ram_address
> yunzip my_ram_address /rootfs/
> If I were in your place, I would probably use the spoace rather to
have space
> for a second root file system, so I can always install into an
> alternative partition while keeping the old (working copy) in place.
> Even if an update fails permanently for some reason (like corrupted
> images on the server) you can then still fall back to the old version.
Is plan B. Compressed RootFS still take less space.
>> So, what do you think ? Sense or no sense ? Is it a way to achieve
this
>> from u-boot ?
> It can be done as you described it, but it makes little sense to me.
What about the implementation of a "yunzip" ? Any suggestions ?
The YAFFS2 code in U-Boot is the one released in 2007. Do you plan any
update in some near future ?
Regards
David
next prev parent reply other threads:[~2010-06-28 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 13:20 [U-Boot] Updating YAFFS2 RootFS David Andrey
2010-06-25 22:01 ` Wolfgang Denk
2010-06-28 6:53 ` David Andrey
2010-06-28 7:32 ` Wolfgang Denk
2010-06-28 12:13 ` David Andrey [this message]
2010-06-28 12:55 ` 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=1OTDDq-0001LY-6O@wolf.netmodule.com \
--to=david.andrey@netmodule.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