public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Ben Dooks <ben-mtd@fluff.org>
To: Russ Dill <russ.dill@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: FPGA NAND Interface tips
Date: Fri, 24 Feb 2006 11:24:25 +0000	[thread overview]
Message-ID: <20060224112425.GA25880@home.fluff.org> (raw)
In-Reply-To: <f9d2a5e10602232107y57accef1r3420d9b903d9cf4c@mail.gmail.com>

On Thu, Feb 23, 2006 at 10:07:36PM -0700, Russ Dill wrote:
> I'm providing some input on the NAND wire up, and FPGA design on a new
> board (80200 + FPGA).  I'm currently using rtc_from4.c and s3c2410.c
> as examples.
> 
> So I'm thinking the following for a basic setup:
> 
> reed solomon encoder
> Bit in the FPGA to reset the reed solomon encoder
> place in the FPGA to read out rs codes from last written/read block
> CLE/ALE as address lines
> Read/Busy connected as gpio/interrupt (multiple chips connect to multiple lines)

these sound like good ideas.
 
> Also, when writing/reading to a single address, the 80200 will not
> burst, and round trip time is horrid, especially when talking to IO
> devices. Would a FIFO with a 32 byte interface be a good solution to
> this? maybe with 16 entries (512 bytes)? I realize that DMA would be
> more ideal, but a fifo seems like it might be simplier.

you might also think about a way of writing cmd+addr in one go, or
at-least the address cycles.
 
> Does anyone have any paticular pet peeves when dealing with their NAND
> interface?
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

-- 
Ben (ben@fluff.org, http://www.fluff.org/)

  'a smiley only costs 4 bytes'

  parent reply	other threads:[~2006-02-24 11:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24  5:07 FPGA NAND Interface tips Russ Dill
2006-02-24  6:26 ` Russ Dill
2006-02-24 11:24 ` Ben Dooks [this message]
2006-02-24 18:01   ` Russ Dill

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=20060224112425.GA25880@home.fluff.org \
    --to=ben-mtd@fluff.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=russ.dill@gmail.com \
    /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