From: Adrian Bunk <bunk@kernel.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: John Linville <linville@tuxdriver.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [PATCH] b44-ssb: Fix the SSB dependency hell
Date: Sat, 11 Aug 2007 02:43:41 +0200 [thread overview]
Message-ID: <20070811004341.GA22213@stusta.de> (raw)
In-Reply-To: <200708110208.21624.mb@bu3sch.de>
On Sat, Aug 11, 2007 at 02:08:21AM +0200, Michael Buesch wrote:
> 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$
> +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
> +
>...
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
--
"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 Seed
next prev parent reply other threads:[~2007-08-11 0:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-11 0:08 [PATCH] b44-ssb: Fix the SSB dependency hell Michael Buesch
2007-08-11 0:43 ` Adrian Bunk [this message]
2007-08-11 0:57 ` Johannes Berg
2007-08-11 1:41 ` Adrian Bunk
2007-08-11 9:36 ` Michael Buesch
2007-08-11 14:30 ` Adrian Bunk
2007-08-11 14:42 ` Michael Buesch
2007-08-11 23:08 ` [RFC: -mm patch] improve the SSB dependencies Adrian Bunk
2007-08-12 12:00 ` Michael Buesch
2007-08-12 22:44 ` Adrian Bunk
2007-08-15 0:40 ` John W. Linville
2007-08-15 12:47 ` Michael Buesch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070811004341.GA22213@stusta.de \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).