public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rogério Brito" <rbrito@ime.usp.br>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-kernel@vger.kernel.org, rt2400-devel@lists.sourceforge.net,
	Linus Torvalds <torvalds@linux-foundation.org>,
	rbrito@ime.usp.br
Subject: Re: [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc (fwd)
Date: Sat, 12 Jul 2008 21:20:07 -0300	[thread overview]
Message-ID: <20080713002006.GA2831@ime.usp.br> (raw)
In-Reply-To: <200807081558.20365.IvDoorn@gmail.com>

[-- 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 --]

  reply	other threads:[~2008-07-13  0:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080713002006.GA2831@ime.usp.br \
    --to=rbrito@ime.usp.br \
    --cc=ivdoorn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rt2400-devel@lists.sourceforge.net \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox