Linux Newbie help
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: Rajat Jain <rajatjain@juniper.net>,
	"linux-newbie@vger.kernel.org" <linux-newbie@vger.kernel.org>,
	kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: x86_64_defconfig and i386_defconfig: What is the difference?
Date: Tue, 09 Sep 2014 10:27:53 -0400	[thread overview]
Message-ID: <75730.1410272873@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 09 Sep 2014 16:06:07 +0200." <540F094F.3040904@gmail.com>

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

On Tue, 09 Sep 2014 16:06:07 +0200, Matthias Brugger said:

> > Can someone tell me if the i386 one is to be used when we want to build for
> > a 32bit machine and the x86_64 is to be used for 64 bit machine?
>
> You can build the kernel with any architecture for any architecture.
> This is called cross-compiling. The homepage [0] should explain you how
> to do that.

Right, but you still need to use a .config appropriate for the target
machine, which is what I think Rajat was asking about.

A defconfig is usually only known verified to boot on a few (possibly one)
examples of that architecture hardware.  For embedded ARM, it may be one
specific development board or hardware device.  For x86, I think they try
to keep it "will probably kind of sort of boot on generic PC hardware with
a common distro, but anything fancylike a webcam or better graphics than
"vga tty emulation" may not work".

A defconfig is pretty much just a proof of concept starting point for
an actual working config for a given hardware system.

[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]

  reply	other threads:[~2014-09-09 14:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09  7:58 x86_64_defconfig and i386_defconfig: What is the difference? Rajat Jain
2014-09-09 13:21 ` Valdis.Kletnieks
2014-09-09 14:19   ` Paul Bolle
2014-09-09 14:26     ` Valdis.Kletnieks
2014-09-09 14:06 ` Matthias Brugger
2014-09-09 14:27   ` Valdis.Kletnieks [this message]
2014-09-09 14:34     ` Abreu, Ian
2014-09-09 15:11     ` Rajat Jain
2014-09-09 15:28       ` Hubert CHAUMETTE
2014-09-09 17:51     ` Rajat Jain
2014-09-13  1:10 ` Peter Teoh
2014-09-13  3:44   ` Rajat Jain

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=75730.1410272873@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-newbie@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=rajatjain@juniper.net \
    /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