public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Max Seidenstücker" <naturally-aligned@web.de>
To: ecos-patches@ecos.sourceware.org
Subject: JFFS2 updated to support writebuffer
Date: Wed, 21 Aug 2013 08:34:00 -0000	[thread overview]
Message-ID: <1377074068386-241667.post@n7.nabble.com> (raw)

Hi folks,

finally I got a first version running. The port is based on the JFFS2
version contained in the 3.9.2 Linux kernel and is only tested on Freescale
MPC5668G PowerPC processor using NOR-ECC flash with 8 Byte aligned write
blocks. With the quality of the code it may be considered a hack, but see
for yourself!

The main goal was to get the writebuffer working, which is also a big part
of the NAND portion of the code, that was out of focus and needs to be
implemented by s.o. else who has got such a flash device.

There are still some aspects that need optimzation and solid testing,
especially the garbage collection. There were some issues described in the
.cdl file with icache locking that I did not understand yet.

Freescale specific files can be obtained from this bugzilla entry (if you
have this hardware):
https://bugzilla.ecoscentric.com/show_bug.cgi?id=1000761

The updated file system is provided in a zip package. Please let me know how
to add this to the project cleanly. I am not used to mailing lists yet.

https://docs.google.com/file/d/0Bw6cJNSOahkWVngzRmRnOThyTDg/edit?usp=sharing

Best regards
Max Seidenstuecker



--
View this message in context: http://sourceware-org.1504.n7.nabble.com/JFFS2-updated-to-support-writebuffer-tp241667.html
Sent from the Sourceware - ecos-patches mailing list archive at Nabble.com.

                 reply	other threads:[~2013-08-21  8:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1377074068386-241667.post@n7.nabble.com \
    --to=naturally-aligned@web.de \
    --cc=ecos-patches@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).