From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Wood <scottwood@freescale.com>
Date: Tue, 07 Oct 2008 12:47:35 -0500
Subject: [U-Boot] [PATCH 07/12 v2] ARM: OMAP3: Add memory and
 syslib	common files, add NAND support
In-Reply-To: <7A436F7769CA33409C6B44B358BFFF0CDD7A73FF@dlee02.ent.ti.com>
References: <48e5f6a5.0305560a.0a0e.ffffe071@mx.google.com>
	<20081003165203.GA11156@ld0162-tx32.am.freescale.net>
	<48EB2F0E.4090805@googlemail.com> <48EB4717.7080904@gmail.com>
	<20081007173016.GB3438@loki.buserror.net>
	<7A436F7769CA33409C6B44B358BFFF0CDD7A73FF@dlee02.ent.ti.com>
Message-ID: <48EBA0B7.5050703@freescale.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Menon, Nishanth wrote:
>>> I do not get it either.. ECCPOS is in offset bytes, and oobfree should
>>> be {.offset=20,.length=44} /*I always hated struct initialization done
>>> as above..*/, but then,
>> Why not offset 14, length 50?
> How about this part being used by ubi/jffs2 or some fs.. I cant think off-hand if there an implication, but yep, I suspect there is no reason why not..

The higher levels allocate their OOB usage from the regions that the 
low-level driver claims are free.

-Scott