linux-kernel - Re: [PATCH] Unbreak MSI on ATI devices

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 for Android: free password hash cracker in your pocket

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

Message-ID: <ada4pr61mie.fsf@cisco.com>
Date:	Thu, 04 Jan 2007 13:59:37 -0800
From:	Roland Dreier <rdreier@...co.com>
To:	Petr Vandrovec <petr@...drovec.name>
Cc:	jeff@...zik.org, linux-kernel@...r.kernel.org, akpm@...l.org
Subject: Re: [PATCH] Unbreak MSI on ATI devices

 > So my question is - what is real reason for disabling INTX when in MSI mode?
 > According to PCI spec it should not be needed, and it hurts at least chips
 > listed below:
 > 
 > 00:13.0 0c03: 1002:4374 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
 > 00:13.1 0c03: 1002:4375 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
 > 00:13.2 0c03: 1002:4373 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller 

heh... I'm not gloating or anything... but I am glad that some ASIC
designer was careless enough to prove me right when I said going
beyond what the PCI spec requires is dangerous.

 - R.
-
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/