From: Ralf Baechle <ralf@oss.sgi.com>
To: Jun Sun <jsun@mvista.com>
Cc: Daniel Jacobowitz <dan@debian.org>,
Matthew Dharm <mdharm@momenco.com>,
Linux-MIPS <linux-mips@oss.sgi.com>
Subject: Re: MIPS 64?
Date: Sun, 19 May 2002 12:30:59 -0700 [thread overview]
Message-ID: <20020519123059.E20670@dea.linux-mips.net> (raw)
In-Reply-To: <3CE2DA46.3070402@mvista.com>; from jsun@mvista.com on Wed, May 15, 2002 at 02:59:34PM -0700
On Wed, May 15, 2002 at 02:59:34PM -0700, Jun Sun wrote:
> Back to 64bit port, it seems to me much of the 32bit work we have done in the
> past a year or so needs to be moved over. Or better yet, if we can clean up
> integer/long issues, we might be able to use 32bit kernel code straight for
> 64bit kernel.
Int vs. long was a very small issue as I discovered during porting for the
first 64-bit machines, the IP22 and IP27.
Ralf
next prev parent reply other threads:[~2002-05-19 19:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 21:34 MIPS 64? Matthew Dharm
2002-05-15 21:48 ` Daniel Jacobowitz
2002-05-15 21:55 ` Kip Walker
2002-05-15 22:08 ` Matthew Dharm
2002-05-15 22:08 ` Matthew Dharm
2002-05-15 22:15 ` Kip Walker
2002-05-15 22:26 ` Matthew Dharm
2002-05-15 22:29 ` Kip Walker
2002-05-19 19:29 ` Ralf Baechle
2002-05-19 19:25 ` Ralf Baechle
2002-05-15 21:59 ` Jun Sun
2002-05-15 22:16 ` Matthew Dharm
2002-05-19 19:32 ` Ralf Baechle
2002-05-16 3:28 ` Dan Malek
2002-05-16 7:15 ` Kevin D. Kissell
2002-05-16 17:13 ` Jun Sun
2002-05-19 19:44 ` Ralf Baechle
2002-05-19 19:41 ` Ralf Baechle
2002-05-19 19:30 ` Ralf Baechle [this message]
2002-05-20 10:06 ` Maciej W. Rozycki
2002-05-20 15:57 ` Greg Lindahl
2002-05-20 16:05 ` Maciej W. Rozycki
2002-05-21 16:47 ` Florian Lohoff
2002-05-21 17:00 ` Greg Lindahl
2002-05-20 19:05 ` Ralf Baechle
2002-05-19 19:24 ` Ralf Baechle
2002-05-19 19:23 ` Ralf Baechle
2002-05-20 6:05 ` Matthew Dharm
2002-05-20 20:30 ` 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=20020519123059.E20670@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=dan@debian.org \
--cc=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=mdharm@momenco.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