linux-kernel - Re: [PATCH] ALSA: hda-intel - Disable MSI support by default

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: <200611150611.13623.ak@suse.de>
Date:	Wed, 15 Nov 2006 06:11:13 +0100
From:	Andi Kleen <ak@...e.de>
To:	Roland Dreier <rdreier@...co.com>
Cc:	Linus Torvalds <torvalds@...l.org>, jeff@...zik.org,
	linux-kernel@...r.kernel.org, tiwai@...e.de
Subject: Re: [PATCH] ALSA: hda-intel - Disable MSI support by default

On Wednesday 15 November 2006 05:57, Roland Dreier wrote:
>  > At least AMD (PCI-X) and Serverworks bridges are known broken with MSI
>  > They should be both quirked though. Or rather one SVW bridge is quirked
>  > there might be more. AMD 8131 is quirked. AMD 8132 is broken too but 
>  > should not have the capability structure in the first place.
> 
> I thought people had AMD 8132 working?  The only MSI erratum I see for
> the 8132 is that a write to the MSI address with all byte-enables
> deasserted is bad.  But do any devices really do that?  It seems like
> a really odd thing to do.

Perhaps with special user space quirks, but not in mainline kernel because it's
not force enabled (see erratum #78).

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/