public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Ben Dooks <ben@fluff.org>
To: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] S3C24XX large page NAND support
Date: Mon, 23 Jul 2007 14:46:17 +0100	[thread overview]
Message-ID: <20070723134617.GA19071@fluff.org.uk> (raw)
In-Reply-To: <4695FC93.7040800@parrot.com>

On Thu, Jul 12, 2007 at 12:04:03PM +0200, Matthieu CASTET wrote:
> Ben Dooks wrote:
> > This adds support for using large page NAND devices
> > with the S3C24XX NAND controllers. This also adds the 
> > file Documentation/arm/Samsung-S3C24XX/NAND.txt to
> > describe the differences.
> > 
> > The basic stratergy is to maintain 3 bytes of ECC for
> > each 256 byte block read from the NAND which is similar
> > to the default kernel layout (altough we are using the
> > hardware ECC generator to make our ECC calculations).
> > 
> > Signed-off-by: Ben Dooks <ben-linux@fluff.org>
> > 

[snip]
> >  
> > -		nmtd->scan_res = nand_scan(&nmtd->mtd, (sets) ? sets->nr_chips : 1);
> > +		nmtd->scan_res = nand_scan_ident(&nmtd->mtd,
> > +						 (sets) ? sets->nr_chips : 1);
> >  
> >  		if (nmtd->scan_res == 0) {
> > +			s3c2410_nand_update_chip(info, nmtd);
> > +			nand_scan_tail(&nmtd->mtd);
> >  			s3c2410_nand_add_partition(info, nmtd, sets);
> >  		}
> Shouldn't nand_scan_ident and nand_scan_tail be used here ?

Sorry, do you mean that they should be used here (and they are
being used in this code) or do you mean that you do not think
that these two are to be used here?

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

  'a smiley only costs 4 bytes'

  reply	other threads:[~2007-07-23 13:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 23:11 [PATCH] S3C24XX large page NAND support Ben Dooks
2007-07-12 10:04 ` Matthieu CASTET
2007-07-23 13:46   ` Ben Dooks [this message]
2007-07-23 15:01     ` Matthieu CASTET

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=20070723134617.GA19071@fluff.org.uk \
    --to=ben@fluff.org \
    --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