On Mon, Nov 21, 2011 at 9:01 AM, Adrian Chadd wrote:
> Well, unless that vendor spun their own silicon, or there's something
> funky on the board that'd change crypto behaviour, the only thing I
> can really think of are EEPROM settings.
> Or maybe the MAC revision is slightly different, I dunno.
On Mon, Apr 19, 2010 at 2:24 AM, Bruno Randolf wrote:
> On Friday 16 April 2010 22:59:07 Stanislaw Gruszka wrote:
>> On Mon, 12 Apr 2010 16:38:47 +0900
>>
>> Bruno Randolf wrote:
>> > There was a confusion in the usage of the bits AR5K_STA_ID1_ACKCTS_6MB
>> > and AR5K_STA_ID1_BASE_RATE_11B. If th
On Wed, Mar 3, 2010 at 9:18 AM, Jouni Malinen wrote:
> On Wed, Mar 03, 2010 at 10:10:49AM +0900, Bruno Randolf wrote:
>> On Tuesday 02 March 2010 18:42:38 Jouni Malinen wrote:
>> > If we want to have an option to prevent hardware from touching the frame
>> > payload, that really should be an optio
On Tue, Mar 2, 2010 at 10:42 AM, Jouni Malinen wrote:
> On Tue, Mar 02, 2010 at 11:51:58AM +0900, Bruno Randolf wrote:
>> injected frames have to use AR5K_PKT_TYPE_NORMAL, otherwise the hardware
>> thinks
>> it can mess with the contents of the frame - e.g. update the TSF of an
>> injected
>> be
Actually, the right thing to check is info->flags &
IEEE80211_TX_CTL_INJECTED - you shouldn't check the mode to determine
injectedness.
On Tue, Mar 2, 2010 at 2:17 AM, Bruno Randolf wrote:
> On Tuesday 02 March 2010 06:26:48 Benoit PAPILLAULT wrote:
>> Bruno Randolf a écrit :
>> > please ignore t
On Thu, May 14, 2009 at 2:18 AM, Luis R. Rodriguez wrote:
> BTW legacy-hal has this stuff :) Just grep for ATH_WOW
>
> Luis
Wow! :-)
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
___
ath5k-devel mailing list
ath5k-devel@lis
