* Re: [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc (fwd)
@ 2008-06-20 17:57 Rogério Brito
2008-06-20 18:48 ` Ivo van Doorn
0 siblings, 1 reply; 14+ messages in thread
From: Rogério Brito @ 2008-06-20 17:57 UTC (permalink / raw)
To: Ivo van Doorn, John W. Linville, linux-kernel, rbrito
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
Dear Ivo and John (among others),
Did you receive my earlier message (attached here for reference)? I'm
willing to experiment with the driver a little bit and I hope that the
information that I have provided so far is helpful to chase the reason
why the driver doesn't work on PowerPC.
BTW, the latest kernel that I tried on a x86-64 machine was a 2.6.26-rc6
and it showed the same results as with kernel 2.6.26-rc5: I couldn't
associate with the AP.
OTOH, reverting back to 2.6.25 on this (x86-64) machine, I can use the
D-Link USB stick without any problems.
If you need more information, I will be glad to assist you to have
everything fixed.
I am willing to use any git tree, if that helps.
Thanks in advance, Rogério Brito.
--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
[-- Attachment #2: Type: message/rfc822, Size: 13859 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 1210 bytes --]
Hi again, Ivo and John.
I have finally made the rt2x00 work on the x86-64 with the kernel
2.6.25.
Just as a reminder:
* with kernel 2.6.26-rc4, I could associate with the AP, but could not
get a DHCP lease;
* with kernel 2.6.26-rc5, I could not even associate with the AP.
So, it seems that we have some regressions here. :-(
> Well, I'm attaching the diff between the regdump from the earlier try
> on the iBook and the regdump from this x86-64. I think that some
> conclusions may be drawn from it, since it seems to be your domain of
> expertise.
I'm attaching here 3 files: the old output from regdump (taken from the
ibook), the new, working (with kernel 2.6.25.4) regdump and their diff.
Notice that there are some inverted values there, but they are shorts
(i.e., 16-bit integers) that are inverted, instead of the inverted
values being bytes.
I think that this may mean that your work may be easier on debugging the
driver (I hope so!).
Thanks for any help, Rogério Brito.
--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
[-- Attachment #2.1.2: old.output-regdump.txt --]
[-- Type: text/plain, Size: 3665 bytes --]
2.6.26-rc5-2
driver: rt2500usb
version: 2.1.4
compiled: Jun 8 2008 17:08:54
dev_flags: 0x00000e2f
rt chip: 1201
rf chip: 0005
revision:00000005
csr length: 128
eeprom length: 53
bbp length: 96
rf length: 5
csr
0 :0x00050000
1 :0x00040000
2 :0x13000000
3 :0xe9460000
4 :0x8a8d0000
5 :0x13000000
6 :0x51460000
7 :0x65100000
8 :0x09800000
9 :0xff1d0000
10 :0x00140000
11 :0x000a0000
12 :0x013a0000
13 :0x11110000
14 :0x1e110000
15 :0x01ee0000
16 :0x00000000
17 :0x01fe0000
18 :0x005a0000
19 :0xff000000
20 :0x00020000
21 :0x1e460000
22 :0x00530000
23 :0x00000000
24 :0x00000000
25 :0x00000000
26 :0x00000000
27 :0x00000000
28 :0x00000000
29 :0x00000000
30 :0x00000000
31 :0x00000000
32 :0x1ec00000
33 :0xb1620000
34 :0x007e0000
35 :0xb3af0000
36 :0xb3aa0000
37 :0x8c8d0000
38 :0x8b8a0000
39 :0x86870000
40 :0x00850000
41 :0x01620000
42 :0x000a0000
43 :0x00000000
44 :0x140a0000
45 :0x70380000
46 :0x0c130000
47 :0x06090000
48 :0x03050000
49 :0x02030000
50 :0xfa000000
51 :0x000b0000
52 :0x00030000
53 :0xe78f0000
54 :0x00000000
55 :0x00000000
56 :0x00000000
57 :0x00000000
58 :0x00000000
59 :0x00000000
60 :0x00000000
61 :0x00000000
62 :0x00000000
63 :0x00000000
64 :0x00000000
65 :0x00000000
66 :0x00000000
67 :0x00000000
68 :0x00000000
69 :0x00000000
70 :0x00000000
71 :0x00000000
72 :0x00000000
73 :0x00000000
74 :0x00000000
75 :0x00000000
76 :0x00000000
77 :0x00000000
78 :0x00000000
79 :0x00000000
80 :0x00000000
81 :0x00000000
82 :0x00000000
83 :0x00000000
84 :0x00000000
85 :0x00000000
86 :0x00000000
87 :0x00000000
88 :0x00000000
89 :0x00000000
90 :0x00000000
91 :0x00000000
92 :0x00000000
93 :0x00000000
94 :0x00000000
95 :0x00000000
96 :0x12210000
97 :0x00030000
98 :0x00000000
99 :0x00000000
100 :0x000f0000
101 :0x82060000
102 :0x821e0000
103 :0x91000000
104 :0x00000000
105 :0x0e070000
106 :0x54000000
107 :0x00000000
108 :0x00000000
109 :0x00000000
110 :0x00000000
111 :0x00000000
112 :0x032c0000
113 :0xfb580000
114 :0x63110000
115 :0x0a1f0000
116 :0x00000000
117 :0x00000000
118 :0x00000000
119 :0x00000000
120 :0x00000000
121 :0x00000000
122 :0x02e10000
123 :0x00000000
124 :0x00000000
125 :0x00000000
126 :0x00000000
127 :0x00000422
eeprom
0 :0x2570
1 :0x0104
2 :0x1300
3 :0xe946
4 :0x8a8d
5 :0xffff
6 :0xffff
7 :0xffff
8 :0xffff
9 :0xffff
10 :0xffff
11 :0x2829
12 :0xfff0
13 :0x00ff
14 :0x112c
15 :0x1518
16 :0x1618
17 :0x3e00
18 :0xffff
19 :0xffff
20 :0xffff
21 :0xffff
22 :0xffff
23 :0xffff
24 :0xffff
25 :0xffff
26 :0xffff
27 :0xffff
28 :0xffff
29 :0xffff
30 :0x1717
31 :0x1717
32 :0x1717
33 :0x1717
34 :0x1617
35 :0x1616
36 :0x1616
37 :0xffff
38 :0xffff
39 :0xffff
40 :0xffff
41 :0xffff
42 :0xffff
43 :0xffff
44 :0xffff
45 :0xffff
46 :0xffff
47 :0xffff
48 :0x0032
49 :0x6880
50 :0x3850
51 :0x6f5f
52 :0xfa00
bbp
0 :0x13
1 :0x55
2 :0x06
3 :0x02
4 :0x19
5 :0x0b
6 :0x10
7 :0x00
8 :0x00
9 :0x00
10 :0x00
11 :0x04
12 :0x01
13 :0xa8
14 :0x1a
15 :0x30
16 :0xac
17 :0x00
18 :0x18
19 :0xff
20 :0x1e
21 :0x18
22 :0x18
23 :0x08
24 :0x80
25 :0x50
26 :0x08
27 :0x23
28 :0x18
29 :0x18
30 :0x10
31 :0x2b
32 :0xb9
33 :0x55
34 :0x12
35 :0x50
36 :0x11
37 :0x05
38 :0x00
39 :0xc4
40 :0x02
41 :0x60
42 :0x09
43 :0x34
44 :0x0b
45 :0x6e
46 :0x70
47 :0x0a
48 :0x04
49 :0x02
50 :0x68
51 :0x18
52 :0x04
53 :0x10
54 :0x18
55 :0x2d
56 :0x08
57 :0x10
58 :0x08
59 :0x02
60 :0x3e
61 :0x5f
62 :0x00
63 :0x00
64 :0x01
65 :0x03
66 :0x00
67 :0x00
68 :0x00
69 :0x00
70 :0x46
71 :0x00
72 :0x00
73 :0x00
74 :0xd4
75 :0xff
76 :0x19
77 :0x05
78 :0x08
79 :0x00
80 :0x00
81 :0x05
82 :0x14
83 :0x50
84 :0xc0
85 :0x10
86 :0xcf
87 :0x00
88 :0x00
89 :0x00
90 :0x00
91 :0x00
92 :0x00
93 :0x00
94 :0x00
95 :0x00
rf
0 :0x00000000
1 :0x00022010
2 :0x000008a6
3 :0x00062d11
4 :0x00000e07
[-- Attachment #2.1.3: new.output-regdump.txt --]
[-- Type: text/plain, Size: 3664 bytes --]
2.6.25.4-1
driver: rt2500usb
version: 2.0.14
compiled: Jun 13 2008 01:33:03
dev_flags: 0x0001012f
rt chip: 1201
rf chip: 0005
revision:00000005
csr length: 128
eeprom length: 53
bbp length: 96
rf length: 5
csr
0 :0x00000005
1 :0x00000004
2 :0x00001300
3 :0x0000e946
4 :0x00008a8d
5 :0x00001300
6 :0x00005146
7 :0x00006510
8 :0x00000980
9 :0x0000ff1d
10 :0x00000014
11 :0x00000005
12 :0x0000016c
13 :0x00001111
14 :0x00001e11
15 :0x000001ee
16 :0x00000000
17 :0x000001fe
18 :0x0000005a
19 :0x0000ff00
20 :0x00000003
21 :0x00001e46
22 :0x00000053
23 :0x00000000
24 :0x00000000
25 :0x00000000
26 :0xffff0000
27 :0x00000000
28 :0x00000000
29 :0x00000000
30 :0x00000000
31 :0x00000000
32 :0x00001ec0
33 :0x0000b11a
34 :0x0000007e
35 :0x0000b3af
36 :0x0000b3aa
37 :0x00008c8d
38 :0x00008b8a
39 :0x00008687
40 :0x00000085
41 :0x00000162
42 :0x0000000e
43 :0x0000015f
44 :0x0000140a
45 :0x00007038
46 :0x00000c13
47 :0x00000609
48 :0x00000305
49 :0x00000203
50 :0x0000fa00
51 :0x00000003
52 :0x00000003
53 :0x0000e78f
54 :0x00000000
55 :0x00000000
56 :0x00000000
57 :0x00000000
58 :0x00000000
59 :0x00000000
60 :0x00000000
61 :0x00000000
62 :0x00000000
63 :0x00000000
64 :0x00000000
65 :0x00000000
66 :0x00000000
67 :0x00000000
68 :0x00000000
69 :0x00000000
70 :0x00000000
71 :0x00000000
72 :0x00000000
73 :0x00000000
74 :0x00000000
75 :0x00000000
76 :0x00000000
77 :0x00000000
78 :0x00000000
79 :0x00000000
80 :0x00000000
81 :0x00000000
82 :0x00000000
83 :0x00000000
84 :0x00000000
85 :0x00000000
86 :0x00000000
87 :0x00000000
88 :0x00000000
89 :0x00000000
90 :0x00000000
91 :0x00000000
92 :0x00000000
93 :0x00000000
94 :0x00000000
95 :0x00000000
96 :0x00001221
97 :0x00000003
98 :0x00000000
99 :0x00000000
100 :0x0000000f
101 :0x00008206
102 :0x0000821e
103 :0x00009160
104 :0x00000000
105 :0x00000e07
106 :0x00005400
107 :0x00000000
108 :0x00000000
109 :0x00000000
110 :0x00000000
111 :0x00000000
112 :0x00000000
113 :0x000001a9
114 :0x00000038
115 :0x00000000
116 :0x00000000
117 :0x00000000
118 :0x00000169
119 :0x00000011
120 :0x00000000
121 :0x00000000
122 :0x00000a01
123 :0x00000000
124 :0x00000000
125 :0x00000000
126 :0x00000000
127 :0x00000000
eeprom
0 :0x2570
1 :0x0104
2 :0x1300
3 :0xe946
4 :0x8a8d
5 :0xffff
6 :0xffff
7 :0xffff
8 :0xffff
9 :0xffff
10 :0xffff
11 :0x2829
12 :0xfff0
13 :0x00ff
14 :0x112c
15 :0x1518
16 :0x1618
17 :0x3e00
18 :0xffff
19 :0xffff
20 :0xffff
21 :0xffff
22 :0xffff
23 :0xffff
24 :0xffff
25 :0xffff
26 :0xffff
27 :0xffff
28 :0xffff
29 :0xffff
30 :0x1717
31 :0x1717
32 :0x1717
33 :0x1717
34 :0x1617
35 :0x1616
36 :0x1616
37 :0xffff
38 :0xffff
39 :0xffff
40 :0xffff
41 :0xffff
42 :0xffff
43 :0xffff
44 :0xffff
45 :0xffff
46 :0xffff
47 :0xffff
48 :0x0032
49 :0x6880
50 :0x3850
51 :0x6f5f
52 :0xff37
bbp
0 :0x13
1 :0x45
2 :0x1e
3 :0x02
4 :0x19
5 :0x09
6 :0x00
7 :0x0e
8 :0x00
9 :0x00
10 :0x00
11 :0x04
12 :0x00
13 :0x70
14 :0x1a
15 :0x30
16 :0xac
17 :0x60
18 :0x18
19 :0xff
20 :0x1e
21 :0x18
22 :0x18
23 :0x08
24 :0x68
25 :0x38
26 :0x08
27 :0x23
28 :0x18
29 :0x18
30 :0x10
31 :0x2b
32 :0xb9
33 :0x55
34 :0x12
35 :0x50
36 :0x11
37 :0x05
38 :0x00
39 :0xc4
40 :0x02
41 :0x60
42 :0x08
43 :0x01
44 :0x78
45 :0x00
46 :0x38
47 :0x0a
48 :0x04
49 :0x02
50 :0x68
51 :0x56
52 :0x2e
53 :0x10
54 :0x18
55 :0x7b
56 :0x08
57 :0x10
58 :0x08
59 :0x02
60 :0x3f
61 :0x6f
62 :0x00
63 :0x00
64 :0x01
65 :0x03
66 :0x00
67 :0x00
68 :0x00
69 :0x00
70 :0x46
71 :0x00
72 :0x00
73 :0x00
74 :0xd4
75 :0xff
76 :0x19
77 :0x05
78 :0x08
79 :0x00
80 :0x00
81 :0x05
82 :0x14
83 :0x50
84 :0xc0
85 :0x10
86 :0x74
87 :0x04
88 :0x00
89 :0x00
90 :0x00
91 :0x00
92 :0x00
93 :0x00
94 :0x00
95 :0x00
rf
0 :0x00000000
1 :0x00022010
2 :0x000008a6
3 :0x00063711
4 :0x00000e07
[-- Attachment #2.1.4: differences.txt --]
[-- Type: text/plain, Size: 4009 bytes --]
--- old.output-regdump.txt 2008-06-13 01:41:12.000000000 -0300
+++ new.output-regdump.txt 2008-06-13 01:42:12.000000000 -0300
@@ -1,8 +1,8 @@
-2.6.26-rc5-2
+2.6.25.4-1
driver: rt2500usb
-version: 2.1.4
-compiled: Jun 8 2008 17:08:54
-dev_flags: 0x00000e2f
+version: 2.0.14
+compiled: Jun 13 2008 01:33:03
+dev_flags: 0x0001012f
rt chip: 1201
rf chip: 0005
revision:00000005
@@ -13,60 +13,60 @@
rf length: 5
csr
-0 :0x00050000
-1 :0x00040000
-2 :0x13000000
-3 :0xe9460000
-4 :0x8a8d0000
-5 :0x13000000
-6 :0x51460000
-7 :0x65100000
-8 :0x09800000
-9 :0xff1d0000
-10 :0x00140000
-11 :0x000a0000
-12 :0x013a0000
-13 :0x11110000
-14 :0x1e110000
-15 :0x01ee0000
+0 :0x00000005
+1 :0x00000004
+2 :0x00001300
+3 :0x0000e946
+4 :0x00008a8d
+5 :0x00001300
+6 :0x00005146
+7 :0x00006510
+8 :0x00000980
+9 :0x0000ff1d
+10 :0x00000014
+11 :0x00000005
+12 :0x0000016c
+13 :0x00001111
+14 :0x00001e11
+15 :0x000001ee
16 :0x00000000
-17 :0x01fe0000
-18 :0x005a0000
-19 :0xff000000
-20 :0x00020000
-21 :0x1e460000
-22 :0x00530000
+17 :0x000001fe
+18 :0x0000005a
+19 :0x0000ff00
+20 :0x00000003
+21 :0x00001e46
+22 :0x00000053
23 :0x00000000
24 :0x00000000
25 :0x00000000
-26 :0x00000000
+26 :0xffff0000
27 :0x00000000
28 :0x00000000
29 :0x00000000
30 :0x00000000
31 :0x00000000
-32 :0x1ec00000
-33 :0xb1620000
-34 :0x007e0000
-35 :0xb3af0000
-36 :0xb3aa0000
-37 :0x8c8d0000
-38 :0x8b8a0000
-39 :0x86870000
-40 :0x00850000
-41 :0x01620000
-42 :0x000a0000
-43 :0x00000000
-44 :0x140a0000
-45 :0x70380000
-46 :0x0c130000
-47 :0x06090000
-48 :0x03050000
-49 :0x02030000
-50 :0xfa000000
-51 :0x000b0000
-52 :0x00030000
-53 :0xe78f0000
+32 :0x00001ec0
+33 :0x0000b11a
+34 :0x0000007e
+35 :0x0000b3af
+36 :0x0000b3aa
+37 :0x00008c8d
+38 :0x00008b8a
+39 :0x00008687
+40 :0x00000085
+41 :0x00000162
+42 :0x0000000e
+43 :0x0000015f
+44 :0x0000140a
+45 :0x00007038
+46 :0x00000c13
+47 :0x00000609
+48 :0x00000305
+49 :0x00000203
+50 :0x0000fa00
+51 :0x00000003
+52 :0x00000003
+53 :0x0000e78f
54 :0x00000000
55 :0x00000000
56 :0x00000000
@@ -109,38 +109,38 @@
93 :0x00000000
94 :0x00000000
95 :0x00000000
-96 :0x12210000
-97 :0x00030000
+96 :0x00001221
+97 :0x00000003
98 :0x00000000
99 :0x00000000
-100 :0x000f0000
-101 :0x82060000
-102 :0x821e0000
-103 :0x91000000
+100 :0x0000000f
+101 :0x00008206
+102 :0x0000821e
+103 :0x00009160
104 :0x00000000
-105 :0x0e070000
-106 :0x54000000
+105 :0x00000e07
+106 :0x00005400
107 :0x00000000
108 :0x00000000
109 :0x00000000
110 :0x00000000
111 :0x00000000
-112 :0x032c0000
-113 :0xfb580000
-114 :0x63110000
-115 :0x0a1f0000
+112 :0x00000000
+113 :0x000001a9
+114 :0x00000038
+115 :0x00000000
116 :0x00000000
117 :0x00000000
-118 :0x00000000
-119 :0x00000000
+118 :0x00000169
+119 :0x00000011
120 :0x00000000
121 :0x00000000
-122 :0x02e10000
+122 :0x00000a01
123 :0x00000000
124 :0x00000000
125 :0x00000000
126 :0x00000000
-127 :0x00000422
+127 :0x00000000
eeprom
0 :0x2570
@@ -195,35 +195,35 @@
49 :0x6880
50 :0x3850
51 :0x6f5f
-52 :0xfa00
+52 :0xff37
bbp
0 :0x13
-1 :0x55
-2 :0x06
+1 :0x45
+2 :0x1e
3 :0x02
4 :0x19
-5 :0x0b
-6 :0x10
-7 :0x00
+5 :0x09
+6 :0x00
+7 :0x0e
8 :0x00
9 :0x00
10 :0x00
11 :0x04
-12 :0x01
-13 :0xa8
+12 :0x00
+13 :0x70
14 :0x1a
15 :0x30
16 :0xac
-17 :0x00
+17 :0x60
18 :0x18
19 :0xff
20 :0x1e
21 :0x18
22 :0x18
23 :0x08
-24 :0x80
-25 :0x50
+24 :0x68
+25 :0x38
26 :0x08
27 :0x23
28 :0x18
@@ -240,26 +240,26 @@
39 :0xc4
40 :0x02
41 :0x60
-42 :0x09
-43 :0x34
-44 :0x0b
-45 :0x6e
-46 :0x70
+42 :0x08
+43 :0x01
+44 :0x78
+45 :0x00
+46 :0x38
47 :0x0a
48 :0x04
49 :0x02
50 :0x68
-51 :0x18
-52 :0x04
+51 :0x56
+52 :0x2e
53 :0x10
54 :0x18
-55 :0x2d
+55 :0x7b
56 :0x08
57 :0x10
58 :0x08
59 :0x02
-60 :0x3e
-61 :0x5f
+60 :0x3f
+61 :0x6f
62 :0x00
63 :0x00
64 :0x01
@@ -284,8 +284,8 @@
83 :0x50
84 :0xc0
85 :0x10
-86 :0xcf
-87 :0x00
+86 :0x74
+87 :0x04
88 :0x00
89 :0x00
90 :0x00
@@ -299,5 +299,5 @@
0 :0x00000000
1 :0x00022010
2 :0x000008a6
-3 :0x00062d11
+3 :0x00063711
4 :0x00000e07
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc (fwd)
2008-06-20 17:57 [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc (fwd) Rogério Brito
@ 2008-06-20 18:48 ` Ivo van Doorn
2008-06-20 19:58 ` Rogério Brito
0 siblings, 1 reply; 14+ messages in thread
From: Ivo van Doorn @ 2008-06-20 18:48 UTC (permalink / raw)
To: Rogério Brito; +Cc: John W. Linville, linux-kernel
Hi,
> Did you receive my earlier message (attached here for reference)? I'm
> willing to experiment with the driver a little bit and I hope that the
> information that I have provided so far is helpful to chase the reason
> why the driver doesn't work on PowerPC.
Sorry I have been quite busy with other things.
I have glanced over the register dumps, and there are no obvious endian problems.
The reason most registers are different with the 16bits swapped is the way
rt2x00 sends the register information through debugfs. rt2500usb only has 16bit
registers and the way the information is dumped through debugfs assumes 32bit
registers.
I will go over the real register differences as soon as possible, but as I said,
I am momentarily quite busy with other things. :(
Ivo
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc (fwd)
2008-06-20 18:48 ` Ivo van Doorn
@ 2008-06-20 19:58 ` Rogério Brito
2008-06-25 19:49 ` Rogério Brito
0 siblings, 1 reply; 14+ messages in thread
From: Rogério Brito @ 2008-06-20 19:58 UTC (permalink / raw)
To: Ivo van Doorn; +Cc: John W. Linville, linux-kernel, rbrito
Hi, Ivo. Thank you for your reply.
On Jun 20 2008, Ivo van Doorn wrote:
> Hi,
>
> > Did you receive my earlier message (attached here for reference)? I'm
> > willing to experiment with the driver a little bit and I hope that the
> > information that I have provided so far is helpful to chase the reason
> > why the driver doesn't work on PowerPC.
>
> Sorry I have been quite busy with other things.
I'm terribly sorry for that, since I would like the driver to work with
the USB stick still in the 2.6.26 release (since that's what some
distributions will probably use).
> I have glanced over the register dumps, and there are no obvious
> endian problems.
OK.
> The reason most registers are different with the 16bits swapped is the way
> rt2x00 sends the register information through debugfs. rt2500usb only has 16bit
> registers and the way the information is dumped through debugfs assumes 32bit
> registers.
I didn't know that and was surprised. I thought that it would have been
something easier to fix, then.
> I will go over the real register differences as soon as possible, but
> as I said, I am momentarily quite busy with other things. :(
Thanks anyway. I am willing to help as much as I can.
Thanks, Rogério Brito.
--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc (fwd)
2008-06-20 19:58 ` Rogério Brito
@ 2008-06-25 19:49 ` Rogério Brito
2008-06-29 18:51 ` Ivo van Doorn
2008-08-04 13:26 ` Ivo van Doorn
0 siblings, 2 replies; 14+ messages in thread
From: Rogério Brito @ 2008-06-25 19:49 UTC (permalink / raw)
To: Ivo van Doorn; +Cc: John W. Linville, linux-kernel, rbrito
Hi, Ivo and John (again).
On Jun 20 2008, Rogério Brito wrote:
> On Jun 20 2008, Ivo van Doorn wrote:
> >
> > > Did you receive my earlier message (attached here for reference)? I'm
> > > willing to experiment with the driver a little bit and I hope that the
> > > information that I have provided so far is helpful to chase the reason
> > > why the driver doesn't work on PowerPC.
> >
> > Sorry I have been quite busy with other things.
>
> I'm terribly sorry for that, since I would like the driver to work with
> the USB stick still in the 2.6.26 release (since that's what some
> distributions will probably use).
Just for your information, I just compiled the -rc7 kernel on x86-64 (where
rt2500usb works if I boot with kernel 2.6.25) and still doesn't work (I'm
not even mentioning here PowerPC).
The "doesn't work" part means that the usual procedure of bringing the
interface up, setting the key (I'm using WEP), setting the essid (at which
point it should already be associated with the AP) and then using a dchp
client on the interface doesn't get a DHCP lease.
The DHCP client just sits there trying to send a broadcast message and
there is no response. After the key is set and after the essid is set, I
see that it is not associated with the AP, even though I get messages on
dmesg that it has associated and then the association was lost (I don't
have the dmesg log here on this computer).
Interestingly, I can see the AP if I do an "iwlist wlan0 scan" command.
I would really like to help with this problem (and have it fixed) before
the actual release of 2.6.26. Since I saw that you had some activity in
your git tree.
To John: would you like me to test any other tree with my hardware, like
the wireless-next tree? Would it make any difference?
Regards, Rogério Brito.
--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc (fwd)
2008-06-25 19:49 ` Rogério Brito
@ 2008-06-29 18:51 ` Ivo van Doorn
2008-07-08 3:55 ` Rogério Brito
2008-08-04 13:26 ` Ivo van Doorn
1 sibling, 1 reply; 14+ messages in thread
From: Ivo van Doorn @ 2008-06-29 18:51 UTC (permalink / raw)
To: Rogério Brito; +Cc: John W. Linville, linux-kernel, rt2400-devel
[-- Attachment #1: Type: text/plain, Size: 1537 bytes --]
Hi,
[Added rt2400-devel to CC list]
> > > > Did you receive my earlier message (attached here for reference)? I'm
> > > > willing to experiment with the driver a little bit and I hope that the
> > > > information that I have provided so far is helpful to chase the reason
> > > > why the driver doesn't work on PowerPC.
> > >
> > > Sorry I have been quite busy with other things.
> >
> > I'm terribly sorry for that, since I would like the driver to work with
> > the USB stick still in the 2.6.26 release (since that's what some
> > distributions will probably use).
>
> Just for your information, I just compiled the -rc7 kernel on x86-64 (where
> rt2500usb works if I boot with kernel 2.6.25) and still doesn't work (I'm
> not even mentioning here PowerPC).
In case other people are interested in the register differences as well,
attached is the real difference between the registers. Registers that are
different have the register name and meaning on the right side.
Interesting things to note:
- SIFS/EIFS timing is different, which is expected since rt2500usb now
listens to mac80211 for this information.
- Activity led is disabled, not interesting for this bug, but it really should have
been set to 1.
- mac80211 now uses short preamble
- Basic rates mask is 0, this is very odd....
- Link tuner value is set to 0, I seriously doubt that is a correct value
- TX power is different, mac80211 probably has set it to something different
Thats it for now, if anybody has any ideas, please let me know. :)
Ivo
[-- Attachment #2: diff.rt2500usb.txt --]
[-- Type: text/plain, Size: 22635 bytes --]
2.6.25.4-1 | 2.6.26-rc5-2
driver: rt2500usb driver: rt2500usb
version: 2.0.14 | version: 2.1.4
compiled: Jun 13 2008 01:33:03 | compiled: Jun 8 2008 17:08:54
dev_flags: 0x0001012f | dev_flags: 0x00000e2f
rt chip: 1201 rt chip: 1201
rf chip: 0005 rf chip: 0005
revision:00000005 revision:00000005
csr length: 128 csr length: 128
eeprom length: 53 eeprom length: 53
bbp length: 96 bbp length: 96
rf length: 5 rf length: 5
csr csr
0 :0x0005 0 :0x0005
1 :0x0004 1 :0x0004
2 :0x1300 2 :0x1300
3 :0xe946 3 :0xe946
4 :0x8a8d 4 :0x8a8d
5 :0x1300 5 :0x1300
6 :0x5146 6 :0x5146
7 :0x6510 7 :0x6510
8 :0x0980 8 :0x0980
9 :0xff1d 9 :0xff1d
10 :0x0014 10 :0x0014
11 :0x0005 | 11 :0x000a MAC_CSR11: SIFS.
12 :0x016c | 12 :0x013a MAC_CSR12: EIFS.
13 :0x1111 13 :0x1111
14 :0x1e11 14 :0x1e11
15 :0x01ee 15 :0x01ee
16 :0x0000 16 :0x0000
17 :0x01fe 17 :0x01fe
18 :0x005a 18 :0x005a
19 :0xff00 19 :0xff00
20 :0x0003 | 20 :0x0002 MAC_CSR20: LED control register.
21 :0x1e46 21 :0x1e46
22 :0x0053 22 :0x0053
23 :0x0000 23 :0x0000
24 :0x0000 24 :0x0000
25 :0x0000 25 :0x0000
26 :0x0000 26 :0x0000
27 :0x0000 27 :0x0000
28 :0x0000 28 :0x0000
29 :0x0000 29 :0x0000
30 :0x0000 30 :0x0000
31 :0x0000 31 :0x0000
32 :0x1ec0 32 :0x1ec0
33 :0xb11a | 33 :0xb162 TXRX_CSR1: TX configuration.
34 :0x007e 34 :0x007e
35 :0xb3af 35 :0xb3af
36 :0xb3aa 36 :0xb3aa
37 :0x8c8d 37 :0x8c8d
38 :0x8b8a 38 :0x8b8a
39 :0x8687 39 :0x8687
40 :0x0085 40 :0x0085
41 :0x0162 41 :0x0162
42 :0x000e | 42 :0x000a TXRX_CSR10: Auto responder control.
43 :0x015f | 43 :0x0000 TXRX_CSR11: Auto responder basic rate.
44 :0x140a 44 :0x140a
45 :0x7038 45 :0x7038
46 :0x0c13 46 :0x0c13
47 :0x0609 47 :0x0609
48 :0x0305 48 :0x0305
49 :0x0203 49 :0x0203
50 :0xfa00 50 :0xfa00
51 :0x0003 | 51 :0x000b TXRX_CSR19: Synchronization control register.
52 :0x0003 52 :0x0003
53 :0xe78f 53 :0xe78f
54 :0x0000 54 :0x0000
55 :0x0000 55 :0x0000
56 :0x0000 56 :0x0000
57 :0x0000 57 :0x0000
58 :0x0000 58 :0x0000
59 :0x0000 59 :0x0000
60 :0x0000 60 :0x0000
61 :0x0000 61 :0x0000
62 :0x0000 62 :0x0000
63 :0x0000 63 :0x0000
64 :0x0000 64 :0x0000
65 :0x0000 65 :0x0000
66 :0x0000 66 :0x0000
67 :0x0000 67 :0x0000
68 :0x0000 68 :0x0000
69 :0x0000 69 :0x0000
70 :0x0000 70 :0x0000
71 :0x0000 71 :0x0000
72 :0x0000 72 :0x0000
73 :0x0000 73 :0x0000
74 :0x0000 74 :0x0000
75 :0x0000 75 :0x0000
76 :0x0000 76 :0x0000
77 :0x0000 77 :0x0000
78 :0x0000 78 :0x0000
79 :0x0000 79 :0x0000
80 :0x0000 80 :0x0000
81 :0x0000 81 :0x0000
82 :0x0000 82 :0x0000
83 :0x0000 83 :0x0000
84 :0x0000 84 :0x0000
85 :0x0000 85 :0x0000
86 :0x0000 86 :0x0000
87 :0x0000 87 :0x0000
88 :0x0000 88 :0x0000
89 :0x0000 89 :0x0000
90 :0x0000 90 :0x0000
91 :0x0000 91 :0x0000
92 :0x0000 92 :0x0000
93 :0x0000 93 :0x0000
94 :0x0000 94 :0x0000
95 :0x0000 95 :0x0000
96 :0x1221 96 :0x1221
97 :0x0003 97 :0x0003
98 :0x0000 98 :0x0000
99 :0x0000 99 :0x0000
100 :0x000f 100 :0x000f
101 :0x8206 101 :0x8206
102 :0x821e 102 :0x821e
103 :0x9160 | 103 :0x9100 PHY_CSR7: BBP access register 0.
104 :0x0000 104 :0x0000
105 :0x0e07 105 :0x0e07
106 :0x5400 106 :0x5400
107 :0x0000 107 :0x0000
108 :0x0000 108 :0x0000
109 :0x0000 109 :0x0000
110 :0x0000 110 :0x0000
111 :0x0000 111 :0x0000
112 :0x0000 | 112 :0x032c STA_CSR0: FCS error count.
113 :0x01a9 | 113 :0xfb58 STA_CSR1: PLCP error count.
114 :0x0038 | 114 :0x6311 STA_CSR2: LONG error count.
115 :0x0000 | 115 :0x0a1f STA_CSR3: CCA false alarm.
116 :0x0000 116 :0x0000
117 :0x0000 117 :0x0000
118 :0x0169 | 118 :0x0000 STA_CSR6
119 :0x0011 | 119 :0x0000 STA_CSR7
120 :0x0000 120 :0x0000
121 :0x0000 121 :0x0000
122 :0x0a01 | 122 :0x02e1 STA_CSR10
123 :0x0000 123 :0x0000
124 :0x0000 124 :0x0000
125 :0x0000 125 :0x0000
126 :0x0000 126 :0x0000
127 :0x0000 127 :0x0000
eeprom eeprom
0 :0x2570 0 :0x2570
1 :0x0104 1 :0x0104
2 :0x1300 2 :0x1300
3 :0xe946 3 :0xe946
4 :0x8a8d 4 :0x8a8d
5 :0xffff 5 :0xffff
6 :0xffff 6 :0xffff
7 :0xffff 7 :0xffff
8 :0xffff 8 :0xffff
9 :0xffff 9 :0xffff
10 :0xffff 10 :0xffff
11 :0x2829 11 :0x2829
12 :0xfff0 12 :0xfff0
13 :0x00ff 13 :0x00ff
14 :0x112c 14 :0x112c
15 :0x1518 15 :0x1518
16 :0x1618 16 :0x1618
17 :0x3e00 17 :0x3e00
18 :0xffff 18 :0xffff
19 :0xffff 19 :0xffff
20 :0xffff 20 :0xffff
21 :0xffff 21 :0xffff
22 :0xffff 22 :0xffff
23 :0xffff 23 :0xffff
24 :0xffff 24 :0xffff
25 :0xffff 25 :0xffff
26 :0xffff 26 :0xffff
27 :0xffff 27 :0xffff
28 :0xffff 28 :0xffff
29 :0xffff 29 :0xffff
30 :0x1717 30 :0x1717
31 :0x1717 31 :0x1717
32 :0x1717 32 :0x1717
33 :0x1717 33 :0x1717
34 :0x1617 34 :0x1617
35 :0x1616 35 :0x1616
36 :0x1616 36 :0x1616
37 :0xffff 37 :0xffff
38 :0xffff 38 :0xffff
39 :0xffff 39 :0xffff
40 :0xffff 40 :0xffff
41 :0xffff 41 :0xffff
42 :0xffff 42 :0xffff
43 :0xffff 43 :0xffff
44 :0xffff 44 :0xffff
45 :0xffff 45 :0xffff
46 :0xffff 46 :0xffff
47 :0xffff 47 :0xffff
48 :0x0032 48 :0x0032
49 :0x6880 49 :0x6880
50 :0x3850 50 :0x3850
51 :0x6f5f 51 :0x6f5f
52 :0xff37 | 52 :0xfa00
bbp bbp
0 :0x13 0 :0x13
1 :0x45 | 1 :0x55
2 :0x1e | 2 :0x06 R2: TX antenna control
3 :0x02 3 :0x02
4 :0x19 4 :0x19
5 :0x09 | 5 :0x0b
6 :0x00 | 6 :0x10
7 :0x0e | 7 :0x00
8 :0x00 8 :0x00
9 :0x00 9 :0x00
10 :0x00 10 :0x00
11 :0x04 11 :0x04
12 :0x00 | 12 :0x01
13 :0x70 | 13 :0xa8
14 :0x1a 14 :0x1a
15 :0x30 15 :0x30
16 :0xac 16 :0xac
17 :0x60 | 17 :0x00
18 :0x18 18 :0x18
19 :0xff 19 :0xff
20 :0x1e 20 :0x1e
21 :0x18 21 :0x18
22 :0x18 22 :0x18
23 :0x08 23 :0x08
24 :0x68 | 24 :0x80
25 :0x38 | 25 :0x50
26 :0x08 26 :0x08
27 :0x23 27 :0x23
28 :0x18 28 :0x18
29 :0x18 29 :0x18
30 :0x10 30 :0x10
31 :0x2b 31 :0x2b
32 :0xb9 32 :0xb9
33 :0x55 33 :0x55
34 :0x12 34 :0x12
35 :0x50 35 :0x50
36 :0x11 36 :0x11
37 :0x05 37 :0x05
38 :0x00 38 :0x00
39 :0xc4 39 :0xc4
40 :0x02 40 :0x02
41 :0x60 41 :0x60
42 :0x08 | 42 :0x09
43 :0x01 | 43 :0x34
44 :0x78 | 44 :0x0b
45 :0x00 | 45 :0x6e
46 :0x38 | 46 :0x70
47 :0x0a 47 :0x0a
48 :0x04 48 :0x04
49 :0x02 49 :0x02
50 :0x68 50 :0x68
51 :0x56 | 51 :0x18
52 :0x2e | 52 :0x04
53 :0x10 53 :0x10
54 :0x18 54 :0x18
55 :0x7b | 55 :0x2d
56 :0x08 56 :0x08
57 :0x10 57 :0x10
58 :0x08 58 :0x08
59 :0x02 59 :0x02
60 :0x3f | 60 :0x3e
61 :0x6f | 61 :0x5f
62 :0x00 62 :0x00
63 :0x00 63 :0x00
64 :0x01 64 :0x01
65 :0x03 65 :0x03
66 :0x00 66 :0x00
67 :0x00 67 :0x00
68 :0x00 68 :0x00
69 :0x00 69 :0x00
70 :0x46 70 :0x46
71 :0x00 71 :0x00
72 :0x00 72 :0x00
73 :0x00 73 :0x00
74 :0xd4 74 :0xd4
75 :0xff 75 :0xff
76 :0x19 76 :0x19
77 :0x05 77 :0x05
78 :0x08 78 :0x08
79 :0x00 79 :0x00
80 :0x00 80 :0x00
81 :0x05 81 :0x05
82 :0x14 82 :0x14
83 :0x50 83 :0x50
84 :0xc0 84 :0xc0
85 :0x10 85 :0x10
86 :0x74 | 86 :0xcf
87 :0x04 | 87 :0x00
88 :0x00 88 :0x00
89 :0x00 89 :0x00
90 :0x00 90 :0x00
91 :0x00 91 :0x00
92 :0x00 92 :0x00
93 :0x00 93 :0x00
94 :0x00 94 :0x00
95 :0x00 95 :0x00
rf rf
0 :0x00000000 0 :0x00000000
1 :0x00022010 1 :0x00022010
2 :0x000008a6 2 :0x000008a6
3 :0x00063711 | 3 :0x00062d11
4 :0x00000e07 4 :0x00000e07
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc (fwd)
2008-06-29 18:51 ` Ivo van Doorn
@ 2008-07-08 3:55 ` Rogério Brito
2008-07-08 13:58 ` Ivo van Doorn
0 siblings, 1 reply; 14+ messages in thread
From: Rogério Brito @ 2008-07-08 3:55 UTC (permalink / raw)
To: Ivo van Doorn
Cc: John W. Linville, linux-kernel, rt2400-devel, rbrito, Linus Torvalds
Hi, all. (And Hi Linus!)
On Jun 29 2008, Ivo van Doorn wrote:
> Rogério Brito wrote:
> > Just for your information, I just compiled the -rc7 kernel on x86-64 (where
> > rt2500usb works if I boot with kernel 2.6.25) and still doesn't work (I'm
> > not even mentioning here PowerPC).
Just to reiterate, for both Ivo and John and people on the rt2400 list
(who may not seem my earlier problem reports that went back and forth with
Ivo), I'm willing to test any tree to get the driver working with my D-Link
DWL-G122 stick revision B (which actually works with with the rt2500usb
driver, if I boot with kernel 2.6.25, as mentioned above, but has problems
with 2.6.26-rc* kernels).
I was a bit busy with the lame project (we have just released a new
upstream release, 3.98, after two years of work!) and I have not kept up
with testing the -rc8 and -rc9 kernels that Linus released in the interim,
but I am downloading the patches so that I can see their behavior.
Actually, I did some tests with 2.6.25.4 (which is the kernel that I am
using on my x86-64, pending and update soon to 2.6.25.10 or whatever is the
point-release du jour) and I was very happy to see that I don't need the
non-free firmware from ralink.
Just as a reminder: with 2.6.25.4, I can work with it on x86-64, but not
with PowerPC. With recent 2.6.26-rc* kernels, it stopped working on x86-64
also. :(
Unfortunately, I may be moving in the near future and I would like to bring
my iBook G3 laptop with me (even if dated) so that I can continue my work
on some projects and the only way to connect and to work on then would be
with the USB stick, as I won't probably have wired conection.
Right now, I am unable to connect to the network with the USB stick, as Ivo
mentioned, due to some register differences, which I keep here (see below)
for reference (sorry for the long e-mail, but this is to keep the context
as we have already entered another month and the issue is not fixed and I
hope that Linus won't release the final 2.6.26 yet, as this kernel will
most probably be the one used by some distributions).
As Linus mentioned on
<alpine.LFD.1.10.0807051557500.3016@woody.linux-foundation.org>, he would
like a lot of people testing the changes---no, this bug submitter has not
been kidnapped :)---and this is what I am trying to do (actually, I'm
willing to do git bisect, test new trees---you name it).
Oh, just as a last piece of information, the USB wireless stick works fine
if I boot MacOS X, but Apple has dropped the support for older PowerPC
machines (and even some not so old ones :( ), this is one reason more for
me to want a working Linux release.
Thanks in advance to everybody, Rogério Brito.
P.S.: Here follows Ivo's comments on the register differences taken from
debugfs:
> In case other people are interested in the register differences as well,
> attached is the real difference between the registers. Registers that are
> different have the register name and meaning on the right side.
>
> Interesting things to note:
> - SIFS/EIFS timing is different, which is expected since rt2500usb now
> listens to mac80211 for this information.
> - Activity led is disabled, not interesting for this bug, but it really should have
> been set to 1.
> - mac80211 now uses short preamble
> - Basic rates mask is 0, this is very odd....
> - Link tuner value is set to 0, I seriously doubt that is a correct value
> - TX power is different, mac80211 probably has set it to something different
>
> Thats it for now, if anybody has any ideas, please let me know. :)
>
> Ivo
> 2.6.25.4-1 | 2.6.26-rc5-2
> driver: rt2500usb driver: rt2500usb
> version: 2.0.14 | version: 2.1.4
> compiled: Jun 13 2008 01:33:03 | compiled: Jun 8 2008 17:08:54
> dev_flags: 0x0001012f | dev_flags: 0x00000e2f
> rt chip: 1201 rt chip: 1201
> rf chip: 0005 rf chip: 0005
> revision:00000005 revision:00000005
>
> csr length: 128 csr length: 128
> eeprom length: 53 eeprom length: 53
> bbp length: 96 bbp length: 96
> rf length: 5 rf length: 5
>
> csr csr
> 0 :0x0005 0 :0x0005
> 1 :0x0004 1 :0x0004
> 2 :0x1300 2 :0x1300
> 3 :0xe946 3 :0xe946
> 4 :0x8a8d 4 :0x8a8d
> 5 :0x1300 5 :0x1300
> 6 :0x5146 6 :0x5146
> 7 :0x6510 7 :0x6510
> 8 :0x0980 8 :0x0980
> 9 :0xff1d 9 :0xff1d
> 10 :0x0014 10 :0x0014
> 11 :0x0005 | 11 :0x000a MAC_CSR11: SIFS.
> 12 :0x016c | 12 :0x013a MAC_CSR12: EIFS.
> 13 :0x1111 13 :0x1111
> 14 :0x1e11 14 :0x1e11
> 15 :0x01ee 15 :0x01ee
> 16 :0x0000 16 :0x0000
> 17 :0x01fe 17 :0x01fe
> 18 :0x005a 18 :0x005a
> 19 :0xff00 19 :0xff00
> 20 :0x0003 | 20 :0x0002 MAC_CSR20: LED control register.
> 21 :0x1e46 21 :0x1e46
> 22 :0x0053 22 :0x0053
> 23 :0x0000 23 :0x0000
> 24 :0x0000 24 :0x0000
> 25 :0x0000 25 :0x0000
> 26 :0x0000 26 :0x0000
> 27 :0x0000 27 :0x0000
> 28 :0x0000 28 :0x0000
> 29 :0x0000 29 :0x0000
> 30 :0x0000 30 :0x0000
> 31 :0x0000 31 :0x0000
> 32 :0x1ec0 32 :0x1ec0
> 33 :0xb11a | 33 :0xb162 TXRX_CSR1: TX configuration.
> 34 :0x007e 34 :0x007e
> 35 :0xb3af 35 :0xb3af
> 36 :0xb3aa 36 :0xb3aa
> 37 :0x8c8d 37 :0x8c8d
> 38 :0x8b8a 38 :0x8b8a
> 39 :0x8687 39 :0x8687
> 40 :0x0085 40 :0x0085
> 41 :0x0162 41 :0x0162
> 42 :0x000e | 42 :0x000a TXRX_CSR10: Auto responder control.
> 43 :0x015f | 43 :0x0000 TXRX_CSR11: Auto responder basic rate.
> 44 :0x140a 44 :0x140a
> 45 :0x7038 45 :0x7038
> 46 :0x0c13 46 :0x0c13
> 47 :0x0609 47 :0x0609
> 48 :0x0305 48 :0x0305
> 49 :0x0203 49 :0x0203
> 50 :0xfa00 50 :0xfa00
> 51 :0x0003 | 51 :0x000b TXRX_CSR19: Synchronization control register.
> 52 :0x0003 52 :0x0003
> 53 :0xe78f 53 :0xe78f
> 54 :0x0000 54 :0x0000
> 55 :0x0000 55 :0x0000
> 56 :0x0000 56 :0x0000
> 57 :0x0000 57 :0x0000
> 58 :0x0000 58 :0x0000
> 59 :0x0000 59 :0x0000
> 60 :0x0000 60 :0x0000
> 61 :0x0000 61 :0x0000
> 62 :0x0000 62 :0x0000
> 63 :0x0000 63 :0x0000
> 64 :0x0000 64 :0x0000
> 65 :0x0000 65 :0x0000
> 66 :0x0000 66 :0x0000
> 67 :0x0000 67 :0x0000
> 68 :0x0000 68 :0x0000
> 69 :0x0000 69 :0x0000
> 70 :0x0000 70 :0x0000
> 71 :0x0000 71 :0x0000
> 72 :0x0000 72 :0x0000
> 73 :0x0000 73 :0x0000
> 74 :0x0000 74 :0x0000
> 75 :0x0000 75 :0x0000
> 76 :0x0000 76 :0x0000
> 77 :0x0000 77 :0x0000
> 78 :0x0000 78 :0x0000
> 79 :0x0000 79 :0x0000
> 80 :0x0000 80 :0x0000
> 81 :0x0000 81 :0x0000
> 82 :0x0000 82 :0x0000
> 83 :0x0000 83 :0x0000
> 84 :0x0000 84 :0x0000
> 85 :0x0000 85 :0x0000
> 86 :0x0000 86 :0x0000
> 87 :0x0000 87 :0x0000
> 88 :0x0000 88 :0x0000
> 89 :0x0000 89 :0x0000
> 90 :0x0000 90 :0x0000
> 91 :0x0000 91 :0x0000
> 92 :0x0000 92 :0x0000
> 93 :0x0000 93 :0x0000
> 94 :0x0000 94 :0x0000
> 95 :0x0000 95 :0x0000
> 96 :0x1221 96 :0x1221
> 97 :0x0003 97 :0x0003
> 98 :0x0000 98 :0x0000
> 99 :0x0000 99 :0x0000
> 100 :0x000f 100 :0x000f
> 101 :0x8206 101 :0x8206
> 102 :0x821e 102 :0x821e
> 103 :0x9160 | 103 :0x9100 PHY_CSR7: BBP access register 0.
> 104 :0x0000 104 :0x0000
> 105 :0x0e07 105 :0x0e07
> 106 :0x5400 106 :0x5400
> 107 :0x0000 107 :0x0000
> 108 :0x0000 108 :0x0000
> 109 :0x0000 109 :0x0000
> 110 :0x0000 110 :0x0000
> 111 :0x0000 111 :0x0000
> 112 :0x0000 | 112 :0x032c STA_CSR0: FCS error count.
> 113 :0x01a9 | 113 :0xfb58 STA_CSR1: PLCP error count.
> 114 :0x0038 | 114 :0x6311 STA_CSR2: LONG error count.
> 115 :0x0000 | 115 :0x0a1f STA_CSR3: CCA false alarm.
> 116 :0x0000 116 :0x0000
> 117 :0x0000 117 :0x0000
> 118 :0x0169 | 118 :0x0000 STA_CSR6
> 119 :0x0011 | 119 :0x0000 STA_CSR7
> 120 :0x0000 120 :0x0000
> 121 :0x0000 121 :0x0000
> 122 :0x0a01 | 122 :0x02e1 STA_CSR10
> 123 :0x0000 123 :0x0000
> 124 :0x0000 124 :0x0000
> 125 :0x0000 125 :0x0000
> 126 :0x0000 126 :0x0000
> 127 :0x0000 127 :0x0000
>
> eeprom eeprom
> 0 :0x2570 0 :0x2570
> 1 :0x0104 1 :0x0104
> 2 :0x1300 2 :0x1300
> 3 :0xe946 3 :0xe946
> 4 :0x8a8d 4 :0x8a8d
> 5 :0xffff 5 :0xffff
> 6 :0xffff 6 :0xffff
> 7 :0xffff 7 :0xffff
> 8 :0xffff 8 :0xffff
> 9 :0xffff 9 :0xffff
> 10 :0xffff 10 :0xffff
> 11 :0x2829 11 :0x2829
> 12 :0xfff0 12 :0xfff0
> 13 :0x00ff 13 :0x00ff
> 14 :0x112c 14 :0x112c
> 15 :0x1518 15 :0x1518
> 16 :0x1618 16 :0x1618
> 17 :0x3e00 17 :0x3e00
> 18 :0xffff 18 :0xffff
> 19 :0xffff 19 :0xffff
> 20 :0xffff 20 :0xffff
> 21 :0xffff 21 :0xffff
> 22 :0xffff 22 :0xffff
> 23 :0xffff 23 :0xffff
> 24 :0xffff 24 :0xffff
> 25 :0xffff 25 :0xffff
> 26 :0xffff 26 :0xffff
> 27 :0xffff 27 :0xffff
> 28 :0xffff 28 :0xffff
> 29 :0xffff 29 :0xffff
> 30 :0x1717 30 :0x1717
> 31 :0x1717 31 :0x1717
> 32 :0x1717 32 :0x1717
> 33 :0x1717 33 :0x1717
> 34 :0x1617 34 :0x1617
> 35 :0x1616 35 :0x1616
> 36 :0x1616 36 :0x1616
> 37 :0xffff 37 :0xffff
> 38 :0xffff 38 :0xffff
> 39 :0xffff 39 :0xffff
> 40 :0xffff 40 :0xffff
> 41 :0xffff 41 :0xffff
> 42 :0xffff 42 :0xffff
> 43 :0xffff 43 :0xffff
> 44 :0xffff 44 :0xffff
> 45 :0xffff 45 :0xffff
> 46 :0xffff 46 :0xffff
> 47 :0xffff 47 :0xffff
> 48 :0x0032 48 :0x0032
> 49 :0x6880 49 :0x6880
> 50 :0x3850 50 :0x3850
> 51 :0x6f5f 51 :0x6f5f
> 52 :0xff37 | 52 :0xfa00
>
> bbp bbp
> 0 :0x13 0 :0x13
> 1 :0x45 | 1 :0x55
> 2 :0x1e | 2 :0x06 R2: TX antenna control
> 3 :0x02 3 :0x02
> 4 :0x19 4 :0x19
> 5 :0x09 | 5 :0x0b
> 6 :0x00 | 6 :0x10
> 7 :0x0e | 7 :0x00
> 8 :0x00 8 :0x00
> 9 :0x00 9 :0x00
> 10 :0x00 10 :0x00
> 11 :0x04 11 :0x04
> 12 :0x00 | 12 :0x01
> 13 :0x70 | 13 :0xa8
> 14 :0x1a 14 :0x1a
> 15 :0x30 15 :0x30
> 16 :0xac 16 :0xac
> 17 :0x60 | 17 :0x00
> 18 :0x18 18 :0x18
> 19 :0xff 19 :0xff
> 20 :0x1e 20 :0x1e
> 21 :0x18 21 :0x18
> 22 :0x18 22 :0x18
> 23 :0x08 23 :0x08
> 24 :0x68 | 24 :0x80
> 25 :0x38 | 25 :0x50
> 26 :0x08 26 :0x08
> 27 :0x23 27 :0x23
> 28 :0x18 28 :0x18
> 29 :0x18 29 :0x18
> 30 :0x10 30 :0x10
> 31 :0x2b 31 :0x2b
> 32 :0xb9 32 :0xb9
> 33 :0x55 33 :0x55
> 34 :0x12 34 :0x12
> 35 :0x50 35 :0x50
> 36 :0x11 36 :0x11
> 37 :0x05 37 :0x05
> 38 :0x00 38 :0x00
> 39 :0xc4 39 :0xc4
> 40 :0x02 40 :0x02
> 41 :0x60 41 :0x60
> 42 :0x08 | 42 :0x09
> 43 :0x01 | 43 :0x34
> 44 :0x78 | 44 :0x0b
> 45 :0x00 | 45 :0x6e
> 46 :0x38 | 46 :0x70
> 47 :0x0a 47 :0x0a
> 48 :0x04 48 :0x04
> 49 :0x02 49 :0x02
> 50 :0x68 50 :0x68
> 51 :0x56 | 51 :0x18
> 52 :0x2e | 52 :0x04
> 53 :0x10 53 :0x10
> 54 :0x18 54 :0x18
> 55 :0x7b | 55 :0x2d
> 56 :0x08 56 :0x08
> 57 :0x10 57 :0x10
> 58 :0x08 58 :0x08
> 59 :0x02 59 :0x02
> 60 :0x3f | 60 :0x3e
> 61 :0x6f | 61 :0x5f
> 62 :0x00 62 :0x00
> 63 :0x00 63 :0x00
> 64 :0x01 64 :0x01
> 65 :0x03 65 :0x03
> 66 :0x00 66 :0x00
> 67 :0x00 67 :0x00
> 68 :0x00 68 :0x00
> 69 :0x00 69 :0x00
> 70 :0x46 70 :0x46
> 71 :0x00 71 :0x00
> 72 :0x00 72 :0x00
> 73 :0x00 73 :0x00
> 74 :0xd4 74 :0xd4
> 75 :0xff 75 :0xff
> 76 :0x19 76 :0x19
> 77 :0x05 77 :0x05
> 78 :0x08 78 :0x08
> 79 :0x00 79 :0x00
> 80 :0x00 80 :0x00
> 81 :0x05 81 :0x05
> 82 :0x14 82 :0x14
> 83 :0x50 83 :0x50
> 84 :0xc0 84 :0xc0
> 85 :0x10 85 :0x10
> 86 :0x74 | 86 :0xcf
> 87 :0x04 | 87 :0x00
> 88 :0x00 88 :0x00
> 89 :0x00 89 :0x00
> 90 :0x00 90 :0x00
> 91 :0x00 91 :0x00
> 92 :0x00 92 :0x00
> 93 :0x00 93 :0x00
> 94 :0x00 94 :0x00
> 95 :0x00 95 :0x00
>
> rf rf
> 0 :0x00000000 0 :0x00000000
> 1 :0x00022010 1 :0x00022010
> 2 :0x000008a6 2 :0x000008a6
> 3 :0x00063711 | 3 :0x00062d11
> 4 :0x00000e07 4 :0x00000e07
--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc (fwd)
2008-07-08 3:55 ` Rogério Brito
@ 2008-07-08 13:58 ` Ivo van Doorn
2008-07-13 0:20 ` Rogério Brito
0 siblings, 1 reply; 14+ messages in thread
From: Ivo van Doorn @ 2008-07-08 13:58 UTC (permalink / raw)
To: Rogério Brito
Cc: John W. Linville, linux-kernel, rt2400-devel, Linus Torvalds
Hi,
Could you try some of the following tests to control the registers:
I have grouped each test together, please don't do them all in one single shot,
since that will not help narrowing down the exact register which breaks everything.
> > 11 :0x0005 | 11 :0x000a MAC_CSR11: SIFS.
> > 12 :0x016c | 12 :0x013a MAC_CSR12: EIFS.
echo 11 > /<debugfsroot>/<mac80211>/rt2500usb/register/csr_offset
echo 5 > /<debugfsroot>/<mac80211>/rt2500usb/register/csr_value
echo 12 > /<debugfsroot>/<mac80211>/rt2500usb/register/csr_offset
echo 364 > /<debugfsroot>/<mac80211>/rt2500usb/register/csr_value
---
> > 33 :0xb11a | 33 :0xb162 TXRX_CSR1: TX configuration.
echo 33 > /<debugfsroot>/<mac80211>/rt2500usb/register/csr_offset
echo 45338 > /<debugfsroot>/<mac80211>/rt2500usb/register/csr_value
---
> > 42 :0x000e | 42 :0x000a TXRX_CSR10: Auto responder control.
> > 43 :0x015f | 43 :0x0000 TXRX_CSR11: Auto responder basic rate.
echo 42 > /<debugfsroot>/<mac80211>/rt2500usb/register/csr_offset
echo 14 > /<debugfsroot>/<mac80211>/rt2500usb/register/csr_value
echo 43 > /<debugfsroot>/<mac80211>/rt2500usb/register/csr_offset
echo 351 > /<debugfsroot>/<mac80211>/rt2500usb/register/csr_value
---
> > 2 :0x1e | 2 :0x06 R2: TX antenna control
echo 2 > /<debugfsroot>/<mac80211>/rt2500usb/register/bbp_offset
echo 30 > /<debugfsroot>/<mac80211>/rt2500usb/register/bbp_value
Ivo
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc (fwd)
2008-07-08 13:58 ` Ivo van Doorn
@ 2008-07-13 0:20 ` Rogério Brito
0 siblings, 0 replies; 14+ messages in thread
From: Rogério Brito @ 2008-07-13 0:20 UTC (permalink / raw)
To: Ivo van Doorn
Cc: John W. Linville, linux-kernel, rt2400-devel, Linus Torvalds, rbrito
[-- Attachment #1: Type: text/plain, Size: 4237 bytes --]
Hi, Ivo, John, Linus and all the people at the mailing lists.
It seems that I'm flooded with bad luck. :-( I tried the modifications
in the script attached (progressively uncommenting the commands, as you
asked me), but it seems that I had the bad luck that nothing worked with
kernel 2.6.26-rc5. I also tried with kernel 2.6.26-rc9, but again,
nothing worked [*].
The only thing that gave a signal of life was when I imitated what you
did and set the led register to the value that was present on the
2.6.25.x kernel. Then, a "iwconfig wlan0 ap any" gave me blinks on the
"Act" led each time that I issued the command.
Attached also is the "meat" of the dmesg of my system. You may notice
that after some time, I tried simply "ifdown wlan0" and "ifup wlan0" in
my Debian system. These commands are responsible, as you should guess,
for bringing an interface down and up.
I have not checked closely, but it seems that the modifications to the
registers are lost when you bring the interface down---is that right?
>From the dmesg logs, this seems to be the case.
On Jul 08 2008, Ivo van Doorn wrote:
> Hi,
>
> Could you try some of the following tests to control the registers:
> I have grouped each test together, please don't do them all in one single shot,
> since that will not help narrowing down the exact register which
> breaks everything.
Again, I didn't do everything in one single shot. I tested your
directions one at a time (first the 1st one, then, the 1st set and the
2nd set, then the 1st, 2nd, and 3rd set etc).
> > > 11 :0x0005 | 11 :0x000a MAC_CSR11: SIFS.
> > > 12 :0x016c | 12 :0x013a MAC_CSR12: EIFS.
>
> echo 11 > /<debugfsroot>/<mac80211>/rt2500usb/register/csr_offset
> echo 5 > /<debugfsroot>/<mac80211>/rt2500usb/register/csr_value
> echo 12 > /<debugfsroot>/<mac80211>/rt2500usb/register/csr_offset
> echo 364 > /<debugfsroot>/<mac80211>/rt2500usb/register/csr_value
>
> ---
>
> > > 33 :0xb11a | 33 :0xb162 TXRX_CSR1: TX configuration.
>
> echo 33 > /<debugfsroot>/<mac80211>/rt2500usb/register/csr_offset
> echo 45338 > /<debugfsroot>/<mac80211>/rt2500usb/register/csr_value
>
> ---
>
> > > 42 :0x000e | 42 :0x000a TXRX_CSR10: Auto responder control.
> > > 43 :0x015f | 43 :0x0000 TXRX_CSR11: Auto responder basic rate.
>
> echo 42 > /<debugfsroot>/<mac80211>/rt2500usb/register/csr_offset
> echo 14 > /<debugfsroot>/<mac80211>/rt2500usb/register/csr_value
> echo 43 > /<debugfsroot>/<mac80211>/rt2500usb/register/csr_offset
> echo 351 > /<debugfsroot>/<mac80211>/rt2500usb/register/csr_value
>
> ---
>
> > > 2 :0x1e | 2 :0x06 R2: TX antenna control
>
> echo 2 > /<debugfsroot>/<mac80211>/rt2500usb/register/bbp_offset
> echo 30 > /<debugfsroot>/<mac80211>/rt2500usb/register/bbp_value
I attach to this message the commands that I used. As you can see, I
tried some which seemed to me (as a layman) that would make some
difference, but they did nothing. :-( My commands were based on some of
the differences that you narrowed down in the last message.
Thank you very much, Rogério Brito.
[*] Actually, I got it once to work/authenticate with kernel 2.6.26-rc9,
but I couldn't reproduce the steps to that. I tried loading all the
registers this time with the script that I attach here, and I was so sad
that it didn't work a second time (and a third, etc) that I was running
a script that did:
"ifconfig wlan0 up; iwconfig wlan0 key s:xxx; iwconfig wlan0 essid
default" && iwconfig wlan0
Not even once it showed that it was associated with the ap, but once in
a while (not every time) that I run the line above the "act" led blinked
and the messages generated on the dmesg were slightly different from one
time to another (compressed, the log is quite small).
--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
[-- Attachment #2: rtusb2500-try04.txt --]
[-- Type: text/plain, Size: 1274 bytes --]
#!/bin/sh
echo 11 > /debug/ieee80211/phy0/rt2500usb/register/csr_offset
echo 5 > /debug/ieee80211/phy0/rt2500usb/register/csr_value
echo 12 > /debug/ieee80211/phy0/rt2500usb/register/csr_offset
echo 364 > /debug/ieee80211/phy0/rt2500usb/register/csr_value
echo 33 > /debug/ieee80211/phy0/rt2500usb/register/csr_offset
echo 45338 > /debug/ieee80211/phy0/rt2500usb/register/csr_value
echo 42 > /debug/ieee80211/phy0/rt2500usb/register/csr_offset
echo 14 > /debug/ieee80211/phy0/rt2500usb/register/csr_value
echo 43 > /debug/ieee80211/phy0/rt2500usb/register/csr_offset
echo 351 > /debug/ieee80211/phy0/rt2500usb/register/csr_value
echo 2 > /debug/ieee80211/phy0/rt2500usb/register/bbp_offset
echo 30 > /debug/ieee80211/phy0/rt2500usb/register/bbp_value
# My modifications
echo 20 > /debug/ieee80211/phy0/rt2500usb/register/csr_offset
echo 3 > /debug/ieee80211/phy0/rt2500usb/register/csr_value
echo 103 > /debug/ieee80211/phy0/rt2500usb/register/csr_offset
echo 37216 > /debug/ieee80211/phy0/rt2500usb/register/csr_value
echo 51 > /debug/ieee80211/phy0/rt2500usb/register/csr_offset
echo 3 > /debug/ieee80211/phy0/rt2500usb/register/csr_value
echo 3 > /debug/ieee80211/phy0/rt2500usb/register/rf_offset
echo 407313 > /debug/ieee80211/phy0/rt2500usb/register/rf_value
[-- Attachment #3: dmesg-with-2.6.25.txt --]
[-- Type: text/plain, Size: 1626 bytes --]
phy0 -> rt2500usb_init_bbp: Debug - Start initialization from EEPROM...
phy0 -> rt2500usb_init_bbp: Debug - BBP: 0x11, value: 0x2c.
phy0 -> rt2500usb_init_bbp: Debug - BBP: 0x15, value: 0x18.
phy0 -> rt2500usb_init_bbp: Debug - BBP: 0x16, value: 0x18.
phy0 -> rt2500usb_init_bbp: Debug - BBP: 0x3e, value: 0x00.
phy0 -> rt2500usb_init_bbp: Debug - ...End initialization from EEPROM.
HW CONFIG: channel=1 freq=2412 phymode=2
phy0 -> rt2x00mac_conf_tx: Info - Configured TX ring 0 - CWmin: 4, CWmax: 10, Aifs: 2.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX ring 1 - CWmin: 4, CWmax: 10, Aifs: 2.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX ring 7 - CWmin: 5, CWmax: 10, Aifs: 2.
HW CONFIG: channel=1 freq=2412 phymode=2
HW CONFIG: channel=2 freq=2417 phymode=2
HW CONFIG: channel=3 freq=2422 phymode=2
HW CONFIG: channel=4 freq=2427 phymode=2
HW CONFIG: channel=5 freq=2432 phymode=2
HW CONFIG: channel=6 freq=2437 phymode=2
HW CONFIG: channel=7 freq=2442 phymode=2
HW CONFIG: channel=8 freq=2447 phymode=2
HW CONFIG: channel=9 freq=2452 phymode=2
HW CONFIG: channel=10 freq=2457 phymode=2
HW CONFIG: channel=11 freq=2462 phymode=2
HW CONFIG: channel=1 freq=2412 phymode=2
HW CONFIG: channel=6 freq=2437 phymode=2
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:13:46:51:10:65
wlan0: RX authentication from 00:13:46:51:10:65 (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:13:46:51:10:65
wlan0: RX AssocResp from 00:13:46:51:10:65 (capab=0x431 status=0 aid=1)
wlan0: associated
wlan0: switched to short barker preamble (BSSID=00:13:46:51:10:65)
phy0: Added STA 00:13:46:51:10:65
[-- Attachment #4: dmesg-2.6.26-rc9.txt.gz --]
[-- Type: application/octet-stream, Size: 1037 bytes --]
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc (fwd)
2008-06-25 19:49 ` Rogério Brito
2008-06-29 18:51 ` Ivo van Doorn
@ 2008-08-04 13:26 ` Ivo van Doorn
2008-08-07 17:01 ` [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc Rogério Brito
2008-11-25 3:19 ` Still some problems with the rt2x00 driver Rogério Brito
1 sibling, 2 replies; 14+ messages in thread
From: Ivo van Doorn @ 2008-08-04 13:26 UTC (permalink / raw)
To: Rogério Brito; +Cc: John W. Linville, linux-kernel
Hi,
> On Jun 20 2008, Rogério Brito wrote:
> > On Jun 20 2008, Ivo van Doorn wrote:
> > >
> > > > Did you receive my earlier message (attached here for reference)? I'm
> > > > willing to experiment with the driver a little bit and I hope that the
> > > > information that I have provided so far is helpful to chase the reason
> > > > why the driver doesn't work on PowerPC.
> > >
> > > Sorry I have been quite busy with other things.
> >
> > I'm terribly sorry for that, since I would like the driver to work with
> > the USB stick still in the 2.6.26 release (since that's what some
> > distributions will probably use).
>
> Just for your information, I just compiled the -rc7 kernel on x86-64 (where
> rt2500usb works if I boot with kernel 2.6.25) and still doesn't work (I'm
> not even mentioning here PowerPC).
I have found the problem and have send it upstream so the patch should
be present in 2.6.27. Note that I am not going to push it to 2.6.26 since
I don't know if the patch will cause problems in other parts of the driver.
Ivo
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc
2008-08-04 13:26 ` Ivo van Doorn
@ 2008-08-07 17:01 ` Rogério Brito
2008-11-25 3:19 ` Still some problems with the rt2x00 driver Rogério Brito
1 sibling, 0 replies; 14+ messages in thread
From: Rogério Brito @ 2008-08-07 17:01 UTC (permalink / raw)
To: Ivo van Doorn; +Cc: John W. Linville, linux-kernel
Hi, Ivo, John and others.
On Aug 04 2008, Ivo van Doorn wrote:
> Rogério Brito wrote:
> > Just for your information, I just compiled the -rc7 kernel on x86-64
> > (where rt2500usb works if I boot with kernel 2.6.25) and still
> > doesn't work (I'm not even mentioning here PowerPC).
>
> I have found the problem and have send it upstream so the patch should
> be present in 2.6.27.
Thanks for your e-mail. Indeed, I just compiled a 2.6.27-rc2 kernel and
it worked fine on x86-64 at least, which is a good thing. The only small
problem that I see is that the activity led doesn't blink when the
interface is sending or receiving data.
Regarding PowerPC, unfortunately, my iBook's battery died and I will get
a replacement to it (as soon as I can afford it). I also have yet to
find some time to compile a kernel for it, but I am happy to report the
results that I get (compiling the kernel will be easy, but installing on
it will take me some time as my Linux installation on it seems to be
messed up).
> Note that I am not going to push it to 2.6.26 since I don't know if
> the patch will cause problems in other parts of the driver.
Ok, I see it. There were lots of changes in mac80211 too, from a quick
glance at the patch.
Thanks, Rogério Brito.
--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
^ permalink raw reply [flat|nested] 14+ messages in thread
* Still some problems with the rt2x00 driver
2008-08-04 13:26 ` Ivo van Doorn
2008-08-07 17:01 ` [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc Rogério Brito
@ 2008-11-25 3:19 ` Rogério Brito
2008-11-25 8:42 ` Ivo van Doorn
1 sibling, 1 reply; 14+ messages in thread
From: Rogério Brito @ 2008-11-25 3:19 UTC (permalink / raw)
To: Ivo van Doorn; +Cc: John W. Linville, linux-kernel
Hi again, Ivo, John and others.
On Aug 04 2008, Ivo van Doorn wrote:
> I have found the problem and have send it upstream so the patch
> should be
> present in 2.6.27.
Well, it works ok (but see below) on powerpc, with a 2.6.27 kernel (I
still have not upgraded it).
There are two strange things that I've noticed, though and that I
feel need to be fixed:
1 - the rt63 driver used by a PCMCIA card DWL-G630 model has, for
many kernels (from 2.6.24 and up to and including kernel 2.6.27, as
shipped by Ubuntu for ia32), shown a strange behavior: after
everything is working correctly, the network simply becomes
unavailable, with the gnome network monitor showing that the card has
no signal. If I issue the command "iwconfig ra0 ap any", for example,
the card starts working again.
(Actually, I put this on a cron job to be executed every minute, but
even then, there are time windows where the card is not working). I'm
not in front of the notebook (a very old Armada V300 that my parents
are using for production), so I don't know if the card looses
association with the Access Point or not. I can check that, if nobody
else reported this problem yet.
2 - the rt2500usb driver that I use on a very old iBook G3 (powerpc)
also works fine and has a similar, but not identical behaviour: the
DWL-G122 USB stick that I have works fine once associated and when it
is transferring data. Once I leave the network unused for, say, 2
minutes, the connection with the AP is dropped. Here, also, issuing
"iwconfig wlan0 ap any" makes it work again.
Notice the difference in both cases: with the PCMCIA/ia32 case, no
matter if there is traffic on the network or not, the the connection
is interrupted. With the USB/powerpc case, if there is traffic, the
connection remains working fine.
> Note that I am not going to push it to 2.6.26 since I don't know if
> the
> patch will cause problems in other parts of the driver.
There's no problem. I can compile vanilla kernels from kernel.org
without any problems.
Thanks for your kind help, Rogério Brito.
--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Still some problems with the rt2x00 driver
2008-11-25 3:19 ` Still some problems with the rt2x00 driver Rogério Brito
@ 2008-11-25 8:42 ` Ivo van Doorn
2008-12-02 1:56 ` Rogério Brito
0 siblings, 1 reply; 14+ messages in thread
From: Ivo van Doorn @ 2008-11-25 8:42 UTC (permalink / raw)
To: Rogério Brito; +Cc: John W. Linville, linux-kernel
Hi,
> There are two strange things that I've noticed, though and that I
> feel need to be fixed:
For both cases:
Is there anything in the log regading the drivers or mac80211?
Ivo
> 1 - the rt63 driver used by a PCMCIA card DWL-G630 model has, for
> many kernels (from 2.6.24 and up to and including kernel 2.6.27, as
> shipped by Ubuntu for ia32), shown a strange behavior: after
> everything is working correctly, the network simply becomes
> unavailable, with the gnome network monitor showing that the card has
> no signal. If I issue the command "iwconfig ra0 ap any", for example,
> the card starts working again.
>
> (Actually, I put this on a cron job to be executed every minute, but
> even then, there are time windows where the card is not working). I'm
> not in front of the notebook (a very old Armada V300 that my parents
> are using for production), so I don't know if the card looses
> association with the Access Point or not. I can check that, if nobody
> else reported this problem yet.
>
> 2 - the rt2500usb driver that I use on a very old iBook G3 (powerpc)
> also works fine and has a similar, but not identical behaviour: the
> DWL-G122 USB stick that I have works fine once associated and when it
> is transferring data. Once I leave the network unused for, say, 2
> minutes, the connection with the AP is dropped. Here, also, issuing
> "iwconfig wlan0 ap any" makes it work again.
>
> Notice the difference in both cases: with the PCMCIA/ia32 case, no
> matter if there is traffic on the network or not, the the connection
> is interrupted. With the USB/powerpc case, if there is traffic, the
> connection remains working fine.
>
> > Note that I am not going to push it to 2.6.26 since I don't know if
> > the
> > patch will cause problems in other parts of the driver.
>
> There's no problem. I can compile vanilla kernels from kernel.org
> without any problems.
>
>
> Thanks for your kind help, Rogério Brito.
>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Still some problems with the rt2x00 driver
2008-11-25 8:42 ` Ivo van Doorn
@ 2008-12-02 1:56 ` Rogério Brito
2008-12-02 2:00 ` Rogério Brito
0 siblings, 1 reply; 14+ messages in thread
From: Rogério Brito @ 2008-12-02 1:56 UTC (permalink / raw)
To: Ivo van Doorn, Rogério Brito; +Cc: John W. Linville, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
Hi, Ivo, John and others.
First of all, sorry for the late reply. But I'm still here and I can
help get things straight. I just had some (once more) health problems
(I'm not currently that well).
On Tue, Nov 25, 2008 at 6:42 AM, Ivo van Doorn <ivdoorn@gmail.com> wrote:
> Hi,
>
>> There are two strange things that I've noticed, though and that I
>> feel need to be fixed:
>
> For both cases:
> Is there anything in the log regading the drivers or mac80211?
Yes, there are. Here I reproduce the logs from both 2.6.27.x which is
an experimental one from the Debian kernel team and the logs from a
2.6.28-rc6 kernel compiled by myself (with some extra debugging
enabled).
Thanks for your kind help, Rogério Brito.
--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
[-- Attachment #2: rt2500usb-disassociation.txt --]
[-- Type: text/plain, Size: 2393 bytes --]
[ 643.246655] usb 2-1: USB disconnect, address 2
[ 663.093109] usb 2-1: new full speed USB device using ohci_hcd and address 3
[ 663.409791] usb 2-1: configuration #1 chosen from 1 choice
[ 663.422026] usb 2-1: New USB device found, idVendor=2001, idProduct=3c00
[ 663.422058] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 663.422067] usb 2-1: Product: 802.11g WLAN Adapter
[ 663.422074] usb 2-1: Manufacturer: ANI
[ 664.631468] phy0: Selected rate control algorithm 'pid'
[ 665.065967] Registered led device: rt2500usb-phy0:radio
[ 665.068869] usbcore: registered new interface driver rt2500usb
[ 692.429861] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 694.125465] wlan0: authenticate with AP 00:13:46:51:10:65
[ 694.127508] wlan0: authenticated
[ 694.127536] wlan0: associate with AP 00:13:46:51:10:65
[ 694.130502] wlan0: RX AssocResp from 00:13:46:51:10:65 (capab=0x431 status=0 aid=1)
[ 694.130522] wlan0: associated
[ 694.138610] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 704.793080] wlan0: no IPv6 routers present
[ 1093.359818] RPC: Registered udp transport module.
[ 1093.359844] RPC: Registered tcp transport module.
[ 2418.297105] ondemand governor failed, too long transition latency of HW, fallback to performance governor
[ 4675.685561] wlan0: disassociated
[ 4676.686006] wlan0: associate with AP 00:13:46:51:10:65
[ 4676.688605] wlan0: RX ReassocResp from 00:13:46:51:10:65 (capab=0x431 status=17 aid=1)
[ 4676.688627] wlan0: AP denied association (code=17)
[ 4676.885138] wlan0: associate with AP 00:13:46:51:10:65
[ 4676.887520] wlan0: RX AssocResp from 00:13:46:51:10:65 (capab=0x431 status=17 aid=1073)
[ 4676.887539] wlan0: AP denied association (code=17)
[ 4677.085099] wlan0: associate with AP 00:13:46:51:10:65
[ 4677.087534] wlan0: RX AssocResp from 00:13:46:51:10:65 (capab=0x431 status=17 aid=1073)
[ 4677.087552] wlan0: AP denied association (code=17)
[ 4677.289225] wlan0: association with AP 00:13:46:51:10:65 timed out
Now, I don't have access to the network. I, now, issue "iwconfig wlan0 ap any"
and it goes working again:
[ 5841.260475] wlan0: authenticate with AP 00:13:46:51:10:65
[ 5841.262529] wlan0: authenticated
[ 5841.262560] wlan0: associate with AP 00:13:46:51:10:65
[ 5841.265499] wlan0: RX AssocResp from 00:13:46:51:10:65 (capab=0x431 status=0 aid=1)
[ 5841.265519] wlan0: associated
[-- Attachment #3: rt2500usb-disassociation-2.6.28-rc6.txt --]
[-- Type: text/plain, Size: 2869 bytes --]
phy0: HW CONFIG: freq=2437
phy0: HW CONFIG: freq=2442
phy0: HW CONFIG: freq=2447
phy0: HW CONFIG: freq=2452
phy0: HW CONFIG: freq=2457
phy0: HW CONFIG: freq=2462
phy0: HW CONFIG: freq=2412
phy0: HW CONFIG: freq=2437
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 4, CWmax: 10, Aifs: 2, TXop: 0.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 4, CWmax: 10, Aifs: 2, TXop: 0.
wlan0: authenticate with AP 00:13:46:51:10:65
wlan0: authenticated
wlan0: associate with AP 00:13:46:51:10:65
wlan0: RX AssocResp from 00:13:46:51:10:65 (capab=0x431 status=0 aid=1)
wlan0: associated
phy0: Allocated STA 00:13:46:51:10:65
phy0: Inserted STA 00:13:46:51:10:65
wlan0: switched to short barker preamble (BSSID=00:13:46:51:10:65)
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
PM: Adding info for No Bus:0:18
wlan0: disassociated
phy0: Removed STA 00:13:46:51:10:65
phy0: Destroyed STA 00:13:46:51:10:65
wlan0: associate with AP 00:13:46:51:10:65
wlan0: RX ReassocResp from 00:13:46:51:10:65 (capab=0x431 status=17 aid=1)
wlan0: AP denied association (code=17)
wlan0: associate with AP 00:13:46:51:10:65
wlan0: RX AssocResp from 00:13:46:51:10:65 (capab=0x431 status=17 aid=1073)
wlan0: AP denied association (code=17)
wlan0: associate with AP 00:13:46:51:10:65
wlan0: RX AssocResp from 00:13:46:51:10:65 (capab=0x431 status=17 aid=1073)
wlan0: AP denied association (code=17)
wlan0: association with AP 00:13:46:51:10:65 timed out
Again, here I lost access to the network. Issuing "iwconfig wlan0 ap any"
restores the access to the network.
phy0: HW CONFIG: freq=2437
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 4, CWmax: 10, Aifs: 2, TXop: 0.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 4, CWmax: 10, Aifs: 2, TXop: 0.
wlan0: direct probe to AP 00:13:46:51:10:65 try 1
wlan0 direct probe responded
wlan0: authenticate with AP 00:13:46:51:10:65
wlan0: authenticated
wlan0: associate with AP 00:13:46:51:10:65
wlan0: RX AssocResp from 00:13:46:51:10:65 (capab=0x431 status=0 aid=1)
wlan0: associated
phy0: Allocated STA 00:13:46:51:10:65
phy0: Inserted STA 00:13:46:51:10:65
wlan0: switched to short barker preamble (BSSID=00:13:46:51:10:65)
Again:
wlan0: disassociated
phy0: Removed STA 00:13:46:51:10:65
phy0: Destroyed STA 00:13:46:51:10:65
wlan0: associate with AP 00:13:46:51:10:65
wlan0: RX ReassocResp from 00:13:46:51:10:65 (capab=0x431 status=17 aid=1)
wlan0: AP denied association (code=17)
wlan0: associate with AP 00:13:46:51:10:65
wlan0: RX AssocResp from 00:13:46:51:10:65 (capab=0x431 status=17 aid=1073)
wlan0: AP denied association (code=17)
wlan0: associate with AP 00:13:46:51:10:65
wlan0: RX AssocResp from 00:13:46:51:10:65 (capab=0x431 status=17 aid=1073)
wlan0: AP denied association (code=17)
wlan0: association with AP 00:13:46:51:10:65 timed out
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Still some problems with the rt2x00 driver
2008-12-02 1:56 ` Rogério Brito
@ 2008-12-02 2:00 ` Rogério Brito
0 siblings, 0 replies; 14+ messages in thread
From: Rogério Brito @ 2008-12-02 2:00 UTC (permalink / raw)
To: Ivo van Doorn, Rogério Brito; +Cc: John W. Linville, linux-kernel
Hi again, Ivo.
On Mon, Dec 1, 2008 at 11:56 PM, Rogério Brito <rbrito@ime.usp.br> wrote:
> On Tue, Nov 25, 2008 at 6:42 AM, Ivo van Doorn <ivdoorn@gmail.com> wrote:
>> For both cases:
>> Is there anything in the log regading the drivers or mac80211?
>
> Yes, there are. Here I reproduce the logs from both 2.6.27.x which is
> an experimental one from the Debian kernel team and the logs from a
> 2.6.28-rc6 kernel compiled by myself (with some extra debugging
> enabled).
Needless to say, if you want me to test anything else here, please let me know.
Thanks again, Rogério Brito.
--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2008-12-02 2:00 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-06-20 17:57 [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc (fwd) Rogério Brito
2008-06-20 18:48 ` Ivo van Doorn
2008-06-20 19:58 ` Rogério Brito
2008-06-25 19:49 ` Rogério Brito
2008-06-29 18:51 ` Ivo van Doorn
2008-07-08 3:55 ` Rogério Brito
2008-07-08 13:58 ` Ivo van Doorn
2008-07-13 0:20 ` Rogério Brito
2008-08-04 13:26 ` Ivo van Doorn
2008-08-07 17:01 ` [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc Rogério Brito
2008-11-25 3:19 ` Still some problems with the rt2x00 driver Rogério Brito
2008-11-25 8:42 ` Ivo van Doorn
2008-12-02 1:56 ` Rogério Brito
2008-12-02 2:00 ` Rogério Brito
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).