Hi!
This problem has been discussed several times [1], [2], but wasn't
resolved yet. The clean solution suggested was to implement a custom
mapping driver [3].
Then I'll do that. It doesn't look terribly complicated.
It would be helpful if someone can test the first version if it's available.
Hi Stephan,
On Sun, 01 Jul 2012 08:47:01 +0200
Stephan Gatzka wrote:
> Hi Albrecht,
>
> > I don't recall who proposed this patch, but exactly this solution is
> > around for a longer time (mayby you search archives...). On my board, I
> > have a flash chip attached to the LocalBus in 16-bit
(SPAM)
Em 01-07-2012 03:47, Stephan Gatzka escreveu:
Hi Albrecht,
> I don't recall who proposed this patch, but exactly this solution is
> around for a longer time (mayby you search archives...). On my
board, I
> have a flash chip attached to the LocalBus in 16-bit mode. Based on
> 3.2.16,
Hi Albrecht,
> I don't recall who proposed this patch, but exactly this solution is
> around for a longer time (mayby you search archives...). On my board, I
> have a flash chip attached to the LocalBus in 16-bit mode. Based on
> 3.2.16, the patch is:
Thanks for your answer and yes, this patch
Hi Stephan:
Am 30.06.12 21:16 schrieb(en) Stephan Gatzka:
I have a problem running jffs2 on an MPC5200b board. I run kernel 3.4, but
older kernels like 3.1.5 are also affected. Every time I mount jffs2,
previously written content gets garbled.
The problem was nailed down to memcpy(&fd->name,
Hello!
First of all, please apologize my cross posting.
I have a problem running jffs2 on an MPC5200b board. I run kernel 3.4,
but older kernels like 3.1.5 are also affected. Every time I mount
jffs2, previously written content gets garbled.
The problem was nailed down to memcpy(&fd->name, r