Re: [PATCH] disable builtin modules

On Sun, 20 Mar 2005 10:51:41 +0100 (MET), Jan Engelhardt <[EMAIL PROTECTED]> 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

Re: [PATCH] disable builtin modules

>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

Re: [PATCH] disable builtin modules

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

Re: [PATCH] disable builtin modules

On Sun, 20 Mar 2005 10:51:41 +0100 (MET), Jan Engelhardt [EMAIL PROTECTED] 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

[PATCH] disable builtin modules

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. Problem: Say that your Firewire PHY breaks and you find yourself unable to

[PATCH] disable builtin modules

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. Problem: Say that your Firewire PHY breaks and you find yourself unable to