From: Ivo van Doorn <ivdoorn@gmail.com>
To: Gertjan van Wingerde <gwingerde@kpnplanet.nl>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
linux-wireless@vger.kernel.org,
rt2400-devel@lists.sourceforge.net, linville@tuxdriver.com,
akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH -mm] rt2x00: fix Kconfig dependencies
Date: Sun, 28 Sep 2008 11:24:07 +0200 [thread overview]
Message-ID: <200809281124.07434.IvDoorn@gmail.com> (raw)
In-Reply-To: <48DF4863.9070806@kpnplanet.nl>
On Sunday 28 September 2008, Gertjan van Wingerde wrote:
> Ivo,
>
> Ivo van Doorn wrote:
> >> Ivo, please explain what rt2x00 module(s) you want to be built. In
> >> English
> >> if possible, not in Kconfig language...
> >>
> >
> > There are 3 kind of rt2x00 modules:
> > rt2x00lib
> > rt2x00pci/usb
> > rt2x00 driver (rt2400pci, rt2500pci, rt61pci, rt2500usb, rt73usb)
> >
> > When the user selects any of the rt2x00 drivers, the rt2x00pci/usb and rt2x00lib
> > are selected. For rt2x00lib there are some additional configuration options like
> > RT2X00_LIB_RFKILL and RT2X00_LIB_LEDS which will build into rt2x00lib.
> >
> > This means that when rt2400pci is selected as module, rt2x00pci and rt2x00lib
> > must be built as modules as well and when rt2400pci is selected as buildin
> > rt2x00pci and rt2x00lib must be buildin as well.
> >
> > But with the optional rt2x00lib configuration options the breakage you reported
> > is possible. So we either need:
> > 1) Force rt2x00lib / driver to be compiled as module when RFKILL/LEDS were
> > compiled as module
> > 2) Disable config option when invalid config combination is found
> >
> > Personally I would favor 1), because 2) could lead to confusion to users
> > who think they selected everything they needed to enable support for it in
> > rt2x00.
> >
>
> Find attached a patch that implements option 2, along with adding a
> warning to the user when rfkill support in rt2x00 is disabled due to the
> invalid config combination. I've looked at implementing option 1, but
> couldn't find a way to do it without disabling the entire rt2x00 module
> when rfkill wasn't available.
>
> I guess we can live with this option for now, until we have figured out
> how to do option 1.
Sounds good, but please change RT2X00 in RT2X00_LIB
default y if (RT2X00=y && RFKILL=y) || (RT2X00=m && RFKILL!=n)
Could you also do a similar thing for the LED handling?
That way we can fix the entire thing with a single patch. :)
Thanks,
Ivo
next prev parent reply other threads:[~2008-09-28 9:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 23:29 [PATCH -mm] rt2x00: fix Kconfig dependencies Randy Dunlap
2008-09-23 7:07 ` Ivo van Doorn
2008-09-23 16:25 ` Randy Dunlap
2008-09-23 17:51 ` Ivo van Doorn
2008-09-23 21:03 ` Randy Dunlap
2008-09-23 21:57 ` Larry Finger
2008-09-23 22:09 ` Ivo van Doorn
2008-09-23 22:30 ` Randy Dunlap
2008-09-23 22:45 ` Ivo van Doorn
2008-09-28 9:03 ` Gertjan van Wingerde
2008-09-28 9:24 ` Ivo van Doorn [this message]
2008-09-28 13:16 ` Gertjan van Wingerde
2008-09-28 14:12 ` Ivo van Doorn
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=200809281124.07434.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=akpm@linux-foundation.org \
--cc=gwingerde@kpnplanet.nl \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=randy.dunlap@oracle.com \
--cc=rt2400-devel@lists.sourceforge.net \
/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).