From: Daniel Drake <dsd@gentoo.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: Uli Kunitz <kune@deine-taler.de>,
Johannes Berg <johannes@sipsolutions.net>,
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: Tue, 31 Oct 2006 20:34:56 -0500 [thread overview]
Message-ID: <4547F9C0.4000107@gentoo.org> (raw)
In-Reply-To: <200611010048.03126.mb@bu3sch.de>
Michael Buesch wrote:
> I think the real question is: What does this "band edge" bit actually do?
Not entirely sure, and I don't think we've even seen a device where this
code path runs (it only runs if a certain bit is set in the EEPROM).
However, considering that this looks like it plays with some kind of
radio stuff, and it's simple to implement, it makes sense to at least
meet the behavior of the vendor driver (as opposed to violating some
weird regulation somewhere).
> I don't know what channel 1 and 11 have in common.
They are the edges of the channel range in most places.
> Why don't we set the
> bit for channel 14? Isn't that an "edge", too?
The vendor driver is full of stuff like this, many corners have been
cut. Chances are that they just wanted to hit the edges in the common
domain while not breaking things for channel 12~14 users, and didn't go
the full way of implementing it accurately. I will email the developers
for clarification.
Daniel
prev parent reply other threads:[~2006-11-01 0:36 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
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 [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=4547F9C0.4000107@gentoo.org \
--to=dsd@gentoo.org \
--cc=holden@pigscanfly.ca \
--cc=holdenk@xandros.com \
--cc=johannes@sipsolutions.net \
--cc=kune@deine-taler.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--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).