From: Ralf Baechle <ralf@linux-mips.org>
To: Matthew Dharm <mdharm@momenco.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: PATCH: linux_2_4: add support for the Ocelot-G board
Date: Mon, 2 Sep 2002 22:46:15 +0200 [thread overview]
Message-ID: <20020902224615.A17378@linux-mips.org> (raw)
In-Reply-To: <20020902123850.A28171@momenco.com>; from mdharm@momenco.com on Mon, Sep 02, 2002 at 12:38:50PM -0700
On Mon, Sep 02, 2002 at 12:38:50PM -0700, Matthew Dharm wrote:
> Oh, I agree that a 64-bit kernel makes sense. I'm just not sure what is
> needed to get from where I am now to where I want to be.
>
> There is _much_ interest from our customers for 64-bit linux. Especially
> if the toolchain catches up so that we can have 64-bit userspace.
The toolchain stuff is being worked on. Hold your breath but cheat every
once in a while when your face turns blue ;-)
> Anyone have some quick pointers on how to get from here to there?
The basic receipe is easy. The 64-bit kernel has a binary compatibility
layer that allows you to use 32-bit software with no changes. Just use
a 64-bit compiler, for now that's probably still the egcs 1.1.2 /
binutils 2.9.5 based mips64-linux / mips64el-linux tool chain. Using your
old .config file do a "make ARCH=mips64 oldconfig" etc. The resulting
binary file will be a 32-bit ELF file so you can just feed that to your
firmware for booting as usual. Problems may be hit along the way ;-)
Ralf
next prev parent reply other threads:[~2002-09-02 19:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <NEBBLJGMNKKEEMNLHGAIKEJOCIAA.mdharm@momenco.com>
2002-09-02 17:00 ` PATCH: linux_2_4: add support for the Ocelot-G board Ralf Baechle
2002-09-02 19:38 ` Matthew Dharm
2002-09-02 20:46 ` Ralf Baechle [this message]
2002-09-02 20:40 ` Matthew Dharm
2002-09-02 22:03 ` 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=20020902224615.A17378@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--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 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.