From: David Andrey <David.Andrey@netmodule.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Updating YAFFS2 RootFS
Date: Mon, 28 Jun 2010 08:53:55 +0200 [thread overview]
Message-ID: <1OT8ED-000558-1r@wolf.netmodule.com> (raw)
In-Reply-To: <20100625220141.E374914EBF4@gemini.denx.de>
Dear Wolfgang,
Seems that a little much infos about background will be a good thing :-)
The idea is to provide an update / restore mechanism from U-boot.
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
But why from U-Boot ? :-)
-> To provide a robust update mechanism.
-> equals what happens with Linux (through end-user), u-boot
will "always" start.
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/
The patch's I means are:
http://lists.denx.de/pipermail/u-boot/2008-September/040910.html
http://lists.denx.de/pipermail/u-boot/2006-September/016867.html
So, what do you think ? Sense or no sense ? Is it a way to achieve this
from u-boot ?
Regards
David
-----Original Message-----
From: Wolfgang Denk [mailto:wd at denx.de]
Sent: Samstag, 26. Juni 2010 00:02
To: David Andrey
Cc: u-boot at lists.denx.de
Subject: Re: [U-Boot] Updating YAFFS2 RootFS
Dear "David Andrey",
In message <1OS8pe-0000df-Uh@wolf.netmodule.com> you wrote:
>
> I'm looking to update the linux yaffs2 rootfs from U-Boot (2009-06).
The
> whole update will be:
Are you positively sure you have to do this in U-Boot? Keep in mind
that U-Boot is a boot loader, so don't throw tasks on it that require
an operating system.
> * Take the rootfs.tgz from the yaffs2 "image" partition (ok,
> with yrdm / ywrm) for update or restore purposes.
OK - but... what for?
> * Unpack it (maybe gunzip)
Why? And: why in U-Boot?
> * Update the Linux YAFFS2 RootFS (how ?)
Just write a new image to another, alternative partition.
> After a quick search (mail list, code) seems that:
>
> * No native support for this operation in u-boot.
What exactly is "this operation" here, which you are missing support
for?
> * Some "user" patch files exists (out of date ?)
Which sort of patches are you referring to?
> * Is the situation really like that ?
Sorry, I don;t undewrstand what exactly you mean by "the situation" ?
> * Which is the actual patch file ?
What do you mean?
> * What about the future for YAFFS2 in U-Boot ? Is there any
> update planned ?
YAFFS2 is supported in mainline U-Boot. What exactly do you think is
missing?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Build a system that even a fool can use and only a fool will want to
use it.
next prev parent reply other threads:[~2010-06-28 6:53 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 [this message]
2010-06-28 7:32 ` Wolfgang Denk
2010-06-28 12:13 ` David Andrey
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=1OT8ED-000558-1r@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