From: Pavel Roskin <proski@gnu.org>
To: prahal@yahoo.com
Cc: John Linville <linville@tuxdriver.com>,
rt2x00 Users List <users@rt2x00.serialmonkey.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Ivo van Doorn <ivdoorn@gmail.com>
Subject: Re: [PATCH 1/2] rt2x00 : hw support txdone implementation. (without fallback change)
Date: Thu, 25 Feb 2010 12:48:12 -0500 [thread overview]
Message-ID: <1267120092.25296.31.camel@mj> (raw)
In-Reply-To: <4B85FA66.2020503@yahoo.com>
Hello!
I have tested both patches on the real hardware, and I don't see any
regressions. Unfortunately, the issue with interrupts is still there,
so ping stops after 11 packets, which limited my ability to test the
change extensively. That said, I was able to use wpa_supplicant and
dhcp to get an IP address using the patched driver in the station mode.
wpa_supplicant worked most of the time. I believe the occasional
failures are due to a preexisting memory corruption issue (I reported
earlier that addr3 can be corrupted in probe requests).
Unfortunately, the patches include corrupt whitespace, so they had to be
applied by "patch -l". Also, there are trailing tabs in two places.
That's not a big deal, but it's better avoided. Please consider using
git or stgit to send patches.
> + for (i=0; i<256; i++) {
checkpatch.pl complains about spacing. There should be spaces around
"=" and "<"
> + txwi = (__le32 *)(entry->skb->data -
> + rt2x00dev->hw->extra_tx_headroom);
I really don't see any point in introducing wrong code in one patch and
fixing it in another. I would just join the patches.
When bisecting for a problem, landing at a broken commit can lead to a
lot of wasted time.
> + rt2x00_desc_read(txwi, 1, &word);
> + tx_wcid = rt2x00_get_field32(word, TXWI_W1_WIRELESS_CLI_ID);
> + tx_ack = rt2x00_get_field32(word, TXWI_W1_ACK);
> + tx_pid = rt2x00_get_field32(word, TXWI_W1_PACKETID);
> +
> + if ((wcid != tx_wcid) || (ack != tx_ack) || (pid != tx_pid))
> + WARNING(rt2x00dev, "invalid TX_STA_FIFO content\n");
Can we make this sanity check optional?
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2010-02-25 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 4:19 [PATCH 1/2] rt2x00 : hw support txdone implementation. (without fallback change) Alban Browaeys
2010-02-25 17:22 ` Gertjan van Wingerde
2010-02-25 18:54 ` Alban Browaeys
2010-02-25 17:48 ` Pavel Roskin [this message]
2010-02-25 19:34 ` Alban Browaeys
2010-02-25 20:21 ` Pavel Roskin
2010-02-25 23:56 ` Alban Browaeys
2010-02-25 20:46 ` Ivo van Doorn
2010-02-25 20:53 ` Josef Bacik
2010-02-26 1:21 ` Alban Browaeys
2010-02-25 23:37 ` Alban Browaeys
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=1267120092.25296.31.camel@mj \
--to=proski@gnu.org \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=prahal@yahoo.com \
--cc=users@rt2x00.serialmonkey.com \
/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;
as well as URLs for NNTP newsgroup(s).