All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aaron Tiensivu" <mojomofo@mojomofo.com>
To: "Linus Torvalds" <torvalds@transmeta.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.0-test12: SiS pirq handling..
Date: Mon, 29 Jan 2001 19:34:42 -0500	[thread overview]
Message-ID: <014001c08a54$70d24bd0$0300a8c0@methusela> (raw)
In-Reply-To: <Pine.LNX.4.10.10101291523470.9984-100000@penguin.transmeta.com>

| > Problem still exists, diffed to last kernel:
| Yes. But everything works for you, no? Including USB?

Mmmhmm..

| The problem is that you have this routing table entry:
|
| 00:01 slot=00 0:62/1eb8 1:00/0000 2:00/0000 3:00/0000
|
| which is really for the USB chip (PCI id 00:01.2), and which the PCI code
| _does_ find for the USB chip. So it should set up the routing happily, and
| everything should be ok.

Leave it to me to have goofy hardware.. :)

| Basically, the way your chipset is laid out PCI-wise, they are
| subfunctions of the same device (subfunction 1 is IDE, subfunction 2 is
| USB. Because of this they share an irq routing entry, and if they were to
| NOT clash they should have been given separate "irq pin" numbers in their
| config space. So a _good_ routing entry might have looked like
|
| 00:01 slot=00 0:fe/4000 1:62/1eb8 2:00/0000 3:00/0000
|
| where the IDE device has "irqpin=1" and the USB device has "irqpin=2", and
| USB points to link 62, while IDE points to link fe (ie "hardcode to 14").

Does anyone know who to prod at ASUS to maybe update their BIOS with a
proper routing table?
Maybe even adding proper K6-2+/K6-3+ ids in the BIOS (we can dream I
suppose)..
This is a simple packet-pumping routing box so one of those chips would be
overkill anyway.

| Now, will the two people in the world who know the pirq black magic now
| stand up and confirm or deride my interpretation?

It sounds correct to me..


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-30  0:35 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-29 21:51 2.4.0-test12: SiS pirq handling Linus Torvalds
2001-01-29 22:06 ` Sven Koch
2001-01-29 22:57 ` Recommended swap for 2.4.x Alan Olsen
2001-01-29 23:04   ` Linus Torvalds
2001-01-29 23:23   ` alex
2001-01-29 23:45     ` Mike Castle
2001-01-29 23:49     ` William T Wilson
2001-01-30  0:24       ` Kevin Krieser
2001-01-30  5:20         ` Jeff Chua
2001-01-30 19:21         ` James H. Cloos Jr.
2001-01-30  1:20     ` idalton
2001-01-30 11:48     ` Rik van Riel
2001-01-30 18:10       ` alex
2001-01-30 18:22         ` Rik van Riel
2001-01-30 18:40           ` Matthew Kirkwood
2001-01-30 18:43             ` Rik van Riel
2001-01-31 19:59               ` Russell King
2001-01-30 19:13           ` alex
2001-01-30 19:28             ` Rik van Riel
2001-02-02 13:51   ` Pavel Machek
2001-02-02 22:58     ` Alan Olsen
2001-02-02 20:27   ` Jonathan Morton
2001-01-29 23:17 ` 2.4.0-test12: SiS pirq handling Aaron Tiensivu
2001-01-29 23:44   ` Linus Torvalds
2001-01-30  0:34     ` Aaron Tiensivu [this message]
2001-01-31 10:19     ` Martin Diehl
2001-01-30  1:38 ` Adam Huffman
2001-01-31 10:21 ` [PATCH] minor ne2k-pci irq fix Martin Diehl
2001-01-31 12:11   ` davej
2001-02-01  0:01     ` Martin Diehl
2001-02-01 15:06       ` Jeff Garzik
2001-02-02 16:49         ` Martin Diehl
2001-02-02 17:05           ` Jeff Garzik
2001-02-03 20:20         ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2001-01-30  1:59 2.4.0-test12: SiS pirq handling Grover, Andrew

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='014001c08a54$70d24bd0$0300a8c0@methusela' \
    --to=mojomofo@mojomofo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.