| 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
| ||
|
Message-ID: <45BF5B1E.6050909@garzik.org> Date: Tue, 30 Jan 2007 09:50:06 -0500 From: Jeff Garzik <jeff@...zik.org> To: Alan <alan@...rguk.ukuu.org.uk> CC: Jean Delvare <jdelvare@...e.de>, Nick Piggin <nickpiggin@...oo.com.au>, Daniel Drake <dsd@...ctivated.net>, linux-kernel <linux-kernel@...r.kernel.org>, Adrian Bunk <bunk@...sta.de> Subject: Re: via irq quirk breakage Alan wrote: >> You have an old VT82C686 south bridge, which was tagged as "special" by >> Alan. For this chip, Alan's code only allows devices 00:00.x to be quirked. >> As my code was merely a reimplementation of Alan's idea, it does the same. >> Your USB controllers are at 00:07.x, so I'm not surprised they weren't >> quirked. >> >> Alan, why were dev_lo and dev_hi both set to 0 for the VT82C868 in your >> implementation? Is it a typo, or...? > > According to the documentation the VT82C686 has the following devices on > the internal bus: bus 0 dev ? fn 0-6. dev ? being the device of the > bridge itself. Re-reading the docs unlike the other the PCI idents aren't > fixed so my assumption of dev 0 is actually unsafe. I can't see anything > in the doc which guarantees 7 either. BTW, older VIA docs are publicly archived at http://gkernel.sourceforge.net/specs/via/ Jeff - 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/
Powered by blists - more mailing lists