netdev - Re: [PATCH V2] bcm43xx: Fix failure to deliver PCI-E interrupts

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4a55afb80701121118r342ec98s8b3312b8c7e59e85@mail.gmail.com>
Date:	Fri, 12 Jan 2007 14:18:51 -0500
From:	"evan foss" <evanfoss@...il.com>
To:	netdev@...r.kernel.org, Bcm43xx-dev@...ts.berlios.de
Subject: Re: [PATCH V2] bcm43xx: Fix failure to deliver PCI-E interrupts

> This hunk is OK, but I just want to point out that bustype is
> always equal to BCM43xx_BUSTYPE_PCI ;)
> The 0x53 timeouts are for an SSB-BUS.
> So strictly said this hunk is a NOP.
>
> The other hunks are OK, too. They fix real bugs.
> Thanks for spotting them, Larry!

So then what fixed int's for Stephen Sinclair? Or did they already
work? I would gladly help test I knew it applied to me.

>> The PCI-E modifications to bcm43xx do not set up the interrupt vector
>> correctly. Tested with BCM4311 (PCI-E) on x86_64 and BCM4306 (PCI) on i386.
>
>This was successful for me.  My 4311 is now getting interrupts, and I
>was able to successfully associate with an AP.  (i386)


-- 
http://www.coe.neu.edu/~efoss/
http://evanfoss.googlepages.com/
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html