From: Johannes Berg <johannes@sipsolutions.net>
To: Uli Kunitz <kune@deine-taler.de>
Cc: Daniel Drake <dsd@gentoo.org>,
Holden Karau <holden@pigscanfly.ca>,
zd1211-devs@lists.sourceforge.net, linville@tuxdriver.com,
netdev <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org, holdenk@xandros.com
Subject: Re: [PATCH] wireless-2.6 zd1211rw check against regulatory domain rather than hardcoded value of 11
Date: Mon, 30 Oct 2006 09:42:29 +0100 [thread overview]
Message-ID: <1162197749.2854.5.camel@ux156> (raw)
In-Reply-To: <4544CBC8.5090305@deine-taler.de>
> I'm not so sure about this. This patching might be US-specific and we
> cannot simply apply the setting for top channel of another domain
> instead of channel 11. One option would be to set the value only under
> the US regulatory domain.
??
What the patch does is replace the top channel which is hardcoded to 11
by the top channel given by the current regulatory domain. How can that
be wrong? Except that you may want to init the regulatory domain from
the EEPROM but I'm not sure how the ieee80211 code works wrt. that.
johannes
next prev parent reply other threads:[~2006-10-30 8:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 18:21 [PATCH] wireless-2.6 zd1211rw check against regulatory domain rather than hardcoded value of 11 Holden Karau
2006-10-23 22:57 ` Daniel Drake
2006-10-24 14:09 ` Holden Karau
2006-10-24 15:09 ` Daniel Drake
2006-10-29 15:42 ` Uli Kunitz
2006-10-30 8:42 ` Johannes Berg [this message]
2006-10-30 17:49 ` Holden Karau
2006-10-30 22:59 ` Uli Kunitz
2006-10-31 14:26 ` Holden Karau
2006-10-31 23:48 ` Michael Buesch
2006-11-01 1:34 ` Daniel Drake
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=1162197749.2854.5.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=dsd@gentoo.org \
--cc=holden@pigscanfly.ca \
--cc=holdenk@xandros.com \
--cc=kune@deine-taler.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=zd1211-devs@lists.sourceforge.net \
/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).