From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Luis Rodriguez <Luis.Rodriguez@atheros.com>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: bisected: 2.6.28-rc broke my iwl4965 wireless
Date: Mon, 27 Oct 2008 17:41:34 +0100 [thread overview]
Message-ID: <1225125694.3796.28.camel@johannes.berg> (raw)
In-Reply-To: <20081027163812.GB6377@tesla> (sfid-20081027_173820_318230_ACAD18C7)
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
On Mon, 2008-10-27 at 09:38 -0700, Luis R. Rodriguez wrote:
> > 2.6.28-rc1 broke my (intel 4965) wireless, and I've bisected it down to
> > the commit below..... something's fishy with this...
> Additionally if the old behaviour is desired for now (until distributions
> catch up and add CRDA) CONFIG_WIRELESS_OLD_REGULATORY can be enabled
> and you'll get the old behaviour of defaulting to country "US".
Luis, Arjan's bug is actually indicative of a driver bug, he told me
that he actually runs into driver message like "cannot set TX power
while scanning", and it's fixed by setting WIRELESS_OLD_REGULATORY for
some reason. Arjan, do you still have the actual messages you get when
it fails? That's a separate bug we should address, rather than relying
on it not happening with the old regulatory setting.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-10-27 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 5:22 bisected: 2.6.28-rc broke my iwl4965 wireless Arjan van de Ven
2008-10-27 16:38 ` Luis R. Rodriguez
2008-10-27 16:41 ` Johannes Berg [this message]
2008-10-27 17:33 ` Arjan van de Ven
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=1225125694.3796.28.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=Luis.Rodriguez@atheros.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.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 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).