From: "John W. Linville" <linville@tuxdriver.com>
To: Marcel Holtmann <holtmann@linux.intel.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
Luis Rodriguez <Luis.Rodriguez@atheros.com>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: The new regulatory code kills my wireless
Date: Sat, 13 Sep 2008 20:52:57 -0400 [thread overview]
Message-ID: <20080914005256.GA32339@tuxdriver.com> (raw)
In-Reply-To: <1221324673.6695.31.camel@californication>
On Sat, Sep 13, 2008 at 06:51:13PM +0200, Marcel Holtmann wrote:
> Hi Johannes,
>
> > > I am pretty happy that you caught it, because that was my whole point
> > > from the discussion we had at OLS. The userspace part might not be in
> > > place and we must ensure that everything still works as before :)
> >
> > I thought your point was that you wanted regulatory_hint_regdom(...)
> > that the driver can use to tell us what the EEPROM regulatory is, which
> > wouldn't have been affected by this bug :) But anyway, yeah, it's a bug.
>
> of course I want regulatory_hint_regdom :)
>
> I was just trying to make clear how important it is to make sure we work
> with a broken userspace or without userspace support at all
Which is, of course, why I asked Luis to implement the compatibility
option, and why I decided to let it cook for a bit in wireless-testing
before sending it to Dave for net-next-2.6... :-)
John
--
John W. Linville
linville@tuxdriver.com
prev parent reply other threads:[~2008-09-14 1:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 17:37 The new regulatory code kills my wireless Larry Finger
2008-09-12 17:40 ` Luis R. Rodriguez
2008-09-12 18:46 ` Larry Finger
2008-09-12 19:19 ` Luis R. Rodriguez
2008-09-12 20:22 ` Johannes Berg
2008-09-12 20:34 ` Luis R. Rodriguez
2008-09-12 20:59 ` Larry Finger
2008-09-12 21:15 ` Luis R. Rodriguez
2008-09-13 2:26 ` Marcel Holtmann
2008-09-13 8:33 ` Johannes Berg
2008-09-13 16:51 ` Marcel Holtmann
2008-09-14 0:52 ` John W. Linville [this message]
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=20080914005256.GA32339@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Larry.Finger@lwfinger.net \
--cc=Luis.Rodriguez@atheros.com \
--cc=holtmann@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.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).