Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Chuanxiao.Dong" <chuanxiao.dong@intel.com>
Cc: Jason Roberts <jason.e.roberts@intel.com>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH v2 2/6]nand/denali: Add bad block management for MRST
Date: Thu, 12 Aug 2010 12:14:28 +0100	[thread overview]
Message-ID: <1281611668.12475.67.camel@localhost> (raw)
In-Reply-To: <20100812105117.GB11634@intel.com>

On Thu, 2010-08-12 at 18:51 +0800, Chuanxiao.Dong wrote:
> 
> +choice
> +       prompt "Compile for"
> +       depends on MTD_NAND_DENALI
> +       default MRST_NAND_CONTROLLER
> +
> +config MRST_NAND_CONTROLLER
> +       bool "MRST NAND controller"
> +       help
> +
> +config CE4100_NAND_CONTROLLER
> +       bool "CE4100 NAND controller"
> +       help
> +
> +endchoice 


Hm, I don't like this much -- we ought to be able to compile a generic
kernel which will support *both* MRST and CE4100. 

(Actually, we *can* -- you don't use these options anywhere (yet?)
except as a gateway to letting us set the BBT_BLOCKNUM value.

It may also be worth switching CE4100 to use the same BBT scheme as
you're using in MRST -- don't all the same arguments apply there?

I'm guessing that you didn't change CE4100 just because you want to
retain on-medium compatibility? Let's ask Jason -- I suspect it would be
OK to change...

I'm also somewhat dubious about the way we abandon the BBT when we're
going to use Spectra -- and especially the use of the scratch register.
Can't we put that information into PCI config space if we really must
have it? I'll look over that in more detail...


-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@intel.com                              Intel Corporation

  reply	other threads:[~2010-08-12 11:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-12 10:51 [PATCH v2 2/6]nand/denali: Add bad block management for MRST Chuanxiao.Dong
2010-08-12 11:14 ` David Woodhouse [this message]
2010-08-12 11:40   ` Dong, Chuanxiao
2010-08-20  7:49   ` Dong, Chuanxiao

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=1281611668.12475.67.camel@localhost \
    --to=dwmw2@infradead.org \
    --cc=chuanxiao.dong@intel.com \
    --cc=jason.e.roberts@intel.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