All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] NAND access via custom interface
Date: Thu, 19 Oct 2006 19:56:23 +0200	[thread overview]
Message-ID: <200610191956.23962.sr@denx.de> (raw)
In-Reply-To: <8e75c3bb0610190556m7c42395cr7cb1d8a564fb59f@mail.gmail.com>

Hi Jack,

On Thursday 19 October 2006 14:56, Jack Hab wrote:
> I'm porting U-Boot to our hardware based on Virtex-II FGPA. We have NAND
> device which cannot be accessed directly but only via our interface which
> takes care of all the control lines and sends the address/command/data
> bytes automatically.

So you have a NAND flash controller on your board, right?

> I understand, low-level macros like NAND_CLRCLE can be skipped.
>
> Will it be OK if I implemet only NAND_WAIT_READY, WRITE_NAND_xxx and
> READ_NAND macros? Or anything else is required.

Seems you are looking at the "old" legacy NAND driver which should _not_ be 
used anymore. Please use the "new" NAND driver which makes it also quite easy 
to support NAND flash controllers. As an example implementation please take a 
look at the cpu/ppc4xx/ndfc.c driver. It's used in the AMCC "sequoia" 
(440EPx) board. Another boardspecific example is the 
board/prodrive/pdnb3/nand.c driver used by the pdnb3 board.

Best regards,
Stefan

  reply	other threads:[~2006-10-19 17:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-19 12:56 [U-Boot-Users] NAND access via custom interface Jack Hab
2006-10-19 17:56 ` Stefan Roese [this message]
     [not found] ` <8e75c3bb0610220729q17e49eb5j335e84dbe1b13b13@mail.gmail.com>
     [not found]   ` <8e75c3bb0610230443u644d02f1w2bd781d5b13f0c4@mail.gmail.com>
     [not found]     ` <200610231356.09870.sr@denx.de>
2006-10-23 12:12       ` Jack Hab
2006-10-23 12:56         ` Stefan Roese

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=200610191956.23962.sr@denx.de \
    --to=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    /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.