* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
@ 2012-05-02 15:22 Kevin Groeneveld
2012-05-02 16:01 ` Dmitry Tarnyagin
0 siblings, 1 reply; 33+ messages in thread
From: Kevin Groeneveld @ 2012-05-02 15:22 UTC (permalink / raw)
To: linux-wireless; +Cc: dmitry.tarnyagin
>Please find below in the patchset implementation of a new driver for
>the ST-Ericsson cw1200 wlan device.
Hello Dmitry,
What firmware version is this driver tested with? Where can I get the
firmware files?
I have build 328 and 380 but I cannot get the driver to work with
either of these. Everything looks like it is working okay but when I
run "iw wlan0 scan" it does not find anything. The debugfs counters
show I am not receiving any valid packets:
PlcpErrors: 6
FcsErrors: 0
TxPackets: 22
RxPackets: 0
RxPacketErrors: 6
RxDecryptionFailures: 0
RxMicFailures: 0
RxNoKeyFailures: 0
TxMulticastFrames: 44
TxFramesSuccess: 0
TxFrameFailures: 0
TxFramesRetried: 0
TxFramesMultiRetried: 0
RxFrameDuplicates: 0
RtsSuccess: 0
RtsFailures: 0
AckFailures: 0
RxMulticastFrames: 0
RxFramesSuccess: 0
RxCMACICVErrors: 0
RxCMACReplays: 0
RxMgmtCCMPReplays: 0
Thanks,
Kevin
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-05-02 15:22 [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver Kevin Groeneveld
@ 2012-05-02 16:01 ` Dmitry Tarnyagin
[not found] ` <CABF+-6XbdG_QMa0iQJMpbOsr4bXCq4mDEB6unkM8jxNGWYwFyQ@mail.gmail.com>
2012-05-09 17:03 ` Kevin Groeneveld
0 siblings, 2 replies; 33+ messages in thread
From: Dmitry Tarnyagin @ 2012-05-02 16:01 UTC (permalink / raw)
To: Kevin Groeneveld; +Cc: linux-wireless
Hi Kevin,
>> Please find below in the patchset implementation of a new driver for
>> the ST-Ericsson cw1200 wlan device.
> Hello Dmitry,
>
> What firmware version is this driver tested with? Where can I get the
> firmware files?
The driver was tested with WSM_A30.02.0380 (and lot of other releases:)).
The firmware was available at igloocommunity.org, I will try to find a link.
>
> I have build 328 and 380 but I cannot get the driver to work with
> either of these. Everything looks like it is working okay but when I
> run "iw wlan0 scan" it does not find anything. The debugfs counters
> show I am not receiving any valid packets:
>
Could you enable following options and send kernel log:
CW1200_DEBUGFS=y
CW1200_WSM_DEBUG=y
CW1200_WSM_DUMPS=y
CW1200_BH_DEBUG=y
and also please send content of
/sys/kernel/debug/ieee80211/phy0/cw1200/status
Best regards,
Dmitry
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
[not found] ` <CABF+-6XbdG_QMa0iQJMpbOsr4bXCq4mDEB6unkM8jxNGWYwFyQ@mail.gmail.com>
@ 2012-05-02 16:51 ` Kevin Groeneveld
[not found] ` <4FA23DA0.3030207@stericsson.com>
1 sibling, 0 replies; 33+ messages in thread
From: Kevin Groeneveld @ 2012-05-02 16:51 UTC (permalink / raw)
To: linux-wireless
Hi Dmitry,
Thanks for the response.
> Could you enable following options and send kernel log:
> CW1200_DEBUGFS=y
> CW1200_WSM_DEBUG=y
> CW1200_WSM_DUMPS=y
> CW1200_BH_DEBUG=y
I already had these options on. The following is the debugfs status
after attempting a scan:
CW1200 Wireless LAN driver status
Hardware: 5.5
Firmware: WSM 3020.380
FW API: 1042
FW caps: 0x000B
Mode: station
Assoc: passive
Channel: 1
EDCA(0): 7, 15, 2, 3264, 200
EDCA(1): 15, 31, 2, 6016, 200
EDCA(2): 31, 1023, 3, 0, 200
EDCA(3): 31, 1023, 7, 0, 200
HT: off
RSSI thold: 0
RSSI hyst: 0
TXFL thold: 0
Linkloss: 60
Bcnloss: 20
Long retr: 4
Short retr: 7
RC in use: 0
BA stat: 0, 0 (0)
Block ACK: off
Queue 0:
capacity: 16
queued: 0
pending: 0
sent: 0
locked: no
overfull: no
link map: 0-> 00 00 00 00 00 00 00 00 <-8
Queue 1:
capacity: 16
queued: 0
pending: 0
sent: 0
locked: no
overfull: no
link map: 0-> 00 00 00 00 00 00 00 00 <-8
Queue 2:
capacity: 16
queued: 0
pending: 0
sent: 0
locked: no
overfull: no
link map: 0-> 00 00 00 00 00 00 00 00 <-8
Queue 3:
capacity: 16
queued: 0
pending: 0
sent: 0
locked: no
overfull: no
link map: 0-> 00 00 00 00 00 00 00 00 <-8
Link map: 0-> .. .. .. .. .. .. .. .. <-7
Asleep map: 0-> .. .. .. .. .. .. .. .. <-7
PSPOLL map: 0-> .. .. .. .. .. .. .. .. <-7
BH status: alive
Pending RX: 0
Pending TX: 0
TX bufs: 8 x 1632 bytes
Used bufs: 0
Powermgmt: on
Device: alseep
WSM status: idle
WSM cmd: 0xFFFF (9 bytes)
WSM retval: 0
Datapath: unlocked
TXed: 0
AGG TXed: 0
MULTI TXed: 0 (0)
RXed: 0
AGG RXed: 0
TX miss: 0
TX align: 0
TX burst: 0
RX burst: 0
TX TTL: 0
Scan: idle
Led state: 0x00
The following is from the kernel log:
[ 8.101627] Compat-wireless backport release: compat-wireless-2012-04-24-1
[ 8.108519] Backport based on linux-next.git next-20120424
[ 8.192370] cfg80211: Calling CRDA to update world regulatory domain
[ 8.215057] cfg80211: World regulatory domain updated:
[ 8.220311] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 8.236156] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[ 8.245162] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz),
(300 mBi, 2000 mBm)
[ 8.254101] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz),
(300 mBi, 2000 mBm)
[ 8.271167] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[ 8.278927] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[ 80.672423] Probe called
[ 80.674493] [BH] register.
[ 80.731090] WLAN device is ready.
[ 80.731108] Cut 2.x silicon is detected.
[ 80.731533] Cut 2.2 detected.
[ 80.731580] cw1200_load_firmware: CW1200 detected.
[ 80.816222] Firmware download completed.
[ 80.816289] SW IRQ subscribe
[ 80.821093] [BH] irq.
[ 80.821140] [BH] irq.
[ 80.821177] [BH] irq.
[ 80.821212] [BH] irq.
[ 80.821246] [BH] irq.
[ 80.821375] [WSM] <<< 0x0801 (168)
[ 80.821398] CW1200 WSM init done.
[ 80.821402] Input buffers: 8 x 1632 bytes
[ 80.821407] Hardware: 5.5
[ 80.821411] WSM firmware [WSM_A30.02.0380_PTA4W Feb 17 2012
10:43:10], ver: 3020, build: 380, api: 1042, cap: 0x000B
[ 80.848338] [WSM] >>> 0x0006 [MIB: 0x1006] (9)
[ 80.848348] [BH] wakeup.
[ 80.848502] [BH] irq.
[ 80.848536] [BH] irq.
[ 80.848570] [BH] irq.
[ 80.848692] [WSM] <<< 0x0406 (8)
[ 80.848701] [BH] Powerave is enabled.
[ 80.848793] [WSM] >>> 0x0006 [MIB: 0x1024] (12)
[ 80.848801] [BH] wakeup.
[ 80.848942] [BH] irq.
[ 80.848975] [BH] irq.
[ 80.849095] [WSM] <<< 0x0406 (8)
[ 80.859122] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 80.861178] is registered as 'phy0'
[ 81.841078] [BH] Device wakedown.
[ 123.215695] [WSM] >>> 0x0013 (48)
[ 123.215711] [BH] wakeup.
[ 123.215758] [BH] Device wakeup.
[ 123.233368] [BH] irq.
[ 123.233418] [BH] irq.
[ 123.233456] [BH] irq.
[ 123.233490] [BH] irq.
[ 123.233537] [BH] Device wakeup.
[ 123.233597] [BH] Device awake.
[ 123.233794] [WSM] <<< 0x0413 (8)
[ 123.233887] [WSM] >>> 0x0006 [MIB: 0x1013] (16)
[ 123.233896] [BH] wakeup.
[ 123.234042] [BH] irq.
[ 123.234075] [BH] irq.
[ 123.234109] [BH] irq.
[ 123.234142] [BH] irq.
[ 123.234264] [WSM] <<< 0x0406 (8)
[ 123.254241] [WSM] >>> 0x0009 (840)
[ 123.254257] [BH] wakeup.
[ 123.254590] [BH] irq.
[ 123.254630] [BH] irq.
[ 123.254667] [BH] irq.
[ 123.254703] [BH] irq.
[ 123.254738] [BH] irq.
[ 123.254872] [WSM] <<< 0x0409 (44)
[ 123.254947] [WSM] >>> 0x0006 [MIB: 0x1009] (12)
[ 123.254956] [BH] wakeup.
[ 123.255109] [BH] irq.
[ 123.255144] [BH] irq.
[ 123.255180] [BH] irq.
[ 123.255314] [WSM] <<< 0x0406 (8)
[ 123.255385] [WSM] >>> 0x0006 [MIB: 0x1009] (12)
[ 123.255394] [BH] wakeup.
[ 123.255545] [BH] irq.
[ 123.255579] [BH] irq.
[ 123.255616] [BH] irq.
[ 123.255743] [WSM] <<< 0x0406 (8)
[ 123.255816] [WSM] >>> 0x0006 [MIB: 0x0003] (12)
[ 123.255824] [BH] wakeup.
[ 123.255975] [BH] irq.
[ 123.256008] [BH] irq.
[ 123.256045] [BH] irq.
[ 123.256080] [BH] irq.
[ 123.256208] [WSM] <<< 0x0406 (8)
[ 123.256284] [WSM] >>> 0x0012 (16)
[ 123.256292] [BH] wakeup.
[ 123.256460] [BH] irq.
[ 123.256494] [BH] irq.
[ 123.256617] [WSM] <<< 0x0412 (8)
[ 123.256683] [WSM] >>> 0x0013 (48)
[ 123.256690] [BH] wakeup.
[ 123.256855] [BH] irq.
[ 123.256890] [BH] irq.
[ 123.257017] [WSM] <<< 0x0413 (8)
[ 123.257080] [WSM] >>> 0x0006 [MIB: 0x1013] (16)
[ 123.257087] [BH] wakeup.
[ 123.257271] [BH] irq.
[ 123.257307] [BH] irq.
[ 123.257346] [BH] irq.
[ 123.257470] [WSM] <<< 0x0406 (8)
[ 123.257533] [WSM] >>> 0x0012 (16)
[ 123.257539] [BH] wakeup.
[ 123.257687] [BH] irq.
[ 123.257722] [BH] irq.
[ 123.258940] [WSM] <<< 0x0412 (8)
[ 123.259080] [WSM] >>> 0x0013 (48)
[ 123.259088] [BH] wakeup.
[ 123.259272] [BH] irq.
[ 123.259307] [BH] irq.
[ 123.259438] [WSM] <<< 0x0413 (8)
[ 123.259477] [WSM] >>> 0x0006 [MIB: 0x1013] (16)
[ 123.259485] [BH] wakeup.
[ 123.259637] [BH] irq.
[ 123.259671] [BH] irq.
[ 123.259706] [BH] irq.
[ 123.259740] [BH] irq.
[ 123.259866] [WSM] <<< 0x0406 (8)
[ 123.259905] [WSM] >>> 0x0012 (16)
[ 123.259912] [BH] wakeup.
[ 123.260058] [BH] irq.
[ 123.260092] [BH] irq.
[ 123.260127] [BH] irq.
[ 123.260161] [BH] irq.
[ 123.260195] [BH] irq.
[ 123.260321] [WSM] <<< 0x0412 (8)
[ 123.260356] [WSM] >>> 0x0013 (48)
[ 123.260363] [BH] wakeup.
[ 123.260508] [BH] irq.
[ 123.260542] [BH] irq.
[ 123.260667] [WSM] <<< 0x0413 (8)
[ 123.260703] [WSM] >>> 0x0006 [MIB: 0x1013] (16)
[ 123.260711] [BH] wakeup.
[ 123.260860] [BH] irq.
[ 123.260894] [BH] irq.
[ 123.260929] [BH] irq.
[ 123.260963] [BH] irq.
[ 123.261125] [WSM] <<< 0x0406 (8)
[ 123.261164] [WSM] >>> 0x0012 (16)
[ 123.261171] [BH] wakeup.
[ 123.261321] [BH] irq.
[ 123.261355] [BH] irq.
[ 123.261390] [BH] irq.
[ 123.261519] [WSM] <<< 0x0412 (8)
[ 123.261555] [WSM] >>> 0x0013 (48)
[ 123.261562] [BH] wakeup.
[ 123.261710] [BH] irq.
[ 123.261743] [BH] irq.
[ 123.261778] [BH] irq.
[ 123.261905] [WSM] <<< 0x0413 (8)
[ 123.261941] [WSM] >>> 0x0006 [MIB: 0x1013] (16)
[ 123.261950] [BH] wakeup.
[ 123.262099] [BH] irq.
[ 123.262133] [BH] irq.
[ 123.262256] [WSM] <<< 0x0406 (8)
[ 123.262303] [WSM] TX is locked.
[ 123.262312] [BH] wakeup.
[ 123.262319] [WSM] TX is unlocked.
[ 123.262332] [WSM] >>> 0x0006 [MIB: 0x0006] (12)
[ 123.262339] [BH] wakeup.
[ 123.262495] [BH] irq.
[ 123.262529] [BH] irq.
[ 123.262658] [WSM] <<< 0x0406 (8)
[ 123.262691] [WSM] TX is locked.
[ 123.262702] [WSM] >>> 0x0016 (8)
[ 123.262708] [BH] wakeup.
[ 123.262874] [BH] irq.
[ 123.262909] [BH] irq.
[ 123.263039] [WSM] <<< 0x0416 (8)
[ 123.284588] [BH] irq.
[ 123.284640] [BH] irq.
[ 123.284783] [WSM] <<< 0x080A (8)
[ 123.284796] [BH] wakeup.
[ 123.284803] [WSM] TX is unlocked.
[ 123.284836] [WSM] TX is locked.
[ 123.284851] [WSM] >>> 0x0006 [MIB: 0x1006] (9)
[ 123.284858] [BH] wakeup.
[ 123.285007] [BH] irq.
[ 123.285040] [BH] irq.
[ 123.285161] [WSM] <<< 0x0406 (8)
[ 123.285173] [BH] Powerave is enabled.
[ 123.285201] [BH] wakeup.
[ 123.285207] [WSM] TX is unlocked.
[ 124.281096] [BH] Device wakedown.
[ 153.599285] [WSM] TX is locked.
[ 153.599309] [WSM] >>> 0x0006 [MIB: 0x1006] (9)
[ 153.599319] [BH] wakeup.
[ 153.599367] [BH] Device wakeup.
[ 153.607490] [BH] irq.
[ 153.607539] [BH] irq.
[ 153.607575] [BH] irq.
[ 153.607609] [BH] irq.
[ 153.607642] [BH] irq.
[ 153.607691] [BH] Device wakeup.
[ 153.607749] [BH] Device awake.
[ 153.607945] [WSM] <<< 0x0406 (8)
[ 153.607957] [BH] Powerave is enabled.
[ 153.608030] [BH] wakeup.
[ 153.608059] [WSM] TX is unlocked.
[ 153.608109] [WSM] >>> 0x0006 [MIB: 0x1002] (82)
[ 153.608116] [BH] wakeup.
[ 153.608255] [BH] irq.
[ 153.608288] [BH] irq.
[ 153.608408] [WSM] <<< 0x0406 (8)
[ 153.608499] [WSM] >>> 0x0006 [MIB: 0x1002] (82)
[ 153.608507] [BH] wakeup.
[ 153.608649] [BH] irq.
[ 153.608681] [BH] irq.
[ 153.608715] [BH] irq.
[ 153.608835] [WSM] <<< 0x0406 (8)
[ 153.608925] [WSM] TX is locked.
[ 153.608963] [WSM] >>> 0x0007 (192)
[ 153.608970] [BH] wakeup.
[ 153.609203] [BH] irq.
[ 153.609240] [BH] irq.
[ 153.609369] [WSM] <<< 0x0407 (8)
[ 154.557453] [BH] irq.
[ 154.557501] [BH] irq.
[ 154.557638] [WSM] <<< 0x0806 (12)
[ 154.557688] [WSM] >>> 0x0007 (64)
[ 154.557696] [BH] wakeup.
[ 154.557935] [BH] irq.
[ 154.557970] [BH] irq.
[ 154.558098] [WSM] <<< 0x0407 (8)
[ 154.831678] [BH] irq.
[ 154.831714] [BH] irq.
[ 154.831842] [WSM] <<< 0x0806 (12)
[ 154.831873] [BH] wakeup.
[ 154.831880] [WSM] TX is unlocked.
[ 154.831925] [WSM] TX is locked.
[ 154.831934] [BH] wakeup.
[ 154.831939] [WSM] TX is unlocked.
[ 154.831948] [WSM] TX is locked.
[ 154.831957] [WSM] >>> 0x0006 [MIB: 0x1006] (9)
[ 154.831964] [BH] wakeup.
[ 154.832172] [BH] irq.
[ 154.832208] [BH] irq.
[ 154.832334] [WSM] <<< 0x0406 (8)
[ 154.832345] [BH] Powerave is enabled.
[ 154.832378] [BH] wakeup.
[ 154.832385] [WSM] TX is unlocked.
[ 155.831063] [BH] Device wakedown.
[ 217.456101] [WSM] >>> 0x0005 (8)
[ 217.456118] [BH] wakeup.
[ 217.456166] [BH] Device wakeup.
[ 217.464294] [BH] irq.
[ 217.464343] [BH] irq.
[ 217.464379] [BH] irq.
[ 217.464413] [BH] irq.
[ 217.464446] [BH] irq.
[ 217.464496] [BH] Device wakeup.
[ 217.464555] [BH] Device awake.
[ 217.464750] [WSM] <<< 0x0405 (104)
[ 218.461064] [BH] Device wakedown.
I ran "ifconfig wlan0 up" at about time stamp 123 and "iw wlan0 scan"
at about 153.
As you can see in the log I am compiling the driver patched into
compat-wireless-2012-04-24. I am using a kernel based on 2.6.35.3.
Maybe this is a bad combination or not even a valid way of doing
things. I don't have much experience with wireless drivers in Linux.
Thanks,
Kevin
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
[not found] ` <4FA23DA0.3030207@stericsson.com>
@ 2012-05-03 16:42 ` Kevin Groeneveld
2012-05-03 17:23 ` Dmitry Tarnyagin
0 siblings, 1 reply; 33+ messages in thread
From: Kevin Groeneveld @ 2012-05-03 16:42 UTC (permalink / raw)
To: linux-wireless; +Cc: Dmitry Tarnyagin
[-- Attachment #1: Type: text/plain, Size: 3132 bytes --]
Hi Dmitry,
> Thank you for logs!
> As I can see the device itself is alive, but nothing is coming back as a
> response to the "scan" command. Something happened with RF part or (likely)
> wrong PLL settings?
> What kind of platform you are running on? What frequency you are providing
> as a master clock for cw1200?
I am running on an iMX51 platform very similar to the Freescale
babbage board. The cw1200 is on a sg901_1091 module from Sagrad.
I measured the clock on the sg901_1091 module and it is 38.4MHz.
Based on some other cw1200 driver source I have changed the PLL init
value from 0x0EC4F121 to 0x100010C1. After that change "iw wlan0
scan" succeeds! :) However, I have not been able to actually connect
to any networks. :(
"iw --debug wlan0 connect cw_test" returns:
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[HEADER] 16 octets
.nlmsg_len = 40
.nlmsg_type = 17 <0x11>
.nlmsg_flags = 5 <REQUEST,ACK>
.nlmsg_seq = 1336063010
.nlmsg_pid = 2087
[PAYLOAD] 24 octets
2e 00 00 00 08 00 03 00 04 00 00 00 0b 00 34 00 63 77 ..............4.cw
5f 74 65 73 74 00 _test.
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[HEADER] 16 octets
.nlmsg_len = 168
.nlmsg_type = 17 <0x11>
.nlmsg_flags = 0 <>
.nlmsg_seq = 0
.nlmsg_pid = 0
[PAYLOAD] 152 octets
21 01 00 00 08 00 01 00 01 00 00 00 08 00 03 00 04 00 !.................
00 00 10 00 2d 00 0b 00 00 00 63 77 5f 74 65 73 74 00 ....-.....cw_test.
74 00 2c 00 08 00 00 00 6c 09 00 00 08 00 01 00 71 09 t.,.....l.......q.
00 00 08 00 02 00 76 09 00 00 08 00 03 00 7b 09 00 00 ......v.......{...
08 00 04 00 80 09 00 00 08 00 05 00 85 09 00 00 08 00 ..................
06 00 8a 09 00 00 08 00 07 00 8f 09 00 00 08 00 08 00 ..................
94 09 00 00 08 00 09 00 99 09 00 00 08 00 0a 00 9e 09 ..................
00 00 08 00 0b 00 a3 09 00 00 08 00 0c 00 a8 09 00 00 ..................
08 00 0d 00 b4 09 00 00 ........
--------------------------- END NETLINK MESSAGE ---------------------------
-- Error: Invalid message: type=0x11 length=168 flags=<> sequence-nr=0 pid=0
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[HEADER] 16 octets
.nlmsg_len = 36
.nlmsg_type = 2 <ERROR>
.nlmsg_flags = 0 <>
.nlmsg_seq = 1336063010
.nlmsg_pid = 2087
[ERRORMSG] 20 octets
.error = 0 "Success"
[ORIGINAL MESSAGE] 16 octets
.nlmsg_len = 16
.nlmsg_type = 17 <0x11>
.nlmsg_flags = 5 <REQUEST,ACK>
.nlmsg_seq = 1336063010
.nlmsg_pid = 2087
--------------------------- END NETLINK MESSAGE ---------------------------
I have also attached a kernel log.
> Also I see unexpectedly high rate of IRQs, they should not come every now
> and then..
Any ideas what could cause this or how I should debug it?
Thanks,
Kevin
[-- Attachment #2: kernel.log --]
[-- Type: application/octet-stream, Size: 33759 bytes --]
[ 15.597456] [WSM] TX is locked.
[ 15.597485] [WSM] >>> 0x0006 [MIB: 0x1006] (9)
[ 15.597494] [BH] wakeup.
[ 15.597528] [BH] Device wakeup.
[ 15.597654] [BH] Device awake.
[ 15.597770] --> 09 00 06 00 06 10 01 00 12 .........
[ 15.597837] [BH] irq.
[ 15.597871] [BH] irq.
[ 15.597907] [BH] irq.
[ 15.597942] [BH] irq.
[ 15.598073] <-- 08 00 06 04 00 00 00 00 ........
[ 15.598088] [WSM] <<< 0x0406 (8)
[ 15.598098] [BH] Powerave is enabled.
[ 15.598192] [BH] wakeup.
[ 15.598219] [WSM] TX is unlocked.
[ 15.598266] [WSM] >>> 0x0006 [MIB: 0x1002] (54)
[ 15.598274] [BH] wakeup.
[ 15.598362] --> 36 00 06 20 02 10 2e 00 00 00 2a 00 40 00 00 00 6.. ......*.@...
[ 15.598381] --> ff ff ff ff ff ff 00 80 e1 3d 80 24 ff ff ff ff .........=.$....
[ 15.598393] --> ff ff 00 00 00 00 01 08 02 04 0b 16 0c 12 18 24 ...............$
[ 15.598404] --> 32 04 30 48 60 6c 2.0H`l
[ 15.598463] [BH] irq.
[ 15.598496] [BH] irq.
[ 15.598618] <-- 08 00 06 24 00 00 00 00 ...$....
[ 15.598631] [WSM] <<< 0x0406 (8)
[ 15.598722] [WSM] >>> 0x0006 [MIB: 0x1002] (54)
[ 15.598731] [BH] wakeup.
[ 15.598822] --> 36 00 06 40 02 10 2e 00 05 00 00 00 40 00 00 00 6..@........@...
[ 15.598835] --> ff ff ff ff ff ff 00 80 e1 3d 80 24 ff ff ff ff .........=.$....
[ 15.598846] --> ff ff 00 00 00 00 01 08 02 04 0b 16 0c 12 18 24 ...............$
[ 15.598857] --> 32 04 30 48 60 6c 2.0H`l
[ 15.598917] [BH] irq.
[ 15.599042] <-- 08 00 06 44 00 00 00 00 ...D....
[ 15.599054] [WSM] <<< 0x0406 (8)
[ 15.599118] [WSM] TX is locked.
[ 15.599146] [WSM] >>> 0x0010 (8)
[ 15.599154] [BH] wakeup.
[ 15.599246] --> 08 00 10 60 01 c8 00 00 ...`....
[ 15.599322] [BH] irq.
[ 15.599453] <-- 08 00 10 64 00 00 00 00 ...d....
[ 15.599467] [WSM] <<< 0x0410 (8)
[ 15.599517] [WSM] >>> 0x0007 (228)
[ 15.599524] [BH] wakeup.
[ 15.599623] --> e4 00 07 80 00 01 01 00 00 00 00 00 02 0b 01 64 ...............d
[ 15.599638] --> 01 00 00 00 32 00 00 00 6e 00 00 00 00 00 00 00 ....2...n.......
[ 15.599650] --> 02 00 00 00 32 00 00 00 6e 00 00 00 00 00 00 00 ....2...n.......
[ 15.599661] --> 03 00 00 00 32 00 00 00 6e 00 00 00 00 00 00 00 ....2...n.......
[ 15.599672] --> 04 00 00 00 32 00 00 00 6e 00 00 00 00 00 00 00 ....2...n.......
[ 15.599683] --> 05 00 00 00 32 00 00 00 6e 00 00 00 00 00 00 00 ....2...n.......
[ 15.599694] --> 06 00 00 00 32 00 00 00 6e 00 00 00 00 00 00 00 ....2...n.......
[ 15.599705] --> 07 00 00 00 32 00 00 00 6e 00 00 00 00 00 00 00 ....2...n.......
[ 15.599716] --> 08 00 00 00 32 00 00 00 6e 00 00 00 00 00 00 00 ....2...n.......
[ 15.599726] --> 09 00 00 00 32 00 00 00 6e 00 00 00 00 00 00 00 ....2...n.......
[ 15.599737] --> 0a 00 00 00 32 00 00 00 6e 00 00 00 00 00 00 00 ....2...n.......
[ 15.599748] --> 0b 00 00 00 32 00 00 00 6e 00 00 00 00 00 00 00 ....2...n.......
[ 15.599760] --> 07 00 00 00 63 77 5f 74 65 73 74 00 00 00 00 00 ....cw_test.....
[ 15.599771] --> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 15.599781] --> 00 00 00 00 ....
[ 15.599841] [BH] irq.
[ 15.599875] [BH] irq.
[ 15.599911] [BH] irq.
[ 15.600037] <-- 0c 00 09 88 00 00 00 00 01 00 00 00 ............
[ 15.600050] [WSM] <<< 0x0809 (12)
[ 15.600142] <-- 08 00 07 a4 00 00 00 00 ........
[ 15.600155] [WSM] <<< 0x0407 (8)
[ 15.835365] [BH] irq.
[ 15.835420] [BH] irq.
[ 15.835570] <-- 89 01 04 c8 00 00 00 00 03 00 00 7c 00 0c 00 00 ...........|....
[ 15.835585] <-- 50 00 3a 01 00 80 e1 3d 80 24 c0 3f 0e 87 f3 0e P.:....=.$.?....
[ 15.835596] <-- c0 3f 0e 87 f3 0e b0 62 62 a9 dd 69 00 00 00 00 .?.....bb..i....
[ 15.835608] <-- 64 00 21 04 00 07 63 77 5f 74 65 73 74 01 08 82 d.!...cw_test...
[ 15.835619] <-- 84 8b 96 0c 12 18 24 03 01 03 07 06 55 53 20 01 ......$.....US .
[ 15.835630] <-- 0b 1b 2a 01 00 32 04 30 48 60 6c dd 18 00 50 f2 ..*..2.0H`l...P.
[ 15.835641] <-- 02 01 01 82 00 03 a4 00 00 27 a4 00 00 42 43 5e .........'...BC^
[ 15.835653] <-- 00 62 32 2f 00 dd 1e 00 90 4c 33 4e 11 1b ff 00 .b2/.....L3N....
[ 15.835664] <-- 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 15.835675] <-- 00 00 00 00 00 2d 1a 4e 11 1b ff 00 00 00 00 00 .....-.N........
[ 15.835686] <-- 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 15.835697] <-- 00 dd 1a 00 90 4c 34 03 05 1b 00 00 00 00 00 00 .....L4.........
[ 15.835708] <-- 00 00 00 00 00 00 00 00 00 00 00 00 00 3d 16 03 .............=..
[ 15.835719] <-- 05 1b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 15.835730] <-- 00 00 00 00 00 dd 09 00 03 7f 01 01 00 00 ff 7f ................
[ 15.835741] <-- dd 0a 00 03 7f 04 01 00 02 00 40 00 dd 8b 00 50 ..........@....P
[ 15.835752] <-- f2 04 10 4a 00 01 10 10 44 00 01 02 10 3b 00 01 ...J....D....;..
[ 15.835763] <-- 03 10 47 00 10 00 00 00 00 00 00 10 00 00 00 c0 ..G.............
[ 15.835774] <-- 3f 0e 87 f3 0e 10 21 00 0d 4e 65 74 67 65 61 72 ?.....!..Netgear
[ 15.835786] <-- 2c 20 49 6e 63 2e 10 23 00 09 57 4e 52 31 30 30 , Inc..#..WNR100
[ 15.835797] <-- 30 76 32 10 24 00 04 56 32 48 31 10 42 00 04 6e 0v2.$..V2H1.B..n
[ 15.835808] <-- 6f 6e 65 10 54 00 08 00 06 00 50 f2 04 00 01 10 one.T.....P.....
[ 15.835819] <-- 11 00 1b 57 4e 52 31 30 30 30 76 32 28 57 69 72 ...WNR1000v2(Wir
[ 15.835830] <-- 65 6c 65 73 73 20 41 50 2d 32 2e 34 47 29 10 08 eless AP-2.4G)..
[ 15.835841] <-- 00 02 00 86 10 3c 00 01 03 .....<...
[ 15.835854] [WSM] <<< 0x0804 (393)
[ 15.839707] [BH] irq.
[ 15.839848] <-- 89 01 04 e8 00 00 00 00 03 00 00 7c 00 0c 00 00 ...........|....
[ 15.839861] <-- 50 00 3a 01 00 80 e1 3d 80 24 c0 3f 0e 87 f3 0e P.:....=.$.?....
[ 15.839873] <-- c0 3f 0e 87 f3 0e c0 62 7d ba dd 69 00 00 00 00 .?.....b}..i....
[ 15.839884] <-- 64 00 21 04 00 07 63 77 5f 74 65 73 74 01 08 82 d.!...cw_test...
[ 15.839895] <-- 84 8b 96 0c 12 18 24 03 01 03 07 06 55 53 20 01 ......$.....US .
[ 15.839906] <-- 0b 1b 2a 01 00 32 04 30 48 60 6c dd 18 00 50 f2 ..*..2.0H`l...P.
[ 15.839917] <-- 02 01 01 82 00 03 a4 00 00 27 a4 00 00 42 43 5e .........'...BC^
[ 15.839928] <-- 00 62 32 2f 00 dd 1e 00 90 4c 33 4e 11 1b ff 00 .b2/.....L3N....
[ 15.839939] <-- 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 15.839950] <-- 00 00 00 00 00 2d 1a 4e 11 1b ff 00 00 00 00 00 .....-.N........
[ 15.839962] <-- 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 15.839973] <-- 00 dd 1a 00 90 4c 34 03 05 1b 00 00 00 00 00 00 .....L4.........
[ 15.839983] <-- 00 00 00 00 00 00 00 00 00 00 00 00 00 3d 16 03 .............=..
[ 15.839994] <-- 05 1b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 15.840005] <-- 00 00 00 00 00 dd 09 00 03 7f 01 01 00 00 ff 7f ................
[ 15.840016] <-- dd 0a 00 03 7f 04 01 00 02 00 40 00 dd 8b 00 50 ..........@....P
[ 15.840027] <-- f2 04 10 4a 00 01 10 10 44 00 01 02 10 3b 00 01 ...J....D....;..
[ 15.840038] <-- 03 10 47 00 10 00 00 00 00 00 00 10 00 00 00 c0 ..G.............
[ 15.840050] <-- 3f 0e 87 f3 0e 10 21 00 0d 4e 65 74 67 65 61 72 ?.....!..Netgear
[ 15.840061] <-- 2c 20 49 6e 63 2e 10 23 00 09 57 4e 52 31 30 30 , Inc..#..WNR100
[ 15.840072] <-- 30 76 32 10 24 00 04 56 32 48 31 10 42 00 04 6e 0v2.$..V2H1.B..n
[ 15.840083] <-- 6f 6e 65 10 54 00 08 00 06 00 50 f2 04 00 01 10 one.T.....P.....
[ 15.840094] <-- 11 00 1b 57 4e 52 31 30 30 30 76 32 28 57 69 72 ...WNR1000v2(Wir
[ 15.840105] <-- 65 6c 65 73 73 20 41 50 2d 32 2e 34 47 29 10 08 eless AP-2.4G)..
[ 15.840116] <-- 00 02 00 86 10 3c 00 01 03 .....<...
[ 15.840127] [WSM] <<< 0x0804 (393)
[ 15.844643] [BH] irq.
[ 15.844679] [BH] irq.
[ 15.844808] <-- 12 01 04 08 00 00 00 00 03 00 00 7c 80 0c 04 00 ...........|....
[ 15.844821] <-- 80 00 00 00 ff ff ff ff ff ff c0 3f 0e 87 f3 0e ...........?....
[ 15.844833] <-- c0 3f 0e 87 f3 0e 10 3c 80 2d df 69 00 00 00 00 .?.....<.-.i....
[ 15.844844] <-- 64 00 21 04 00 07 63 77 5f 74 65 73 74 01 08 82 d.!...cw_test...
[ 15.844855] <-- 84 8b 96 0c 12 18 24 03 01 03 05 04 00 03 00 00 ......$.........
[ 15.844866] <-- 07 06 55 53 20 01 0b 1b 2a 01 00 32 04 30 48 60 ..US ...*..2.0H`
[ 15.844877] <-- 6c dd 18 00 50 f2 02 01 01 82 00 03 a4 00 00 27 l...P..........'
[ 15.844888] <-- a4 00 00 42 43 5e 00 62 32 2f 00 dd 1e 00 90 4c ...BC^.b2/.....L
[ 15.844899] <-- 33 4e 11 1b ff 00 00 00 00 00 00 00 00 00 00 00 3N..............
[ 15.844910] <-- 00 00 00 00 00 00 00 00 00 00 00 2d 1a 4e 11 1b ...........-.N..
[ 15.844921] <-- ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 15.844933] <-- 00 00 00 00 00 00 00 dd 1a 00 90 4c 34 03 05 1b ...........L4...
[ 15.844944] <-- 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 15.844954] <-- 00 00 00 3d 16 03 05 1b 00 00 00 00 00 00 00 00 ...=............
[ 15.844966] <-- 00 00 00 00 00 00 00 00 00 00 00 dd 09 00 03 7f ................
[ 15.844977] <-- 01 01 00 00 ff 7f dd 0a 00 03 7f 04 01 00 02 00 ................
[ 15.844988] <-- 40 00 dd 0e 00 50 f2 04 10 4a 00 01 10 10 44 00 @....P...J....D.
[ 15.844998] <-- 01 02 ..
[ 15.845009] [WSM] <<< 0x0804 (274)
[ 16.836431] [BH] Device wakedown.
[ 16.858909] [BH] irq.
[ 16.858944] [BH] irq.
[ 16.858979] [BH] irq.
[ 16.859013] [BH] irq.
[ 16.859047] [BH] irq.
[ 16.859181] <-- 0c 00 06 28 00 00 00 00 01 0b 00 00 ...(........
[ 16.859195] [WSM] <<< 0x0806 (12)
[ 16.859246] [WSM] >>> 0x0007 (100)
[ 16.859254] [BH] wakeup.
[ 16.859274] [BH] Device wakeup.
[ 16.859333] [BH] Device awake.
[ 16.859425] --> 64 00 07 a0 00 01 01 00 00 00 00 00 00 03 01 64 d..............d
[ 16.859438] --> 0c 00 00 00 32 00 00 00 6e 00 00 00 00 00 00 00 ....2...n.......
[ 16.859449] --> 0d 00 00 00 32 00 00 00 6e 00 00 00 00 00 00 00 ....2...n.......
[ 16.859460] --> 0e 00 00 00 32 00 00 00 6e 00 00 00 00 00 00 00 ....2...n.......
[ 16.859471] --> 07 00 00 00 63 77 5f 74 65 73 74 00 00 00 00 00 ....cw_test.....
[ 16.859482] --> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 16.859493] --> 00 00 00 00 ....
[ 16.859619] [BH] irq.
[ 16.859653] [BH] irq.
[ 16.859779] <-- 08 00 07 44 00 00 00 00 ...D....
[ 16.859791] [WSM] <<< 0x0407 (8)
[ 17.205546] [BH] irq.
[ 17.205681] <-- 0c 00 06 68 00 00 00 00 01 03 00 00 ...h........
[ 17.205694] [WSM] <<< 0x0806 (12)
[ 17.205729] [WSM] >>> 0x0010 (8)
[ 17.205736] [BH] wakeup.
[ 17.205834] --> 08 00 10 c0 00 c8 00 00 ........
[ 17.205904] [BH] irq.
[ 17.206032] <-- 08 00 10 84 00 00 00 00 ........
[ 17.206044] [WSM] <<< 0x0410 (8)
[ 17.206076] [BH] wakeup.
[ 17.206083] [WSM] TX is unlocked.
[ 17.206128] [WSM] TX is locked.
[ 17.206137] [BH] wakeup.
[ 17.206142] [WSM] TX is unlocked.
[ 17.206151] [WSM] TX is locked.
[ 17.206161] [WSM] >>> 0x0006 [MIB: 0x1006] (9)
[ 17.206168] [BH] wakeup.
[ 17.206246] wlan0: authenticate with c0:3f:0e:87:f3:0e
[ 17.206389] --> 09 00 06 e0 06 10 01 00 12 .........
[ 17.206482] [BH] irq.
[ 17.206518] [BH] irq.
[ 17.206554] [BH] irq.
[ 17.206679] <-- 08 00 06 a4 00 00 00 00 ........
[ 17.206693] [WSM] <<< 0x0406 (8)
[ 17.206701] [BH] Powerave is enabled.
[ 17.206728] [BH] wakeup.
[ 17.206735] [WSM] TX is unlocked.
[ 17.206761] [WSM] TX is locked.
[ 17.206779] [WSM] >>> 0x0006 [MIB: 0x1006] (9)
[ 17.206786] [BH] wakeup.
[ 17.206807] <-- 0c 00 09 c8 00 00 00 00 00 00 00 00 ............
[ 17.206819] [WSM] <<< 0x0809 (12)
[ 17.206934] --> 09 00 06 00 06 10 01 00 12 .........
[ 17.207001] [BH] irq.
[ 17.207035] [BH] irq.
[ 17.207069] [BH] irq.
[ 17.207195] <-- 08 00 06 e4 00 00 00 00 ........
[ 17.207208] [WSM] <<< 0x0406 (8)
[ 17.207215] [BH] Powerave is enabled.
[ 17.207243] [BH] wakeup.
[ 17.207250] [WSM] TX is unlocked.
[ 17.207266] [WSM] >>> 0x0006 [MIB: 0x1009] (12)
[ 17.207273] [BH] wakeup.
[ 17.207374] --> 0c 00 06 20 09 10 04 00 0d 00 00 10 ... ........
[ 17.207449] [BH] irq.
[ 17.207483] [BH] irq.
[ 17.207612] <-- 08 00 06 04 00 00 00 00 ........
[ 17.207624] [WSM] <<< 0x0406 (8)
[ 17.207685] wlan0: send auth to c0:3f:0e:87:f3:0e (try 1/3)
[ 17.207734] [TX] TX 30 bytes (queue: 0, link_id: 0 (0)).
[ 17.207747] [TX] EPTA priority 5.
[ 17.207764] [BH] wakeup.
[ 17.207870] [WSM] >>> 0x0004 (54) 8e49b458
[ 17.207969] --> 36 00 04 40 00 00 00 02 00 03 00 0a 00 00 00 00 6..@............
[ 17.207983] --> 00 00 00 00 01 00 00 00 b0 00 3a 01 c0 3f 0e 87 ..........:..?..
[ 17.207994] --> f3 0e 00 80 e1 3d 80 24 c0 3f 0e 87 f3 0e 90 04 .....=.$.?......
[ 17.208005] --> 00 00 01 00 00 00 ......
[ 17.208837] [BH] irq.
[ 17.208870] [BH] irq.
[ 17.208998] <-- 18 00 04 24 00 00 00 02 00 00 00 00 00 00 00 00 ...$............
[ 17.209011] <-- 42 03 00 00 2f 00 00 00 B.../...
[ 17.209023] [WSM] <<< 0x0404 (24)
[ 17.209032] [TX] TX confirm: 0, 0.
[ 17.209339] [BH] irq.
[ 17.209374] [BH] irq.
[ 17.209408] [BH] irq.
[ 17.209535] <-- 2e 00 04 48 00 00 00 00 03 00 00 76 00 08 01 00 ...H.......v....
[ 17.209548] <-- b0 00 3a 01 00 80 e1 3d 80 24 c0 3f 0e 87 f3 0e ..:....=.$.?....
[ 17.209559] <-- c0 3f 0e 87 f3 0e a0 00 00 00 02 00 00 00 .?............
[ 17.209570] [WSM] <<< 0x0804 (46)
[ 17.209638] wlan0: authenticated
[ 17.216442] wlan0: associate with c0:3f:0e:87:f3:0e (try 1/3)
[ 17.216480] [TX] TX 62 bytes (queue: 0, link_id: 0 (0)).
[ 17.216491] [TX] EPTA priority 5.
[ 17.216502] [BH] wakeup.
[ 17.216524] [WSM] >>> 0x0004 (86) 8e49b418
[ 17.216622] --> 56 00 04 60 00 00 00 02 00 03 00 0a 00 00 00 00 V..`............
[ 17.216635] --> 00 00 00 00 01 00 00 00 00 00 3a 01 c0 3f 0e 87 ..........:..?..
[ 17.216647] --> f3 0e 00 80 e1 3d 80 24 c0 3f 0e 87 f3 0e a0 04 .....=.$.?......
[ 17.216658] --> 21 04 05 00 00 07 63 77 5f 74 65 73 74 01 08 02 !.....cw_test...
[ 17.216669] --> 04 0b 16 0c 12 18 24 32 04 30 48 60 6c dd 07 00 ......$2.0H`l...
[ 17.216680] --> 50 f2 02 00 01 0f P.....
[ 17.222581] [BH] irq.
[ 17.222713] <-- 18 00 04 64 00 00 00 02 00 00 00 00 00 00 00 00 ...d............
[ 17.222726] <-- 23 17 00 00 11 13 00 00 #.......
[ 17.222737] [WSM] <<< 0x0404 (24)
[ 17.222745] [TX] TX confirm: 0, 0.
[ 17.223791] [BH] irq.
[ 17.223825] [BH] irq.
[ 17.223949] <-- 6f 00 04 88 00 00 00 00 03 00 00 78 00 08 01 00 o..........x....
[ 17.223962] <-- 10 00 3a 01 00 80 e1 3d 80 24 c0 3f 0e 87 f3 0e ..:....=.$.?....
[ 17.223974] <-- c0 3f 0e 87 f3 0e b0 00 21 04 00 00 01 c0 01 08 .?......!.......
[ 17.223985] <-- 82 84 8b 0c 12 96 18 24 32 04 30 48 60 6c dd 18 .......$2.0H`l..
[ 17.223997] <-- 00 50 f2 02 01 01 82 00 03 a4 00 00 27 a4 00 00 .P..........'...
[ 17.224008] <-- 42 43 5e 00 62 32 2f 00 dd 09 00 03 7f 01 01 00 BC^.b2/.........
[ 17.224019] <-- 00 ff 7f dd 0a 00 03 7f 04 01 00 02 00 40 00 .............@.
[ 17.224030] [WSM] <<< 0x0804 (111)
[ 17.224121] wlan0: RX AssocResp from c0:3f:0e:87:f3:0e (capab=0x421 status=0 aid=1)
[ 17.224134] wlan0: associated
[ 17.224978] [WSM] >>> 0x0012 (16)
[ 17.224985] [BH] wakeup.
[ 17.225091] --> 10 00 12 80 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 17.225167] [BH] irq.
[ 17.225201] [BH] irq.
[ 17.225236] [BH] irq.
[ 17.225365] <-- 08 00 12 a4 00 00 00 00 ........
[ 17.225378] [WSM] <<< 0x0412 (8)
[ 17.225440] [WSM] >>> 0x0013 (48)
[ 17.225448] [BH] wakeup.
[ 17.225546] --> 30 00 13 a0 0f 00 0f 00 07 00 03 00 ff 03 ff 03 0...............
[ 17.225559] --> 0f 00 07 00 07 03 02 02 00 00 00 00 c0 0b e0 05 ................
[ 17.225570] --> c8 00 00 00 c8 00 00 00 c8 00 00 00 c8 00 00 00 ................
[ 17.225638] [BH] irq.
[ 17.225672] [BH] irq.
[ 17.225707] [BH] irq.
[ 17.225835] <-- 08 00 13 c4 00 00 00 00 ........
[ 17.225847] [WSM] <<< 0x0413 (8)
[ 17.225906] [WSM] >>> 0x0006 [MIB: 0x1013] (16)
[ 17.225914] [BH] wakeup.
[ 17.226011] --> 10 00 06 c0 13 10 08 00 02 00 00 00 00 00 00 00 ................
[ 17.226080] [BH] irq.
[ 17.226113] [BH] irq.
[ 17.226239] <-- 08 00 06 e4 00 00 00 00 ........
[ 17.226251] [WSM] <<< 0x0406 (8)
[ 17.226310] [WSM] >>> 0x0012 (16)
[ 17.226317] [BH] wakeup.
[ 17.226414] --> 10 00 12 e0 01 00 00 00 00 00 00 00 00 00 00 00 ................
[ 17.226501] [BH] irq.
[ 17.226535] [BH] irq.
[ 17.226663] <-- 08 00 12 04 00 00 00 00 ........
[ 17.226676] [WSM] <<< 0x0412 (8)
[ 17.226732] [WSM] >>> 0x0013 (48)
[ 17.226739] [BH] wakeup.
[ 17.226836] --> 30 00 13 00 0f 00 0f 00 07 00 03 00 ff 03 ff 03 0...............
[ 17.226849] --> 0f 00 07 00 07 03 02 02 00 00 00 00 c0 0b e0 05 ................
[ 17.226861] --> c8 00 00 00 c8 00 00 00 c8 00 00 00 c8 00 00 00 ................
[ 17.226928] [BH] irq.
[ 17.226962] [BH] irq.
[ 17.227088] <-- 08 00 13 24 00 00 00 00 ...$....
[ 17.227100] [WSM] <<< 0x0413 (8)
[ 17.227156] [WSM] >>> 0x0006 [MIB: 0x1013] (16)
[ 17.227164] [BH] wakeup.
[ 17.227261] --> 10 00 06 20 13 10 08 00 03 00 00 00 00 00 00 00 ... ............
[ 17.227330] [BH] irq.
[ 17.227363] [BH] irq.
[ 17.227398] [BH] irq.
[ 17.227432] [BH] irq.
[ 17.227557] <-- 08 00 06 44 00 00 00 00 ...D....
[ 17.227569] [WSM] <<< 0x0406 (8)
[ 17.227628] [WSM] >>> 0x0012 (16)
[ 17.227635] [BH] wakeup.
[ 17.227733] --> 10 00 12 40 02 00 00 00 00 00 00 00 00 00 00 00 ...@............
[ 17.227801] [BH] irq.
[ 17.227835] [BH] irq.
[ 17.227870] [BH] irq.
[ 17.227995] <-- 08 00 12 64 00 00 00 00 ...d....
[ 17.228008] [WSM] <<< 0x0412 (8)
[ 17.228064] [WSM] >>> 0x0013 (48)
[ 17.228071] [BH] wakeup.
[ 17.228168] --> 30 00 13 60 0f 00 0f 00 07 00 03 00 ff 03 ff 03 0..`............
[ 17.228181] --> 0f 00 07 00 07 03 02 02 00 00 00 00 c0 0b e0 05 ................
[ 17.228193] --> c8 00 00 00 c8 00 00 00 c8 00 00 00 c8 00 00 00 ................
[ 17.228260] [BH] irq.
[ 17.228294] [BH] irq.
[ 17.228421] <-- 08 00 13 84 00 00 00 00 ........
[ 17.228434] [WSM] <<< 0x0413 (8)
[ 17.228490] [WSM] >>> 0x0006 [MIB: 0x1013] (16)
[ 17.228498] [BH] wakeup.
[ 17.228595] --> 10 00 06 80 13 10 08 00 07 00 00 00 00 00 00 00 ................
[ 17.228664] [BH] irq.
[ 17.228793] <-- 08 00 06 a4 00 00 00 00 ........
[ 17.228806] [WSM] <<< 0x0406 (8)
[ 17.228858] [WSM] >>> 0x0012 (16)
[ 17.228866] [BH] wakeup.
[ 17.228978] --> 10 00 12 a0 03 00 00 00 00 00 00 00 00 00 00 00 ................
[ 17.229048] [BH] irq.
[ 17.229081] [BH] irq.
[ 17.229115] [BH] irq.
[ 17.229241] <-- 08 00 12 c4 00 00 00 00 ........
[ 17.229254] [WSM] <<< 0x0412 (8)
[ 17.229313] [WSM] >>> 0x0013 (48)
[ 17.229320] [BH] wakeup.
[ 17.229417] --> 30 00 13 c0 0f 00 0f 00 07 00 03 00 ff 03 ff 03 0...............
[ 17.229430] --> 0f 00 07 00 07 03 02 02 00 00 00 00 c0 0b e0 05 ................
[ 17.229441] --> c8 00 00 00 c8 00 00 00 c8 00 00 00 c8 00 00 00 ................
[ 17.229509] [BH] irq.
[ 17.229542] [BH] irq.
[ 17.229669] <-- 08 00 13 e4 00 00 00 00 ........
[ 17.229681] [WSM] <<< 0x0413 (8)
[ 17.229739] [WSM] >>> 0x0006 [MIB: 0x1013] (16)
[ 17.229747] [BH] wakeup.
[ 17.229844] --> 10 00 06 e0 13 10 08 00 0f 00 00 00 00 00 00 00 ................
[ 17.229912] [BH] irq.
[ 17.229946] [BH] irq.
[ 17.230072] <-- 08 00 06 04 00 00 00 00 ........
[ 17.230085] [WSM] <<< 0x0406 (8)
[ 17.230146] [WSM] >>> 0x0006 [MIB: 0x1001] (16)
[ 17.230154] [BH] wakeup.
[ 17.230253] --> 10 00 06 00 01 10 08 00 00 00 00 00 00 00 00 00 ................
[ 17.230321] [BH] irq.
[ 17.230355] [BH] irq.
[ 17.230481] <-- 08 00 06 24 00 00 00 00 ...$....
[ 17.230494] [WSM] <<< 0x0406 (8)
[ 17.230522] [WSM] TX is locked.
[ 17.230529] [BH] wakeup.
[ 17.230535] [WSM] TX is unlocked.
[ 17.230549] [WSM] >>> 0x0006 [MIB: 0x1021] (12)
[ 17.230556] [BH] wakeup.
[ 17.230655] --> 0c 00 06 20 21 10 04 00 00 00 00 00 ... !.......
[ 17.230724] [BH] irq.
[ 17.230758] [BH] irq.
[ 17.230884] <-- 08 00 06 44 00 00 00 00 ...D....
[ 17.230896] [WSM] <<< 0x0406 (8)
[ 17.230928] [WSM] >>> 0x0006 [MIB: 0x1010] (16)
[ 17.230936] [BH] wakeup.
[ 17.231034] --> 10 00 06 40 10 10 08 00 1f 01 00 00 0f 00 00 00 ...@............
[ 17.231660] [BH] irq.
[ 17.231693] [BH] irq.
[ 17.231820] <-- 08 00 06 64 00 00 00 00 ...d....
[ 17.231832] [WSM] <<< 0x0406 (8)
[ 17.231865] [WSM] >>> 0x0006 [MIB: 0x1025] (12)
[ 17.231873] [BH] wakeup.
[ 17.231970] --> 0c 00 06 60 25 10 04 00 1e 00 00 00 ...`%.......
[ 17.232038] [BH] irq.
[ 17.232072] [BH] irq.
[ 17.232198] <-- 08 00 06 84 00 00 00 00 ........
[ 17.232215] [WSM] <<< 0x0406 (8)
[ 17.232248] [WSM] >>> 0x0011 (12)
[ 17.232255] [BH] wakeup.
[ 17.232352] --> 0c 00 11 80 00 14 01 00 cf 3f 00 00 .........?..
[ 17.232421] [BH] irq.
[ 17.232455] [BH] irq.
[ 17.232491] [BH] irq.
[ 17.232617] <-- 08 00 11 a4 00 00 00 00 ........
[ 17.232629] [WSM] <<< 0x0411 (8)
[ 17.232660] [WSM] >>> 0x0006 [MIB: 0x1007] (12)
[ 17.232668] [BH] wakeup.
[ 17.232766] --> 0c 00 06 a0 07 10 04 00 03 00 00 00 ............
[ 17.232834] [BH] irq.
[ 17.232867] [BH] irq.
[ 17.232902] [BH] irq.
[ 17.233029] <-- 08 00 06 c4 00 00 00 00 ........
[ 17.233042] [WSM] <<< 0x0406 (8)
[ 17.233078] [WSM] >>> 0x0006 [MIB: 0x1002] (28)
[ 17.233085] [BH] wakeup.
[ 17.233183] --> 1c 00 06 c0 02 10 14 00 04 ff 10 00 a4 00 01 c0 ................
[ 17.233196] --> c0 3f 0e 87 f3 0e 00 80 e1 3d 80 24 .?.......=.$
[ 17.233264] [BH] irq.
[ 17.233297] [BH] irq.
[ 17.233332] [BH] irq.
[ 17.233457] <-- 08 00 06 e4 00 00 00 00 ........
[ 17.233470] [WSM] <<< 0x0406 (8)
[ 17.233505] [WSM] >>> 0x0006 [MIB: 0x1002] (36)
[ 17.233513] [BH] wakeup.
[ 17.233611] --> 24 00 06 e0 02 10 1c 00 02 ff 18 00 48 01 00 00 $...........H...
[ 17.233625] --> c0 3f 0e 87 f3 0e 00 80 e1 3d 80 24 c0 3f 0e 87 .?.......=.$.?..
[ 17.233636] --> f3 0e 00 00 ....
[ 17.233703] [BH] irq.
[ 17.233737] [BH] irq.
[ 17.233772] [BH] irq.
[ 17.233805] [BH] irq.
[ 17.233931] <-- 08 00 06 04 00 00 00 00 ........
[ 17.233944] [WSM] <<< 0x0406 (8)
[ 17.233976] [WSM] >>> 0x0006 [MIB: 0x100F] (12)
[ 17.233984] [BH] wakeup.
[ 17.234082] --> 0c 00 06 00 0f 10 04 00 06 00 00 00 ............
[ 17.234152] [BH] irq.
[ 17.234185] [BH] irq.
[ 17.234311] <-- 08 00 06 24 00 00 00 00 ...$....
[ 17.234324] [WSM] <<< 0x0406 (8)
[ 17.234355] [WSM] >>> 0x0006 [MIB: 0x0003] (12)
[ 17.234362] [BH] wakeup.
[ 17.234460] --> 0c 00 06 20 03 00 04 00 09 00 00 00 ... ........
[ 17.234529] [BH] irq.
[ 17.234562] [BH] irq.
[ 17.234688] <-- 08 00 06 44 00 00 00 00 ...D....
[ 17.234701] [WSM] <<< 0x0406 (8)
[ 17.234732] [WSM] >>> 0x0006 [MIB: 0x1009] (12)
[ 17.234739] [BH] wakeup.
[ 17.234837] --> 0c 00 06 40 09 10 04 00 0d 00 00 08 ...@........
[ 17.234905] [BH] irq.
[ 17.234938] [BH] irq.
[ 17.234973] [BH] irq.
[ 17.235100] <-- 08 00 06 64 00 00 00 00 ...d....
[ 17.235112] [WSM] <<< 0x0406 (8)
[ 17.235150] [WSM] >>> 0x0010 (8)
[ 17.235157] [BH] wakeup.
[ 17.235256] --> 08 00 10 60 01 c8 00 00 ...`....
[ 17.235326] [BH] irq.
[ 17.235360] [BH] irq.
[ 17.235486] <-- 08 00 10 84 00 00 00 00 ........
[ 17.235498] [WSM] <<< 0x0410 (8)
[ 17.235740] cfg80211: Calling CRDA for country: US
[ 17.240651] [BH] irq.
[ 17.240685] [BH] irq.
[ 17.242391] <-- 0c 00 09 a8 00 00 00 00 01 00 00 00 ............
[ 17.242414] [WSM] <<< 0x0809 (12)
[ 17.242622] cfg80211: Regulatory domain changed to country: US
[ 17.250925] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 17.259188] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[ 17.266954] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
[ 17.274706] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 17.282468] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 17.290320] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 17.298109] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
[ 18.236467] [BH] Device wakedown.
[ 18.926444] wlan0: Connection to AP c0:3f:0e:87:f3:0e lost.
[ 18.926525] [WSM] >>> 0x0010 (8)
[ 18.926534] [BH] wakeup.
[ 18.926551] [BH] Device wakeup.
[ 18.934628] [BH] irq.
[ 18.934668] [BH] irq.
[ 18.934704] [BH] irq.
[ 18.934748] [BH] Device wakeup.
[ 18.934806] [BH] Device awake.
[ 18.934902] --> 08 00 10 80 00 c8 00 00 ........
[ 18.935798] [BH] irq.
[ 18.935930] <-- 08 00 10 c4 00 00 00 00 ........
[ 18.935944] [WSM] <<< 0x0410 (8)
[ 18.935985] [WSM] >>> 0x0006 [MIB: 0x1009] (12)
[ 18.935993] [BH] wakeup.
[ 18.936093] --> 0c 00 06 a0 09 10 04 00 0d 00 00 10 ............
[ 18.936164] [BH] irq.
[ 18.936198] [BH] irq.
[ 18.936326] <-- 0c 00 09 e8 00 00 00 00 00 00 00 00 ............
[ 18.936339] [WSM] <<< 0x0809 (12)
[ 18.936451] <-- 08 00 06 04 00 00 00 00 ........
[ 18.936464] [WSM] <<< 0x0406 (8)
[ 18.936497] [WSM] >>> 0x0006 [MIB: 0x1001] (16)
[ 18.936505] [BH] wakeup.
[ 18.936604] --> 10 00 06 c0 01 10 08 00 00 00 00 00 00 00 00 00 ................
[ 18.936672] [BH] irq.
[ 18.936706] [BH] irq.
[ 18.936832] <-- 08 00 06 24 00 00 00 00 ...$....
[ 18.936845] [WSM] <<< 0x0406 (8)
[ 18.936873] [WSM] TX is locked.
[ 18.936881] [BH] wakeup.
[ 18.936887] [WSM] TX is unlocked.
[ 18.936896] [WSM] >>> 0x0006 [MIB: 0x0003] (12)
[ 18.936903] [BH] wakeup.
[ 18.937001] --> 0c 00 06 e0 03 00 04 00 14 00 00 00 ............
[ 18.937072] [BH] irq.
[ 18.937106] [BH] irq.
[ 18.937140] [BH] irq.
[ 18.937267] <-- 08 00 06 44 00 00 00 00 ...D....
[ 18.937279] [WSM] <<< 0x0406 (8)
[ 18.937311] [WSM] >>> 0x0006 [MIB: 0x1009] (12)
[ 18.937319] [BH] wakeup.
[ 18.937416] --> 0c 00 06 00 09 10 04 00 0d 00 00 08 ............
[ 18.937485] [BH] irq.
[ 18.937518] [BH] irq.
[ 18.937553] [BH] irq.
[ 18.937586] [BH] irq.
[ 18.937714] <-- 08 00 06 64 00 00 00 00 ...d....
[ 18.937726] [WSM] <<< 0x0406 (8)
[ 18.937764] [WSM] >>> 0x0012 (16)
[ 18.937771] [BH] wakeup.
[ 18.937870] --> 10 00 12 20 03 00 00 00 00 00 00 00 00 00 00 00 ... ............
[ 18.937940] [BH] irq.
[ 18.937973] [BH] irq.
[ 18.938009] [BH] irq.
[ 18.938135] <-- 08 00 12 84 00 00 00 00 ........
[ 18.938147] [WSM] <<< 0x0412 (8)
[ 18.938183] [WSM] >>> 0x0013 (48)
[ 18.938190] [BH] wakeup.
[ 18.938287] --> 30 00 13 40 0f 00 0f 00 07 00 03 00 ff 03 ff 03 0..@............
[ 18.938300] --> 0f 00 07 00 07 03 02 02 00 00 00 00 c0 0b e0 05 ................
[ 18.938312] --> c8 00 00 00 c8 00 00 00 c8 00 00 00 c8 00 00 00 ................
[ 18.938381] [BH] irq.
[ 18.938415] [BH] irq.
[ 18.938450] [BH] irq.
[ 18.938576] <-- 08 00 13 a4 00 00 00 00 ........
[ 18.938589] [WSM] <<< 0x0413 (8)
[ 18.938620] [WSM] >>> 0x0006 [MIB: 0x1013] (16)
[ 18.938628] [BH] wakeup.
[ 18.938726] --> 10 00 06 60 13 10 08 00 07 00 00 00 00 00 00 00 ...`............
[ 18.938797] [BH] irq.
[ 18.938832] [BH] irq.
[ 18.938959] <-- 08 00 06 c4 00 00 00 00 ........
[ 18.938971] [WSM] <<< 0x0406 (8)
[ 18.939003] [WSM] >>> 0x0012 (16)
[ 18.939010] [BH] wakeup.
[ 18.939108] --> 10 00 12 80 02 00 00 00 00 00 00 00 00 00 00 00 ................
[ 18.939177] [BH] irq.
[ 18.939211] [BH] irq.
[ 18.939338] <-- 08 00 12 e4 00 00 00 00 ........
[ 18.939350] [WSM] <<< 0x0412 (8)
[ 18.939381] [WSM] >>> 0x0013 (48)
[ 18.939388] [BH] wakeup.
[ 18.939486] --> 30 00 13 a0 0f 00 0f 00 07 00 03 00 ff 03 ff 03 0...............
[ 18.939500] --> 0f 00 07 00 07 03 02 02 00 00 00 00 c0 0b e0 05 ................
[ 18.939512] --> c8 00 00 00 c8 00 00 00 c8 00 00 00 c8 00 00 00 ................
[ 18.939581] [BH] irq.
[ 18.939615] [BH] irq.
[ 18.939743] <-- 08 00 13 04 00 00 00 00 ........
[ 18.939756] [WSM] <<< 0x0413 (8)
[ 18.939788] [WSM] >>> 0x0006 [MIB: 0x1013] (16)
[ 18.939796] [BH] wakeup.
[ 18.939894] --> 10 00 06 c0 13 10 08 00 03 00 00 00 00 00 00 00 ................
[ 18.939963] [BH] irq.
[ 18.939996] [BH] irq.
[ 18.940031] [BH] irq.
[ 18.940158] <-- 08 00 06 24 00 00 00 00 ...$....
[ 18.940170] [WSM] <<< 0x0406 (8)
[ 18.940201] [WSM] >>> 0x0012 (16)
[ 18.940208] [BH] wakeup.
[ 18.940306] --> 10 00 12 e0 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 18.940375] [BH] irq.
[ 18.940504] <-- 08 00 12 44 00 00 00 00 ...D....
[ 18.940517] [WSM] <<< 0x0412 (8)
[ 18.940547] [WSM] >>> 0x0013 (48)
[ 18.940553] [BH] wakeup.
[ 18.940652] --> 30 00 13 00 0f 00 0f 00 07 00 03 00 ff 03 ff 03 0...............
[ 18.940665] --> 0f 00 07 00 07 03 02 02 00 00 00 00 c0 0b e0 05 ................
[ 18.940676] --> c8 00 00 00 c8 00 00 00 c8 00 00 00 c8 00 00 00 ................
[ 18.940746] [BH] irq.
[ 18.940779] [BH] irq.
[ 18.940906] <-- 08 00 13 64 00 00 00 00 ...d....
[ 18.940918] [WSM] <<< 0x0413 (8)
[ 18.940949] [WSM] >>> 0x0006 [MIB: 0x1013] (16)
[ 18.940957] [BH] wakeup.
[ 18.941055] --> 10 00 06 20 13 10 08 00 01 00 00 00 00 00 00 00 ... ............
[ 18.941123] [BH] irq.
[ 18.941253] <-- 08 00 06 84 00 00 00 00 ........
[ 18.941266] [WSM] <<< 0x0406 (8)
[ 18.941296] [WSM] >>> 0x0012 (16)
[ 18.941302] [BH] wakeup.
[ 18.941400] --> 10 00 12 40 01 00 00 00 00 00 00 00 00 00 00 00 ...@............
[ 18.941469] [BH] irq.
[ 18.941502] [BH] irq.
[ 18.941537] [BH] irq.
[ 18.941662] <-- 08 00 12 a4 00 00 00 00 ........
[ 18.941674] [WSM] <<< 0x0412 (8)
[ 18.941705] [WSM] >>> 0x0013 (48)
[ 18.941712] [BH] wakeup.
[ 18.941810] --> 30 00 13 60 0f 00 0f 00 07 00 03 00 ff 03 ff 03 0..`............
[ 18.941823] --> 0f 00 07 00 07 03 02 02 00 00 00 00 c0 0b e0 05 ................
[ 18.941834] --> c8 00 00 00 c8 00 00 00 c8 00 00 00 c8 00 00 00 ................
[ 18.941902] [BH] irq.
[ 18.941936] [BH] irq.
[ 18.941971] [BH] irq.
[ 18.942097] <-- 08 00 13 c4 00 00 00 00 ........
[ 18.942109] [WSM] <<< 0x0413 (8)
[ 18.942140] [WSM] >>> 0x0006 [MIB: 0x1013] (16)
[ 18.942148] [BH] wakeup.
[ 18.942245] --> 10 00 06 80 13 10 08 00 00 00 00 00 00 00 00 00 ................
[ 18.942314] [BH] irq.
[ 18.942348] [BH] irq.
[ 18.942475] <-- 08 00 06 e4 00 00 00 00 ........
[ 18.942487] [WSM] <<< 0x0406 (8)
[ 18.942565] [WSM] TX is locked.
[ 18.942574] [BH] wakeup.
[ 18.942580] [WSM] TX is unlocked.
[ 18.942587] [WSM] TX is locked.
[ 18.942596] [WSM] >>> 0x0006 [MIB: 0x1006] (9)
[ 18.942603] [BH] wakeup.
[ 18.942674] cfg80211: Calling CRDA to update world regulatory domain
[ 18.949076] --> 09 00 06 a0 06 10 01 00 12 .........
[ 18.949136] [BH] irq.
[ 18.949169] [BH] irq.
[ 18.950817] <-- 08 00 06 04 00 00 00 00 ........
[ 18.950839] [WSM] <<< 0x0406 (8)
[ 18.950848] [BH] Powerave is enabled.
[ 18.950973] [BH] wakeup.
[ 18.950997] [WSM] TX is unlocked.
[ 18.951097] cfg80211: World regulatory domain updated:
[ 18.956243] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 18.966897] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 18.974657] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 18.982462] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 18.990231] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 18.997998] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 19.946425] [BH] Device wakedown.
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-05-03 16:42 ` Kevin Groeneveld
@ 2012-05-03 17:23 ` Dmitry Tarnyagin
2012-05-03 18:57 ` Kevin Groeneveld
0 siblings, 1 reply; 33+ messages in thread
From: Dmitry Tarnyagin @ 2012-05-03 17:23 UTC (permalink / raw)
To: Kevin Groeneveld; +Cc: linux-wireless
Hi Kevin,
> However, I have not been able to actually connect
> to any networks. :(
You actually connected :)
AUTH request:
[ 17.207870] [WSM] >>> 0x0004 (54) 8e49b458
[ 17.207969] --> 36 00 04 40 00 00 00 02 00 03 00 0a 00 00 00 00
6..@............
[ 17.207983] --> 00 00 00 00 01 00 00 00 b0 00 3a 01 c0 3f 0e 87
..........:..?..
[ 17.207994] --> f3 0e 00 80 e1 3d 80 24 c0 3f 0e 87 f3 0e 90 04
.....=.$.?......
[ 17.208005] --> 00 00 01 00 00 00 ......
AUTH response:
[ 17.209535] <-- 2e 00 04 48 00 00 00 00 03 00 00 76 00 08 01 00
...H.......v....
[ 17.209548] <-- b0 00 3a 01 00 80 e1 3d 80 24 c0 3f 0e 87 f3 0e
..:....=.$.?....
[ 17.209559] <-- c0 3f 0e 87 f3 0e a0 00 00 00 02 00 00 00
.?............
[ 17.209570] [WSM] <<< 0x0804 (46)
ASSOC request:
[ 17.216524] [WSM] >>> 0x0004 (86) 8e49b418
[ 17.216622] --> 56 00 04 60 00 00 00 02 00 03 00 0a 00 00 00 00
V..`............
[ 17.216635] --> 00 00 00 00 01 00 00 00 00 00 3a 01 c0 3f 0e 87
..........:..?..
[ 17.216647] --> f3 0e 00 80 e1 3d 80 24 c0 3f 0e 87 f3 0e a0 04
.....=.$.?......
[ 17.216658] --> 21 04 05 00 00 07 63 77 5f 74 65 73 74 01 08 02
!.....cw_test...
[ 17.216669] --> 04 0b 16 0c 12 18 24 32 04 30 48 60 6c dd 07 00
......$2.0H`l...
[ 17.216680] --> 50 f2 02 00 01 0f P.....
ASSOC response:
[ 17.223949] <-- 6f 00 04 88 00 00 00 00 03 00 00 78 00 08 01 00
o..........x....
[ 17.223962] <-- 10 00 3a 01 00 80 e1 3d 80 24 c0 3f 0e 87 f3 0e
..:....=.$.?....
[ 17.223974] <-- c0 3f 0e 87 f3 0e b0 00 21 04 00 00 01 c0 01 08
.?......!.......
[ 17.223985] <-- 82 84 8b 0c 12 96 18 24 32 04 30 48 60 6c dd 18
.......$2.0H`l..
[ 17.223997] <-- 00 50 f2 02 01 01 82 00 03 a4 00 00 27 a4 00 00
.P..........'...
[ 17.224008] <-- 42 43 5e 00 62 32 2f 00 dd 09 00 03 7f 01 01 00
BC^.b2/.........
[ 17.224019] <-- 00 ff 7f dd 0a 00 03 7f 04 01 00 02 00 40 00
.............@.
[ 17.224030] [WSM] <<< 0x0804 (111)
,
but then you've got almost immediately
[ 18.926444] wlan0: Connection to AP c0:3f:0e:87:f3:0e lost.
It looks like mac80211 tries to monitor beacons and they are filtered by
cw1200 device.
IEEE80211_HW_CONNECTION_MONITOR and / or IEEE80211_HW_BEACON_FILTER flags
(I don't remember, but both of them should be set) should prevent
mac80211 from
monitoring. Please check if they are set in
drivers/net/wireless/cw1200/main.c
>
>> Also I see unexpectedly high rate of IRQs, they should not come every now
>> and then..
> Any ideas what could cause this or how I should debug it?
Are you running with SDIO or GPIO IRQ?
With best regards,
Dmitry
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-05-03 17:23 ` Dmitry Tarnyagin
@ 2012-05-03 18:57 ` Kevin Groeneveld
2012-05-03 21:57 ` Janusz Dziedzic
0 siblings, 1 reply; 33+ messages in thread
From: Kevin Groeneveld @ 2012-05-03 18:57 UTC (permalink / raw)
To: Dmitry Tarnyagin; +Cc: linux-wireless
Hi Dmitry,
> It looks like mac80211 tries to monitor beacons and they are filtered by
> cw1200 device.
>
> IEEE80211_HW_CONNECTION_MONITOR and / or IEEE80211_HW_BEACON_FILTER flags
> (I don't remember, but both of them should be set) should prevent mac80211
> from
> monitoring. Please check if they are set in
> drivers/net/wireless/cw1200/main.c
main.c contains the following as in the patches that you posted:
hw->flags = IEEE80211_HW_SIGNAL_DBM |
IEEE80211_HW_SUPPORTS_PS |
IEEE80211_HW_SUPPORTS_DYNAMIC_PS |
IEEE80211_HW_REPORTS_TX_ACK_STATUS |
IEEE80211_HW_SUPPORTS_UAPSD |
IEEE80211_HW_CONNECTION_MONITOR |
IEEE80211_HW_NEED_DTIM_PERIOD;
IEEE80211_HW_BEACON_FILTER does not seem to be defined anywhere in the
header files. Do I need this?
>>> Also I see unexpectedly high rate of IRQs, they should not come every now
>>> and then..
>>
>> Any ideas what could cause this or how I should debug it?
>
> Are you running with SDIO or GPIO IRQ?
I am using SDIO IRQ.
Thanks,
Kevin
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-05-03 18:57 ` Kevin Groeneveld
@ 2012-05-03 21:57 ` Janusz Dziedzic
2012-05-04 0:10 ` Kevin Groeneveld
0 siblings, 1 reply; 33+ messages in thread
From: Janusz Dziedzic @ 2012-05-03 21:57 UTC (permalink / raw)
To: Kevin Groeneveld; +Cc: Dmitry Tarnyagin, linux-wireless
2012/5/3 Kevin Groeneveld <kgroeneveld@gmail.com>:
> Hi Dmitry,
>
>> It looks like mac80211 tries to monitor beacons and they are filtered by
>> cw1200 device.
>>
>> IEEE80211_HW_CONNECTION_MONITOR and / or IEEE80211_HW_BEACON_FILTER flags
>> (I don't remember, but both of them should be set) should prevent mac80211
>> from
>> monitoring. Please check if they are set in
>> drivers/net/wireless/cw1200/main.c
>
> main.c contains the following as in the patches that you posted:
>
> hw->flags = IEEE80211_HW_SIGNAL_DBM |
> IEEE80211_HW_SUPPORTS_PS |
> IEEE80211_HW_SUPPORTS_DYNAMIC_PS |
> IEEE80211_HW_REPORTS_TX_ACK_STATUS |
> IEEE80211_HW_SUPPORTS_UAPSD |
> IEEE80211_HW_CONNECTION_MONITOR |
> IEEE80211_HW_NEED_DTIM_PERIOD;
>
> IEEE80211_HW_BEACON_FILTER does not seem to be defined anywhere in the
> header files. Do I need this?
>
>>>> Also I see unexpectedly high rate of IRQs, they should not come every now
>>>> and then..
>>>
>>> Any ideas what could cause this or how I should debug it?
>>
>> Are you running with SDIO or GPIO IRQ?
>
> I am using SDIO IRQ.
>
>
Seems this flag is per vif in new compat now.
IEEE80211_VIF_BEACON_FILTER
IEEE80211_VIF_SUPPORTS_CQM_RSSI
So, you should configure this in cw1200_add_interface() for new compat-wireless:
vif->driver_flags |= IEEE80211_VIF_BEACON_FILTER |
IEEE80211_VIF_SUPPORTS_CQM_RSSI;
BR
Janusz
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-05-03 21:57 ` Janusz Dziedzic
@ 2012-05-04 0:10 ` Kevin Groeneveld
2012-05-04 21:40 ` Kevin Groeneveld
0 siblings, 1 reply; 33+ messages in thread
From: Kevin Groeneveld @ 2012-05-04 0:10 UTC (permalink / raw)
To: Janusz Dziedzic; +Cc: Dmitry Tarnyagin, linux-wireless
Hello Janusz,
> Seems this flag is per vif in new compat now.
> IEEE80211_VIF_BEACON_FILTER
> IEEE80211_VIF_SUPPORTS_CQM_RSSI
>
> So, you should configure this in cw1200_add_interface() for new
> compat-wireless:
>
> vif->driver_flags |= IEEE80211_VIF_BEACON_FILTER |
> IEEE80211_VIF_SUPPORTS_CQM_RSSI;
Thanks for the suggestion. I will take a look at this tomorrow.
On a positive note, just before leaving for the day I fired up hostapd
and was able to connect a couple clients to the cw1200 in AP mode! I
didn't test it very much but it seemed to be working okay. I
transferred a couple hundred MB of data without any issue. I was only
getting about 500kB per second but I suspect all the logging I have
turned on may be slowing it down. I am not even sure what rate I was
connected at as I was using an old MacBook for the test and not being
a Mac guy I couldn't figure out how to see what rate the WiFi was
connected at.
So if AP mode is working station mode can't be that far off...
Thanks,
Kevin
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-05-04 0:10 ` Kevin Groeneveld
@ 2012-05-04 21:40 ` Kevin Groeneveld
2012-05-05 7:20 ` Janusz Dziedzic
0 siblings, 1 reply; 33+ messages in thread
From: Kevin Groeneveld @ 2012-05-04 21:40 UTC (permalink / raw)
To: linux-wireless; +Cc: Dmitry Tarnyagin
>> So, you should configure this in cw1200_add_interface() for new
>> compat-wireless:
>>
>> vif->driver_flags |= IEEE80211_VIF_BEACON_FILTER |
>> IEEE80211_VIF_SUPPORTS_CQM_RSSI;
I tried adding the above code today and I can now connect in station mode.
While connected in station mode I get a lot of the following warnings
in the log:
ieee80211 phy1: Slowpath: tailroom is not big enough. Req: 8, got: 0.
Is that anything to worry about?
The driver did seem to crash on me once today spewing out a lot of
WARNINGs and trace info to the log. Unfortunately I didn't save the
log. I will try to pay more attention to it if it happens again.
I also did a bit more testing in AP mode. After changing hostapd to
802.11g mode I got much better throughput. However, I did see quite a
few warnings in the log such as the following:
[ 296.854219] ieee80211 phy2: Missed interrupt?
[ 297.104219] ieee80211 phy2: Multicast delivery timeout.
[ 254.194450] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
asleep: 0x00000002
[ 34.731942] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
asleep: 0x00000002
[ 462.159614] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
asleep: 0x00000002
[ 482.560642] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
asleep: 0x00000002
[ 482.568372] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
asleep: 0x00000002
[ 482.601447] ieee80211 phy2: Multicast delivery timeout.
[ 482.736948] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
asleep: 0x00000006
[ 482.879955] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
asleep: 0x00000006
[ 483.052676] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
asleep: 0x00000006
[ 483.570836] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
asleep: 0x00000006
[ 483.578685] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
asleep: 0x00000006
[ 483.765740] ieee80211 phy2: Requeue for link_id 1 (try 2). STAs
asleep: 0x00000006
[ 483.773462] ieee80211 phy2: Requeue for link_id 1 (try 2). STAs
asleep: 0x00000006
[ 484.340904] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
asleep: 0x00000006
[ 484.348626] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
asleep: 0x00000006
[ 484.356344] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
asleep: 0x00000006
[ 484.670846] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
asleep: 0x00000006
[ 484.903498] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
asleep: 0x00000006
[ 2.101774] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
asleep: 0x00000000
[ 2.109569] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
asleep: 0x00000000
[ 2.119271] ieee80211 phy2: Requeue for link_id 0 (try 2). STAs
asleep: 0x00000000
[ 2.128483] ieee80211 phy2: Requeue for link_id 0 (try 2). STAs
asleep: 0x00000004
[ 2.137894] ieee80211 phy2: Requeue for link_id 0 (try 3). STAs
asleep: 0x00000004
[ 5.629055] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
asleep: 0x00000004
[ 81.020541] ieee80211 phy2: Missed interrupt?
[ 85.050556] ieee80211 phy2: Missed interrupt?
[ 96.410571] ieee80211 phy2: Missed interrupt?
[ 100.410560] ieee80211 phy2: Missed interrupt?
[ 105.700565] ieee80211 phy2: Missed interrupt?
[ 119.410573] ieee80211 phy2: Missed interrupt?
[ 140.050548] ieee80211 phy2: Missed interrupt?
[ 156.993680] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
asleep: 0x00000004
[ 157.001679] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
asleep: 0x00000004
[ 157.240546] ieee80211 phy2: Multicast delivery timeout.
[ 167.400528] ieee80211 phy2: Missed interrupt?
Should I be worried about these?
Thanks,
Kevin
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-05-04 21:40 ` Kevin Groeneveld
@ 2012-05-05 7:20 ` Janusz Dziedzic
2012-05-07 9:25 ` Janusz Dziedzic
0 siblings, 1 reply; 33+ messages in thread
From: Janusz Dziedzic @ 2012-05-05 7:20 UTC (permalink / raw)
To: Kevin Groeneveld; +Cc: linux-wireless, Dmitry Tarnyagin
2012/5/4 Kevin Groeneveld <kgroeneveld@gmail.com>:
>>> So, you should configure this in cw1200_add_interface() for new
>>> compat-wireless:
>>>
>>> vif->driver_flags |= IEEE80211_VIF_BEACON_FILTER |
>>> IEEE80211_VIF_SUPPORTS_CQM_RSSI;
>
> I tried adding the above code today and I can now connect in station mode.
>
> While connected in station mode I get a lot of the following warnings
> in the log:
>
> ieee80211 phy1: Slowpath: tailroom is not big enough. Req: 8, got: 0.
>
> Is that anything to worry about?
Yes we have patch for this in mac80211. I can send you on monday.
cw1200 firmware required pre-allocated IVs.
Without that performance will be very poor.
There is similar patch in community code - but seems not fullfill all
our requirements.
>
> The driver did seem to crash on me once today spewing out a lot of
> WARNINGs and trace info to the log. Unfortunately I didn't save the
> log. I will try to pay more attention to it if it happens again.
>
> I also did a bit more testing in AP mode. After changing hostapd to
> 802.11g mode I got much better throughput. However, I did see quite a
> few warnings in the log such as the following:
>
> [ 296.854219] ieee80211 phy2: Missed interrupt?
This is critical and this is firmware issue.
After that driver can do recovery ...
So, logs after that are not important much ...
> [ 297.104219] ieee80211 phy2: Multicast delivery timeout.
> [ 254.194450] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
> asleep: 0x00000002
> [ 34.731942] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
> asleep: 0x00000002
> [ 462.159614] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
> asleep: 0x00000002
> [ 482.560642] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
> asleep: 0x00000002
> [ 482.568372] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
> asleep: 0x00000002
> [ 482.601447] ieee80211 phy2: Multicast delivery timeout.
> [ 482.736948] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
> asleep: 0x00000006
> [ 482.879955] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
> asleep: 0x00000006
> [ 483.052676] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
> asleep: 0x00000006
> [ 483.570836] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
> asleep: 0x00000006
> [ 483.578685] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
> asleep: 0x00000006
> [ 483.765740] ieee80211 phy2: Requeue for link_id 1 (try 2). STAs
> asleep: 0x00000006
> [ 483.773462] ieee80211 phy2: Requeue for link_id 1 (try 2). STAs
> asleep: 0x00000006
> [ 484.340904] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
> asleep: 0x00000006
> [ 484.348626] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
> asleep: 0x00000006
> [ 484.356344] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
> asleep: 0x00000006
> [ 484.670846] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
> asleep: 0x00000006
> [ 484.903498] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
> asleep: 0x00000006
> [ 2.101774] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
> asleep: 0x00000000
> [ 2.109569] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
> asleep: 0x00000000
> [ 2.119271] ieee80211 phy2: Requeue for link_id 0 (try 2). STAs
> asleep: 0x00000000
> [ 2.128483] ieee80211 phy2: Requeue for link_id 0 (try 2). STAs
> asleep: 0x00000004
> [ 2.137894] ieee80211 phy2: Requeue for link_id 0 (try 3). STAs
> asleep: 0x00000004
> [ 5.629055] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
> asleep: 0x00000004
> [ 81.020541] ieee80211 phy2: Missed interrupt?
> [ 85.050556] ieee80211 phy2: Missed interrupt?
> [ 96.410571] ieee80211 phy2: Missed interrupt?
> [ 100.410560] ieee80211 phy2: Missed interrupt?
> [ 105.700565] ieee80211 phy2: Missed interrupt?
> [ 119.410573] ieee80211 phy2: Missed interrupt?
> [ 140.050548] ieee80211 phy2: Missed interrupt?
> [ 156.993680] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
> asleep: 0x00000004
> [ 157.001679] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
> asleep: 0x00000004
> [ 157.240546] ieee80211 phy2: Multicast delivery timeout.
> [ 167.400528] ieee80211 phy2: Missed interrupt?
>
> Should I be worried about these?
>
Yes :)
--
Janusz Dziedzic
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-05-05 7:20 ` Janusz Dziedzic
@ 2012-05-07 9:25 ` Janusz Dziedzic
2012-05-07 19:54 ` Kevin Groeneveld
0 siblings, 1 reply; 33+ messages in thread
From: Janusz Dziedzic @ 2012-05-07 9:25 UTC (permalink / raw)
To: Kevin Groeneveld; +Cc: linux-wireless, Dmitry Tarnyagin
W dniu 5 maja 2012 09:20 użytkownik Janusz Dziedzic
<janusz.dziedzic@gmail.com> napisał:
> 2012/5/4 Kevin Groeneveld <kgroeneveld@gmail.com>:
>>>> So, you should configure this in cw1200_add_interface() for new
>>>> compat-wireless:
>>>>
>>>> vif->driver_flags |= IEEE80211_VIF_BEACON_FILTER |
>>>> IEEE80211_VIF_SUPPORTS_CQM_RSSI;
>>
>> I tried adding the above code today and I can now connect in station mode.
>>
>> While connected in station mode I get a lot of the following warnings
>> in the log:
>>
>> ieee80211 phy1: Slowpath: tailroom is not big enough. Req: 8, got: 0.
>>
>> Is that anything to worry about?
>
> Yes we have patch for this in mac80211. I can send you on monday.
> cw1200 firmware required pre-allocated IVs.
> Without that performance will be very poor.
>
> There is similar patch in community code - but seems not fullfill all
> our requirements.
Please check such patch, some modification added to:
mac80211: support adding IV-room in the skb for CCMP keys
diff --git a/drivers/staging/cw1200/sta.c b/drivers/staging/cw1200/sta.c
index db05b84..2011fda 100644
--- a/drivers/staging/cw1200/sta.c
+++ b/drivers/staging/cw1200/sta.c
@@ -701,6 +701,8 @@ int cw1200_set_key(struct ieee80211_hw *dev, enum
set_key_cmd cmd,
if (sta)
peer_addr = sta->addr;
+ key->flags |= IEEE80211_KEY_FLAG_PUT_IV_SPACE;
+
switch (key->cipher) {
case WLAN_CIPHER_SUITE_WEP40:
case WLAN_CIPHER_SUITE_WEP104:
diff --git a/include/net/mac80211.h b/include/net/mac80211.h
index 965eca8..0da1806 100644
--- a/include/net/mac80211.h
+++ b/include/net/mac80211.h
@@ -939,7 +939,7 @@ static inline bool ieee80211_vif_is_mesh(struct
ieee80211_vif *vif)
* CCMP key if it requires CCMP encryption of management frames (MFP) to
* be done in software.
* @IEEE80211_KEY_FLAG_PUT_IV_SPACE: This flag should be set by the driver
- * for a CCMP key if space should be prepared for the IV, but the IV
+ * for a CCMP key <why only ccmp?> if space should be prepared for
the IV, but the IV
* itself should not be generated. Do not set together with
* @IEEE80211_KEY_FLAG_GENERATE_IV on the same key.
*/
diff --git a/net/mac80211/wpa.c b/net/mac80211/wpa.c
index 0ae23c6..8c9ae77 100644
--- a/net/mac80211/wpa.c
+++ b/net/mac80211/wpa.c
@@ -399,8 +399,7 @@ static int ccmp_encrypt_skb(struct
ieee80211_tx_data *tx, struct sk_buff *skb)
u8 scratch[6 * AES_BLOCK_SIZE];
if (info->control.hw_key &&
- !(info->control.hw_key->flags & IEEE80211_KEY_FLAG_GENERATE_IV) &&
- !(info->control.hw_key->flags & IEEE80211_KEY_FLAG_PUT_IV_SPACE)) {
+ !(info->control.hw_key->flags & IEEE80211_KEY_FLAG_GENERATE_IV)) {
/*
* hwaccel has no need for preallocated room for CCMP
* header or MIC fields
BR
Janusz
>
>>
>> The driver did seem to crash on me once today spewing out a lot of
>> WARNINGs and trace info to the log. Unfortunately I didn't save the
>> log. I will try to pay more attention to it if it happens again.
>>
>> I also did a bit more testing in AP mode. After changing hostapd to
>> 802.11g mode I got much better throughput. However, I did see quite a
>> few warnings in the log such as the following:
>>
>> [ 296.854219] ieee80211 phy2: Missed interrupt?
>
> This is critical and this is firmware issue.
> After that driver can do recovery ...
> So, logs after that are not important much ...
>
>
>> [ 297.104219] ieee80211 phy2: Multicast delivery timeout.
>> [ 254.194450] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
>> asleep: 0x00000002
>> [ 34.731942] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
>> asleep: 0x00000002
>> [ 462.159614] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
>> asleep: 0x00000002
>> [ 482.560642] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
>> asleep: 0x00000002
>> [ 482.568372] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
>> asleep: 0x00000002
>> [ 482.601447] ieee80211 phy2: Multicast delivery timeout.
>> [ 482.736948] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
>> asleep: 0x00000006
>> [ 482.879955] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
>> asleep: 0x00000006
>> [ 483.052676] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
>> asleep: 0x00000006
>> [ 483.570836] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
>> asleep: 0x00000006
>> [ 483.578685] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
>> asleep: 0x00000006
>> [ 483.765740] ieee80211 phy2: Requeue for link_id 1 (try 2). STAs
>> asleep: 0x00000006
>> [ 483.773462] ieee80211 phy2: Requeue for link_id 1 (try 2). STAs
>> asleep: 0x00000006
>> [ 484.340904] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
>> asleep: 0x00000006
>> [ 484.348626] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
>> asleep: 0x00000006
>> [ 484.356344] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
>> asleep: 0x00000006
>> [ 484.670846] ieee80211 phy2: Requeue for link_id 1 (try 1). STAs
>> asleep: 0x00000006
>> [ 484.903498] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
>> asleep: 0x00000006
>> [ 2.101774] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
>> asleep: 0x00000000
>> [ 2.109569] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
>> asleep: 0x00000000
>> [ 2.119271] ieee80211 phy2: Requeue for link_id 0 (try 2). STAs
>> asleep: 0x00000000
>> [ 2.128483] ieee80211 phy2: Requeue for link_id 0 (try 2). STAs
>> asleep: 0x00000004
>> [ 2.137894] ieee80211 phy2: Requeue for link_id 0 (try 3). STAs
>> asleep: 0x00000004
>> [ 5.629055] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
>> asleep: 0x00000004
>> [ 81.020541] ieee80211 phy2: Missed interrupt?
>> [ 85.050556] ieee80211 phy2: Missed interrupt?
>> [ 96.410571] ieee80211 phy2: Missed interrupt?
>> [ 100.410560] ieee80211 phy2: Missed interrupt?
>> [ 105.700565] ieee80211 phy2: Missed interrupt?
>> [ 119.410573] ieee80211 phy2: Missed interrupt?
>> [ 140.050548] ieee80211 phy2: Missed interrupt?
>> [ 156.993680] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
>> asleep: 0x00000004
>> [ 157.001679] ieee80211 phy2: Requeue for link_id 0 (try 1). STAs
>> asleep: 0x00000004
>> [ 157.240546] ieee80211 phy2: Multicast delivery timeout.
>> [ 167.400528] ieee80211 phy2: Missed interrupt?
>>
>> Should I be worried about these?
>>
> Yes :)
>
>
> --
> Janusz Dziedzic
--
Janusz Dziedzic
^ permalink raw reply related [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-05-07 9:25 ` Janusz Dziedzic
@ 2012-05-07 19:54 ` Kevin Groeneveld
0 siblings, 0 replies; 33+ messages in thread
From: Kevin Groeneveld @ 2012-05-07 19:54 UTC (permalink / raw)
To: Janusz Dziedzic; +Cc: linux-wireless, Dmitry Tarnyagin
> Please check such patch, some modification added to:
> mac80211: support adding IV-room in the skb for CCMP keys
Thanks for the patch. Applying it does get rid of the "Slowpath:
tailroom is not big enough" message I was seeing.
Kevin
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-05-02 16:01 ` Dmitry Tarnyagin
[not found] ` <CABF+-6XbdG_QMa0iQJMpbOsr4bXCq4mDEB6unkM8jxNGWYwFyQ@mail.gmail.com>
@ 2012-05-09 17:03 ` Kevin Groeneveld
2012-05-09 18:24 ` Dmitry Tarnyagin
1 sibling, 1 reply; 33+ messages in thread
From: Kevin Groeneveld @ 2012-05-09 17:03 UTC (permalink / raw)
To: Dmitry Tarnyagin; +Cc: linux-wireless
Hi Dmitry,
> The driver was tested with WSM_A30.02.0380 (and lot of other releases:)).
> The firmware was available at igloocommunity.org, I will try to find a link.
I found cw1200 firmware files within the following:
http://releases.linaro.org/12.04/ubuntu/leb-snowball/hwpack_linaro-lt-snowball-x11-base_20120424-15_armhf_supported.tar.gz
The wsm_xx.bin files from that tarball are identical to the ones I
already had for build 380. However, the sdd_xx.bin files are
different. When I use the sdd files from snowball nothing seems to
work. I cannot scan or make any connections.
What are the sdd files for and why would they be different?
I noticed the driver parses some information directly from the sdd
file in the cw1200_parse_SDD_file function. Does the file get used
for anything else?
With both sdd files I have the log shows:
PTA element found.
Listen Interval 5
If a PTA element is found the code always sets priv->is_BT_Present =
true. If I do not have Blue Tooth in my system should this still be
set?
Thanks,
Kevin
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-05-09 17:03 ` Kevin Groeneveld
@ 2012-05-09 18:24 ` Dmitry Tarnyagin
2012-05-09 18:33 ` Johannes Berg
2012-05-09 18:56 ` Kevin Groeneveld
0 siblings, 2 replies; 33+ messages in thread
From: Dmitry Tarnyagin @ 2012-05-09 18:24 UTC (permalink / raw)
To: Kevin Groeneveld; +Cc: Dmitry Tarnyagin, linux-wireless
Hi Kevin,
> What are the sdd files for and why would they be different?
>
SDD files contains some kind of radio calibration data and Bluetooth
arbitrage tables.
They must be aligned with particular RF design and presence of Bluetooth PTA.
If you are using PTA is your design, you should have SDD with PTA tables in.
> I noticed the driver parses some information directly from the sdd
> file in the cw1200_parse_SDD_file function. Does the file get used
> for anything else?
>
It is downloaded to firmware and the firmware uses data from it.
> If a PTA element is found the code always sets priv->is_BT_Present =
> true. If I do not have Blue Tooth in my system should this still be
> set?
>
Yes if you share antenna and use PTA (Bluetooth arbitrage) in your design.
But in this case you should have SDD with PTA entry in.
Dmitry
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-05-09 18:24 ` Dmitry Tarnyagin
@ 2012-05-09 18:33 ` Johannes Berg
2012-05-09 18:56 ` Kevin Groeneveld
1 sibling, 0 replies; 33+ messages in thread
From: Johannes Berg @ 2012-05-09 18:33 UTC (permalink / raw)
To: Dmitry Tarnyagin; +Cc: Kevin Groeneveld, Dmitry Tarnyagin, linux-wireless
On Wed, 2012-05-09 at 20:24 +0200, Dmitry Tarnyagin wrote:
> SDD files contains some kind of radio calibration data and Bluetooth
> arbitrage tables.
> They must be aligned with particular RF design and presence of Bluetooth PTA.
> If you are using PTA is your design, you should have SDD with PTA tables in.
Just to note, this is pretty ugly from a distro point of view, it
essentially means that no distro can possibly ship the firmware and you
can't get it included into linux-firmware.git either ...
Is there any way you could differentiate those to be able to ship them?
johannes
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-05-09 18:24 ` Dmitry Tarnyagin
2012-05-09 18:33 ` Johannes Berg
@ 2012-05-09 18:56 ` Kevin Groeneveld
2012-05-09 19:37 ` Dmitry Tarnyagin
2012-05-09 20:37 ` Solomon Peachy
1 sibling, 2 replies; 33+ messages in thread
From: Kevin Groeneveld @ 2012-05-09 18:56 UTC (permalink / raw)
To: Dmitry Tarnyagin; +Cc: Dmitry Tarnyagin, linux-wireless
Hi Dmitry,
Thanks for the information.
>> If a PTA element is found the code always sets priv->is_BT_Present =
>> true. If I do not have Blue Tooth in my system should this still be
>> set?
>>
> Yes if you share antenna and use PTA (Bluetooth arbitrage) in your design.
> But in this case you should have SDD with PTA entry in.
My system does not have Bluetooth at all. Will the existence of a PTA
record in my SDD file have any negative impact?
Can I just delete the PTA record? (Easier said than done since it is
a binary file... but it can be done.)
Are there any other records in the SDD file that could cause problems?
Thanks,
Kevin
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-05-09 18:56 ` Kevin Groeneveld
@ 2012-05-09 19:37 ` Dmitry Tarnyagin
2012-05-09 20:37 ` Solomon Peachy
1 sibling, 0 replies; 33+ messages in thread
From: Dmitry Tarnyagin @ 2012-05-09 19:37 UTC (permalink / raw)
To: Kevin Groeneveld; +Cc: Dmitry Tarnyagin, linux-wireless
Hi Kevin,
> My system does not have Bluetooth at all. Will the existence of a PTA
> record in my SDD file have any negative impact?
>
It will not have any valuable impact to the driver, just listen interval
will be limited a bit. And you can disable check for PTA record in the
driver code. Maybe it would be smart to make it configurable (?).
More interesting question is if presence of PTA entry affects firmware
and arbiter. I do not have a good answer for that, but I can guess it depends
on actual logical values on the PTA interface.
> Can I just delete the PTA record? (Easier said than done since it is
> a binary file... but it can be done.)
>
But why can't you use SDD from your distribution, calibrated for your RF design?
It can be really huge difference in calibration parameters with different FEMs,
antennas etc. SDDs are independent from the firmware and you can use an SDD
with any firmware version.
Dmitry
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-05-09 18:56 ` Kevin Groeneveld
2012-05-09 19:37 ` Dmitry Tarnyagin
@ 2012-05-09 20:37 ` Solomon Peachy
2012-05-09 20:59 ` Kevin Groeneveld
1 sibling, 1 reply; 33+ messages in thread
From: Solomon Peachy @ 2012-05-09 20:37 UTC (permalink / raw)
To: Kevin Groeneveld; +Cc: Dmitry Tarnyagin, Dmitry Tarnyagin, linux-wireless
[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]
On Wed, May 09, 2012 at 02:56:34PM -0400, Kevin Groeneveld wrote:
> Can I just delete the PTA record? (Easier said than done since it is
> a binary file... but it can be done.)
>
> Are there any other records in the SDD file that could cause problems?
For any given design with the cw1200, you're likely to need an SDD file
specific to that design. That's because the SDD file includes GPIO
mappings to control the RF front end, plus things like bluetooth
coexistence parameters, reference clocking information, and some
calibration data and output power limitations. Oh, and a macaddr too,
but that's generally overridden by the device driver anyway (eg via
platform data)
Most wifi chipsets requiring this sort of information have an embedded
or attached eeprom, but the cw1200 doesn't (presumably for cost
reasons), as it was intended to be used in cellphones that already
maintained per-device platform data.
So in short, there's no way to include a generic SDD file that will work
on all cw1200-based modules, and there's no way to detect which
particular cw1200-based device has been plugged in without the
information in the SDD file. It's a right kerfuffle.
- Solomon [who has some experience with this chipset...]
--
Solomon Peachy pizza at shaftnet dot org
Melbourne, FL ^^ (mail/jabber/gtalk) ^^
Quidquid latine dictum sit, altum viditur.
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-05-09 20:37 ` Solomon Peachy
@ 2012-05-09 20:59 ` Kevin Groeneveld
2012-05-10 13:07 ` Solomon Peachy
0 siblings, 1 reply; 33+ messages in thread
From: Kevin Groeneveld @ 2012-05-09 20:59 UTC (permalink / raw)
To: Solomon Peachy; +Cc: Dmitry Tarnyagin, Dmitry Tarnyagin, linux-wireless
> For any given design with the cw1200, you're likely to need an SDD file
> specific to that design. That's because the SDD file includes GPIO
> ...
Thanks for the further info on the SDD files Solomon.
As I mentioned in a previous post I am using the SG901-1091 module
from Sagrad. The only SDD file I have tried that works is also from
Sagrad. It makes perfect sense now that SDD files from other sources
do not work.
I still wonder why there is a PTA record in the SDD file if the
SG901-1091 module does not have Bluetooth. Could this negatively
effect performance if it is trying to play nice with Bluetooth when
Bluetooth is not being used?
Kevin
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-05-09 20:59 ` Kevin Groeneveld
@ 2012-05-10 13:07 ` Solomon Peachy
2012-05-10 20:03 ` Kevin Groeneveld
0 siblings, 1 reply; 33+ messages in thread
From: Solomon Peachy @ 2012-05-10 13:07 UTC (permalink / raw)
To: Kevin Groeneveld; +Cc: Dmitry Tarnyagin, Dmitry Tarnyagin, linux-wireless
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
On Wed, May 09, 2012 at 04:59:21PM -0400, Kevin Groeneveld wrote:
> As I mentioned in a previous post I am using the SG901-1091 module
> from Sagrad. The only SDD file I have tried that works is also from
> Sagrad. It makes perfect sense now that SDD files from other sources
> do not work.
>
> I still wonder why there is a PTA record in the SDD file if the
> SG901-1091 module does not have Bluetooth. Could this negatively
> effect performance if it is trying to play nice with Bluetooth when
> Bluetooth is not being used?
I don't believe it will cause any problems, as the bluetooth pins aren't
hooked up on the SG901-1091 module. That said, the PTA record on the
current Sagrad SDD files for the 1091/1098 modules specifies that BT
coexistence is disabled (ePTA mode = 0), so it should be functionally
equivalent to no PTA record being present.
- Solomon
--
Solomon Peachy pizza at shaftnet dot org
Melbourne, FL ^^ (mail/jabber/gtalk) ^^
Quidquid latine dictum sit, altum viditur.
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-05-10 13:07 ` Solomon Peachy
@ 2012-05-10 20:03 ` Kevin Groeneveld
0 siblings, 0 replies; 33+ messages in thread
From: Kevin Groeneveld @ 2012-05-10 20:03 UTC (permalink / raw)
To: Solomon Peachy; +Cc: Dmitry Tarnyagin, Dmitry Tarnyagin, linux-wireless
Hi Solomon,
> I don't believe it will cause any problems, as the bluetooth pins aren't
> hooked up on the SG901-1091 module. That said, the PTA record on the
> current Sagrad SDD files for the 1091/1098 modules specifies that BT
> coexistence is disabled (ePTA mode = 0), so it should be functionally
> equivalent to no PTA record being present.
It is good to know the Sagrad SDD file is disabling PTA in the
hardware even though there is a PTA record present.
Although, at least with the driver Dmitry posted on this mailing list,
the driver is taking action simply on the presence of the PTA record.
I can easily disable this for my testing.
I wonder if the parsing of the SDD file in the driver could be a
little smarter to detect that the PTA record is actually disabling PTA
and not assume the existence of a PTA record means PTA is being used.
Kevin
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-12-12 16:20 ` Johannes Berg
@ 2012-12-13 14:53 ` Solomon Peachy
0 siblings, 0 replies; 33+ messages in thread
From: Solomon Peachy @ 2012-12-13 14:53 UTC (permalink / raw)
To: Johannes Berg
Cc: Christian Lamparter, John W. Linville, Steev Klimaszewski,
Janusz Dziedzic, Dmitry Tarnyagin, linux-wireless
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
On Wed, Dec 12, 2012 at 05:20:48PM +0100, Johannes Berg wrote:
> > Is there a better way to handle this now?
> There's IEEE80211_KEY_FLAG_PUT_IV_SPACE now which does exactly that.
Excellent! I just cut all of the old crap out in favor of this.
I'm working on a revamp of the platform_data to be a little more
generic/useful/sane, but once I'm done with that, I'll put it through
checkpatch and then I think I'll be in shape to submit a patch series
for review. This weekend sometime, I think.
- Solomon
--
Solomon Peachy pizza at shaftnet dot org
Melbourne, FL ^^ (mail/jabber/gtalk) ^^
Quidquid latine dictum sit, altum viditur.
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-12-11 23:23 ` Solomon Peachy
2012-12-12 14:40 ` Kalle Valo
2012-12-12 15:13 ` Christian Lamparter
@ 2012-12-12 18:19 ` John W. Linville
2 siblings, 0 replies; 33+ messages in thread
From: John W. Linville @ 2012-12-12 18:19 UTC (permalink / raw)
To: Solomon Peachy
Cc: Steev Klimaszewski, Janusz Dziedzic, Dmitry Tarnyagin,
Johannes Berg, linux-wireless
On Tue, Dec 11, 2012 at 06:23:11PM -0500, Solomon Peachy wrote:
> > So anyway, it seems like a repost of the current version (i.e. with
> > Bob's fixes, etc) is in order?
>
> I'll have to go back and see if any of those fixes are still relevant.
>
> Anyway, let me know how I should proceed from here..
It looks like others are interacting with you on this, and you
are getting good feedback. I have no problem with you being the
maintainer for this driver -- just get it into shape and post it.
As Kalle suggested, posting it in pieces for review is usually a
good idea. A final merge patch could be posted as one single patch,
or in many cases I just combine them into a single patch myself at
the final merge.
Hth!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-12-12 16:18 ` Solomon Peachy
@ 2012-12-12 16:20 ` Johannes Berg
2012-12-13 14:53 ` Solomon Peachy
0 siblings, 1 reply; 33+ messages in thread
From: Johannes Berg @ 2012-12-12 16:20 UTC (permalink / raw)
To: Solomon Peachy
Cc: Christian Lamparter, John W. Linville, Steev Klimaszewski,
Janusz Dziedzic, Dmitry Tarnyagin, linux-wireless
On Wed, 2012-12-12 at 11:18 -0500, Solomon Peachy wrote:
> On Wed, Dec 12, 2012 at 04:13:12PM +0100, Christian Lamparter wrote:
> > Mac80211 already reserves at least 18 bytes tailroom [which can be
> > allocated by a simple skb_put]. In fact p54 uses this tailroom to
> > pass the MIC (8 bytes) + ICV (4 bytes) to the firmware. Do you need
> > more than 18 bytes?
>
> I just went back and had a look at the code -- There were two related
> workarounds: One made room for the MIC, but as you said, that hasn't
> been necessary for a while so the code was disabled.
>
> The other workaround is still in place, however -- cw1200 also needs a
> gap in the frame payload for the IV, even though it's generated by the
> firmware. I worked around this by telling setting the
> IEEE80211_KEY_FLAG_GENERATE_IV flag on the mac80211 keys, and then
> zeroing that part of the payload when the frame went out to the harware.
>
> I figured it was a less costly approach than memmoving the whole payload
> over by sizeof(ICV).
>
> Is there a better way to handle this now?
There's IEEE80211_KEY_FLAG_PUT_IV_SPACE now which does exactly that.
johannes
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-12-12 15:13 ` Christian Lamparter
@ 2012-12-12 16:18 ` Solomon Peachy
2012-12-12 16:20 ` Johannes Berg
0 siblings, 1 reply; 33+ messages in thread
From: Solomon Peachy @ 2012-12-12 16:18 UTC (permalink / raw)
To: Christian Lamparter
Cc: John W. Linville, Steev Klimaszewski, Janusz Dziedzic,
Dmitry Tarnyagin, Johannes Berg, linux-wireless
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
On Wed, Dec 12, 2012 at 04:13:12PM +0100, Christian Lamparter wrote:
> Mac80211 already reserves at least 18 bytes tailroom [which can be
> allocated by a simple skb_put]. In fact p54 uses this tailroom to
> pass the MIC (8 bytes) + ICV (4 bytes) to the firmware. Do you need
> more than 18 bytes?
I just went back and had a look at the code -- There were two related
workarounds: One made room for the MIC, but as you said, that hasn't
been necessary for a while so the code was disabled.
The other workaround is still in place, however -- cw1200 also needs a
gap in the frame payload for the IV, even though it's generated by the
firmware. I worked around this by telling setting the
IEEE80211_KEY_FLAG_GENERATE_IV flag on the mac80211 keys, and then
zeroing that part of the payload when the frame went out to the harware.
I figured it was a less costly approach than memmoving the whole payload
over by sizeof(ICV).
Is there a better way to handle this now?
- Solomon
--
Solomon Peachy pizza at shaftnet dot org
Melbourne, FL ^^ (mail/jabber/gtalk) ^^
Quidquid latine dictum sit, altum viditur.
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-12-11 23:23 ` Solomon Peachy
2012-12-12 14:40 ` Kalle Valo
@ 2012-12-12 15:13 ` Christian Lamparter
2012-12-12 16:18 ` Solomon Peachy
2012-12-12 18:19 ` John W. Linville
2 siblings, 1 reply; 33+ messages in thread
From: Christian Lamparter @ 2012-12-12 15:13 UTC (permalink / raw)
To: Solomon Peachy
Cc: John W. Linville, Steev Klimaszewski, Janusz Dziedzic,
Dmitry Tarnyagin, Johannes Berg, linux-wireless
On Wednesday, December 12, 2012 12:23:11 AM Solomon Peachy wrote:
> On Fri, Jul 06, 2012 at 04:18:40PM -0400, John W. Linville wrote:
>
> IIRC it's because mac80211 doesn't provide a way of pre-allocating MIC
> space at the tail end of the frame -- the hardware performs the work but
> still needs the space in the payload. The code I'm maintaining has
> workarounds for this; not the most efficient solution but I'd rather see
> the code merged as-is, and then we can incrementally improve things
> (perhaps by enhancing mac80211 as needed)
Mac80211 already reserves at least 18 bytes tailroom [which can be
allocated by a simple skb_put]. In fact p54 uses this tailroom to
pass the MIC (8 bytes) + ICV (4 bytes) to the firmware. Do you need
more than 18 bytes?
Regards,
Chr
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-12-11 23:23 ` Solomon Peachy
@ 2012-12-12 14:40 ` Kalle Valo
2012-12-12 15:13 ` Christian Lamparter
2012-12-12 18:19 ` John W. Linville
2 siblings, 0 replies; 33+ messages in thread
From: Kalle Valo @ 2012-12-12 14:40 UTC (permalink / raw)
To: Solomon Peachy
Cc: John W. Linville, Steev Klimaszewski, Janusz Dziedzic,
Dmitry Tarnyagin, Johannes Berg, linux-wireless
Solomon Peachy <pizza@shaftnet.org> writes:
> I've been maintaining it on top of compat-wireless, and I'm wanting to
> give it another upstream push, and be listed as the maintainer. What's
> the best way for me to do that? The patch series they posted originally
> (one file per patch) seems rather silly, but at the same time, doing it
> all at once is a rather substantial chunk to digest/review.
With ath6kl I did so that for review I sent multiple patches (one file
per patch) but the final submission, after the review, was one huge
patch containing everything. I don't know if John still prefers that but
at least I would recommend to do so.
--
Kalle Valo
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-07-06 20:18 ` John W. Linville
@ 2012-12-11 23:23 ` Solomon Peachy
2012-12-12 14:40 ` Kalle Valo
` (2 more replies)
0 siblings, 3 replies; 33+ messages in thread
From: Solomon Peachy @ 2012-12-11 23:23 UTC (permalink / raw)
To: John W. Linville
Cc: Steev Klimaszewski, Janusz Dziedzic, Dmitry Tarnyagin,
Johannes Berg, linux-wireless
[-- Attachment #1: Type: text/plain, Size: 3485 bytes --]
On Fri, Jul 06, 2012 at 04:18:40PM -0400, John W. Linville wrote:
> Sorry, I kinda lost track of this. I guess I was expecting a repost,
> including Bob Copeland's patches and something to address the endian
> issues mentioned by Kevin Groenevel. Was anyone planning to address
> those concerns? Also, I'm not sure that bit about needing custom
> SDD files was fully addressed?
Unfortunately, the SDD needs to be supplied by the module vendor, as
it's specific to the design. Even more troubling is that there's a
register value we have to program that also depends on the design, and
there's no way to know that generically. I've solved this by resorting
to platform data.
Anyway. Onto my main point.
ST-E hasn't publically done any work on this driver since around April
2012, and they haven't given me an answer on whether or not it's been
abandoned. In light of recent announcements relating to ST-E's future,
I'm not hopeful that it'll see any more official support.
That said, I've done a ton of work on this driver for my employer. It
has far fewer bugs than what ST-E has previously released; including
fixing up major endian problems (I brought it up on a uClinux m68k
target for another client). It's also vastly more stable, now has SPI
support, and has also managed to pass WFA testing. That's not to say
it's bug-free, but it at least can be counted on to not HACF randomly.
I've been maintaining it on top of compat-wireless, and I'm wanting to
give it another upstream push, and be listed as the maintainer. What's
the best way for me to do that? The patch series they posted originally
(one file per patch) seems rather silly, but at the same time, doing it
all at once is a rather substantial chunk to digest/review.
> On top of that, there were some style quirks that I was hoping
> someone could address. There were "if 0" blocks in the code, which
> is rather questionable. Was anyone planning to remove them? Also,
> the block comment formats seemed a little random. In particular, the
> single-line "/* ********* */" thing looks a bit funny. Perhaps that
> isn't the worst thing ever but if you are going to respin anyway than
> I'd prefer if you just deleted them.
The code I have has a lot of changes there, but I imagine there are more
remaining. I'll have to go back and audit things, as I've since given
up on keeping my code close to ST-E's "upstream"
> There was also talk of a mac80211 patch needed to fix a bug observed
> with the driver as posted? Has that mac80211 fix been posted and
> merged? If not, when will we see it?
IIRC it's because mac80211 doesn't provide a way of pre-allocating MIC
space at the tail end of the frame -- the hardware performs the work but
still needs the space in the payload. The code I'm maintaining has
workarounds for this; not the most efficient solution but I'd rather see
the code merged as-is, and then we can incrementally improve things
(perhaps by enhancing mac80211 as needed)
> So anyway, it seems like a repost of the current version (i.e. with
> Bob's fixes, etc) is in order?
I'll have to go back and see if any of those fixes are still relevant.
Anyway, let me know how I should proceed from here..
- Solomon
--
Solomon Peachy pizza at shaftnet dot org
Melbourne, FL ^^ (mail/jabber/gtalk) ^^
Quidquid latine dictum sit, altum viditur.
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-07-05 18:16 ` Steev Klimaszewski
@ 2012-07-06 20:18 ` John W. Linville
2012-12-11 23:23 ` Solomon Peachy
0 siblings, 1 reply; 33+ messages in thread
From: John W. Linville @ 2012-07-06 20:18 UTC (permalink / raw)
To: Steev Klimaszewski
Cc: Janusz Dziedzic, Dmitry Tarnyagin, Johannes Berg, linux-wireless
On Thu, Jul 05, 2012 at 01:16:31PM -0500, Steev Klimaszewski wrote:
> On Thu, May 31, 2012 at 12:45 AM, Janusz Dziedzic
> <janusz.dziedzic@gmail.com> wrote:
> > 2012/5/9 Dmitry Tarnyagin <abi.dmitryt@gmail.com>:
> >> Hi,
> >>
> >> Could you please check status of this submission? It looks like review
> >> was passed, but patchset was not taken in. Have I done something
> >> wrong?
> >>
> >
> > Any news?
> >
> >
> > BR
> > Janusz
> > --
>
> Any news on this?
Sorry, I kinda lost track of this. I guess I was expecting a repost,
including Bob Copeland's patches and something to address the endian
issues mentioned by Kevin Groenevel. Was anyone planning to address
those concerns? Also, I'm not sure that bit about needing custom
SDD files was fully addressed?
On top of that, there were some style quirks that I was hoping
someone could address. There were "if 0" blocks in the code, which
is rather questionable. Was anyone planning to remove them? Also,
the block comment formats seemed a little random. In particular, the
single-line "/* ********* */" thing looks a bit funny. Perhaps that
isn't the worst thing ever but if you are going to respin anyway than
I'd prefer if you just deleted them.
There was also talk of a mac80211 patch needed to fix a bug observed
with the driver as posted? Has that mac80211 fix been posted and
merged? If not, when will we see it?
So anyway, it seems like a repost of the current version (i.e. with
Bob's fixes, etc) is in order?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-05-31 5:45 ` Janusz Dziedzic
@ 2012-07-05 18:16 ` Steev Klimaszewski
2012-07-06 20:18 ` John W. Linville
0 siblings, 1 reply; 33+ messages in thread
From: Steev Klimaszewski @ 2012-07-05 18:16 UTC (permalink / raw)
To: Janusz Dziedzic
Cc: Dmitry Tarnyagin, Johannes Berg, John W. Linville, linux-wireless
On Thu, May 31, 2012 at 12:45 AM, Janusz Dziedzic
<janusz.dziedzic@gmail.com> wrote:
> 2012/5/9 Dmitry Tarnyagin <abi.dmitryt@gmail.com>:
>> Hi,
>>
>> Could you please check status of this submission? It looks like review
>> was passed, but patchset was not taken in. Have I done something
>> wrong?
>>
>
> Any news?
>
>
> BR
> Janusz
> --
Any news on this?
--
Best Regards,
Steev
Steev Klimaszewski <steev@genesi-usa.com>
Senior Software Engineer, Genesi USA, Inc.
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-05-09 6:58 ` Dmitry Tarnyagin
@ 2012-05-31 5:45 ` Janusz Dziedzic
2012-07-05 18:16 ` Steev Klimaszewski
0 siblings, 1 reply; 33+ messages in thread
From: Janusz Dziedzic @ 2012-05-31 5:45 UTC (permalink / raw)
To: Dmitry Tarnyagin, Johannes Berg, John W. Linville; +Cc: linux-wireless
2012/5/9 Dmitry Tarnyagin <abi.dmitryt@gmail.com>:
> Hi,
>
> Could you please check status of this submission? It looks like review
> was passed, but patchset was not taken in. Have I done something
> wrong?
>
Any news?
BR
Janusz
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
2012-03-02 20:26 ` Dmitry Tarnyagin
@ 2012-05-09 6:58 ` Dmitry Tarnyagin
2012-05-31 5:45 ` Janusz Dziedzic
0 siblings, 1 reply; 33+ messages in thread
From: Dmitry Tarnyagin @ 2012-05-09 6:58 UTC (permalink / raw)
To: Johannes Berg, John W. Linville; +Cc: linux-wireless
Hi,
Could you please check status of this submission? It looks like review
was passed, but patchset was not taken in. Have I done something
wrong?
Thank you and with best regards,
Dmitry Tarnyagin
On Fri, Mar 2, 2012 at 9:26 PM, Dmitry Tarnyagin
<dmitry.tarnyagin@stericsson.com> wrote:
> Please find below in the patchset implementation of a new driver for
> the ST-Ericsson cw1200 wlan device.
>
> Signed-off-by: Dmitry Tarnyagin <dmitry.tarnyagin@stericsson.com>
> --
^ permalink raw reply [flat|nested] 33+ messages in thread
* [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
[not found] <983b0e2d75af161b8e4dec02fc3497926a0080df-submit>
@ 2012-03-02 20:26 ` Dmitry Tarnyagin
2012-05-09 6:58 ` Dmitry Tarnyagin
0 siblings, 1 reply; 33+ messages in thread
From: Dmitry Tarnyagin @ 2012-03-02 20:26 UTC (permalink / raw)
To: linux-wireless
Please find below in the patchset implementation of a new driver for
the ST-Ericsson cw1200 wlan device.
Signed-off-by: Dmitry Tarnyagin <dmitry.tarnyagin@stericsson.com>
^ permalink raw reply [flat|nested] 33+ messages in thread
end of thread, other threads:[~2012-12-13 14:53 UTC | newest]
Thread overview: 33+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-05-02 15:22 [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver Kevin Groeneveld
2012-05-02 16:01 ` Dmitry Tarnyagin
[not found] ` <CABF+-6XbdG_QMa0iQJMpbOsr4bXCq4mDEB6unkM8jxNGWYwFyQ@mail.gmail.com>
2012-05-02 16:51 ` Kevin Groeneveld
[not found] ` <4FA23DA0.3030207@stericsson.com>
2012-05-03 16:42 ` Kevin Groeneveld
2012-05-03 17:23 ` Dmitry Tarnyagin
2012-05-03 18:57 ` Kevin Groeneveld
2012-05-03 21:57 ` Janusz Dziedzic
2012-05-04 0:10 ` Kevin Groeneveld
2012-05-04 21:40 ` Kevin Groeneveld
2012-05-05 7:20 ` Janusz Dziedzic
2012-05-07 9:25 ` Janusz Dziedzic
2012-05-07 19:54 ` Kevin Groeneveld
2012-05-09 17:03 ` Kevin Groeneveld
2012-05-09 18:24 ` Dmitry Tarnyagin
2012-05-09 18:33 ` Johannes Berg
2012-05-09 18:56 ` Kevin Groeneveld
2012-05-09 19:37 ` Dmitry Tarnyagin
2012-05-09 20:37 ` Solomon Peachy
2012-05-09 20:59 ` Kevin Groeneveld
2012-05-10 13:07 ` Solomon Peachy
2012-05-10 20:03 ` Kevin Groeneveld
[not found] <983b0e2d75af161b8e4dec02fc3497926a0080df-submit>
2012-03-02 20:26 ` Dmitry Tarnyagin
2012-05-09 6:58 ` Dmitry Tarnyagin
2012-05-31 5:45 ` Janusz Dziedzic
2012-07-05 18:16 ` Steev Klimaszewski
2012-07-06 20:18 ` John W. Linville
2012-12-11 23:23 ` Solomon Peachy
2012-12-12 14:40 ` Kalle Valo
2012-12-12 15:13 ` Christian Lamparter
2012-12-12 16:18 ` Solomon Peachy
2012-12-12 16:20 ` Johannes Berg
2012-12-13 14:53 ` Solomon Peachy
2012-12-12 18:19 ` John W. Linville
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.