Re: [PATCH] disable builtin modules

From: Magnus Damm (magnus.damm_at_gmail.com)
Date: 03/20/05

  • Next message: Domen Puncer: "Re: [patch 06/10 with proper signed-off] init/do_mounts_initrd.c: fix sparse warning"
    Date:	Sun, 20 Mar 2005 11:53:42 +0100
    To: Jan Engelhardt <jengelh@linux01.gwdg.de>
    
    

    On Sun, 20 Mar 2005 10:51:41 +0100 (MET), Jan Engelhardt
    <jengelh@linux01.gwdg.de> wrote:
    >
    > >This patch makes it possible to disable built in code from the kernel
    > >command line. The patch is rather simple - it extends the compiled-in case
    > >of module_init() to include __setup() with a name based on KBUILD_MODNAME.
    >
    > What if there is already an option like the modname? I do not know of any
    > code that currently does so, but you never know.
    >
    > Are acpi= and apm= already what your patch wants to extend to other modules?
    > If not, there's conflict.

    There is a conflict. Thanks for pointing that out.

    Both the obsolete __setup() parameter code and the module parameter
    code in kernel/params.c are limited to a single matching parameter.
    The first matching parameter will be used, and non-early obsoleted
    parameters are overridden by module parameter code. If I understand
    the code correctly that is. =)

    Maybe it is possible to (mis)use early_param instead of __setup and
    let these parameters become "high priority" parameters that only are
    parsed by do_early_param()...?

    / magnus
    -
    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: Domen Puncer: "Re: [patch 06/10 with proper signed-off] init/do_mounts_initrd.c: fix sparse warning"

    Relevant Pages

    • Re: time for some drivers to be removed?
      ... > The code in question is obsolete if it wont build because its out of date ... There had been need of rain for many days. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: starting with 2.7
      ... Rik van Riel wrote: ... and additionally obsolete but used code like ... or developer effort. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [2.6 patch] remove BK documentation
      ... >> There's no longer a reason to document the obsolete BK usage. ... There had been need of rain for many days. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [2.6 patch] remove the obsolete raw driver
      ... >> obsolete. ... > In general there are staging rules for this sort of affair, ... There had been need of rain for many days. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 3ware queue depth [was: Re: HIGHMEM4G config for 1GB RAM on desktop?]
      ... > makes queue_depth writable for the 3ware driver. ... - the writeable queue_depth sysfs attr is fine, ... - I'm not so sure about the module parameter, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)