mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Krzysztof Halasa <khc@pm.waw.pl>,
	Udo van den Heuvel <udovdh@xs4all.nl>,
	linux-kernel@vger.kernel.org
Subject: Re: PCI riser cards and PCI irq routing, etc
Date: Wed, 21 Feb 2007 23:55:25 +0000	[thread overview]
Message-ID: <200702212355.25601.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <20070221224027.GK22464@csclub.uwaterloo.ca>

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.

  reply	other threads:[~2007-02-21 23:55 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-18 14:07 Udo van den Heuvel
2007-02-18 15:54 ` Lennart Sorensen
2007-02-18 16:15   ` Udo van den Heuvel
2007-02-18 19:39     ` Lennart Sorensen
2007-02-19  1:50       ` Alistair John Strachan
2007-02-19  4:04       ` Udo van den Heuvel
2007-02-19 15:17         ` Lennart Sorensen
2007-02-19 15:43           ` Udo van den Heuvel
2007-02-19 17:13             ` Lennart Sorensen
2007-02-19 15:09       ` Udo van den Heuvel
2007-02-19 20:37         ` Krzysztof Halasa
2007-02-20  4:17           ` Udo van den Heuvel
2007-02-20 14:56             ` Alistair John Strachan
2007-02-20 15:44               ` Udo van den Heuvel
2007-02-20 19:51                 ` Alistair John Strachan
2007-02-21  9:24                 ` Udo van den Heuvel
2007-02-21 12:24                   ` Krzysztof Halasa
2007-02-21 14:59                     ` Udo van den Heuvel
2007-02-21 15:12                       ` Lennart Sorensen
     [not found]                         ` <m3hctfqjna.fsf@maximus.localdomain>
2007-02-21 22:40                           ` Lennart Sorensen
2007-02-21 23:55                             ` Alistair John Strachan [this message]
2007-02-22  1:19                               ` Krzysztof Halasa
2007-02-23 15:45                                 ` Udo van den Heuvel
2007-02-23 15:54                                   ` Lennart Sorensen
2007-02-23 17:55                                   ` Krzysztof Halasa
2007-02-23 18:17                                     ` Udo van den Heuvel
2007-02-23 19:42                                       ` Krzysztof Halasa
2007-03-03 14:35                                         ` Udo van den Heuvel
2007-02-23 18:12                                   ` Krzysztof Halasa
2007-02-23 18:44                                     ` Udo van den Heuvel
2007-02-23 20:00                                       ` Krzysztof Halasa
2007-02-25 15:59                                     ` Udo van den Heuvel
2007-02-22  1:16                             ` Krzysztof Halasa
2007-02-21 18:11                       ` Udo van den Heuvel
2007-02-21 19:54                         ` Krzysztof Halasa
2007-02-21 20:13                         ` Lennart Sorensen
2007-02-21 19:36                       ` Krzysztof Halasa
2007-02-21 13:44                   ` Lennart Sorensen
2007-02-21 18:55                     ` Udo van den Heuvel
2007-02-20 20:47             ` Krzysztof Halasa
2007-02-20 21:51               ` Lennart Sorensen
2007-02-21  0:11                 ` Krzysztof Halasa
2007-02-21 13:46                   ` Lennart Sorensen
2007-02-20  4:35           ` Udo van den Heuvel
2007-02-21  0:03             ` Krzysztof Halasa
2007-02-18 20:50     ` Krzysztof Halasa
2007-02-18 20:42   ` Krzysztof Halasa
2007-02-19 15:03     ` Lennart Sorensen
2007-02-19 18:23       ` Krzysztof Halasa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200702212355.25601.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=udovdh@xs4all.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®