From: Matthew Reimer <mreimer@vpop.net>
To: Joshua Wise <joshua@joshuawise.com>
Cc: linux-mtd@lists.infradead.org,
h2200-port mailing list <h2200-port@handhelds.org>,
Kernel-discuss@handhelds.org
Subject: Re: [H2200-port] HAMCOP NAND driver
Date: Thu, 26 Aug 2004 14:57:44 -0700 [thread overview]
Message-ID: <412E5CD8.5020706@vpop.net> (raw)
In-Reply-To: <412E5AFC.5050000@joshuawise.com>
Hi Joshua.
Joshua Wise wrote:
> Hi folks,
>
> Is there any reason why HAMCOP NAND driver is not in the MTD directory
> and MTD CVS as all the other NAND drivers are?
I can't recall exactly, but I probably put it there because it seemed
like it ought to live with the rest of its SoC brethren, or it was
easier. I think my first version did live in with mtd. It doesn't matter
to me where it lives. Where does its cousin S3C2410 NAND driver live?
> Also, what is the status of that driver? A quick flip through seems to
> show that it's only got support for read-in commands, although I'm not
> too familiar with the HAMCOP's NAND architecture. If it's only got
> read support, is someone already working on write? (If not, I will
> volunteer to do that... don't want to duplicate work, though.)
Write support is there, but I haven't had the courage to try it out. :-)
There is a write_enable module_param for shamcop_nand, which if set to 1
would theoretically allow writes (which amounts to just setting the
write enable bit).
Now that you're all set up with JTAG, you seem like the best person to
try it out. :-)
Matt
next prev parent reply other threads:[~2004-08-26 21:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 21:49 HAMCOP NAND driver Joshua Wise
2004-08-26 21:57 ` Matthew Reimer [this message]
2004-08-26 21:59 ` [H2200-port] " Ben Dooks
2004-08-26 22:03 ` Matthew Reimer
2004-08-26 22:23 ` Joshua Wise
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=412E5CD8.5020706@vpop.net \
--to=mreimer@vpop.net \
--cc=Kernel-discuss@handhelds.org \
--cc=h2200-port@handhelds.org \
--cc=joshua@joshuawise.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