mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mark Shelby" <mshelby1@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel autoconfig option?
Date: Thu, 12 Jul 2007 11:02:15 -0400	[thread overview]
Message-ID: <78ecab220707120802p11ab3e1fye497f4107fe18c1d@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707121635120.25352@fbirervta.pbzchgretzou.qr>

That's an excellent idea. I am still thinking along the lines of
"idiot proof simplicity." It would be nice to have a configure script
that scanned your system board, sound card/chip various input ports,
etc, and went ahead and preselected those to build when you type
"make.

If you could combine this with the make "allmodconfig" command in a
user friendly interface, I think you'd really be on to something!
--as long as it's still configurable after the preselected choices are
made.


On 7/12/07, Jan Engelhardt <jengelh@computergmbh.de> wrote:
>
> On Jul 12 2007 10:18, Mark Shelby wrote:
> >
> > Would it be possible to design a program to scan your existing system
> > hardware and pre-select your onboard hardware options within the
> > kernel config menus?
>
> > Am I just crazy, or wouldn't this idea mke a lot of sense? Wouldn't it
> > pretty much make the kernel "idiot proof" when installing from source?
>
> Why not just use `make allmodconfig`? If you happen to suddenly have a new
> device you never had before (and I can assure you: this happens!), you
> already have all modules.
>
>
>
>        Jan
> --
>

  reply	other threads:[~2007-07-12 15:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12 14:18 Mark Shelby
2007-07-12 14:37 ` Jan Engelhardt
2007-07-12 15:02   ` Mark Shelby [this message]
2007-07-12 16:14     ` Greg KH
2007-07-12 16:33       ` Mark Shelby
2007-07-12 18:56         ` Greg KH
2007-07-12 18:35 ` Valdis.Kletnieks
2007-07-12 18:46   ` Mark Shelby

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=78ecab220707120802p11ab3e1fye497f4107fe18c1d@mail.gmail.com \
    --to=mshelby1@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®