From: Thomas Gleixner <gleixner@autronix.de>
To: Jason Chan <jason@emsoftltd.com>,
"'linux-arm-kernel@lists.arm.linux.org.uk'"
<linux-arm-kernel@lists.arm.linux.org.uk>,
linux-mtd@lists.infradead.org
Subject: Re: Need Some help to write NandFlash Driver
Date: Sun, 9 Jun 2002 15:24:32 +0200 [thread overview]
Message-ID: <200206091324.g59DOW901667@thomas.tec.autronix.de> (raw)
In-Reply-To: <3CFECA68.6060709@emsoftltd.com>
On Thursday, 6. June 2002 04:35, Jason Chan wrote:
> Dear all,
> I am currently implementing Samsung Nand-Flash Driver for edb7312 block on
> 2.4.18 kernel. I am seeking for suggestion on which method should be used
> to improve my nandflash driver.
There is a working nand flash driver for edb7312 in mtd CVS.
JFFS2 support is working
--
Thomas
___________________________________
autronix automation GmbH
http://www.autronix.de gleixner@autronix.de
prev parent reply other threads:[~2002-06-09 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 2:35 Need Some help to write NandFlash Driver Jason Chan
2002-06-09 13:24 ` Thomas Gleixner [this message]
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=200206091324.g59DOW901667@thomas.tec.autronix.de \
--to=gleixner@autronix.de \
--cc=jason@emsoftltd.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--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