On Sun, 2006-01-01 at 08:54 -0600, Matteo Frigo wrote:
I would appreciate if other people could confirm whether
handle_irq_transmit_status() is called on their system, so that I can
try to further diagnose the problem.
It's not being called here -- I see precisely the same as you. It stops
On Sunday 01 January 2006 19:35, David Woodhouse wrote:
On Sun, 2006-01-01 at 08:54 -0600, Matteo Frigo wrote:
I would appreciate if other people could confirm whether
handle_irq_transmit_status() is called on their system, so that I can
try to further diagnose the problem.
It's not
On Sunday 01 January 2006 19:35, David Woodhouse wrote:
On Sun, 2006-01-01 at 08:54 -0600, Matteo Frigo wrote:
I would appreciate if other people could confirm whether
handle_irq_transmit_status() is called on their system, so that I can
try to further diagnose the problem.
It's not
On Sunday 01 January 2006 22:21, Matteo Frigo wrote:
Michael Buesch [EMAIL PROTECTED] writes:
You have a device with a wlcore rev 5, which uses
one DMA engine for TX status blobs.
This code is untested and indeed likely to be wrong.
I have no facilities to test it (neither has any
This patch seems to do the trick. I am ignoring the
bcm43xx_rx_transmitstatus() mechanism and calling
bcm43xx_dma_handle_xmitstatus() directly.
patch
Description: Binary data
On Sunday 01 January 2006 23:52, you wrote:
This patch seems to do the trick. I am ignoring the
bcm43xx_rx_transmitstatus() mechanism and calling
bcm43xx_dma_handle_xmitstatus() directly.
Ok, very good. I will apply this patch and also remove
the dead bcm43xx_rx_transmitstatus code.
Thanks.
