[U-Boot] NAND JFFS2 support in U-Boot 2009.03
Hi, In previous versions of U-Boot, there were options for writing JFFS2 file systems to NAND (i.e., nand write.jffs2).
Is this command no longer supported in the latest U-Boot release or is the command the same as the nand write command?
In other words, was there something special about the" nand write.jffs2" command? or is the same thing accomplished by just doing a ""nand write" command and specifying the RAM address where a JFFS2 filesystem was downloaded?
Thanks.
Christopher M. Fairfax Sr. Software Engineer Rockwell Collins +1 540-428-3344 +1 540-428-3301 cmfairfa@rockwellcollins.com This message contains PRIVILEGED AND PROPRIETARY INFORMATION intended solely for the use of the addressee(s) named above. Any disclosure, distribution, copying or use of the information by others is strictly prohibited. If you have received this message in error, please advise the sender by immediate reply and delete the original message. Thank you.
On Monday 27 April 2009 08:59:11 cmfairfa@rockwellcollins.com wrote:
In previous versions of U-Boot, there were options for writing JFFS2 file systems to NAND (i.e., nand write.jffs2).
the name was a misnomer. it didnt do anything jffs2 specific, it just handled bad block detection.
Is this command no longer supported in the latest U-Boot release or is the command the same as the nand write command?
reading 'nand help' indicates the latter
This message contains PRIVILEGED AND PROPRIETARY INFORMATION intended
please fix your e-mail system so that this bogus crap is not included in your e-mails -mike
Mike Frysinger wrote:
On Monday 27 April 2009 08:59:11 cmfairfa@rockwellcollins.com wrote:
In previous versions of U-Boot, there were options for writing JFFS2 file systems to NAND (i.e., nand write.jffs2).
the name was a misnomer. it didnt do anything jffs2 specific, it just handled bad block detection.
Is this command no longer supported in the latest U-Boot release or is the command the same as the nand write command?
reading 'nand help' indicates the latter
This message contains PRIVILEGED AND PROPRIETARY INFORMATION intended
please fix your e-mail system so that this bogus crap is not included in your e-mails
Most people posting from .com's that include this stuff are in no position to do anything about them. Since this was sent to a public list, the intended distribution is everyone, so I see no reason to harass people over them. (Well, unless it says no one can read this email, even the intended recipient)
Philip
On Monday 27 April 2009 14:32:09 Philip Balister wrote:
Mike Frysinger wrote:
On Monday 27 April 2009 08:59:11 cmfairfa@rockwellcollins.com wrote:
This message contains PRIVILEGED AND PROPRIETARY INFORMATION intended
please fix your e-mail system so that this bogus crap is not included in your e-mails
Most people posting from .com's that include this stuff are in no position to do anything about them.
they certainly can: either talk to their local dept or use any of the free systems out there (like gmail)
Since this was sent to a public list, the intended distribution is everyone, so I see no reason to harass people over them. (Well, unless it says no one can read this email, even the intended recipient)
their garbage doesnt belong on the list -mike
participants (3)
-
cmfairfa＠rockwellcollins.com -
Mike Frysinger -
Philip Balister