On Thu, Aug 13, 2009 at 05:58:57PM -0500, alfred steele wrote:
> > That controls whether the "jffs2" command supports NAND.
> Iis it a MUST HAVE if you are using a jffs2 root filesystem? I mean do
> i have to turn on "CONFIG_JFFS2_NAND" if i have a jff2 rootfs.
> Are there any other configuration f
> That controls whether the "jffs2" command supports NAND.
Iis it a MUST HAVE if you are using a jffs2 root filesystem? I mean do
i have to turn on "CONFIG_JFFS2_NAND" if i have a jff2 rootfs.
Are there any other configuration flags i need to turn on for JFFS2 support?
Thanks,
Alfred.
_
alfred steele wrote:
> Just realised that i dis reply instead of "reply all".
>> We have been using 2009.1 based version.. We have been using "nand
>> read.e/write.e". Is that fine? After skimming through the u-boot code,
>> it seems though.
>> Please confirm.
> Apart from this, what does the "CONF
Just realised that i dis reply instead of "reply all".
> We have been using 2009.1 based version.. We have been using "nand
> read.e/write.e". Is that fine? After skimming through the u-boot code,
> it seems though.
> Please confirm.
Apart from this, what does the "CONFIG_JFFS2_NAND" do?
Thanks, Al
On Wed, Aug 12, 2009 at 12:30:02AM -0500, alfred steele wrote:
> I have been using the "nand erase.e" command with favourable results
> till now. I was enticed by the "CONFIG_JFFS2_NAND" option in the
> platform config. When i turn this config option on and use the "NAND.
> write.jffs2 ", and use t
Hi All,
I have been using the "nand erase.e" command with favourable results
till now. I was enticed by the "CONFIG_JFFS2_NAND" option in the
platform config. When i turn this config option on and use the "NAND.
write.jffs2 ", and use the resulting image, i get abnormal results
including a kernel
On Fri, Feb 13, 2009 at 10:39:34AM -0700, Derek Ou wrote:
> 1) The nand_util.c does not have WATCHDOG_RESET() in the
> nand_read_skip_bad() and nand_write_skip_bad() while the original
> nand_write_opts() and nand_read_opts() do. Is there a special reason
> this is removed? It's likely that wa
I have a few issues/questions regarding the NAND commands in the latest
git main tree.
1) The nand_util.c does not have WATCHDOG_RESET() in the
nand_read_skip_bad() and nand_write_skip_bad() while the original
nand_write_opts() and nand_read_opts() do. Is there a special reason
this is removed
8 matches
Mail list logo
