On Wed, Sep 20, 2006 at 02:20:07PM +1200, Charles Manning wrote:
> On Wednesday 20 September 2006 11:51, Jonathan McDowell wrote:
> > On Tue, Sep 19, 2006 at 11:31:34PM +0400, Vitaly Wool wrote:
> > > On 9/19/06, Jonathan McDowell <noodles@earth.li> wrote:
> > > >On Sat, Sep 16, 2006 at 12:41:53AM +0400, Vitaly Wool wrote:
> > > >> Anyway, can you please answer if you are sure that the NAND
> > > >> driver is fine wrt recent MTD code changes.
> > > >
> > > >I can't say if this is the case for certain just yet; the
> > > >behaviour I'm seeing looks very much like OOB access is unhappy.
> > > >Unfortunately other more pressing things have come up this week
> > > >and I haven't had a chance to narrow down the problem, but as
> > > >soon as I'm able to confirm one way or the other I'll let you
> > > >know.
> > >
> > > can you please try the updated patch I sent this weekend?
> >
> > This is much better, in that I can mount an empty file system fine
> > though I'm seeing some corruption on a mount/umount/mount cycle.
> > I'll continue trying to find time proving the MTD layer is happy.
>
> Have a look at the things I mentioned in my last respose. You might
> find that those cure your probs.
>
> Generally the "works OK until I umount and mount" probs are caused by
> tags corruption.
I haven't had any time to look at this in the past couple of weeks, but
I've just updated my tree to use the latest yaffs2 CVS code and have
managed to mount my NAND using YAFFS, write a file system to it,
unmount, remount and see it all ok, then reboot and use the NAND as /
successfully. Very slow to mount, but seems to work from the minimal
testing I've tried so far.
J.
--
How I wish, how I wish you were | .''`. Debian GNU/Linux Developer
here. | : :' : Happy to accept PGP signed
| `. `' or encrypted mail - RSA +
| `- DSA keys on the keyservers.
(text/plain)