Larry,
Thanks for responding...
I tried both the compat-wireless-3.5.1-1-snpc you recommended
and even compat-wireless-3.5.1-1-sn but the "iw set bitrates" command
still doesn't change the advertised bit rates on the beacons.
What do we make of this? Do you (or anyone) have any idea
what's going on? Are we sure that this driver really works with the
AR9285 chip ...ie has at least one person verified it to be working
and/or is it working in at least one product? Is there a
recommended way to debug or trace this such as with printk's in the
beacon.c file (or similar) or higher up?
-Patrick
On Wed, Aug 29, 2012 at 2:34 PM, Larry Finger <Larry.Finger@xxxxxxxxxxxx> wrote:
>
> On 08/29/2012 04:09 PM, Patrick Connolly wrote:
>>
>> Can anyone comment on whether "iw set bitrates" should be fully
>> functional using compat-wireless version 3.2.5-1 ?
>> ( if not, what do I have to do to get this to work? )
>
>
> The version of compat-wireless (3.2.5) is the version of the kernel that is backported, and I don't think that is new enough.
>
> If you use the version at
> http://www.orbit-lab.org/kernel/compat-wireless-3-stable/v3.5/compat-wireless-3.5.1-1-snpc.tar.bz2, you should be OK.
>
> Larry
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
