From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-gy0-f177.google.com ([209.85.160.177]) by merlin.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1SEfbu-0004hH-5X for barebox@lists.infradead.org; Mon, 02 Apr 2012 11:39:46 +0000 Received: by ghbf11 with SMTP id f11so1165413ghb.36 for ; Mon, 02 Apr 2012 04:39:42 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20120402113002.GA18712@sapphire.tkos.co.il> References: <20120401104934.GD22835@sapphire.tkos.co.il> <20120401144518.73c1cf53@eb-e6520> <20120401125209.GE22835@sapphire.tkos.co.il> <20120401150507.465b4a6d@eb-e6520> <20120402113002.GA18712@sapphire.tkos.co.il> Date: Mon, 2 Apr 2012 13:39:42 +0200 Message-ID: From: Gabriel Tisan List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: barebox-bounces@lists.infradead.org Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: nand_imx 4k support ? To: Baruch Siach Cc: barebox@lists.infradead.org Hi Baruch ! Sorry, but I didn't catch it. Do you mean that I don't need an OOB description for 218 byte OOB ? Regards, Gabriel On Mon, Apr 2, 2012 at 1:30 PM, Baruch Siach wrote: > Hi Gabriel, > > On Mon, Apr 02, 2012 at 11:03:06AM +0200, Gabriel Tisan wrote: >> Yes, Baruch I meant write support, especially ECC layout for 4K flashes. >> >> Actually the 4k flashes could have 128 or 218 bytes OOB. >> >> Could you point me to some docs about this layout ? I use a flash with >> 218 bytes spare. > > See commit 2c1c5f199 of the Linux kernel at > http://git.kernel.org/linus/2c1c5f199. > > As Eric has pointed out, this may not be necessary for Barebox. > > baruch > >> On Sun, Apr 1, 2012 at 3:05 PM, Eric B=E9nard wrote: >> > Le Sun, 1 Apr 2012 15:52:09 +0300, >> > Baruch Siach a =E9crit : >> >> Does the Linux kernel detect your flash correctly? >> >> >> > I'm not at this stage for the moment as I'm using a SDcard rootfs to >> > validate the hardware for the moment, but I'm sure the actual problem >> > (in my case at least) in barebox is a detection problem as I get the >> > right values from the flash but these value are ONFI and thus are not >> > right with he actual flash detection code which leads to a wrong >> > configuration of the NFC. Once I hardcode the NFC settings I manage to >> > read/write in the 4k NAND Flash from barebox (environment & kernel >> > are in the flash for the moment). > > -- > =A0 =A0 http://baruch.siach.name/blog/ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0~. .~ =A0 Tk Open Systems > =3D}------------------------------------------------ooO--U--Ooo----------= --{=3D > =A0 - baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il - _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox