From: pebolle@tiscali.nl (Paul Bolle)
To: kernelnewbies@lists.kernelnewbies.org
Subject: x86_64_defconfig and i386_defconfig: What is the difference?
Date: Tue, 09 Sep 2014 16:19:54 +0200 [thread overview]
Message-ID: <1410272394.16079.10.camel@x220> (raw)
In-Reply-To: <22561.1410268883@turing-police.cc.vt.edu>
On Tue, 2014-09-09 at 09:21 -0400, Valdis.Kletnieks at vt.edu wrote:
> On Tue, 09 Sep 2014 07:58:49 -0000, Rajat Jain 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?
>
> I wouldn't run either one on an actual machine. Defconfigs are *example*
> configs, only useful as a template for customizing for actual hardware.
It is probably easiest to take the .config file of the latest kernel of
the distribution you are using as a starting point. In that case you
know that this starting point at least works on your machine.
(I remember seeing tutorials that show you how to generate a .config
from scratch. I wonder whether anyone actually does that. It should be
quite a bit of work for an uncertain outcome. Ie, you might end up
trying quite a few configurations before hitting one that works
reasonably for your machine.)
Hope this helps,
Paul Bolle
next prev parent reply other threads:[~2014-09-09 14:19 UTC|newest]
Thread overview: 11+ 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 at vt.edu
2014-09-09 14:19 ` Paul Bolle [this message]
2014-09-09 14:26 ` Valdis.Kletnieks at vt.edu
2014-09-09 14:06 ` Matthias Brugger
2014-09-09 14:27 ` Valdis.Kletnieks at vt.edu
2014-09-09 14:34 ` Abreu, Ian
2014-09-09 15:11 ` Rajat Jain
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=1410272394.16079.10.camel@x220 \
--to=pebolle@tiscali.nl \
--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).