All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Fleury <fleury@cs.aau.dk>
To: Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: Automatic Configuration of a Kernel
Date: Thu, 15 Sep 2005 11:12:04 +0200	[thread overview]
Message-ID: <43293AE4.5050308@cs.aau.dk> (raw)
In-Reply-To: <4328B710.5080503@in.tum.de>

Daniel Thaler wrote:
> 
> I like the idea.
> I'm a power user and of course I can do make menuconfig, but it would be
> useful when building a kernel for new hardware for example.

I agree ! When compiling for a new platform you would like to have at
least a minimal skeleton of the .config which is working for your
machine and then add stuff like NFS, netfilter, and other stuff.

Something like:

make autoconfig ---> generate a skeleton (compile and run)
make menuconfig ---> add the stuff you want (file systems, firewall, ...)

However, if the "make autoconfig" target generate nothing but a bare
minimal .config which is fitting exactly your hardware, which would
compile and run on your platform (with a stripped down network layer,
only one file system, etc). Then I would like to have this.

> Currently that involves looking at dmesg output to figure out the correct
> options; this would provide a nice base config to work with and reduce the
> amount of effort.

Yes. Especially for strange platforms where you usually end-up with a
try and error methodology... (yes, I got a Transmeta Crusoe Sony Vaio
C1-MZX once ! :)).

Regards
-- 
Emmanuel Fleury

Assistant Professor          | Office: B1-201
Computer Science Department, | Phone:  +45 96 35 72 23
Aalborg University,          | Mobile: +45 26 22 98 03
Fredriks Bajersvej 7E,       | E-mail: fleury@cs.aau.dk
9220 Aalborg East, Denmark   | URL: www.cs.aau.dk/~fleury


  parent reply	other threads:[~2005-09-15  9:13 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-14 22:38 Automatic Configuration of a Kernel Ahmad Reza Cheraghi
2005-09-14 22:53 ` Michal Piotrowski
2005-09-14 23:49   ` Daniel Thaler
2005-09-15  0:09     ` Marek W
2005-09-15  0:37       ` Hua Zhong
2005-09-15  2:03         ` David Lang
2005-09-15  3:04           ` Lee Revell
2005-09-15  3:37             ` Daniel Thaler
2005-09-15  4:16               ` Lee Revell
2005-09-15  8:12                 ` Ahmad Reza Cheraghi
2005-09-15 11:20                   ` Masoud Sharbiani
2005-09-15 20:58               ` Ahmad Reza Cheraghi
2005-09-15 21:04                 ` Jesper Juhl
2005-09-15  4:18             ` Marek W
2005-09-15  6:18               ` Valdis.Kletnieks
2005-09-15  7:33                 ` Marek W
2005-09-15  9:48                   ` Ahmad Reza Cheraghi
2005-09-15 10:44                 ` David Lang
2005-09-15 10:26             ` David Lang
2005-09-15 14:58               ` Nix
2005-09-15 17:08                 ` David Lang
2005-09-15 20:36                 ` Valdis.Kletnieks
2005-09-15 20:50                   ` Nix
2005-09-15  8:53       ` Chris White
2005-09-15  7:58         ` Ahmad Reza Cheraghi
2005-09-15  9:12     ` Emmanuel Fleury [this message]
2005-09-15  9:56   ` Ahmad Reza Cheraghi
2005-09-16  4:02     ` Chris White
2005-09-16  7:12       ` Emmanuel Fleury
2005-09-16 17:38   ` Pavel Machek
2005-09-16 17:50     ` Enrico Weigelt
2005-09-15 11:21 ` Roman Zippel
2005-09-15 12:01   ` Emmanuel Fleury
2005-09-15 13:02     ` Ahmad Reza Cheraghi
2005-09-15 13:28       ` Emmanuel Fleury
2005-09-15 13:03     ` Ahmad Reza Cheraghi
2005-09-17  1:27     ` Roman Zippel
2005-09-16  8:11 ` Coywolf Qi Hunt
2005-09-16  8:19   ` Emmanuel Fleury
2005-09-16  8:32     ` Ahmad Reza Cheraghi
2005-09-16  8:50       ` Emmanuel Fleury
2005-09-16  9:19         ` Ahmad Reza Cheraghi
  -- strict thread matches above, loose matches on Subject: below --
2005-09-26 12:08 Ahmad Reza Cheraghi
2005-09-26 13:57 ` Michal Piotrowski
2005-09-26 14:06 ` Michal Piotrowski
2005-09-27  8:05 ` Coywolf Qi Hunt
2005-09-27  8:11   ` Emmanuel Fleury

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=43293AE4.5050308@cs.aau.dk \
    --to=fleury@cs.aau.dk \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.