From: Junio C Hamano <junkio@twinsun.com>
To: linux-mtd@lists.infradead.org
Subject: TX49 NAND supported?
Date: Thu, 11 Sep 2003 12:01:14 -0700 [thread overview]
Message-ID: <7vy8wvgnet.fsf@mae.twinsun.com> (raw)
Does anybody have a working tx4925 NAND driver that can be used
with the latest mtd from infradead CVS? I have located a copy
of tx4925ndfmc.c with 2002 timestamp by Toshiba Corporation
(GPLv2) but it appears to use an API incompatible with the
current one. Among other things, it seems to think that struct
nand_chip has fields like IO_ADDR, CTRL_ADDR, CLE, ALE, NCE,
ioread, iowrite, etc, and appears to predate the following
change in include/linux/mtd/nand.h:
* 10-29-2001 TG changed nand_chip structure to support
* hardwarespecific function for accessing
* control lines
next reply other threads:[~2003-09-11 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 19:01 Junio C Hamano [this message]
2003-09-12 11:02 ` TX49 NAND supported? David Woodhouse
2003-09-15 10:10 ` Alice Hennessy
2003-09-19 14:09 ` Alice Hennessy
-- strict thread matches above, loose matches on Subject: below --
2003-10-22 21:44 Alice Hennessy
2003-10-23 8:31 ` David Woodhouse
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=7vy8wvgnet.fsf@mae.twinsun.com \
--to=junkio@twinsun.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