Re: x86_64_defconfig and i386_defconfig: What is the difference?

[email protected] Tue, 09 Sep 2014 10:27:53 -0400
Newsgroups org.kernel.vger.linux-newbie,org.kernelnewbies.kernelnewbies
Message-ID <[email protected]>
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.
signature.asc (application/pgp-signature, 848 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Exmh version 2.5 07/13/2001

iQIVAwUBVA8OaQdmEQWDXROgAQIwaA/+IEq/530zbXlObWeQQULdCS/XV5luMLcO
szpD8SRXK7uaxoLe3Hy4EgHMpvTYx3TsmJ1uFgG4WCmn8gRJ3h7evrjXszJ2WaR1
yrUnPXTcWOoddcHYiuxCiJeAHyqF+Srt+v1Pou7OL86unHhNOp79YfVZcAjjSMfr
mGZdTjgsFwI9OQ9nO6rWe9PpwOLMYgNPMVosMlWwIe7zQeVCw73NTRKS++68AMvn
IVXWvdL9rSmo0RwH9W29G8QgQrHeImpGGcmPBFPtGGcIXxVK9xZTWx0qCw5igCgF
msqsSd3+UsJ6DtiKrD8IYv9SHTvlu3Lfn5pAHWh+T4bHw0bop1oW+70zprrm9wU8
BI1GVlO/PP4B6l8s6FyMXvetMOln8ZTIy5LiZZZ0v/M/jHl/Fz0HvUeQyPDSn9h4
iFWczzF2OJUSeqFlDB5TJMmYIy4f2/irffXn6MSwluV0gPPQdtU1JEQZS/Vbn22G
/yW0K9aOeJqNEHPwEETKT6pqVo867Od0er6hKXnHuOeMAo1hA/O0Na5BbpTPSLuv
u9WTFSgGvihBbDBpYE43Joi1iobT3yqiybmA13fb074Y92f8oV5StP+cJumfx/ef
MvVn0FlQ4zF0nAr2o8pbasr3oBAo3gNSZbo0vr7nn44wJtyQLfTRvPTPDjhX5FxI
3F7eoRXjnVU=
=Rgg0
-----END PGP SIGNATURE-----