Marco Amadori wrote:
qemu + binfmt could permit that on a number of architecture.
you're running them virtualized/emulated, which changes the endiannes to
whatever the target system is. unless you want partially build some
things virtualized/emulated, and some not. which is unclean and opening
a
Alle martedì 4 marzo 2008, Daniel Baumann ha scritto:
Marco Amadori wrote:
qemu + binfmt could permit that on a number of architecture.
you're running them virtualized/emulated, which changes the endiannes to
whatever the target system is. unless you want partially build some
things
Marco Amadori wrote:
Flashes devices often needs a different erase size than default, a config
option for that should be added like [ -e,--eraseblock=SIZE ] from
mkfs.jffs2,
added --jffs2-eraseblock in git, thanks.
for correct results also endianess should be take care of (e.g.
power pc
Alle sabato 1 marzo 2008, Daniel Baumann ha scritto:
Marco Amadori wrote:
Flashes devices often needs a different erase size than default, a config
option for that should be added like [ -e,--eraseblock=SIZE ] from
mkfs.jffs2,
added --jffs2-eraseblock in git, thanks.
You are welcome and
Hi,
I want to put just a minor note since jffs2 code is not uploaded yet.
Flashes devices often needs a different erase size than default, a config
option for that should be added like [ -e,--eraseblock=SIZE ] from
mkfs.jffs2, for correct results also endianess should be take care of (e.g.
5 matches
Mail list logo
