Re: Automatic Configuration of a Kernel

From: Marek W (marekw1977_at_yahoo.com.au)
Date: 09/15/05

  • Next message: David Brownell: "Re: [RFC][PATCH] SPI subsystem" 
    To: linux-kernel@vger.kernel.org
Date:	Thu, 15 Sep 2005 10:09:59 +1000

    On Thu, 15 Sep 2005 09:49, Daniel Thaler wrote:
    > Michal Piotrowski wrote:
    > > Hi,
    > >
    > > On 15/09/05, Ahmad Reza Cheraghi <a_r_cheraghi@yahoo.com> wrote:
    > >>Hi
    > >>
    > >>I wrote this Framework for making a .config based on
    > >>the System Hardwares. It would be a great help if some
    > >>people would give me their opinion about it.
    > >>
    > >>Regards
    > >
    > > It's for new linux users? They should use distributions kernels.
    > > It's for "power users"? They just do make menuconfig...
    > > It's for kernel developers? They just do vi .config.
    >
    > 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.
    >
    > 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.

    I second that. Unlike majority of users I suppose, I upgrade the kernel often
    and I am on the bleeding edge (laptop user with some drivers still being in
    development). Even with oldconfig it's easy to miss a useful driver
    (sometimes there's no help or the volume of new options is too large).

    Something that can do the hardware detection, then maps that to drivers would
    be very useful. 

    --
Marek W
Send instant messages to your online friends http://au.messenger.yahoo.com 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
  • Next message: David Brownell: "Re: [RFC][PATCH] SPI subsystem"

    Relevant Pages

    • Re: udev is too slow creating devices
      ... and drivers like the microcode module are the ... demand by userspace when the kernel sees the device. ... PCI and USB both use the same probe core code. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: New proposed DRM interface design
      ... >> drivers out of Xorg or better still Mesa, rather than waiting for a full ... >> kernel releases are very frequent. ... after this the XFree86 slow-motion trainwreck started, and history overtook ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: starting with 2.7
      ... >> to stability, but the ability to keep up with kernel development. ... > That is the price for closed-source drivers. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH 2/5] atomic: introduce atomic_inc_not_zero
      ... > without polluting the kernel too much. ... Send instant messages to your online friends http://au.messenger.yahoo.com ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: making kmalloc BUG() might not be a good idea
      ... >-ENOMEM kinds of failures will now BUG() the kernel. ... Send instant messages to your online friends http://au.messenger.yahoo.com ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)