From: "John W. Linville" <linville@tuxdriver.com>
To: "J.A. Magallón" <jamagallon@ono.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.27-git3: rtl8169 oops and wireless missing symbols
Date: Tue, 14 Oct 2008 12:59:31 -0400 [thread overview]
Message-ID: <20081014165931.GC3349@tuxdriver.com> (raw)
In-Reply-To: <20081014014406.318db8e7@werewolf.home>
On Tue, Oct 14, 2008 at 01:44:06AM +0200, J.A. Magallón wrote:
> On Mon, 13 Oct 2008 19:24:33 -0400, "John W. Linville" <linville@tuxdriver.com> wrote:
> > config WIRELESS_OLD_REGULATORY
> > bool "Old wireless static regulatory definitions"
> ...
> >
> > Is this not clear enough?
> >
>
> NO.
>
> I'm a complete literate in wireles internals. Not in other areas. And I
> don't undestand a word about regulations and so on. The only thing
> I see there is 'OLD WAY of doing things', so I disable it. I expect
> two things:
You blindly disable things because they say "old", you don't update
anything in your userland, and then you expect things to work?
> - As it is an optional thing I can toggle, no driver depends on it.
> - If I choose a driver that depends on it, it will get automagically
> selected.
And this fits neither of your scenarios. The drivers will work just
fine with the code as you built it -- even better if you update your
userland with the required component.
The problem is that you were setting a module option that no longer
existed because you didn't want to do things the "old" way. Should we
support a useless module option, even when you expressly disable the
compatibility option that provides it?
> So, please, if migration is not finished:
>
> - Default it as Y, or add a depend on every driver that uses it
> - Hide it under the famous 'crazy hacker-only things' boolean
Neither of these are necessary -- just stop specifying the module
option that doesn't exist, or simply enable the compatibility option
in the kernel.
> It is enough to have to choose between mac80211 and ieee80211.
Perhaps we should change the name of "ieee80211" to
"old_ipw2x00_support_crap"?
John
--
John W. Linville Linux should be at the core
linville@tuxdriver.com of your literate lifestyle.
next prev parent reply other threads:[~2008-10-14 17:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 23:02 Linux 2.6.27-git3: rtl8169 oops and wireless missing symbols J.A. Magallón
2008-10-13 23:12 ` David Miller
2008-10-13 23:24 ` J.A. Magallón
2008-10-14 0:30 ` J.A. Magallón
2008-10-14 19:33 ` Francois Romieu
2008-10-14 20:03 ` J.A. Magallón
2008-10-14 23:39 ` Stefan Lippers-Hollmann
2008-10-13 23:24 ` John W. Linville
2008-10-13 23:44 ` J.A. Magallón
2008-10-14 16:59 ` John W. Linville [this message]
2008-10-14 0:23 ` Luis R. Rodriguez
2008-10-14 0:23 ` Luis R. Rodriguez
2008-10-14 1:13 ` J.A. Magallón
2008-10-17 20:41 ` Stefanik Gábor
2008-10-17 21:24 ` Luis R. Rodriguez
2008-10-17 21:24 ` Luis R. Rodriguez
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=20081014165931.GC3349@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=jamagallon@ono.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.