From: Michael Buesch <[EMAIL PROTECTED]>
Drain the Microcode TX-status-FIFO before we enable IRQs.
This is required, because the FIFO may still have entries left
from a previous run. Those would immediately fire after enabling
IRQs and would lead to an oops in the DMA TXstatus handling code.
Sign
From: Michael Buesch <[EMAIL PROTECTED]>
Drain the Microcode TX-status-FIFO before we enable IRQs.
This is required, because the FIFO may still have entries left
from a previous run. Those would immediately fire after enabling
IRQs and would lead to an oops in the DMA TXstatus handling code.
Sign
Jouni Malinen wrote:
On Thu, Nov 02, 2006 at 09:45:46AM +0100, Johannes Berg wrote:
On Wed, 2006-11-01 at 23:46 -0600, Larry Finger wrote:
Has anyone used this patch, particularly with WPA encryption? When I try it, wpa_supplicant
immediately uses 90+% of the cpu and never actually authenticate
On Thu, Nov 02, 2006 at 09:45:46AM +0100, Johannes Berg wrote:
> On Wed, 2006-11-01 at 23:46 -0600, Larry Finger wrote:
> > Has anyone used this patch, particularly with WPA encryption? When I try
> > it, wpa_supplicant
> > immediately uses 90+% of the cpu and never actually authenticates with my
On Wed, 2006-11-01 at 23:46 -0600, Larry Finger wrote:
> Has anyone used this patch, particularly with WPA encryption? When I try it,
> wpa_supplicant
> immediately uses 90+% of the cpu and never actually authenticates with my AP.
> I wonder if it is
> something with my system.
Unless wpa sup
Michael Buesch wrote:
Drain the Microcode TX-status-FIFO before we enable IRQs.
This is required, because the FIFO may still have entries left
from a previous run. Those would immediately fire after enabling
IRQs and would lead to an oops in the DMA TXstatus handling code.
Signed-off-by: Michael
On Thu, 2006-10-19 at 17:29 +0200, Michael Buesch wrote:
> Drain the Microcode TX-status-FIFO before we enable IRQs.
> This is required, because the FIFO may still have entries left
> from a previous run. Those would immediately fire after enabling
> IRQs and would lead to an oops in the DMA TXstat
Drain the Microcode TX-status-FIFO before we enable IRQs.
This is required, because the FIFO may still have entries left
from a previous run. Those would immediately fire after enabling
IRQs and would lead to an oops in the DMA TXstatus handling code.
Signed-off-by: Michael Buesch <[EMAIL PROTECTE
