From: alex@archeleus.com (Alex John)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Compiling for two different processors
Date: Sun, 26 Dec 2010 04:44:37 -0700 [thread overview]
Message-ID: <20101226044437.59293b48@alex-debian> (raw)
In-Reply-To: <AANLkTi=Fr9FBfZTMgzOF0Ry0wLaBvTn-1uGc8wqQHuC7@mail.gmail.com>
Hello,
On Wed, 8 Dec 2010 15:46:36 +0700
Mulyadi Santosa <mulyadi.santosa@gmail.com> wrote:
> Hi :)
>
> On Wed, Dec 8, 2010 at 15:16, John Mahoney <jmahoney@waav.com> wrote:
> > Just a heads up. Try not to top post here. See my comment inline.
> >
> > On Dec 8, 2010, at 2:10 AM, Alex John <alex@archeleus.com> wrote:
> >
> >> Thanks, I'll compile for P4 then.
> >
> > I was just thinking and realized the core2 may have been based off
> > the p3 arch and the p4 was a dead end, but normally with intel you
> > can compile for the LCD, but I may have lied this time. Also, I
> > believe one is 32bit and the other is 64bit, but a 32 bit kernel
> > will work on both.
>
> I think Core 2 is more like "almost new" arch....I bet it tends to be
> closer to newer Xeon (according to related Kbuild message)
Apparently Core 2 is similar to the Coppermine T in some ways
(such as netburst) but I think that its new as well since it's the
model for quads, i7's etc;
>
> > If you want to guarantee it works on both I would compile for 32bit
> > i386, but feel free to have some fun. If you do compile with p4
> > post if it worked on the core2, I am sort of interested now.
> >
>
> I suggest to start with i686 first, then work gradually up
>
Compiled a generic for i686 and it worked perfectly with both
processors, but then my old gentoo instincts kicked in and I compiled
two different versions.
Cheers
- Alex.
parent reply other threads:[~2010-12-26 11:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <AANLkTi=Fr9FBfZTMgzOF0Ry0wLaBvTn-1uGc8wqQHuC7@mail.gmail.com>]
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=20101226044437.59293b48@alex-debian \
--to=alex@archeleus.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).