2009-04-15 14:02:19

by Tilman Schmidt

[permalink] [raw]
Subject: Kconfig Q: expressing a modularity dependency

My current attempts to port the Gigaset driver from isdn4linux
to CAPI require the following Kconfig dependency:

- If isdn4linux or kernelcapi or both are built as a module
(CONFIG_ISDN_I4L=m || CONFIG_ISDN_CAPI=m)
then gigaset can only be built as a module
(CONFIG_ISDN_DRV_GIGASET depends on m).

- If neither isdn4linux nor kernelcapi ar built as a module
(CONFIG_ISDN_I4L!=m && CONFIG_ISDN_CAPI!=m),
including the case that neither is being built at all
(CONFIG_ISDN_I4L=n && CONFIG_ISDN_CAPI=n),
then gigaset may be built statically or as a module
(all three tristate settings for CONFIG_ISDN_DRV_GIGASET are
legal).

How is that best expressed in Kconfig?

Thanks,
Tilman

--
Tilman Schmidt E-Mail: [email protected]
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Unge?ffnet mindestens haltbar bis: (siehe R?ckseite)


Attachments:
signature.asc (250.00 B)
OpenPGP digital signature