From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Nitin Garg <nitingarg98@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
David Woodhouse <dwmw2@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Bug in MTD NAND ONFI chipsize detection
Date: Thu, 12 May 2011 09:47:24 +0200 [thread overview]
Message-ID: <4DCB908C.80505@parrot.com> (raw)
In-Reply-To: <BANLkTin5X7d+_b5+7N5g941bz12jc+zMZA@mail.gmail.com>
Hi,
What's the difference between one lun and multiple lun for mtd ?
Aren't any command to select the current lun ?
Matthieu
Nitin Garg a écrit :
> Why isn't my patch going through? re-sending again,
>
> Signed-off-by: Nitin Garg <nitingarg98@xxxxxxxx>
> ---
> drivers/mtd/nand/nand_base.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/mtd/nand/nand_base.c b/drivers/mtd/nand/nand_base.c
> index c54a4cb..cdf6015 100644
> --- a/drivers/mtd/nand/nand_base.c
> +++ b/drivers/mtd/nand/nand_base.c
> @@ -2892,7 +2892,7 @@ static int nand_flash_detect_onfi(struct
> mtd_info *mtd, struct nand_chip *chip,
> mtd->writesize = le32_to_cpu(p->byte_per_page);
> mtd->erasesize = le32_to_cpu(p->pages_per_block) * mtd->writesize;
> mtd->oobsize = le16_to_cpu(p->spare_bytes_per_page);
> - chip->chipsize = (uint64_t)le32_to_cpu(p->blocks_per_lun) * mtd->erasesize;
> + chip->chipsize = (uint64_t)le32_to_cpu(p->blocks_per_lun) *
> le32_to_cpu(p->lun_count) * mtd->erasesize;
> busw = 0;
> if (le16_to_cpu(p->features) & 1)
> busw = NAND_BUSWIDTH_16;
next prev parent reply other threads:[~2011-05-12 7:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 16:25 Bug in MTD NAND ONFI chipsize detection Nitin Garg
2011-05-12 1:33 ` Andrew Morton
2011-05-12 6:54 ` Nitin Garg
2011-05-12 7:05 ` Nitin Garg
2011-05-12 7:16 ` Nitin Garg
2011-05-12 7:47 ` Matthieu CASTET [this message]
2011-05-12 12:34 ` Nitin Garg
2011-05-12 13:53 ` Artem Bityutskiy
2011-05-12 13:53 ` Artem Bityutskiy
2011-05-12 15:19 ` Nitin Garg
2011-05-12 15:39 ` 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=4DCB908C.80505@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nitingarg98@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