From: grante@visi.com (Grant Edwards)
To: linux-mtd@lists.infradead.org
Subject: Problems with BIG_ENDIAN
Date: Fri, 14 Feb 2003 16:28:20 -0600 [thread overview]
Message-ID: <20030214162819.A15729@visi.com> (raw)
In-Reply-To: <3DF38B3E.CD3CA322@imc-berlin.de>; from steven.scholz@imc-berlin.de on Sun, Dec 08, 2002 at 07:11:10PM +0100
On Sun, Dec 08, 2002 at 07:11:10PM +0100, Steven Scholz wrote:
> I am having trouble creating a big endian image with the latest
> CVS version of mkfs.jffs2!
>
> > mkfs.jffs2 -d /tmp/initrd.tmp.5530 -o images/pFlashdisk -l -p
> > hexdump -n 16 -x images/pFlashdisk
> 0000000 1985 2003 000c 0000 b0b1 e41e 1985 e001
>
> > mkfs.jffs2 -d /tmp/initrd.tmp.5530 -o images/pFlashdisk -b -p
> > hexdump -n 16 -x images/pFlashdisk
> 0000000 1985 2003 000c 0000 b0b1 e41e 1985 e001
>
> Both options -l _and_ -b result in the same byteorder!!!
Yup. And it looks like it's still that way. Oddly, a comment
at the top of the file says that cross-endian support has been
added, but it sure looks like "-l" and "-b" are just ignored.
I tried undefining JFFS2_NATIVE_ENDIAN and defining
JFFS2_BIG_ENDIAN, but then nothing builds. (RH7.3 IA32 host)
Where can I get a version of mkfs.jffs2 that pays attention to
the "-b" flag? [I unfortunately can't access the CVS archives.]
Thanks,
--
Grant Edwards
grante at visi.com
next prev parent reply other threads:[~2003-02-14 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-08 18:11 Problems with BIG_ENDIAN Steven Scholz
2003-02-14 22:28 ` Grant Edwards [this message]
2003-02-14 23:04 ` Grant Edwards
2003-02-14 23:20 ` Grant Edwards
2003-02-15 0:16 ` David Woodhouse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030214162819.A15729@visi.com \
--to=grante@visi.com \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.