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 12:33:18 -0400	[thread overview]
Message-ID: <78ecab220707120933q31a4efb5tb6dbed7a4787f5a@mail.gmail.com> (raw)
In-Reply-To: <20070712161402.GA18550@kroah.com>

Thanks, greg... Just wondering... If this topic comes up every 6
months or so -seems like there is a "need" for this sort of thing.
Wonder why it has not been implemented yet? Especially if as you say
the system calls are out there already to do it -when you know the
right commands to type in.

Just curious... In my never ending quest to make Linux accessible to the masses
:-)


I'll look up the info and try what you suggested.


On 7/12/07, Greg KH <greg@kroah.com> wrote:
> On Thu, Jul 12, 2007 at 11:02:15AM -0400, Mark Shelby wrote:
> >  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.
>
> Check the archives, this comes up every 6 months or so.
>
> Also, you can just use the simple scripts as described in the book,
> "Linux Kernel in a Nutshell", free online, to do most of what you are
> looking for here (automatic detection of what driver is needed for what
> device.)
>
> good luck,
>
> greg k-h
>

  reply	other threads:[~2007-07-12 16:33 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
2007-07-12 16:14     ` Greg KH
2007-07-12 16:33       ` Mark Shelby [this message]
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=78ecab220707120933q31a4efb5tb6dbed7a4787f5a@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®