From: Michael Buesch <mb@bu3sch.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: arm allmodconfig
Date: Thu, 9 Aug 2007 00:38:05 +0200 [thread overview]
Message-ID: <200708090038.05320.mb@bu3sch.de> (raw)
In-Reply-To: <20070808152606.9ea3010f.akpm@linux-foundation.org>
On Thursday 09 August 2007 00:26:06 Andrew Morton wrote:
> On Thu, 9 Aug 2007 00:13:06 +0200
> Michael Buesch <mb@bu3sch.de> wrote:
>
> > On Wednesday 08 August 2007 23:57:05 Andrew Morton wrote:
> > > drivers/net/wireless/bcm43xx-mac80211/bcm43xx_main.c:4038: error: implicit declaration of function `ssb_pcihost_register'
> > > drivers/net/wireless/bcm43xx-mac80211/bcm43xx_main.c:4055: error: implicit declaration of function `ssb_pcihost_unregister'
> >
> > I have no idea how this is possible.
>
> tee hee
>
> > select SSB_PCIHOST
> > select SSB_DRIVER_PCICORE
>
> You used select. Anything is possible with select.
>
> You can do the below without an arm toolchain:
>
> setenv arch ARM
> make mrproper
> make allmodconfig
> akpm:/usr/src/25> grep BCM .config
> CONFIG_BT_HCIBCM203X=m
> CONFIG_BCM43XX=m
> CONFIG_BCM43XX_DEBUG=y
> CONFIG_BCM43XX_DMA=y
> CONFIG_BCM43XX_PIO=y
> CONFIG_BCM43XX_DMA_AND_PIO_MODE=y
> # CONFIG_BCM43XX_DMA_MODE is not set
> # CONFIG_BCM43XX_PIO_MODE is not set
> CONFIG_BCM43XX_MAC80211=m
> CONFIG_BCM43XX_MAC80211_PCI=y
> CONFIG_BCM43XX_MAC80211_PCMCIA=y
> CONFIG_BCM43XX_MAC80211_DEBUG=y
> CONFIG_BCM43XX_MAC80211_DMA=y
> CONFIG_BCM43XX_MAC80211_PIO=y
> CONFIG_BCM43XX_MAC80211_DMA_AND_PIO_MODE=y
> # CONFIG_BCM43XX_MAC80211_DMA_MODE is not set
> # CONFIG_BCM43XX_MAC80211_PIO_MODE is not set
> CONFIG_DVB_BCM3510=m
> akpm:/usr/src/25> grep SSB .config
> akpm:/usr/src/25>
>
> > So what is going on? CONFIG_BCM43XX_MAC80211_PCI must be enabled.
> > Otherwise the func call would be ifdef'ed out. So but if
> > it is enabled, it would SELECT SSB_PCIHOST. Which would enable
> > the declaration and definition of ssb_pcihost_register().
> > What am I missing?
>
> Just stop using select. It's busted.
Ok, I have no problem with that. BUT my users and other people
in the kernel community do certainly have. Nobody will find
the bcm43xx option anymore, if we depend on SSB.
I mean, people do even seriously complain about the filenames
of the firmware and so on.
So adding a dep on SSB would generate about 3 to 4
bugreports each day, I'd say from experience.
So, once you suggested that menuconfig should be changed to
show options "greyed out" when deps are not met. Are there
any patches available? Any starting point?
--
Greetings Michael.
next prev parent reply other threads:[~2007-08-08 22:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 21:57 arm allmodconfig Andrew Morton
2007-08-08 22:10 ` Ivo van Doorn
2007-08-08 22:13 ` Michael Buesch
2007-08-08 22:26 ` Andrew Morton
2007-08-08 22:32 ` Andrew Morton
2007-08-08 22:37 ` Andrew Morton
2007-08-08 22:38 ` Michael Buesch [this message]
2007-08-08 22:52 ` Andrew Morton
2007-08-08 23:03 ` Michael Buesch
2007-08-09 0:04 ` Michael Buesch
2007-08-09 0:21 ` Andrew Morton
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=200708090038.05320.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=akpm@linux-foundation.org \
--cc=linux-wireless@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).