From: Pete Popov <ppopov@mvista.com>
To: Keith Owens <kaos@sgi.com>
Cc: linux-mips <linux-mips@oss.sgi.com>
Subject: Re: xfs
Date: Sat, 09 Mar 2002 10:12:42 -0800 [thread overview]
Message-ID: <1015697562.1199.1.camel@localhost.localdomain> (raw)
In-Reply-To: <7338.1015665420@ocs3.intra.ocs.com.au>
On Sat, 2002-03-09 at 01:17, Keith Owens wrote:
> On 08 Mar 2002 10:22:07 -0800,
> Pete Popov <ppopov@mvista.com> wrote:
> >I see on SGI's web site that XFS is supported only on x86 and IA64. Has
> >anyone tried it on mips?
>
> Anybody wanting to port XFS to new architectures should start with
> ftp://oss.sgi.com/projects/xfs/download/patches/2.4.18
> I split the XFS patches up so people can pick and choose which
> components they use, it makes it easier to exclude code like kdb,
> kbuild 2.5 or ia64 from the port. Note the ia64 patch, you will need a
> MIPS equivalent.
Great, thank you.
> When you get it working, send us the changes from the split patches.
I will, if I get to work on it.
Pete
next prev parent reply other threads:[~2002-03-09 19:16 UTC|newest]
Thread overview: 20+ 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 ` Pete Popov [this message]
2002-03-10 5:30 ` xfs Steven J. Hill
[not found] <BE7DD4DC7F4F024FA32FB6E94B73461A02BB3DE9@MAIL-NY.norwalk.medtechinc.com>
2006-12-22 17:42 ` XFS Geir A. Myrestrand
2006-12-22 23:12 ` XFS Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2006-12-22 16:06 XFS Jaideep Nandy
2006-12-22 16:39 ` XFS Geir A. Myrestrand
2005-06-17 9:23 XFS Marco Gerards
2005-06-17 11:05 ` XFS Nico -telmich- Schottelius
2005-06-20 10:54 ` XFS Yoshinori K. Okuji
2003-12-05 12:09 XFS Alexander Economou
2003-12-05 12:32 ` XFS Mike Harrison
2002-03-13 1:29 XFS Pete Popov
2002-02-06 14:16 xfs Timothy Wood
2002-02-06 15:04 ` xfs Stephen Smalley
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=1015697562.1199.1.camel@localhost.localdomain \
--to=ppopov@mvista.com \
--cc=kaos@sgi.com \
--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 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.