public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeremy Huddleston <eradicator@gentoo.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Mixing Architectures... AMD64 bit kernel on 32bit build.
Date: Sat, 29 Oct 2005 01:34:07 -0700	[thread overview]
Message-ID: <1130574848.11723.97.camel@cloud.outersquare.org> (raw)
In-Reply-To: <1130572763.8213.4.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]

> Can I safely put a 64bit compiled kernel image into /boot/ along
> with /lib/modules<version> and the source in /usr/src/<version>
> into a fully 32bit image? 

Yes, as long as you don't have a 32bit kernel also in /lib/modules/* of
the same version.

> If so what other utilities on the system NEED to be 64bit for this to
> work? 

Assuming you have 32bit support in the kernel, nothing...

> I have a 32bit precooked image I use, and have dumped it onto a Turion
> laptop (see http://aenertia.net/megabook_m635.html for coverage). 
> 
> I am getting alot of issues with IRQ and USB f$%#ups. And am wondering
> if a native 64bit kernel will help. But want to know if I can simply
> drop an am64 kernel into the middle of a 32bit environment and have it
> boot? 

Yep, you can.  This is what sparc64 does.

> What is the easiest route for me to do this based on the above linked
> report.

You'll need to get an x86_64 compiler on your system (crossdev should
work fine, or you can modify gcc64), then you'll need to cross-compile
the kernel (there are plenty of docs online about how to do this).

--Jeremy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-10-29  8:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29  7:59 [gentoo-amd64] Mixing Architectures... AMD64 bit kernel on 32bit build Joel Wiramu Pauling
2005-10-29  8:34 ` Jeremy Huddleston [this message]
2005-10-29  8:46   ` Joel Wiramu Pauling
2005-10-29  8:50   ` Joel Wiramu Pauling

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=1130574848.11723.97.camel@cloud.outersquare.org \
    --to=eradicator@gentoo.org \
    --cc=gentoo-amd64@lists.gentoo.org \
    /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