Hi,
I'm looking to update the linux yaffs2 rootfs from U-Boot (2009-06). The whole update will be:
* Take the rootfs.tgz from the yaffs2 "image" partition (ok, with yrdm / ywrm) for update or restore purposes.
* Unpack it (maybe gunzip)
* Update the Linux YAFFS2 RootFS (how ?)
After a quick search (mail list, code) seems that:
* No native support for this operation in u-boot.
* Some "user" patch files exists (out of date ?)
So, my questions:
* Is the situation really like that ?
* Which is the actual patch file ?
* What about the future for YAFFS2 in U-Boot ? Is there any update planned ?
Regards
David
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 anyupdate planned ?
YAFFS2 is supported in mainline U-Boot. What exactly do you think is missing?
Best regards,
Wolfgang Denk
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@denx.de] Sent: Samstag, 26. Juni 2010 00:02 To: David Andrey Cc: u-boot@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 anyupdate planned ?
YAFFS2 is supported in mainline U-Boot. What exactly do you think is missing?
Best regards,
Wolfgang Denk
Dear "David Andrey",
Please do not top post / full qoute. Read http://www.netmeister.org/news/learn2quote.html
In message 1OT8ED-000558-1r@wolf.netmodule.com you wrote:
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:
- 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.
But why from U-Boot ? :-) -> To provide a robust update mechanism. -> equals what happens with Linux (through end-user), u-boot will "always" start.
OK.
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/
For me the reason to have the images partition is missing. 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.
And as long as you download the images anyway there is little reason to store these locally in a non-installed form. At least I cannt see one.
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
That's old and obsolete stuff. Should not be needed at all.
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.
Best regards,
Wolfgang Denk
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:
- 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
Dear "David Andrey",
In message 1OTDDq-0001LY-6O@wolf.netmodule.com you wrote:
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.
As mentioned: you can do that, but I would not recommend it.
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.
Use a file system type which supports compression?
The YAFFS2 code in U-Boot is the one released in 2007. Do you plan any update in some near future ?
I am not aware of any such plans. Patches are welcome.
Best regards,
Wolfgang Denk
participants (2)
-
David Andrey -
Wolfgang Denk