[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4547F9C0.4000107@gentoo.org>
Date: Tue, 31 Oct 2006 20:34:56 -0500
From: Daniel Drake <dsd@...too.org>
To: Michael Buesch <mb@...sch.de>
CC: Uli Kunitz <kune@...ne-taler.de>,
Johannes Berg <johannes@...solutions.net>,
Holden Karau <holden@...scanfly.ca>,
zd1211-devs@...ts.sourceforge.net, linville@...driver.com,
netdev <netdev@...r.kernel.org>, linux-kernel@...r.kernel.org,
holdenk@...dros.com
Subject: Re: [PATCH] wireless-2.6 zd1211rw check against regulatory domain
rather than hardcoded value of 11
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists