From: "Brian Norris" <computersforpeace@gmail.com>
To: "Artem Bityutskiy" <dedekind1@gmail.com>
Cc: brian.foster@maxim-ic.com,
Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org
Subject: [PATCH 5/9] doc: nand: update YAFFS URL
Date: Mon, 8 Aug 2011 12:37:15 -0700 [thread overview]
Message-ID: <1312832239-21759-6-git-send-email-computersforpeace@gmail.com> (raw)
In-Reply-To: <1312832239-21759-1-git-send-email-computersforpeace@gmail.com>
The YAFFS website has moved. They're sitll redirecting, but we should
switch.
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
---
doc/nand.xml | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/nand.xml b/doc/nand.xml
index 1d55685..281e0e0 100644
--- a/doc/nand.xml
+++ b/doc/nand.xml
@@ -139,7 +139,7 @@ designed for the usage of DiskOnChip devices. JFFS2 supports raw NAND chips and
SmartMediaCards at the moment. A JFFS2 support for DiskOnChip devices, based on the
NAND code, is planned. There are some other Open Source projects for NAND filesystem
support, but there's no other working solution than JFFS, YAFFS, and UBIFS at the moment of this writing.
-YAFFS is available from <a href="http://www.aleph1.co.uk/armlinux/projects/yaffs">YAFFS-Homepage</a>.
+YAFFS is available from <a href="http://www.yaffs.net/">YAFFS-Homepage</a>.
YAFFS is faster than JFFS2 and consumes less RAM, JFFS2 provides on the fly file compression and
decompression, which is very helpful for small FLASHs. UBIFS provides compression similar to JFFS2, but
is usually a better choice for large NAND flash chips (see <a href="ubifs.html">here</a> for more
@@ -334,7 +334,7 @@ CONFIG_JFFS2_FS_NAND=y</p>
<h2>References:</h2>
<h3>Open Source</h3>
<p>JFFS2, NTFL, and UBIFS are located on this <a href="../index.html">website</a>.<br />
-YAFFS is located at <a href="http://www.aleph1.co.uk/armlinux/projects/yaffs">YAFFS-Homepage</a>.</p>
+YAFFS is located at <a href="http://www.yaffs.net/">YAFFS-Homepage</a>.</p>
<h3>Hardware</h3>
<p><a href="http://www.toshiba.com/taec">Toshiba</a></p>
<p><a href="http://samsungelectronics.com">Samsung</a></p>
--
1.7.0.4
next prev parent reply other threads:[~2011-08-08 19:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 19:37 [PATCH 0/9] mtd-www: various fixes, bug reporting info Brian Norris
2011-08-08 19:37 ` [PATCH 1/9] UBIFS FAQ: spelling, grammar Brian Norris
2011-08-08 19:37 ` [PATCH 2/9] faq: general: update "pleonasm" description Brian Norris
2011-08-08 19:37 ` [PATCH 3/9] faq: general: turn statement into a question Brian Norris
2011-08-08 19:37 ` [PATCH 4/9] faq/doc: ubi(fs): move "bug report" questions to FAQ Brian Norris
2011-08-08 19:37 ` Brian Norris [this message]
2011-08-08 19:37 ` [PATCH 6/9] doc: update info on compiling mtd-utils Brian Norris
2011-08-08 19:37 ` [PATCH 7/9] faq: ubi(fs): sending bug reports using `mtdinfo' Brian Norris
2011-08-09 22:03 ` [PATCH v2 " Brian Norris
2011-08-08 19:37 ` [PATCH 8/9] faq: ubi(fs): small spelling, URL fixups Brian Norris
2011-08-09 22:05 ` [PATCH v2 " Brian Norris
2011-08-08 19:37 ` [PATCH 9/9] faq: general: add bug reporting FAQ Brian Norris
2011-08-09 8:10 ` Brian Foster
2011-08-09 22:05 ` [PATCH v2 " Brian Norris
2011-08-10 7:54 ` Brian Foster
2011-08-10 8:34 ` [PATCH " Brian Norris
2011-08-08 20:00 ` [PATCH 0/9] mtd-www: various fixes, bug reporting info Artem Bityutskiy
2011-08-15 12:19 ` Artem Bityutskiy
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=1312832239-21759-6-git-send-email-computersforpeace@gmail.com \
--to=computersforpeace@gmail.com \
--cc=brian.foster@maxim-ic.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
/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