From: Alice Hennessy <ahennessy@mvista.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: TX49 NAND supported?
Date: Mon, 15 Sep 2003 10:10:03 +0000 [thread overview]
Message-ID: <3F658FFB.AC66C0C9@mvista.com> (raw)
In-Reply-To: 1063364525.23778.423.camel@hades.cambridge.redhat.com
David Woodhouse wrote:
> On Thu, 2003-09-11 at 12:01 -0700, Junio C Hamano wrote:
> > 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.
>
> At the time I changed the API, I also updated every driver which had
> been submitted to me and put in my CVS tree.
>
> If there are drivers out there from people who couldn't be bothered to
> do that, they broke.
>
> Please complain to the author of the module in question and ask them why
> they didn't let me have a copy.
>
>
> dwmw2
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
I'm in the process of updated tx4925ndfmc.c and tx4938ndfmc.c now. I will
submit them
soon. One problem I'm trying to work around is I have had to set and
clear NAND_CTL_SETWP and
NAND_CTL_CLRWP around the writes. Since this isn't already in nand.c, it
seems to be
unique to these chips. I will investigate more to see if I really need to
do this or if I can
move this code into the mapping files.
Alice
next prev parent reply other threads:[~2003-09-15 17:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 19:01 TX49 NAND supported? Junio C Hamano
2003-09-12 11:02 ` David Woodhouse
2003-09-15 10:10 ` Alice Hennessy [this message]
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
2003-09-11 5:34 Junio C Hamano
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=3F658FFB.AC66C0C9@mvista.com \
--to=ahennessy@mvista.com \
--cc=dwmw2@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.