From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Marcel Holtmann <holtmann@linux.intel.com>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
Zhu Yi <yi.zhu@intel.com>,
Johannes Berg <johannes@sipsolutions.net>,
Tomas Winkler <tomasw@gmail.com>,
"Kolekar, Abhijeet" <abhijeet.kolekar@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: New Regulatory Domain Api.
Date: Tue, 21 Oct 2008 14:05:12 -0400 [thread overview]
Message-ID: <20081021180512.GK17268@tuxdriver.com> (raw)
In-Reply-To: <20081021110203.GA8224@tesla>
On Tue, Oct 21, 2008 at 04:02:03AM -0700, Luis R. Rodriguez wrote:
> On Tue, Oct 21, 2008 at 10:48:00AM -0700, John W. Linville wrote:
> > On Tue, Oct 21, 2008 at 07:43:53PM +0200, Marcel Holtmann wrote:
> >
> > > > > No we can't have a new (or updated) driver require new userspace. If you
> > > > > install a 2.6.30 kernel on an Ubuntu Hardy system, it should make the
> > > > > hardware work without installing an extra userspace component. And yes,
> > > > > it works for the first card if it provides a regulatory hint, but it
> > > > > should also work for the second card.
> > > >
> > > > That is what WIRELESS_OLD_REGULATORY is for, no?
> > >
> > > but that would go away with 2.6.29 if it proceeds as planned.
> >
> > I don't see a huge maintenance burden to it the way it is implemented
> > now. I know Luis will hate the idea, but perhaps we could just let
> > it linger indefinitely?
>
> This thread has about 65 messages on it, and no patches yet from Intel.
> I rather we talk productively about trying to resolve it with actual
> code like Johannes or I am. OLD_REGULATORY should still go IMO.
Ok, but it isn't clear to me that any patch will resolve the issue of
someone running a new kernel on an old userland unless OLD_REGULATORY
is enabled...?
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-21 18:06 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 22:17 New Regulatory Domain Api Kolekar, Abhijeet
2008-10-09 15:45 ` Luis R. Rodriguez
2008-10-10 3:22 ` Zhu Yi
2008-10-10 16:49 ` Luis R. Rodriguez
2008-10-14 6:59 ` Zhu Yi
2008-10-14 7:04 ` Luis R. Rodriguez
2008-10-14 7:36 ` Zhu Yi
2008-10-14 9:04 ` Luis R. Rodriguez
2008-10-14 9:13 ` Luis R. Rodriguez
2008-10-14 9:23 ` Zhu Yi
2008-10-14 9:27 ` Zhu Yi
2008-10-14 9:32 ` Johannes Berg
2008-10-14 9:30 ` Luis R. Rodriguez
2008-10-14 20:35 ` John W. Linville
2008-10-14 21:15 ` Johannes Berg
2008-10-14 21:19 ` John W. Linville
2008-10-14 21:27 ` Johannes Berg
2008-10-14 21:50 ` John W. Linville
2008-10-14 21:57 ` Johannes Berg
2008-10-15 15:46 ` Marcel Holtmann
2008-10-15 15:59 ` Johannes Berg
2008-10-15 17:26 ` Marcel Holtmann
2008-10-15 17:39 ` Luis R. Rodriguez
2008-10-15 17:45 ` Johannes Berg
2008-10-15 18:11 ` Luis R. Rodriguez
2008-10-15 17:47 ` Marcel Holtmann
2008-10-15 11:25 ` Luis R. Rodriguez
2008-10-15 19:25 ` Marcel Holtmann
2008-10-15 13:16 ` Luis R. Rodriguez
2008-10-15 23:31 ` Tomas Winkler
2008-10-15 17:08 ` Luis R. Rodriguez
2008-10-16 0:35 ` Tomas Winkler
2008-10-15 17:44 ` Luis R. Rodriguez
2008-10-16 0:57 ` Tomas Winkler
2008-10-15 18:56 ` Luis R. Rodriguez
2008-10-16 3:00 ` Zhu Yi
2008-10-16 11:38 ` Luis R. Rodriguez
2008-10-20 2:51 ` Zhu Yi
2008-10-20 3:40 ` Luis R. Rodriguez
2008-10-20 5:18 ` Zhu Yi
2008-10-20 6:33 ` Luis R. Rodriguez
2008-10-20 6:38 ` Johannes Berg
2008-10-20 6:46 ` Luis R. Rodriguez
2008-10-20 6:50 ` Johannes Berg
2008-10-20 6:59 ` Luis R. Rodriguez
2008-10-20 7:22 ` Zhu Yi
2008-10-20 16:43 ` Marcel Holtmann
2008-10-21 1:34 ` Zhu Yi
2008-10-21 1:42 ` Luis R. Rodriguez
2008-10-21 1:58 ` Zhu Yi
2008-10-21 2:37 ` Luis R. Rodriguez
2008-10-21 4:02 ` Zhu Yi
2008-10-21 4:58 ` Luis R. Rodriguez
2008-10-21 5:28 ` Zhu Yi
2008-10-21 6:02 ` Luis R. Rodriguez
2008-10-21 6:46 ` Zhu Yi
2008-10-21 6:07 ` Marcel Holtmann
2008-10-21 6:29 ` Luis R. Rodriguez
2008-10-21 6:51 ` Marcel Holtmann
2008-10-21 17:13 ` John W. Linville
2008-10-21 17:43 ` Marcel Holtmann
2008-10-21 17:48 ` John W. Linville
2008-10-21 11:02 ` Luis R. Rodriguez
2008-10-21 18:05 ` John W. Linville [this message]
2008-10-21 11:21 ` Luis R. Rodriguez
2008-10-22 9:20 ` Zhu Yi
2008-10-22 10:13 ` Luis R. Rodriguez
2008-10-23 2:29 ` Zhu Yi
2008-10-21 6:40 ` Johannes Berg
2008-10-21 6:47 ` Marcel Holtmann
2008-10-21 7:05 ` Johannes Berg
[not found] ` <79124FD53D2E084387D88C71BEB48F3EDD3625@CPEXBE-EML29.kpnsp.local>
2008-10-21 7:37 ` Johannes Berg
2008-10-21 16:39 ` Marcel Holtmann
2008-10-21 11:04 ` Luis R. Rodriguez
2008-10-21 16:40 ` Johannes Berg
2008-10-15 17:40 ` Johannes Berg
2008-10-15 2:00 ` Zhu Yi
2008-10-14 9:19 ` Johannes Berg
2008-10-15 1:40 ` Zhu Yi
2008-10-15 15:50 ` Marcel Holtmann
2008-10-15 16:01 ` Johannes Berg
2008-10-15 17:29 ` Marcel Holtmann
2008-10-15 17:36 ` Johannes Berg
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=20081021180512.GK17268@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=abhijeet.kolekar@intel.com \
--cc=holtmann@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=tomasw@gmail.com \
--cc=yi.zhu@intel.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).