From: Pete Popov <ppopov@mvista.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-mips <linux-mips@oss.sgi.com>
Subject: Re: reiserfs
Date: Sat, 27 Apr 2002 13:05:53 -0700 [thread overview]
Message-ID: <1019937954.1260.22.camel@localhost.localdomain> (raw)
In-Reply-To: <E171Yfh-0000gA-00@the-village.bc.nu>
On Sat, 2002-04-27 at 13:19, Alan Cox wrote:
> > Has anyone been able to run reiserfs on big endian systems?
>
> Should work on newer 2.4 kernels
Yes, it does. I sent an email yesterday explaining what the problem
was. The 2.95.3 toolchain is miscompiling the cpu_to_le16 and
le16_to_cpu functions. The problem appears to be fixed in 2.96 and 3.x
so reiserfs is looking good for both, LE and BE mips systems.
Pete
next prev parent reply other threads:[~2002-04-27 20:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 23:13 reiserfs Pete Popov
2002-04-25 7:51 ` reiserfs Ralf Baechle
2002-04-25 8:11 ` reiserfs Geert Uytterhoeven
2002-04-25 16:08 ` reiserfs Pete Popov
2002-04-25 16:17 ` reiserfs George Gensure
2002-04-26 18:34 ` reiserfs Pete Popov
2002-04-27 20:19 ` reiserfs Alan Cox
2002-04-27 20:05 ` Pete Popov [this message]
2002-04-29 17:35 ` reiserfs Jun Sun
2002-04-30 1:04 ` reiserfs Hiroyuki Machida
2002-04-27 20:19 ` reiserfs Alan Cox
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=1019937954.1260.22.camel@localhost.localdomain \
--to=ppopov@mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-mips@oss.sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox