public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <holtmann@linux.intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
	John Linville <linville@tuxdriver.com>,
	wireless <linux-wireless@vger.kernel.org>
Subject: Re: The new regulatory code kills my wireless
Date: Sat, 13 Sep 2008 18:51:13 +0200	[thread overview]
Message-ID: <1221324673.6695.31.camel@californication> (raw)
In-Reply-To: <1221294810.3700.3.camel@johannes.berg>

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

Regards

Marcel



  reply	other threads:[~2008-09-13 16:50 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 [this message]
2008-09-14  0:52               ` 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=1221324673.6695.31.camel@californication \
    --to=holtmann@linux.intel.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --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