From: John W. Linville <linville@tuxdriver.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org, b43-dev <b43-dev@lists.infradead.org>
Subject: [PATCH] b43: add default option to avoid duplicating device support with brcmsmac
Date: Thu, 12 Jan 2012 11:17:20 -0500 [thread overview]
Message-ID: <20120112161720.GI11093@tuxdriver.com> (raw)
In-Reply-To: <CACna6rxffpPhYVqKNttu79JET=NkBP4NrAayywQHWcj=mw=T9A@mail.gmail.com>
On Thu, Jan 12, 2012 at 05:11:50PM +0100, Rafa? Mi?ecki wrote:
> 2012/1/11 John W. Linville <linville@tuxdriver.com>:
> > +config B43_BCMA_EXTRA
> > + ? ? ? bool "Support for devices also supported by brcmsmac"
> > + ? ? ? depends on B43_BCMA
> > + ? ? ? default n
> > +
>
> Is this really *the* solution? I wonder if we can do whatever you're
> trying to do in a better way? To let final users try both drivers
> without recompiling kernel?
Saying "y" would let users try both drivers. That is up to the
distros or other kernel builders to choose.
At present, they have no choice but to let the two drivers race to
see who gets loaded first or whatever. I imagine that some would
prefer to have an option that prevents that.
> The description also isn't saying too much. I can't imagine anyone
> taking decision advisedly other than "n, as it's the default". On
> other hand, what should we put here? The whole comparison of drivers?
> Can be hard, but I really think there should be more info.
More info could be put in a "---help---" section. The summary line
could be different as well, if you can think of a better way to
describe the issue. I am open to suggestions.
John
--
John W. Linville Someday the world will need a hero, and you
linville at tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2012-01-12 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1326315180-29398-1-git-send-email-linville@tuxdriver.com>
2012-01-12 16:11 ` [PATCH] b43: add default option to avoid duplicating device support with brcmsmac Rafał Miłecki
2012-01-12 16:17 ` John W. Linville [this message]
2012-01-13 1:32 ` Peter Stuge
2012-01-13 19:20 ` John W. Linville
[not found] ` <CAGRGNgUkBUvoBJydcdprBXP0ufR+PQ6nXFXdW546xjHbQ-O2Bg@mail.gmail.com>
2012-01-13 19:20 ` John W. Linville
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=20120112161720.GI11093@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.com \
/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).