lkml.org 
[lkml]   [2006]   [Oct]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH] wireless-2.6 zd1211rw check against regulatory domain rather than hardcoded value of 11
    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 behaves correctly [and there is no indication it does
    not], then setting the upper channel to be that in the geo object
    would appear to be safe for any of the supported regulatory domains.

    Cheers,

    Holden :-)

    On 10/30/06, Johannes Berg <johannes@sipsolutions.net> wrote:
    >
    > > 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
    >


    --
    Cell: 613-276-1645
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2006-10-30 18:53    [W:0.034 / U:0.020 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site