From: "Steven J. Hill" <sjhill@cotw.com>
To: Pete Popov <ppopov@mvista.com>
Cc: linux-mips <linux-mips@oss.sgi.com>
Subject: Re: xfs
Date: Sat, 09 Mar 2002 23:30:55 -0600 [thread overview]
Message-ID: <3C8AEF8F.21DB96B9@cotw.com> (raw)
In-Reply-To: 1015611727.12994.441.camel@zeus
Pete Popov wrote:
>
> I see on SGI's web site that XFS is supported only on x86 and IA64. Has
> anyone tried it on mips?
>
Oh most definitely. I've been using it on my NEC 5432 platform for almost
a year now, little endian. Works great. I've compiled the Linux/MIPS 2.4.x
kernel with toolchains based on latest binutils, gcc-3.0.x, gcc-3.1 and
glibc-2.2.3 and glibc-2.2.5 combinations.
-Steve
--
Steven J. Hill - Embedded SW Engineer
next prev parent reply other threads:[~2002-03-10 6:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-08 18:22 xfs Pete Popov
2002-03-08 18:42 ` xfs Seth Mos
2002-03-08 19:22 ` xfs Martin K. Petersen
2002-03-09 0:07 ` xfs Pete Popov
2002-03-10 23:04 ` xfs Liam Davies
2002-03-09 9:17 ` xfs Keith Owens
2002-03-09 18:12 ` xfs Pete Popov
2002-03-10 5:30 ` Steven J. Hill [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-13 1:29 XFS Pete Popov
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=3C8AEF8F.21DB96B9@cotw.com \
--to=sjhill@cotw.com \
--cc=linux-mips@oss.sgi.com \
--cc=ppopov@mvista.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