lkml.org 
[lkml]   [2008]   [Feb]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: distributed module configuration
    On Wed, Feb 13, 2008 at 12:54:33AM -0800, David Miller wrote:
    > From: Sam Ravnborg <sam@ravnborg.org>
    > Date: Wed, 13 Feb 2008 09:45:41 +0100
    >
    > > So we could do:
    > >
    > > config foo
    > > tristate "do you want foo?"
    > > depends on USB && BAR
    > > module
    > > obj-$(CONFIG_FOO) += foo.o
    > > foo-y := file1.o file2.o
    > > help
    > > foo will allow you to explode your PC
    > ...
    > > Does this fit what you had in mind?
    >
    > Yes it does.
    >
    > Now I'll ask if you think embedding this information in one of the C
    > files for a module would be even nicer?
    I have no good idea for the syntax and I and not sure what is gained
    by reducing a driver with one file.
    Agreed - simple drivers would then be a single file - and thats a good argument.

    >
    > Also, we need to make sure we can properly handle top-level
    > container-like items. For example, where would menuconfigs like
    > NETDEV_10000 go if we adopt this kind of scheme?

    If it makes sense to group stuff inside a menuconfig it would
    also make sense to put the same modules in a subdirectory.
    And then we would have the menuconfig in the Kconfig
    file that would source the others.

    So I do not see this as an issue for the 'embedded' syntax described above.

    Sam


    \
     
     \ /
      Last update: 2008-02-13 10:09    [W:7.069 / U:0.800 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site