The patch was based off the FIXME comment in the code [which suggested
replacing 11 with the boundary for the regulatory domain]. I'll take a
look at the vendors driver and see about modifying the patch to fit
more with its logic or just limmiting it to the FCC regulatory domain.
On 10/30/06, Uli
Hi Ulrich,
I'm fairly certain the patch is safe, even for non-US regulatory domains.
Looking at the zd1211rw code the highest channel in the geo object
would appear to be set in zd_geo_init as determined by
zd_channel_range which just does a simple look up in channel_ranges[],
so if this code be
D]> wrote:
Holden Karau wrote:
> From: Holden Karau <[EMAIL PROTECTED]> http://www.holdenkarau.com
>
> I have made a small patch for the zd1211rw driver which uses the
> boundry channels of the regulatory domain, rather than the hard coded
> values of 1 & 11.
> Signe
From: Holden Karau <[EMAIL PROTECTED]> http://www.holdenkarau.com
I have made a small patch for the zd1211rw driver which uses the
boundry channels of the regulatory domain, rather than the hard coded
values of 1 & 11.
Signed-off-by: Holden Karau <[EMAIL PROTECTED]> http://www
From: Holden Karau <[EMAIL PROTECTED]> http://www.holdenkarau.com
I have made a small patch for the atmel driver [included in the 2.6.18
kernel] to output signal strength information as part of iwlist scan
[before it did not output any signal strength related information].
Signed-off-by:
