linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sean MacLennan <smaclennan@pikatech.com>
To: "Josh Boyer" <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] ndfc driver
Date: Mon, 8 Dec 2008 19:51:24 -0500	[thread overview]
Message-ID: <20081208195124.14988307@lappy.seanm.ca> (raw)
In-Reply-To: <20081204090107.20269571@zod.rchland.ibm.com>

On Thu, 4 Dec 2008 09:01:07 -0500
"Josh Boyer" <jwboyer@linux.vnet.ibm.com> wrote:

> You also seem to only support a single NAND chip, however the NDFC can
> support multiple chips.  Have you looked at how the the fsl_elbc_nand
> driver does multiple chip support?  If not, could you at least
> document the limitation in the patch?

Signed-off-by: Sean MacLennan <smaclennan@pikatech.com>
---
diff --git a/drivers/mtd/nand/ndfc.c b/drivers/mtd/nand/ndfc.c
index 0352d5c..3dd85e8 100644
--- a/drivers/mtd/nand/ndfc.c
+++ b/drivers/mtd/nand/ndfc.c
@@ -2,11 +2,15 @@
  *  drivers/mtd/ndfc.c
  *
  *  Overview:
- *   Platform independend driver for NDFC (NanD Flash Controller)
+ *   Platform independent driver for NDFC (NanD Flash Controller)
  *   integrated into EP440 cores
  *
  *   Ported to an OF platform driver by Sean MacLennan
  *
+ *   The NDFC supports multiple chips, but this driver only supports a
+ *   single chip since I do not have access to any boards with
+ *   multiple chips.
+ *
  *  Author: Thomas Gleixner
  *
  *  Copyright 2006 IBM

  parent reply	other threads:[~2008-12-09  0:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20081203222832.3fc77d28@lappy.seanm.ca>
2008-12-04 14:01 ` [PATCH] ndfc driver Josh Boyer
2008-12-04 17:17   ` Sean MacLennan
2008-12-09  0:34   ` Sean MacLennan
2008-12-09  2:11     ` Anton Vorontsov
2008-12-09  2:45       ` Sean MacLennan
2008-12-09  3:32         ` Josh Boyer
2008-12-09  4:54           ` Sean MacLennan
2008-12-09  7:57             ` Mitch Bradley
2008-12-10  4:01               ` Sean MacLennan
2008-12-10  8:28                 ` Mitch Bradley
2008-12-09  6:10     ` Stefan Roese
2008-12-09 11:24       ` Josh Boyer
2008-12-10 23:16       ` Sean MacLennan
2008-12-17  4:14         ` Sean MacLennan
2008-12-17 11:34           ` Josh Boyer
2008-12-17 13:26         ` Josh Boyer
2008-12-09  0:51   ` Sean MacLennan [this message]
     [not found] <9293074.419171225391386417.JavaMail.nabble@isper.nabble.com>
     [not found] ` <20081030195858.28900ee5@lappy.seanm.ca>
     [not found]   ` <490D68A8.4060905@embedded-sol.com>
     [not found]     ` <20081102124804.15003002@lappy.seanm.ca>
     [not found]       ` <490E02D7.5050402@embedded-sol.com>
     [not found]         ` <20081102145811.6da10ef4@lappy.seanm.ca>
     [not found]           ` <490E074F.5050909@embedded-sol.com>
     [not found]             ` <20081102152958.42e88283@lappy.seanm.ca>
     [not found]               ` <490E4D0D.9060207@embedded-sol.com>
     [not found]                 ` <20081102204510.3d8e71f2@lappy.seanm.ca>
2008-11-03 10:56                   ` Felix Radensky
2008-10-30  6:08 Sean MacLennan

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=20081208195124.14988307@lappy.seanm.ca \
    --to=smaclennan@pikatech.com \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).