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: <200702212355.25601.s0348365@sms.ed.ac.uk>
Date:	Wed, 21 Feb 2007 23:55:25 +0000
From:	Alistair John Strachan <s0348365@....ed.ac.uk>
To:	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>
Cc:	Krzysztof Halasa <khc@...waw.pl>,
	Udo van den Heuvel <udovdh@...all.nl>,
	linux-kernel@...r.kernel.org
Subject: Re: PCI riser cards and PCI irq routing, etc

On Wednesday 21 February 2007 22:40, Lennart Sorensen wrote:
> On Wed, Feb 21, 2007 at 10:35:05PM +0100, Krzysztof Halasa wrote:
> > Do you mean both slots on the riser card? No, they have to be rotated.
> >
> > Given the table from the manual:
> > > The IRQ (interrupt request line) are hardware lines over which devices
> > > can send interrupt signals to the microprocessor. The ??PCI & LAN?? IRQ
> > > pins are typically connected to the PCI bus INT A# ~ INT D# pins as
> > > follows: Order 1		Order 2 	Order 3 	Order 4
> > > PCI Slot 1	INT B# 		INT C# 		INT D# 		INT A#
> > > IEEE1394 	INT B#
> >
> > (I assume Order 1 is device's INT A and so on)
> > the chipset-centric view is:
>
> Well someone said the VIA uses INTA for the DN19 on their riser card,
> although is that INTA from the CPUs point of view or INTA from the slot
> the riser card is plugged into?  There was also mention of a BIOS update
> needed on some boards to even support the riser card at all.  Maybe that
> applies.

It applies on the M10000, I'm sure the newer EN series boards have always 
supported the feature.

One warning to you though, I found the riser to be pretty flaky, causing 
bizarre lockups and periodic crashes of Linux. Maybe this is a Linux bug, but 
it really didn't seem like it.

-- 
Cheers,
Alistair.

Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ