From: "Steven J. Hill" <sjhill@cotw.com>
To: linux-mips@oss.sgi.com, binutils@sources.redhat.com
Subject: Comments on new Linux MIPS FAQ...
Date: Wed, 06 Feb 2002 09:22:24 -0600 [thread overview]
Message-ID: <3C614A30.928E6BC5@cotw.com> (raw)
First off, this is not a replacement for the awesome FAQ at
SGI maintained by Ralf. The FAQ I wrote addresses 32-bit and
64-bit Linux kernel/userspace questions (well, starts to). I
would greatly appreciate comments from everyone on this. You
can read it here:
http://www.cotw.com/mips/mips64.txt
Please send me comments and corrections and make sure you copy
the mailing list(s). After the corrections settle down a bit,
we can come up with a name and get it hosted on SGI's site or
the http://www.linuxmips.net/ site or even my site, I don't care.
The inspiration for this came from Matthew Dharm's questions as
well as my management asking about 32-bit versus 64-bit Linux
kernels and wanting to know current toolchain status. Thanks.
-Steve
--
Steven J. Hill - Embedded SW Engineer
next reply other threads:[~2002-02-06 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 15:22 Steven J. Hill [this message]
2002-02-06 17:04 ` Comments on new Linux MIPS FAQ Florian Lohoff
2002-02-06 17:08 ` Ralf Baechle
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=3C614A30.928E6BC5@cotw.com \
--to=sjhill@cotw.com \
--cc=binutils@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox