From: "Richard Purdie" <rpurdie@rpsys.net>
To: <linux-mtd@lists.infradead.org>
Subject: Sharp SL Series NAND Driver
Date: Fri, 12 Nov 2004 17:38:54 -0000 [thread overview]
Message-ID: <010b01c4c8de$82cc2b90$0f01a8c0@max> (raw)
As mentioned on IRC, I've ported the nand driver for the Sharp SL series to
the current kernel. This first patch adds the driver which supports all the
Zaurus models that use nand flash. (thanks for the pointers in trimming it
down! :)
http://www.rpsys.net/openzaurus/mtd/rp-mtd-sharpsl.patch
I also have some other patches I'd appreciate your views on. Two of these
should be straightforward. The third is more for comments.
http://www.rpsys.net/openzaurus/mtd/rp-mtd-sharpsl-map.patch - maps a ROM on
the device (I think its used to access configuration information?).
http://www.rpsys.net/openzaurus/mtd/rp-jffs2-longfilename.patch - if you try
and create filenames longer than 255 characters, the fs gets corrupted. This
adds a couple of checks to prevent it.
http://www.rpsys.net/openzaurus/mtd/rp-mtd-sharpsl-extra.patch - This is for
comments. The sharp driver uses a smaller eraseblock than the current mtd
code supports so I have to disable a check to get the code to work properly.
I think this is due to a limitation on kmalloc? The code gets around this by
using dma_alloc_coherent. Is there a way I can do this in an acceptable
manner? (I'm assuming the above patch isn't acceptable?)
(NB: The filesystem is written out by an older driver we can't change so we
have to remain compatible with it - changing eraseblock size therefore isn't
an option).
Thanks,
Richard
next reply other threads:[~2004-11-12 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-12 17:38 Richard Purdie [this message]
2004-11-12 22:17 ` Sharp SL Series NAND Driver John Lenz
2004-11-12 22:54 ` Richard Purdie
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='010b01c4c8de$82cc2b90$0f01a8c0@max' \
--to=rpurdie@rpsys.net \
--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