Re: tristate and bool not enogh for Kconfig anymore

2007-10-22 Thread Henrik Carlqvist
On Mon, 22 Oct 2007 13:46:43 +0200 > > In that kernel CONFIG_SCSI_QLA_FC is set to y but still it is not > > possible to boot from any of those cards as the driver requires a > > firmware file. > Then an initrd-less boot is impossible for this > device - even the modular approach needs > an initrd

Re: tristate and bool not enogh for Kconfig anymore

2007-10-21 Thread Henrik Carlqvist
> config FOO > depends on BAR && m > > restricts FOO to module-only. Thanks alot! That really did the trick! With the following file: -8<--- config SCSI_QLA_FC tristate "QLogic QLA2XXX Fibre Channel Support" depends on PCI && SCSI && m se

Re: tristate and bool not enogh for Kconfig anymore

2007-10-21 Thread Henrik Carlqvist
On Sun, 21 Oct 2007 00:47:38 -0400 [EMAIL PROTECTED] wrote: > On Sat, 20 Oct 2007 21:17:00 +0200, Sam Ravnborg said: > > I assume > > depends on MODULES > > > > should do the trick. > > Umm... I think that will work backwards, and give you CONFIG_FOO=y > if.f the kernel *supports* modules. W

tristate and bool not enogh for Kconfig anymore

2007-10-20 Thread Henrik Carlqvist
I think there is a need for Kconfig to specify that a functionality could be built as a module or not built at all. Some drivers require that firmware is loaded when the driver is initialized. The kernel has functionalities for this by using a userspace program. However, this userspace program is