| 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: <m3wt2bem13.fsf@maximus.localdomain> Date: Wed, 21 Feb 2007 13:24:24 +0100 From: Krzysztof Halasa <khc@...waw.pl> To: Udo van den Heuvel <udovdh@...all.nl> Cc: linux-kernel@...r.kernel.org, Alistair John Strachan <s0348365@....ed.ac.uk>, Lennart Sorensen <lsorense@...lub.uwaterloo.ca> Subject: Re: PCI riser cards and PCI irq routing, etc Udo van den Heuvel <udovdh@...all.nl> writes: > So if my non-VIA riser card can use DN 19 and also INT_A things should work? That INT_A may be INT_A from their (motherboard) point of view, but the riser card doesn't know about that, it only knows INTs as seen at its PCI edge connector (so this INT_A here is meaningless). Device numbers aren't rotated but rather derived from address lines (address/data). AD0-31 lines are the same across the whole PCI bus. That means device numbers are independent of POV. > (assuming that VIA Epia EN BIOS 1.07 is enough to use this card) My VIA EPIA-M 600 is probably older than your one, so I'd assume it should work as well. When you configure 0x13 and 0x14, both devices get IRQs - that means the BIOS can see both of them. > The DN is the only variable so INT lines are hardwired on the riser card? Yep. You just need a bit of soldering. -- Krzysztof Halasa - 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