b44-ssb: Fix the SSB dependency hell
Subsystems (5)
PATCH 1/1 b44-ssb: Fix the SSB dependency hell
This fixes the SSB dependency hell and introduces some fake-options that only give some advice on what to select.
We live with these fake options only until menuconfig is able to tell more about needed dependencies and how to resolve them.
--
I think this should be merged into the ssb branch of wireless-dev, unless you plan to maintain a seperate branch for b44-ssb. But I think merging it with the ssb core is probably OK.
drivers/net/Kconfig +24 -5
@@ -1452,10 +1452,31 @@ config APRICOT <file:Documentation/networking/net-modules.txt>. The module will be called apricot. +config B44_DEP_HACK + bool + depends on SSB && SSB_PCIHOST && SSB_DRIVER_PCICORE + default y + +config B44_ADVICE_HACK + bool "B44 for PCI not available. Read the help text of this option!" + depends on !B44_DEP_HACK + ---help--- + The Broadcom 440x/47xx driver for PCI devices can not be enabled, + because the required dependencies are not selected. + + In order to be able to select the Broadcom 440x/47xx PCI driver, you + need to enable the following options first: + + CONFIG_SSB found in menu: + Device Drivers/Sonics Silicon Backplane/Sonics Silicon Backplane support + CONFIG_SSB_PCIHOST found in menu: + Device Drivers/Sonics Silicon Backplane/Support for SSB on PCI-bus host + CONFIG_SSB_DRIVER_PCICORE found in menu: + Device Drivers/Sonics Silicon Backplane/SSB PCI core driver + config B44 tristate "Broadcom 440x/47xx ethernet support" - depends on HAS_IOMEM - select SSB + depends on SSB select MII help If you have a network (Ethernet) controller of this type, say Y
@@ -1473,9 +1494,7 @@ config B44 config B44_PCI bool "Broadcom 440x PCI device support" - depends on B44 && NET_PCI - select SSB_PCIHOST - select SSB_DRIVER_PCICORE + depends on B44 && SSB_PCIHOST && SSB_DRIVER_PCICORE && NET_PCI default y help Support for Broadcom 440x PCI devices.
Quoted 6 lines · Michael Buesch
This fixes the SSB dependency hell and introduces some fake-options that only give some advice on what to select.
We live with these fake options only until menuconfig is able to tell more about needed dependencies and how to resolve them.
...
-ENOMENUCONFIGPATCH
IOW: $t\rightarrow\infty$
Quoted 8 lines
drivers/net/Kconfig +8
-0+config B44_ADVICE_HACK + bool "B44 for PCI not available. Read the help text of this option!" + depends on !B44_DEP_HACK + ---help--- + The Broadcom 440x/47xx driver for PCI devices can not be enabled, + because the required dependencies are not selected. + + In order to be able to select the Broadcom 440x/47xx PCI driver, you
drivers/net/Kconfig config APRICOT · line 1476
Quoted 10 lines
drivers/net/Kconfig +9
-0+ need to enable the following options first: + + CONFIG_SSB found in menu: + Device Drivers/Sonics Silicon Backplane/Sonics Silicon Backplane support + CONFIG_SSB_PCIHOST found in menu: + Device Drivers/Sonics Silicon Backplane/Support for SSB on PCI-bus host + CONFIG_SSB_DRIVER_PCICORE found in menu: + Device Drivers/Sonics Silicon Backplane/SSB PCI core driver +
That's horrible - you shouldn't force the user to manually enable three options.
What is the problem you are trying to solve?
The dependencies of SSB?
There are less horrible solutions for this issue, e.g. [1]:
drivers/ssb/Kconfig:
config SSB_POSSIBLE
bool depends on EXPERIMENTAL && HAS_IOMEM
config SSB
tristate
config SSB_PCIHOST_POSSIBLE
bool depends on SSB_POSSIBLE && PCI
config SSB_PCIHOST
bool
drivers/net/Kconfig:
config B44
tristate "Broadcom 440x/47xx ethernet support" depends on SSB_PCIHOST_POSSIBLE select SSB select SSB_PCIHOST
I can make a complete patch for the SSB options, but I need some pieces of information before starting:
Is there any extremely good reason why options like SSB or SSB_PCIHOST have to be user visible?
And according to the kconfig help text, we should remove the B44_PCI option and enable the code unconditionally?
(Or what was the person writing this help text smoking^Wthinking when
writing it?)
cu
Adrian
[1] incomplete example for demonstrating an idea
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedJohannes Berg
maintainerQuoted 1 line · Adrian Bunk
-ENOMENUCONFIGPATCH
Has anybody decided how it could possibly even look like anyhow? It should be fixed, but nobody has a plan.
Quoted 2 lines
That's horrible - you shouldn't force the user to manually enable three options.
Well, akpm says: "select is broken. do not ever use it"
Quoted 1 line
config
SSB_PCIHOST_POSSIBLE
[...]
Quoted 3 lines
depends on
SSB_PCIHOST_POSSIBLE
select SSB
selectSSB_PCIHOST
That would, indeed, be possible. But it's ... ugly ... you've now effectively pushed the information on what *SSB* depends on into each SSB *user* instead of SSB itself...
Quoted 2 lines
Is there any extremely good reason why options like SSB or
SSB_PCIHOSThave to be user visible?
Yes. Embedded systems like the small Linksys routers come with SSB as the system bus. No PCI/PCIHOST.
Quoted 4 lines
And according to the kconfig help text, we should remove the
B44_PCIoption and enable the code unconditionally?
(Or what was the person writing this help text smoking^Wthinking when
writing it?)
Same reason. They have a b44 core there but no pci.
johannes
Quoted 6 lines · Johannes Berg
Quoted 1 line · Adrian Bunk
-ENOMENUCONFIGPATCHHas anybody decided how it could possibly even look like anyhow? It should be fixed, but nobody has a plan.
The simplest idea would be that an option select'ing some other option inherits the dependencies of the latter. That should fix all problems select currently has.
There are for sure some problems hidden that will show up during implementation, but since noone is implementing it we'll never know...
Quoted 4 lines
Quoted 2 lines
That's horrible - you shouldn't force the user to manually enable three options.
Well, akpm says: "select is broken. do not ever use it"
select works fine if you understand the pitfalls.
Kconfig is a _user interface_, and making using it easy for the user is therefore important.
Whenever there's a mistake in a help text or something confusing users will run into problems with the kernel they compiled.
Quoted 10 lines
Quoted 1 line
config
SSB_PCIHOST_POSSIBLE[...]
Quoted 3 lines
depends on
SSB_PCIHOST_POSSIBLE
select SSB
selectSSB_PCIHOSTThat would, indeed, be possible. But it's ... ugly ... you've now effectively pushed the information on what *SSB* depends on into each SSB *user* instead of SSB itself...
No, this information is still in drivers/ssb/Kconfig.
This would replace:
config B44
depends on SSB_PCIHOST
with:
config B44
depends on SSB_PCIHOST_POSSIBLE
select SSB_PCIHOST
That's an easily understandable pattern without redundant information about the required dependencies of SSB_PCIHOST.
Quoted 5 lines
Quoted 2 lines
Is there any extremely good reason why options like SSB or
SSB_PCIHOSThave to be user visible?Yes. Embedded systems like the small Linksys routers come with SSB as the system bus. No PCI/PCIHOST.
OK.
Quoted 6 lines
Quoted 4 lines
And according to the kconfig help text, we should remove the
B44_PCIoption and enable the code unconditionally?
(Or what was the person writing this help text smoking^Wthinking when
writing it?)Same reason. They have a b44 core there but no pci.
OK, that's understandable.
But the kconfig user currently only gets:
config B44_PCI
bool "Broadcom 440x PCI device support"
...
help
Support for Broadcom 440x PCI devices.
Say Y, unless you know what you are doing.
If you say N here I will _not_ listen to your
bugreports!An example how to make it better:
config USB_OHCI_HCD_SSB
bool "OHCI support for the Broadcom SSB OHCI core (embedded systems only)"
...
help
Support for the Sonics Silicon Backplane (SSB) attached Broadcom USB OHCI core.
This device is only present in some embedded devices with Broadcom based SSB bus.
If unsure, say N.
That's the difference between a silly sounding help text ("I will _not_ listen to your bugreports!") and a help text that gives the kconfig user all required information ("only present in some embedded devices").
And I'm not yet convinced B44_PCI is really worth bothering the user with - what about automatically enabling PCI support in the driver if PCI support is enabled in the kernel?
Quoted 1 line
johannes
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 98 lines · On Saturday 11 August 2007 03:41:11 Adrian Bunk wrote:
Quoted 6 lines · Johannes Berg
Quoted 1 line · Adrian Bunk
-ENOMENUCONFIGPATCHHas anybody decided how it could possibly even look like anyhow? It should be fixed, but nobody has a plan.
The simplest idea would be that an option select'ing some other option inherits the dependencies of the latter. That should fix all problems select currently has.
There are for sure some problems hidden that will show up during implementation, but since noone is implementing it we'll never know...
Quoted 4 lines
Quoted 2 lines
That's horrible - you shouldn't force the user to manually enable three options.
Well, akpm says: "select is broken. do not ever use it"
select works fine if you understand the pitfalls.
Kconfigis a_userinterface_, and making using it easy for the user is therefore important.Whenever there's a mistake in a help text or something confusing users will run into problems with the kernel they compiled.
Quoted 10 lines
Quoted 1 line
config
SSB_PCIHOST_POSSIBLE[...]
Quoted 3 lines
depends on
SSB_PCIHOST_POSSIBLE
select SSB
selectSSB_PCIHOSTThat would, indeed, be possible. But it's ... ugly ... you've now effectively pushed the information on what *SSB* depends on into each SSB *user* instead of SSB itself...
No, this information is still in
drivers/ssb/Kconfig.This would replace:
config B44
depends onSSB_PCIHOSTwith:
config B44
depends onSSB_PCIHOST_POSSIBLE
selectSSB_PCIHOSTThat's an easily understandable pattern without redundant information about the required dependencies of
SSB_PCIHOST.Quoted 5 lines
Quoted 2 lines
Is there any extremely good reason why options like SSB or
SSB_PCIHOSThave to be user visible?Yes. Embedded systems like the small Linksys routers come with SSB as the system bus. No PCI/PCIHOST.
OK.
Quoted 6 lines
Quoted 4 lines
And according to the kconfig help text, we should remove the
B44_PCIoption and enable the code unconditionally?
(Or what was the person writing this help text smoking^Wthinking when
writing it?)Same reason. They have a b44 core there but no pci.
OK, that's understandable.
But the kconfig user currently only gets:
config
B44_PCIbool "Broadcom 440x PCI device support" ... help Support for Broadcom 440x PCI devices. Say Y, unless you know what you are doing. If you say N here I will _not_ listen to your bugreports!An example how to make it better:
config
USB_OHCI_HCD_SSB
bool "OHCI support for the Broadcom SSB OHCI core (embedded systems only)"
...
help
Support for the Sonics Silicon Backplane (SSB) attached Broadcom USB OHCI core.This device is only present in some embedded devices with Broadcom based SSB bus.
If unsure, say N.
Quoted 8 lines
That's the difference between a silly sounding help text ("I will _not_ listen to your bugreports!") and a help text that gives the kconfig user all required information ("only present in some embedded devices").
And I'm not yet convinced
B44_PCIis really worth bothering the user with - what about automatically enabling PCI support in the driver if PCI support is enabled in the kernel?
That's all a silly discussion, guys.
I personally do _not_ care which way we do this.
BUT: My users do care. There is currently no way telling them to first enable SSB, when they want to select b44 (for example).
Select _does_ introduce breakage. I did use select and I am pretty sure I got the dependencies right. And it _still_ broken on weird architectures.
So, I do not care how this is implemented. I do care however, that users do get an advice (at least) on what to do. And that's what my patch does. If someone has a better idea, please provide a patch.
Signature · 1 line
Greetings Michael.
Quoted 5 lines · Michael Buesch
That's all a silly discussion, guys.
I personally do _not_ care which way we do this.
BUT: My users do care. There is currently no way telling them to first enable SSB, when they want to select b44 (for example).
The current status quo is that select handles it.
You want to send the users into menus to manually enable options. That's worse for your users.
Quoted 2 lines
Select _does_ introduce breakage. I did use select and I am pretty sure I got the dependencies right. And it _still_ broken on weird architectures.
Have you looked at how I proposed to handle the SSB dependencies?
If yes, why is this broken?
Quoted 3 lines
So, I do not care how this is implemented. I do care however, that users do get an advice (at least) on what to do. And that's what my patch does. If someone has a better idea, please provide a patch.
I do care about your users.
And offering more options than required or manually sending users into other menus are bad thing for your users.
Quoted 1 line
Greetings Michael.
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 2 lines · On Saturday 11 August 2007 16:30:02 Adrian Bunk wrote:
And offering more options than required or manually sending users into other menus are bad thing for your users.
Breaking compilations are as bad.
So, does your example actually work in practice and not only in theory, too? My select stuff should have worked in theory, too. But it broke, for whatever reasons on whatever weird setups.
We somehow are in an endless loop here:
loop:
implement it with select
people complain select it bad and suggest to implement it with depends on implement it with depends on
either
users don't find it anymore
users complain
or
it needs way to tell the user what to select first developers complain
goto loop
;)
Signature · 1 line
Greetings Michael.
RFC PATCH 1/1 improve the SSB dependencies
Quoted 23 lines · Michael Buesch
Quoted 2 lines · On Saturday 11 August 2007 16:30:02 Adrian Bunk wrote:
And offering more options than required or manually sending users into other menus are bad thing for your users.
Breaking compilations are as bad.
So, does your example actually work in practice and not only in theory, too? My select stuff should have worked in theory, too. But it broke, for whatever reasons on whatever weird setups.We somehow are in an endless loop here:
loop:
implement it with select
people complain select it bad and suggest to implement it with depends on implement it with depends on
either
users don't find it anymore
users complain
or
it needs way to tell the user what to select first developers complain
goto loop
Quoted 1 line
;)
It's your fault that you base your work on an algorithm lacking the essential steps
fix it properly
goto out
;-)
More seriously, below is a patch doing what I have in mind.
Quoted 1 line
Greetings Michael.
cu
Adrian
<-- snip -->
This patch adds *_POSSIBLE helper variables for all SSB* variables that get select'ed. They indicate whether this variable can be select'ed,
IOW: whether it's dependencies are fulfilled.
Usage in drivers:
If you need SSB support:
config FOO
tristate "foo"
depends on SSB_POSSIBLE
select SSB
If you need SSB_BAZ support:
config BAR
tristate "bar"
depends on SSB_BAZ_POSSIBLE
select SSB
select SSB_BAZ
If your driver needs SSB and has optional functionality requiring SSB_BAZ:
config FOOBAR
tristate "foobar
depends on SSB_POSSIBLE
select SSB
# due to being "bool" this suboption shouldn't directly select SSB # SSB is already select'ed by FOOBAR config FOOBAR_BAZ bool "baz support in foobar" depends on FOOBAR && SSB_BAZ_POSSIBLE select SSB_BAZ
After this patch, SSB_BAZ can be one of:
- SSB_PCIHOST
- SSB_DRIVER_PCICORE
- SSB_PCMCIAHOST
- SSB_DEBUG
Additional changes in this patch:
- small help text changes
- B44_PCI is no longer usr visible (automatically enabled when possible)
- let SSB_SILENT depend on EMBEDDED (unless you are in a very space restricted environment you don't need to enable it)
- make the following options no longer user visible
(they are select'ed when required):
- SSB_PCIHOST
- SSB_DRIVER_PCICORE
- SSB_PCMCIAHOST
---
drivers/net/Kconfig | 12 --- drivers/net/wireless/bcm43xx-mac80211/Kconfig | 10 +- drivers/ssb/Kconfig | 72 ++++++++++-------- drivers/usb/host/Kconfig | 4 - 4 files changed, 51 insertions(+), 47 deletions(-)
6ed573214282b96e7714b33b89a7221c01efbb86
drivers/net/Kconfig +3 -9
@@ -1435,6 +1435,7 @@ config APRICOT config B44 tristate "Broadcom 440x/47xx ethernet support" depends on HAS_IOMEM + depends on SSB_POSSIBLE select SSB select MII help
@@ -1452,17 +1453,10 @@ config B44 called b44. config B44_PCI - bool "Broadcom 440x PCI device support" - depends on B44 && NET_PCI - select SSB_PCIHOST + bool + depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE select SSB_DRIVER_PCICORE default y - help - Support for Broadcom 440x PCI devices. - - Say Y, unless you know what you are doing. - If you say N here I will _not_ listen to your - bugreports! config FORCEDETH tristate "nForce Ethernet support"
drivers/net/wireless/bcm43xx-mac80211/Kconfig +5 -5
@@ -1,6 +1,6 @@ config BCM43XX_MAC80211 tristate "Broadcom BCM43xx wireless support (mac80211 stack)" - depends on MAC80211 && WLAN_80211 && EXPERIMENTAL + depends on MAC80211 && WLAN_80211 && SSB_POSSIBLE && EXPERIMENTAL select FW_LOADER select SSB select HW_RANDOM
@@ -10,8 +10,8 @@ config BCM43XX_MAC80211 config BCM43XX_MAC80211_PCI bool "BCM43xx PCI device support" - depends on BCM43XX_MAC80211 && PCI - select SSB_PCIHOST + depends on BCM43XX_MAC80211 + depends on SSB_DRIVER_PCICORE_POSSIBLE select SSB_DRIVER_PCICORE default y ---help---
@@ -24,7 +24,7 @@ config BCM43XX_MAC80211_PCI config BCM43XX_MAC80211_PCMCIA bool "BCM43xx PCMCIA device support" - depends on BCM43XX_MAC80211 && PCMCIA + depends on BCM43XX_MAC80211 && SSB_PCMCIAHOST_POSSIBLE select SSB_PCMCIAHOST ---help--- Broadcom 43xx PCMCIA device support.
@@ -45,7 +45,7 @@ config BCM43XX_MAC80211_PCMCIA config BCM43XX_MAC80211_DEBUG bool "Broadcom BCM43xx debugging (RECOMMENDED)" depends on BCM43XX_MAC80211 - select SSB_DEBUG if !SSB_SILENT + select SSB_DEBUG if SSB_DEBUG_POSSIBLE default y ---help--- Broadcom 43xx debugging messages.
drivers/ssb/Kconfig +41 -31
121 lines not on this page · raw message
drivers/usb/host/Kconfig +2 -2
@@ -101,6 +101,7 @@ config USB_OHCI_HCD depends on USB && USB_ARCH_HAS_OHCI select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 select I2C if ARCH_PNX4008 + select SSB if USB_OHCI_HCD_SSB ---help--- The Open Host Controller Interface (OHCI) is a standard for accessing USB 1.1 host controller hardware. It does more in hardware than Intel's
@@ -156,8 +157,7 @@ config USB_OHCI_HCD_PCI config USB_OHCI_HCD_SSB bool "OHCI support for the Broadcom SSB OHCI core (embedded systems only)" - depends on USB_OHCI_HCD && ((USB_OHCI_HCD=m && SSB) || (USB_OHCI_HCD=y && SSB=y)) && EXPERIMENTAL - default n + depends on USB_OHCI_HCD && SSB_POSSIBLE && EXPERIMENTAL ---help--- Support for the Sonics Silicon Backplane (SSB) attached Broadcom USB OHCI core.
Re: [RFC: -mm patch] improve the SSB dependencies
Ok, I'll give it a try, with small modifications.
Quoted 3 lines · Adrian Bunk
Additional changes in this patch:
- small help text changes
-B44_PCIis no longer usr visible (automatically enabled when possible)
I think we want that to be selectable, as it's not needed on some embedded devices. And we need to save memory there.
Quoted 2 lines
- let
SSB_SILENTdepend on EMBEDDED (unless you are in a very space restricted environment you don't need to enable it)
Good idea.
Quoted 5 lines
- make the following options no longer user visible (they are select'ed when required):
-SSB_PCIHOST-
SSB_DRIVER_PCICORE
No, we need that to be selectable.
Quoted 241 lines
-
SSB_PCMCIAHOSTSigned-off-by Adrian Bunk <[email protected]>---
drivers/net/Kconfig | 12 --- drivers/net/wireless/bcm43xx-mac80211/Kconfig | 10 +- drivers/ssb/Kconfig | 72 ++++++++++-------- drivers/usb/host/Kconfig | 4 - 4 files changed, 51 insertions(+), 47 deletions(-)
6ed573214282b96e7714b33b89a7221c01efbb86drivers/net/Kconfig +3
-9@@ -1435,6 +1435,7 @@ config APRICOT config B44 tristate "Broadcom 440x/47xx ethernet support" depends on HAS_IOMEM + depends on SSB_POSSIBLE select SSB select MII help@@ -1452,17 +1453,10 @@ config B44 called b44. config B44_PCI - bool "Broadcom 440x PCI device support" - depends on B44 && NET_PCI - select SSB_PCIHOST + bool + depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE select SSB_DRIVER_PCICORE default y - help - Support for Broadcom 440x PCI devices. - - Say Y, unless you know what you are doing. - If you say N here I will _not_ listen to your - bugreports! config FORCEDETH tristate "nForce Ethernet support"drivers/net/wireless/bcm43xx-mac80211/Kconfig +5
-5@@ -1,6 +1,6 @@ config BCM43XX_MAC80211 tristate "Broadcom BCM43xx wireless support (mac80211 stack)" - depends on MAC80211 && WLAN_80211 && EXPERIMENTAL + depends on MAC80211 && WLAN_80211 && SSB_POSSIBLE && EXPERIMENTAL select FW_LOADER select SSB select HW_RANDOM@@ -10,8 +10,8 @@ config BCM43XX_MAC80211 config BCM43XX_MAC80211_PCI bool "BCM43xx PCI device support" - depends on BCM43XX_MAC80211 && PCI - select SSB_PCIHOST + depends on BCM43XX_MAC80211 + depends on SSB_DRIVER_PCICORE_POSSIBLE select SSB_DRIVER_PCICORE default y ---help---@@ -24,7 +24,7 @@ config BCM43XX_MAC80211_PCI config BCM43XX_MAC80211_PCMCIA bool "BCM43xx PCMCIA device support" - depends on BCM43XX_MAC80211 && PCMCIA + depends on BCM43XX_MAC80211 && SSB_PCMCIAHOST_POSSIBLE select SSB_PCMCIAHOST ---help--- Broadcom 43xx PCMCIA device support.@@ -45,7 +45,7 @@ config BCM43XX_MAC80211_PCMCIA config BCM43XX_MAC80211_DEBUG bool "Broadcom BCM43xx debugging (RECOMMENDED)" depends on BCM43XX_MAC80211 - select SSB_DEBUG if !SSB_SILENT + select SSB_DEBUG if SSB_DEBUG_POSSIBLE default y ---help--- Broadcom 43xx debugging messages.drivers/ssb/Kconfig +41
-31@@ -1,37 +1,42 @@ menu "Sonics Silicon Backplane" +config SSB_POSSIBLE + bool + depends on EXPERIMENTAL && HAS_IOMEM + default y + config SSB tristate "Sonics Silicon Backplane support" - depends on EXPERIMENTAL && HAS_IOMEM + depends on SSB_POSSIBLE help - Support for the Sonics Silicon Backplane bus + Support for the Sonics Silicon Backplane bus. + You only need to enable this option if you are + configuring a kernel for an embedded system with + this bus. - The module will be called ssb + The module will be called ssb. - If unsure, say M + If unsure, say N. -config SSB_PCIHOST - bool "Support for SSB on PCI-bus host" - depends on SSB && PCI +config SSB_PCIHOST_POSSIBLE + bool + depends on SSB_POSSIBLE && PCI default y - help - Support for a Sonics Silicon Backplane on top - of a PCI device. - If unsure, say Y +config SSB_PCIHOST + bool -config SSB_PCMCIAHOST - bool "Support for SSB on PCMCIA-bus host" - depends on SSB && PCMCIA - help - Support for a Sonics Silicon Backplane on top - of a PCMCIA device. +config SSB_PCMCIAHOST_POSSIBLE + bool + depends on SSB_POSSIBLE && PCMCIA + default y - If unsure, say N +config SSB_PCMCIAHOST + bool config SSB_SILENT bool "No SSB kernel messages" - depends on SSB + depends on SSB && EMBEDDED help This option turns off all Sonics Silicon Backplane printks. Note that you won't be able to identify problems, once@@ -39,30 +44,35 @@ config SSB_SILENT This might only be desired for production kernels on embedded devices to reduce the kernel size. - Say N + If unsure, say N. + +config SSB_DEBUG_POSSIBLE + bool + depends on SSB && !SSB_SILENT + default y config SSB_DEBUG bool "SSB debugging" - depends on SSB && !SSB_SILENT + depends on SSB_DEBUG_POSSIBLE help This turns on additional runtime checks and debugging messages. Turn this on for SSB troubleshooting. - If unsure, say N + If unsure, say N. config SSB_SERIAL bool depends on SSB # ChipCommon and ExtIf serial support routines. -config SSB_DRIVER_PCICORE - bool "SSB PCI core driver" - depends on SSB && SSB_PCIHOST - help - Driver for the Sonics Silicon Backplane attached - Broadcom PCI core. +config SSB_DRIVER_PCICORE_POSSIBLE + bool + depends on SSB_PCIHOST_POSSIBLE + default y - If unsure, say Y +config SSB_DRIVER_PCICORE + bool + select SSB_PCIHOST config SSB_PCICORE_HOSTMODE bool "Hostmode support for SSB PCI core"@@ -78,7 +88,7 @@ config SSB_DRIVER_MIPS Driver for the Sonics Silicon Backplane attached Broadcom MIPS core. - If unsure, say N + If unsure, say N. config SSB_DRIVER_EXTIF bool "SSB Broadcom EXTIF core driver"@@ -87,6 +97,6 @@ config SSB_DRIVER_EXTIF Driver for the Sonics Silicon Backplane attached Broadcom EXTIF core. - If unsure, say N + If unsure, say N. endmenudrivers/usb/host/Kconfig +2
-2@@ -101,6 +101,7 @@ config USB_OHCI_HCD depends on USB && USB_ARCH_HAS_OHCI select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 select I2C if ARCH_PNX4008 + select SSB if USB_OHCI_HCD_SSB ---help--- The Open Host Controller Interface (OHCI) is a standard for accessing USB 1.1 host controller hardware. It does more in hardware than Intel's@@ -156,8 +157,7 @@ config USB_OHCI_HCD_PCI config USB_OHCI_HCD_SSB bool "OHCI support for the Broadcom SSB OHCI core (embedded systems only)" - depends on USB_OHCI_HCD && ((USB_OHCI_HCD=m && SSB) || (USB_OHCI_HCD=y && SSB=y)) && EXPERIMENTAL - default n + depends on USB_OHCI_HCD && SSB_POSSIBLE && EXPERIMENTAL ---help--- Support for the Sonics Silicon Backplane (SSB) attached Broadcom USB OHCI core.
Re: [RFC: -mm patch] improve the SSB dependencies
Quoted 1 line · Michael Buesch
Ok, I'll give it a try, with small modifications.
Thanks.
Quoted 8 lines · Adrian Bunk
Quoted 3 lines
Additional changes in this patch:
- small help text changes
-B44_PCIis no longer usr visible (automatically enabled when possible)I think we want that to be selectable, as it's not needed on some embedded devices. And we need to save memory there.
...
Makes sense, but then:
config B44_PCI
bool "Broadcom 440x PCI device support" if EMBEDDED ... default y ...
I don't care about how many options we present if CONFIG_EMBEDDED=y, but for the normal CONFIG_EMBEDDED=n case we should not bother the user with this option.
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedRe: [RFC: -mm patch] improve the SSB dependencies
Quoted 17 lines · Adrian Bunk
Quoted 1 line · Michael Buesch
Ok, I'll give it a try, with small modifications.
Thanks.
Quoted 8 lines · Adrian Bunk
Quoted 3 lines
Additional changes in this patch:
- small help text changes
-B44_PCIis no longer usr visible (automatically enabled when possible)I think we want that to be selectable, as it's not needed on some embedded devices. And we need to save memory there.
...Makes sense, but then:
config
B44_PCI
Quoted 8 lines
bool "Broadcom 440x PCI device support" if EMBEDDED ... default y ...I don't care about how many options we present if
CONFIG_EMBEDDED=y, but for the normalCONFIG_EMBEDDED=ncase we should not bother the user with this option.
Was all this resolved? Was there another patch? If so, I missed it...
John
Signature · 2 lines
John W. Linville [email protected]
Re: [RFC: -mm patch] improve the SSB dependencies
Quoted 23 lines · On Wednesday 15 August 2007 02:40:35 John W. Linville wrote:
Quoted 22 lines · Adrian Bunk
Quoted 1 line · Michael Buesch
Ok, I'll give it a try, with small modifications.
Thanks.
Quoted 8 lines · Adrian Bunk
Quoted 3 lines
Additional changes in this patch:
- small help text changes
-B44_PCIis no longer usr visible (automatically enabled when possible)I think we want that to be selectable, as it's not needed on some embedded devices. And we need to save memory there.
...Makes sense, but then:
config
B44_PCIbool "Broadcom 440x PCI device support" if EMBEDDED ... default y ...
Quoted 5 lines
Quoted 3 lines
I don't care about how many options we present if
CONFIG_EMBEDDED=y, but for the normalCONFIG_EMBEDDED=ncase we should not bother the user with this option.Was all this resolved? Was there another patch? If so, I missed it...
I am going to send one, soon.
Signature · 1 line
Greetings Michael.