From: Huang Shijie <b32955@freescale.com>
To: <dedekind1@gmail.com>
Cc: linux-mtd@lists.infradead.org,
Matthieu CASTET <matthieu.castet@parrot.com>
Subject: Re: [PATCH] mtd nand : print flash size during detection
Date: Fri, 16 Nov 2012 16:38:17 +0800 [thread overview]
Message-ID: <50A5FB79.3030305@freescale.com> (raw)
In-Reply-To: <1353054248.3618.3.camel@sauron.fi.intel.com>
于 2012年11月16日 16:24, Artem Bityutskiy 写道:
> On Tue, 2012-11-06 at 12:03 +0100, Matthieu CASTET wrote:
>> This help to detect bad flash identification in case the size is not present
>> on the name (ONFI).
>>
>> Signed-off-by: Matthieu CASTET<matthieu.castet@parrot.com>
>> ---
>> drivers/mtd/nand/nand_base.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/mtd/nand/nand_base.c b/drivers/mtd/nand/nand_base.c
>> index c90ef66..8916bc6 100644
>> --- a/drivers/mtd/nand/nand_base.c
>> +++ b/drivers/mtd/nand/nand_base.c
>> @@ -3292,10 +3292,10 @@ ident_done:
>> chip->cmdfunc = nand_command_lp;
>>
>> pr_info("NAND device: Manufacturer ID: 0x%02x, Chip ID: 0x%02x (%s %s),"
>> - " page size: %d, OOB size: %d\n",
>> + " %dMiB page size: %d, OOB size: %d\n",
> Is this readable? No comma after the size. I guess it is better to add
> "size %dMiB," instead?
>
In multi chip enables nand chips, such as some Micron nand chips, you
will find half size is printed
after this patch is applied. Why? because we only scan one #CE, but this
nand chip has two #CE, the #CE0 and #CE1.
a little confused.
Best Regards
Huang Shijie
next prev parent reply other threads:[~2012-11-16 8:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 11:03 [PATCH] mtd nand : print flash size during detection Matthieu CASTET
2012-11-07 6:22 ` Huang Shijie
2012-11-22 17:19 ` Matthieu CASTET
2012-11-16 8:24 ` Artem Bityutskiy
2012-11-16 8:38 ` Huang Shijie [this message]
2012-11-22 17:36 ` Matthieu CASTET
2012-11-22 17:20 ` 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=50A5FB79.3030305@freescale.com \
--to=b32955@freescale.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=matthieu.castet@parrot.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;
as well as URLs for NNTP newsgroup(s).