On 2014-06-13 16:14, Mathy Vanhoef wrote:
[snip]
> Just saw a spelling mistake in the comment, s/Threat/Treat.
One more mistake in the comment.
Change the word "of" to "or":
...underwent a CCK of OFDM reset...
should be
...underwent a CCK or OFDM reset...
Gus
On 03/20/2010 11:39 PM, Pavel Roskin wrote:
> On Sun, 2010-03-21 at 02:06 +0100, Jiri Moravec wrote:
>> 2.6.33.1/2.6.34-rc2:
>> --
>> ~ # modprobe ath5k
>> ~ # brctl addbr br0
>> ~ # brctl addif br0 wlan0
>> can't add wlan0
On 03/10/2010 05:33 PM, Derek Smithies wrote:
> Hi,
> Acks are generated by hardware. One of the hardware registers might delay
> the acks - you could randomly try different registers and see what
> happens.
Randomly poke registers? I'm going over the reg.h file to see what I can
actually play
I saw that coverage class was recently added to the ath5k driver and it
appears to be the first mac80211 driver to offer it. That's great! Now I
would like to test it out without having to be 5 kilometers away.
I have a testbed consisting of a few high power AR5414 and some low
power AR5213a as we
On 03/08/2010 12:30 AM, Holger Schurig wrote:
>> i don't know where "Rx invalid nwid", etc. went unfortunately...
>
> To limbo, as it's kind of useless. When you have SSID "BLAH" and receive a
> beacon for SSID "MURPS", it's increasing.
>
> As this doesn't say much that, I don't cry now it's gon
On 11/13/2009 06:45 PM, Felix Fietkau wrote:
> Gus Wirth wrote:
>> On 11/13/2009 03:59 PM, Pavel Roskin wrote:
>>> On Fri, 2009-11-13 at 15:26 -0800, Gus Wirth wrote:
>>>
>>>> # ath_info 0xb000
>>>>
>>>> And it promptly reboots.
&
On 11/13/2009 03:59 PM, Pavel Roskin wrote:
> On Fri, 2009-11-13 at 15:26 -0800, Gus Wirth wrote:
>
>> # ath_info 0xb000
>>
>> And it promptly reboots.
>>
>> So at this point I'm not sure if the problem is in the madwifi_multi or
>> if this won
On 11/13/2009 03:04 PM, Pavel Roskin wrote:
> On Fri, 2009-11-13 at 12:06 -0800, Gus Wirth wrote:
>> The ath_info utility can be used to read and set various parameters in
>> the EEPROM for Atheros chipsets. But from what I've seen it only works
>> for PCI style cards
The ath_info utility can be used to read and set various parameters in
the EEPROM for Atheros chipsets. But from what I've seen it only works
for PCI style cards. Is there some equivalent that works with the AR2316
or AR2317 (like in the Mesh Potato) WiSoC chips since these chips have
the ahb b
I've looked through the source code and the mail archives trying to see
if any work has started yet on support for the Atheros AR2315 and AR2317
SoC chips but I haven't seen anything yet except a reference to an
rfbuffer file. I know a couple products are using the AR2317 including
the Ubiquity
10 matches
Mail list logo