jffs2 32-bit access issue

[ARXX Dev Team]

That is exactly what we have done. Hence we have added calls to
jffs2_fill_scan_buf(..) in our patch instead of direct access that was
in jffs2 code. Without MTD layer function calls, jffs2 scan/erase
functions fail. As you will see in our code patch, we have accessed
flash data using MTD layer functions (or 16-bit pointers) instead of
32-bit access that exist in jffs2 code.


>
> Why don't you write a custom mapping driver that prevents the 32-bit
> accesses at the MTD level?  That seems like a more appropriate place
> than sticking it in JFFS2 code, which is supposed to be fairly
> hardware independent (with the obvious exception of major flash class
> types like NOR, NAND, etc).
>
> josh
>