From: Russ Dill <Russ.Dill@asu.edu>
To: jasmine@regolith.co.uk
Cc: linux-mtd@lists.infradead.org
Cc: Charles Manning <manningc2@actrix.gen.nz>
Cc: David Woodhouse <dwmw2@infradead.org>
Subject: Re: nand flash driver
Date: 10 Jul 2003 09:50:38 -0700 [thread overview]
Message-ID: <1057855838.2659.333.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.53.0307101611170.844@hex.linuxgrrls.org>
On Thu, 2003-07-10 at 08:12, jasmine@regolith.co.uk wrote:
> On Thu, 10 Jul 2003, David Woodhouse wrote:
>
> > Hmmm. When sending multiple bytes of address, isn't ALE supposed to
> > remain high for the entire duration, without going low again between
> > cycles? How do you achieve this if it's on the address bus?
>
> By waiting to see if the next write is to the same address- it's not hard
> to do that sort of thing in an FPGA or SoC. Since the only line involved
> is the ALE to the NAND, there's no downside in hanging on a little longer
> before dropping it.
yup, and a CPLD only costs about $1 (32 io, 32 mc) or $2.65 for a
72io/72 mc. Makes this sort of thing pretty trivial, although for 2 or 3
signals, discrete logic will do just fine.
--
Russ Dill <Russ.Dill@asu.edu>
next prev parent reply other threads:[~2003-07-10 16:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-07 2:33 nand flash driver gjx
2003-07-08 23:21 ` Charles Manning
2003-07-10 13:05 ` jasmine
2003-07-10 14:20 ` David Woodhouse
2003-07-10 15:12 ` jasmine
2003-07-10 15:32 ` David Woodhouse
2003-07-11 0:18 ` Thomas Gleixner
2003-07-11 7:33 ` Stephan Linke
2003-07-10 16:50 ` Russ Dill [this message]
2003-07-10 22:16 ` Charles Manning
2003-07-10 22:12 ` nand flash driver -> ALE etc Charles Manning
-- strict thread matches above, loose matches on Subject: below --
2009-08-05 19:40 Nand flash driver Spinelli, Claudio (Claudio)
2023-07-24 7:52 nand " momo aubin
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=1057855838.2659.333.camel@localhost \
--to=russ.dill@asu.edu \
--cc=jasmine@regolith.co.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 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.