linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Davide Libenzi <davidel@xmailserver.org>
To: Thomas Winischhofer <thomas@winischhofer.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Martin Diehl <lists@mdiehl.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] sis650 irq router fix for 2.4.x
Date: Tue, 27 May 2003 10:06:56 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.55.0305271000550.2340@bigblue.dev.mcafeelabs.com> (raw)
In-Reply-To: <3ED32BA4.4040707@winischhofer.net>

On Tue, 27 May 2003, Thomas Winischhofer wrote:

>
> To Alan who is perhaps reading this: Who is an expert on this type of stuff?

Alan, are you there ?

(I also Cc'ed Martin that helped me with the patch)


> Davide Libenzi wrote:
> > On Mon, 26 May 2003, Thomas Winischhofer wrote:
> >
> >
> >>and I had (and have) no problems with irqs or USB (or anything) on any
> >>of these machines.
>
> First, let me say that I know NIL about irq routing. But fact is, I had
> my machines running with webcams, floppy drives and mice (all via USB,
> that is) - and had no problem.
>
> But you got me puzzled: As a matter of fact, it seems that ALL (!) my
> 650 variants show different routing tables, mostly like yours.
>
> dmesg with pci-debug enabled and lspci -vxxx printouts attached.
>
> 650 = "ISA bridge" revision 0
> M650 = revision 4
> 651 = revision 0x25
>
> Interestingly, as soon as pci-debugging was enabled, the log is full
> with error messages, and I suddenly actually _had_ problems with my
> network card and my wireless card (and assumingly the USB stuff, too,
> conclusing from the "failed" statements in the log)....
>
> >>Are you sure that checking the revision number of the device is enough?
> >
> >
> > It seems reasonble, at least without having the spec for the chipset. All
> > my searches failed about docs. Previous cases are correctly handled like
> > before, as you can see from the patch.
>
> I myself doubt this now. If I am reading the dmesg output correctly,
> even the machine with revision 0 (plain 650) is routing _some_ of the
> interrupts with 0x6x requests...

Yes, it seems that those request can be handled as pass thru, so might
have two options :

1) Use the new routing to handle only rev-04 and let users of other
	revisions to use the "stdroute" boot line

2) Use the new routing by default, except for the revisions that are known
	to work well with the old one


> > You happen to have the spec for the SIS650 ?
>
> That's a good one :) I have been bugging SiS since 2001 for docs, all I
> got was nothing.

Yes, I digged badly. Nothing beat Intel about documentation.



- Davide


  reply	other threads:[~2003-05-27 16:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-26 13:55 [patch] sis650 irq router fix for 2.4.x Thomas Winischhofer
2003-05-26 17:20 ` Davide Libenzi
2003-05-26 21:52 ` Davide Libenzi
2003-05-27  9:11   ` Thomas Winischhofer
2003-05-27 17:06     ` Davide Libenzi [this message]
2003-05-27 16:45       ` Alan Cox
2003-05-27 17:53         ` Davide Libenzi
2003-05-27 20:45           ` Thomas Winischhofer
2003-05-27 20:42         ` Thomas Winischhofer
2003-05-27 20:51           ` Alan Cox
2003-05-27 22:48             ` Thomas Winischhofer
2003-05-27 22:29           ` Davide Libenzi
2003-05-27 22:55             ` Thomas Winischhofer
2003-05-27 22:58               ` Davide Libenzi
2003-05-27 10:59   ` SiS USB IRQ (Was: [patch] sis650 irq router fix for 2.4.x) Thomas Winischhofer

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=Pine.LNX.4.55.0305271000550.2340@bigblue.dev.mcafeelabs.com \
    --to=davidel@xmailserver.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@mdiehl.de \
    --cc=thomas@winischhofer.net \
    /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;
as well as URLs for NNTP newsgroup(s).