lkml.org 
[lkml]   [2001]   [Jan]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: 2.4.0-test12: SiS pirq handling..
Date
| > 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/

\
 
 \ /
  Last update: 2005-03-22 13:25    [W:0.068 / U:0.156 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site