From: Alban Browaeys <prahal@yahoo.com>
To: Josef Bacik <josef@redhat.com>
Cc: Ivo van Doorn <ivdoorn@gmail.com>, Pavel Roskin <proski@gnu.org>,
John Linville <linville@tuxdriver.com>,
rt2x00 Users List <users@rt2x00.serialmonkey.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Gertjan van Wingerde <gwingerde@gmail.com>
Subject: Re: [PATCH 1/2] rt2x00 : hw support txdone implementation. (without fallback change)
Date: Fri, 26 Feb 2010 02:21:53 +0100 [thread overview]
Message-ID: <4B872231.5020609@yahoo.com> (raw)
In-Reply-To: <20100225205342.GF10960@localhost.localdomain>
On 25/02/2010 21:53, Josef Bacik wrote:
> On Thu, Feb 25, 2010 at 09:46:22PM +0100, Ivo van Doorn wrote:
>
>> Hi,
>>
>> Overall this patch has great similarities to something which Josef (CC added)
>> has posted earlier. The patch in question was not merged due to some issues,
>> but he is working on an updated. You might want to synchronize your work
>> with him. :)
>>
>>
> I was just looking at this patch series, but I couldn't get it to apply at all.
> Alban, does your patch series depend on other patches not in wireless-testing?
> It may have just been the whitespaces or something, cause the context looked
> right, it just wouldn't apply anything. Anyway I'm happy to work together, or
> I can just send you what I have and I'll be the guinea pig, since this really
> isn't my area of expertise. Thanks,
>
>
Well I cannot agree on the replacement from TX_STA_FIFO by DMA DONE
interrupts
handlers. As the latter prevents from having any success/failure status.
The txdone was borked and could not worked since WirelessCliId was read
as a queue entry index
and written as an encryption key. What you noticed too though with the
weird values you got.
Could you try
http://article.gmane.org/gmane.linux.kernel.wireless.general/47183
probably and also "pull" from
http://git.prahal.homelinux.net/?p=rt2x00.git;a=shortlog;h=refs/heads/rtt3070v2-next-debug.
It is not a clean set of patches though I am doing my best to get it
ready at least for to be sent to the ML.
The last commits adds a lot of printk (this is a debug branch) to try to
decipher a weird issue with long range issues.
Best regards
Alban
next prev parent reply other threads:[~2010-02-26 1:21 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
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 [this message]
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=4B872231.5020609@yahoo.com \
--to=prahal@yahoo.com \
--cc=gwingerde@gmail.com \
--cc=ivdoorn@gmail.com \
--cc=josef@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=proski@gnu.org \
--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).