From apgmoorthi@hotmail.com Thu Aug 21 10:17:13 2008 Received: from blu0-omc1-s4.blu0.hotmail.com ([65.55.116.15]) by stoneboat.aleph1.co.uk with esmtp (Exim 4.63) (envelope-from ) id 1KW6Hn-0001fB-W9 for yaffs@lists.aleph1.co.uk; Thu, 21 Aug 2008 10:17:13 +0100 Received: from BLU149-W9 ([65.55.116.9]) by blu0-omc1-s4.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 21 Aug 2008 02:16:49 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_bcad3f33-f265-48ac-afd0-dbdab41ad960_" X-Originating-IP: [203.78.214.150] From: Gangheya moorthy To: Date: Thu, 21 Aug 2008 14:46:50 +0530 Importance: Normal In-Reply-To: References: MIME-Version: 1.0 X-OriginalArrivalTime: 21 Aug 2008 09:16:49.0757 (UTC) FILETIME=[A47AD8D0:01C9036E] X-SA-Exim-Connect-IP: 65.55.116.15 X-SA-Exim-Mail-From: apgmoorthi@hotmail.com X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on stoneboat.aleph1.co.uk X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE, SPF_PASS autolearn=ham version=3.2.3 X-SA-Exim-Version: 4.2.1 (built Tue, 09 Jan 2007 17:23:22 +0000) X-SA-Exim-Scanned: Yes (on stoneboat.aleph1.co.uk) Subject: [Yaffs] Re : Re: Yaffs2 and MLC NAND with Block size 256K X-BeenThere: yaffs@lists.aleph1.co.uk X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of YAFFS NAND flash filesystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Aug 2008 09:17:13 -0000 --_bcad3f33-f265-48ac-afd0-dbdab41ad960_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Amol=2C =20 I have seen the latest Yaffs2 code =2C As you said =20 I guess =2C =20 dev->nChunksPerBlock =3D mtd->erasesize / mtd->writesize=3B =20 will override =20 dev->nChunksPerBlock =3D YAFFS_CHUNKS_PER_BLOCK =20 in YAFFS2. =20 =20 With Regards Moorthy =20 > From: yaffs-request@lists.aleph1.co.uk> Subject: yaffs Digest=2C Vol 39= =2C Issue 9> To: yaffs@lists.aleph1.co.uk> Date: Tue=2C 19 Aug 2008 12:00:0= 7 +0100> > Send yaffs mailing list submissions to> yaffs@lists.aleph1.co.uk= > > To subscribe or unsubscribe via the World Wide Web=2C visit> http://lis= ts.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs> or=2C via email=2C send a m= essage with subject or body 'help' to> yaffs-request@lists.aleph1.co.uk> > = You can reach the person managing the list at> yaffs-owner@lists.aleph1.co.= uk> > When replying=2C please edit your Subject line so it is more specific= > than "Re: Contents of yaffs digest..."> > > Today's Topics:> > 1. yaffs_t= agscompat aliasing problem (James Kehl)> 2. Yaffs2 and MLC NAND with Block = size 256K (Amol Lad)> 3. Re: Yaffs2 and MLC NAND with Block size 256K (Jame= s Kehl)> 4. notification about data error during read (Evgeny Habinsky)> 5.= Can't open files under "/" (Evgeny Habinsky)> 6. Re: Yaffs2 and MLC NAND w= ith Block size 256K (Amol Lad)> > > ---------------------------------------= -------------------------------> > Message: 1> Date: Tue=2C 19 Aug 2008 16:= 11:11 +1000> From: "James Kehl" > Subject: [Yaffs] yaff= s_tagscompat aliasing problem> To: > Message-ID:>= > Content-Type:= text/plain=3B charset=3D"us-ascii"> > Hi all=2C> > The Yaffs1 tag ECC rout= ine runs into aliasing problems when I compile it> with ARM GCC (CodeSource= ry 2008q1-126)=2C and causes the check routine to> flip random bits. I atta= ch a fix (a slightly cleaner fix than> -fno-strict-aliasing!)> > There are = some other problems with the yaffs1 tag ECC: it can't cope> with a single b= it error in the ECC data itself (it either causes> miscorrections=2C or mak= es the check routine return -1)=2C and it only ever> uses 7 bits out of the= 12 provided for ECC. Yaffs2 probably doesn't have> these problems=2C and I= think Yaffs1 folk wouldn't want backwards> compatibility broken=2C so thes= e remain unfixed :)> > (This is unrelated to the problems I was seeing unde= r mingw=2C btw)> > James> -------------- next part --------------> A non-te= xt attachment was scrubbed...> Name: yaffs_tagscompat-aliasing.patch> Type:= application/octet-stream> Size: 826 bytes> Desc: yaffs_tagscompat-aliasing= .patch> Url : http://lists.aleph1.co.uk/lurker/list/yaffs.html/attachments/= 20080819/75d129ff/attachment.obj > > ------------------------------> > Mess= age: 2> Date: Tue=2C 19 Aug 2008 11:57:58 +0530> From: "Amol Lad" > Subject: [Yaffs] Yaffs2 and MLC NAND with Block size 256K> To:= yaffs@lists.aleph1.co.uk> Message-ID:> <8c675e9b0808182327g35cafc21k61b45f= 05b9f03901@mail.gmail.com>> Content-Type: text/plain=3B charset=3DISO-8859-= 1> > Hi=2C> > I'm using a year old snapshot of Yaffs2 cvs tree. I want to k= now if> there are any assumptions about the block size for 2K page NAND. Fo= r> example=2C Samsung K9F4G08U0A is SLC NAND with 2K page size and 128K> bl= ock size. Samsung K9G4G08U0A is MLC NAND with 2K page size and 256K> block = size (both have same device id - 0xDC)> > So=2C are there any assumptions a= bout block size for 2K page ? or 256K> block size will work as is..> > >Fro= m README-linux: "Block - Eraseable unit. 64 Pages. (128K on 2K> NAND=2C 32K= on 512b NAND)"> > Thanks> Amol> > > > ------------------------------> > Me= ssage: 3> Date: Tue=2C 19 Aug 2008 17:04:56 +1000> From: "James Kehl" > Subject: Re: [Yaffs] Yaffs2 and MLC NAND with Block size 2= 56K> To: "Amol Lad" =2C > Mes= sage-ID:> > Cont= ent-Type: text/plain=3B charset=3D"us-ascii"> > > -----Original Message----= -> > From: yaffs-bounces@lists.aleph1.co.uk [mailto:yaffs-> > bounces@lists= .aleph1.co.uk] On Behalf Of Amol Lad> > Sent: Tuesday=2C 19 August 2008 4:2= 8 PM> > To: yaffs@lists.aleph1.co.uk> > Subject: [Yaffs] Yaffs2 and MLC NAN= D with Block size 256K> > > > Hi=2C> > > > I'm using a year old snapshot of= Yaffs2 cvs tree. I want to know if> > there are any assumptions about the = block size for 2K page NAND. For> > example=2C Samsung K9F4G08U0A is SLC NA= ND with 2K page size and 128K> > block size. Samsung K9G4G08U0A is MLC NAND= with 2K page size and 256K> > block size (both have same device id - 0xDC)= > > > > So=2C are there any assumptions about block size for 2K page ? or 2= 56K> > block size will work as is..> > > > The define YAFFS_CHUNKS_PER_BLOC= K (from yaffs_guts.h) might be what> you're looking for. That=2C or dev->nC= hunksPerBlock if you're using> Yaffs-Direct.> > If you've got no way of kno= wing whether it's a 128K block size or a 256K> block size=2C then you might= be best off telling Yaffs to use a 256K block> size=2C and tweaking your N= AND driver to send two erase commands (so 128K> NAND will behave like 256K = NAND).> > James> > > > > ------------------------------> > Message: 4> Date= : Tue=2C 19 Aug 2008 10:59:11 +0300> From: "Evgeny Habinsky" > Subject: [Yaffs] notification about data error during read> To: <= yaffs@lists.aleph1.co.uk>> Message-ID:> <17E66600668C05419793F4C955966EF554= 25EA@everest_n.Surfdom.dom>> Content-Type: text/plain=3B charset=3D"us-asci= i"> > Hi!> > I use YAFFS via direct interface.> > When YAFFS encounters unr= ecoverable ECC error during file read it> retires the block but the applica= tion gets no notification from the file> system that the file data is corru= pted (except for printed error> message).> > One could pass such notificati= on via global variable from directly from> yaffs_ReadChunkFromNAND() to app= lication. I'd like to know how do you> deal with this problem or think it s= hould be dealt with.> > Thanks.> -------------- next part --------------> A= n HTML attachment was scrubbed...> URL: http://lists.aleph1.co.uk/lurker/li= st/yaffs.html/attachments/20080819/62f0de4f/attachment.htm > > ------------= ------------------> > Message: 5> Date: Tue=2C 19 Aug 2008 11:00:54 +0300> = From: "Evgeny Habinsky" > Subject: [Yaffs] Can't open= files under "/"> To: > Message-ID:> <17E66600668= C05419793F4C955966EF55425EB@everest_n.Surfdom.dom>> Content-Type: text/plai= n=3B charset=3D"us-ascii"> > I found that after upgrading to the latest ver= sion of YAFFS I'm no> longer able to create files in root directory. My fla= sh is mounted as> "/" and it seems like yaffsfs_FindDevice() does not allow= to open files> directly under "/".> > I am trying to open /testfile for wr= iting. Before matching the file> prefix to YAFFS device prefix yaffsfs_Find= Device() strips leading> slashes from both file name and the device prefix.= This means it will> try to match "testfile" to "\0" which fails. > > Was t= his change introduced intentionally to prevent mounting under root?> > Rega= rds> Evgeny Habinsky> > > > ------------------------------> > Message: 6> D= ate: Tue=2C 19 Aug 2008 14:03:33 +0530> From: "Amol Lad" > Subject: Re: [Yaffs] Yaffs2 and MLC NAND with Block size 256K> To: "Jam= es Kehl" > Cc: yaffs@lists.aleph1.co.uk> Message-ID:> <= 8c675e9b0808190133o2fa8ca1dw9b79294463faf33d@mail.gmail.com>> Content-Type:= text/plain=3B charset=3DISO-8859-1> > >> So=2C are there any assumptions a= bout block size for 2K page ? or 256K> >> block size will work as is..> >>>= >> > The define YAFFS_CHUNKS_PER_BLOCK (from yaffs_guts.h) might be what> = > you're looking for. That=2C or dev->nChunksPerBlock if you're using> > Ya= ffs-Direct.> >> > If you've got no way of knowing whether it's a 128K block= size or a 256K> > block size=2C then you might be best off telling Yaffs t= o use a 256K block> > size=2C and tweaking your NAND driver to send two era= se commands (so 128K> > NAND will behave like 256K NAND).> > It seems for y= affs2=2C these parameters are not set using #defines but> from mtd. Please = see below snippet.> > yaffs_fs.c:> > if (yaffsVersion =3D=3D 2) {> ....> ..= ..> #if (LINUX_VERSION_CODE > KERNEL_VERSION(2=2C6=2C17))> dev->nDataBytesP= erChunk =3D mtd->writesize=3B> dev->nChunksPerBlock =3D mtd->erasesize / mt= d->writesize=3B> #else> dev->nDataBytesPerChunk =3D mtd->oobblock=3B> dev->= nChunksPerBlock =3D mtd->erasesize / mtd->oobblock=3B> #endif> nBlocks =3D = mtd->size / mtd->erasesize=3B> > dev->startBlock =3D 0=3B> dev->endBlock = =3D nBlocks - 1=3B> > So are above the only parameters ? or some other plac= e also I need to verify.> > >> > James> > Thanks> Amol> > > > -------------= -----------------> > _______________________________________________> yaffs= mailing list> yaffs@lists.aleph1.co.uk> http://lists.aleph1.co.uk/cgi-bin/= mailman/listinfo/yaffs> > > End of yaffs Digest=2C Vol 39=2C Issue 9> *****= ******************************* _________________________________________________________________ Searching for the best deals on travel? Visit MSN Travel. http://msn.coxandkings.co.in/cnk/cnk.do= --_bcad3f33-f265-48ac-afd0-dbdab41ad960_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Amol=2C
 =3B
 =3BI have seen the latest Yaffs2 code =3B = =2C As you said
 =3B
 =3BI guess =2C
 =3B
 =3B dev->=3BnChunksPerBlock= =3D mtd->=3Berasesize / mtd->=3Bwritesize=3B

 =3B

 =3B&n= bsp=3B =3B =3B =3B =3B =3B =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B will&nb= sp=3B override

 =3B&n= bsp=3B

 =3B&n= bsp=3B dev->=3BnChunksPerBlock =3D YAFFS_CHUNKS_PER_BLOCK

 =3B
 =3Bin YAFFS2.
 =3B
 =3B
With Regards
 =3B =3BMoorthy
 =3B
 =3B

>=3B From: yaffs-request@lists.aleph1.co.uk
>=3B Sub= ject: yaffs Digest=2C Vol 39=2C Issue 9
>=3B To: yaffs@lists.aleph1.co= .uk
>=3B Date: Tue=2C 19 Aug 2008 12:00:07 +0100
>=3B
>=3B = Send yaffs mailing list submissions to
>=3B yaffs@lists.aleph1.co.uk>=3B
>=3B To subscribe or unsubscribe via the World Wide Web=2C v= isit
>=3B http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs
= >=3B or=2C via email=2C send a message with subject or body 'help' to
= >=3B yaffs-request@lists.aleph1.co.uk
>=3B
>=3B You can reach = the person managing the list at
>=3B yaffs-owner@lists.aleph1.co.uk>=3B
>=3B When replying=2C please edit your Subject line so it is = more specific
>=3B than "Re: Contents of yaffs digest..."
>=3B >=3B
>=3B Today's Topics:
>=3B
>=3B 1. yaffs_tagscompa= t aliasing problem (James Kehl)
>=3B 2. Yaffs2 and MLC NAND with Block= size 256K (Amol Lad)
>=3B 3. Re: Yaffs2 and MLC NAND with Block size = 256K (James Kehl)
>=3B 4. notification about data error during read (E= vgeny Habinsky)
>=3B 5. Can't open files under "/" (Evgeny Habinsky)>=3B 6. Re: Yaffs2 and MLC NAND with Block size 256K (Amol Lad)
>= =3B
>=3B
>=3B -------------------------------------------------= ---------------------
>=3B
>=3B Message: 1
>=3B Date: Tue= =2C 19 Aug 2008 16:11:11 +1000
>=3B From: "James Kehl" <=3Bjamesk@ed= mi.com.au>=3B
>=3B Subject: [Yaffs] yaffs_tagscompat aliasing proble= m
>=3B To: <=3Byaffs@lists.aleph1.co.uk>=3B
>=3B Message-ID:<= BR>>=3B <=3BDA07ABAEC04C914DB72E4885251CCF8AB474A2@MERCURY.edmi.local&g= t=3B
>=3B Content-Type: text/plain=3B charset=3D"us-ascii"
>=3B <= BR>>=3B Hi all=2C
>=3B
>=3B The Yaffs1 tag ECC routine runs in= to aliasing problems when I compile it
>=3B with ARM GCC (CodeSourcery= 2008q1-126)=2C and causes the check routine to
>=3B flip random bits.= I attach a fix (a slightly cleaner fix than
>=3B -fno-strict-aliasing= !)
>=3B
>=3B There are some other problems with the yaffs1 tag E= CC: it can't cope
>=3B with a single bit error in the ECC data itself = (it either causes
>=3B miscorrections=2C or makes the check routine re= turn -1)=2C and it only ever
>=3B uses 7 bits out of the 12 provided f= or ECC. Yaffs2 probably doesn't have
>=3B these problems=2C and I thin= k Yaffs1 folk wouldn't want backwards
>=3B compatibility broken=2C so = these remain unfixed :)
>=3B
>=3B (This is unrelated to the prob= lems I was seeing under mingw=2C btw)
>=3B
>=3B James
>=3B = -------------- next part --------------
>=3B A non-text attachment was= scrubbed...
>=3B Name: yaffs_tagscompat-aliasing.patch
>=3B Type= : application/octet-stream
>=3B Size: 826 bytes
>=3B Desc: yaffs_= tagscompat-aliasing.patch
>=3B Url : http://lists.aleph1.co.uk/lurker/= list/yaffs.html/attachments/20080819/75d129ff/attachment.obj
>=3B >=3B ------------------------------
>=3B
>=3B Message: 2
&= gt=3B Date: Tue=2C 19 Aug 2008 11:57:58 +0530
>=3B From: "Amol Lad" &l= t=3Bamol.lad@gmail.com>=3B
>=3B Subject: [Yaffs] Yaffs2 and MLC NAND= with Block size 256K
>=3B To: yaffs@lists.aleph1.co.uk
>=3B Mess= age-ID:
>=3B <=3B8c675e9b0808182327g35cafc21k61b45f05b9f03901@mail.g= mail.com>=3B
>=3B Content-Type: text/plain=3B charset=3DISO-8859-1>=3B
>=3B Hi=2C
>=3B
>=3B I'm using a year old snapsho= t of Yaffs2 cvs tree. I want to know if
>=3B there are any assumptions= about the block size for 2K page NAND. For
>=3B example=2C Samsung K9= F4G08U0A is SLC NAND with 2K page size and 128K
>=3B block size. Samsu= ng K9G4G08U0A is MLC NAND with 2K page size and 256K
>=3B block size (= both have same device id - 0xDC)
>=3B
>=3B So=2C are there any a= ssumptions about block size for 2K page ? or 256K
>=3B block size will= work as is..
>=3B
>=3B >=3BFrom README-linux: "Block - Erasea= ble unit. 64 Pages. (128K on 2K
>=3B NAND=2C 32K on 512b NAND)"
>= =3B
>=3B Thanks
>=3B Amol
>=3B
>=3B
>=3B
&g= t=3B ------------------------------
>=3B
>=3B Message: 3
>= =3B Date: Tue=2C 19 Aug 2008 17:04:56 +1000
>=3B From: "James Kehl" &l= t=3Bjamesk@edmi.com.au>=3B
>=3B Subject: Re: [Yaffs] Yaffs2 and MLC = NAND with Block size 256K
>=3B To: "Amol Lad" <=3Bamol.lad@gmail.com= >=3B=2C <=3Byaffs@lists.aleph1.co.uk>=3B
>=3B Message-ID:
>= =3B <=3BDA07ABAEC04C914DB72E4885251CCF8AB474C3@MERCURY.edmi.local>=3B>=3B Content-Type: text/plain=3B charset=3D"us-ascii"
>=3B
>= =3B >=3B -----Original Message-----
>=3B >=3B From: yaffs-bounces@= lists.aleph1.co.uk [mailto:yaffs-
>=3B >=3B bounces@lists.aleph1.co.= uk] On Behalf Of Amol Lad
>=3B >=3B Sent: Tuesday=2C 19 August 2008 = 4:28 PM
>=3B >=3B To: yaffs@lists.aleph1.co.uk
>=3B >=3B Subj= ect: [Yaffs] Yaffs2 and MLC NAND with Block size 256K
>=3B >=3B
= >=3B >=3B Hi=2C
>=3B >=3B
>=3B >=3B I'm using a year old= snapshot of Yaffs2 cvs tree. I want to know if
>=3B >=3B there are = any assumptions about the block size for 2K page NAND. For
>=3B >=3B= example=2C Samsung K9F4G08U0A is SLC NAND with 2K page size and 128K
&g= t=3B >=3B block size. Samsung K9G4G08U0A is MLC NAND with 2K page size an= d 256K
>=3B >=3B block size (both have same device id - 0xDC)
>= =3B >=3B
>=3B >=3B So=2C are there any assumptions about block si= ze for 2K page ? or 256K
>=3B >=3B block size will work as is..
&= gt=3B >=3B
>=3B
>=3B The define YAFFS_CHUNKS_PER_BLOCK (from = yaffs_guts.h) might be what
>=3B you're looking for. That=2C or dev-&g= t=3BnChunksPerBlock if you're using
>=3B Yaffs-Direct.
>=3B
&= gt=3B If you've got no way of knowing whether it's a 128K block size or a 2= 56K
>=3B block size=2C then you might be best off telling Yaffs to use= a 256K block
>=3B size=2C and tweaking your NAND driver to send two e= rase commands (so 128K
>=3B NAND will behave like 256K NAND).
>= =3B
>=3B James
>=3B
>=3B
>=3B
>=3B
>=3B = ------------------------------
>=3B
>=3B Message: 4
>=3B Da= te: Tue=2C 19 Aug 2008 10:59:11 +0300
>=3B From: "Evgeny Habinsky" <= =3Bevgenyh@Surf-com.com>=3B
>=3B Subject: [Yaffs] notification about= data error during read
>=3B To: <=3Byaffs@lists.aleph1.co.uk>=3B<= BR>>=3B Message-ID:
>=3B <=3B17E66600668C05419793F4C955966EF55425E= A@everest_n.Surfdom.dom>=3B
>=3B Content-Type: text/plain=3B charset= =3D"us-ascii"
>=3B
>=3B Hi!
>=3B
>=3B I use YAFFS via= direct interface.
>=3B
>=3B When YAFFS encounters unrecoverable= ECC error during file read it
>=3B retires the block but the applicat= ion gets no notification from the file
>=3B system that the file data = is corrupted (except for printed error
>=3B message).
>=3B
&g= t=3B One could pass such notification via global variable from directly fro= m
>=3B yaffs_ReadChunkFromNAND() to application. I'd like to know how = do you
>=3B deal with this problem or think it should be dealt with.>=3B
>=3B Thanks.
>=3B -------------- next part ------------= --
>=3B An HTML attachment was scrubbed...
>=3B URL: http://lists= .aleph1.co.uk/lurker/list/yaffs.html/attachments/20080819/62f0de4f/attachme= nt.htm
>=3B
>=3B ------------------------------
>=3B
&= gt=3B Message: 5
>=3B Date: Tue=2C 19 Aug 2008 11:00:54 +0300
>= =3B From: "Evgeny Habinsky" <=3Bevgenyh@Surf-com.com>=3B
>=3B Subj= ect: [Yaffs] Can't open files under "/"
>=3B To: <=3Byaffs@lists.ale= ph1.co.uk>=3B
>=3B Message-ID:
>=3B <=3B17E66600668C05419793F= 4C955966EF55425EB@everest_n.Surfdom.dom>=3B
>=3B Content-Type: text/= plain=3B charset=3D"us-ascii"
>=3B
>=3B I found that after upgra= ding to the latest version of YAFFS I'm no
>=3B longer able to create = files in root directory. My flash is mounted as
>=3B "/" and it seems = like yaffsfs_FindDevice() does not allow to open files
>=3B directly u= nder "/".
>=3B
>=3B I am trying to open /testfile for writing. B= efore matching the file
>=3B prefix to YAFFS device prefix yaffsfs_Fin= dDevice() strips leading
>=3B slashes from both file name and the devi= ce prefix. This means it will
>=3B try to match "testfile" to "\0" whi= ch fails.
>=3B
>=3B Was this change introduced intentionally to= prevent mounting under root?
>=3B
>=3B Regards
>=3B Evgeny= Habinsky
>=3B
>=3B
>=3B
>=3B ----------------------= --------
>=3B
>=3B Message: 6
>=3B Date: Tue=2C 19 Aug 2008= 14:03:33 +0530
>=3B From: "Amol Lad" <=3Bamol.lad@gmail.com>=3B>=3B Subject: Re: [Yaffs] Yaffs2 and MLC NAND with Block size 256K
&= gt=3B To: "James Kehl" <=3Bjamesk@edmi.com.au>=3B
>=3B Cc: yaffs@l= ists.aleph1.co.uk
>=3B Message-ID:
>=3B <=3B8c675e9b0808190133o= 2fa8ca1dw9b79294463faf33d@mail.gmail.com>=3B
>=3B Content-Type: text= /plain=3B charset=3DISO-8859-1
>=3B
>=3B >=3B>=3B So=2C are = there any assumptions about block size for 2K page ? or 256K
>=3B >= =3B>=3B block size will work as is..
>=3B >=3B>=3B
>=3B >= =3B
>=3B >=3B The define YAFFS_CHUNKS_PER_BLOCK (from yaffs_guts.h) = might be what
>=3B >=3B you're looking for. That=2C or dev->=3BnCh= unksPerBlock if you're using
>=3B >=3B Yaffs-Direct.
>=3B >= =3B
>=3B >=3B If you've got no way of knowing whether it's a 128K bl= ock size or a 256K
>=3B >=3B block size=2C then you might be best of= f telling Yaffs to use a 256K block
>=3B >=3B size=2C and tweaking y= our NAND driver to send two erase commands (so 128K
>=3B >=3B NAND w= ill behave like 256K NAND).
>=3B
>=3B It seems for yaffs2=2C the= se parameters are not set using #defines but
>=3B from mtd. Please see= below snippet.
>=3B
>=3B yaffs_fs.c:
>=3B
>=3B if (y= affsVersion =3D=3D 2) {
>=3B ....
>=3B ....
>=3B #if (LINUX_= VERSION_CODE >=3B KERNEL_VERSION(2=2C6=2C17))
>=3B dev->=3BnDataBy= tesPerChunk =3D mtd->=3Bwritesize=3B
>=3B dev->=3BnChunksPerBlock = =3D mtd->=3Berasesize / mtd->=3Bwritesize=3B
>=3B #else
>=3B = dev->=3BnDataBytesPerChunk =3D mtd->=3Boobblock=3B
>=3B dev->=3B= nChunksPerBlock =3D mtd->=3Berasesize / mtd->=3Boobblock=3B
>=3B #= endif
>=3B nBlocks =3D mtd->=3Bsize / mtd->=3Berasesize=3B
>= =3B
>=3B dev->=3BstartBlock =3D 0=3B
>=3B dev->=3BendBlock = =3D nBlocks - 1=3B
>=3B
>=3B So are above the only parameters ? = or some other place also I need to verify.
>=3B
>=3B >=3B
&= gt=3B >=3B James
>=3B
>=3B Thanks
>=3B Amol
>=3B >=3B
>=3B
>=3B ------------------------------
>=3B
= >=3B _______________________________________________
>=3B yaffs mail= ing list
>=3B yaffs@lists.aleph1.co.uk
>=3B http://lists.aleph1.c= o.uk/cgi-bin/mailman/listinfo/yaffs
>=3B
>=3B
>=3B End of = yaffs Digest=2C Vol 39=2C Issue 9
>=3B *******************************= *****


Do you have a You@live.in id yet? Get it now. Sign= up for a Windows Live ID Try it! = --_bcad3f33-f265-48ac-afd0-dbdab41ad960_--