From: peter meng <mengsanshui@yahoo.com.cn>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Question relates 2K page size flash chip
Date: Wed, 7 Jan 2009 10:47:46 +0800 (CST) [thread overview]
Message-ID: <696227.81552.qm@web15701.mail.cnb.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0901050852060.31730@lnxricardw.se.axis.com>
Hi,Ricard
Thanks a lot.
Because linux deem all block is bad block when scan flash .
I debug it that found need u-boot add OOB information into flash .
Best Regards.
Peter Meng
--- On Mon, 1/5/09, Ricard Wanderlof <ricard.wanderlof@axis.com> wrote:
> From: Ricard Wanderlof <ricard.wanderlof@axis.com>
> Subject: Re: Question relates 2K page size flash chip
> To: "peter meng" <mengsanshui@yahoo.com.cn>
> Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
> Date: Monday, January 5, 2009, 3:52 PM
> On Sat, 3 Jan 2009, peter meng wrote:
>
> > I met a problem that use K9F1G08 flash with 2K page
> size on Linux .
> > I tried jffs2 and yaffs2 file system but occurs same
> error info as following
> >
> > NAND device: Manufacturer ID: 0xec, Chip ID: 0xa1
> (Samsung NAND 128MiB 1,8V 8-bit)
> > ...
> > Seems this problem is caused since 2K page size with
> flash ,so how to resolve this problem ? Whether need do
> related work within u-boot because I suppose u-boot given
> wrong data format to flash that Linux mtd does not know it ?
>
> Why do you think it is related to the 2k page size? This
> type of flash has been supported by mtd for a very long time
> now.
>
> /Ricard
> --
> Ricard Wolf Wanderlöf
> ricardw(at)axis.com
> Axis Communications AB, Lund, Sweden
> www.axis.com
> Phone +46 46 272 2016 Fax +46 46
> 13 61 30
prev parent reply other threads:[~2009-01-07 2:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 9:15 Question relates 2K page size flash chip peter meng
2009-01-05 7:52 ` Ricard Wanderlof
2009-01-07 2:47 ` peter meng [this message]
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=696227.81552.qm@web15701.mail.cnb.yahoo.com \
--to=mengsanshui@yahoo.com.cn \
--cc=linux-mtd@lists.infradead.org \
--cc=ricard.wanderlof@axis.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