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 15:29:08 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.55.0305271519210.1362@bigblue.dev.mcafeelabs.com> (raw)
In-Reply-To: <3ED3CDA9.5090605@winischhofer.net>

On Tue, 27 May 2003, Thomas Winischhofer wrote:

> I patched the kernels of my 3 650 variants today (using a simpler
> variant than submitted by Davide), and it works well. They are running a
> webcam permanently, one is copying from and to a USB floppy in a loop,
> and I am using a USB mouse on all of them.
>
> The issue is that the 0x6x register hack seems to be required for _all_
> 96x variants. These come with the 740 as well as all 650 versions, and
> probably many of the older chips (645, etc), too.
>
> Unfortunately, I know of no way how to find out about these south
> bridges. They have the same PCI ID like the IRQ controller and ISA
> bridge of the 620, 530, 630 and the old 5595... and partly even the same
> revision number. Typical SiS stuff, lines up exactly with their graphics
> hardware...
>
> Vojtech recommended doing it like the IDE drivers, but - as I said to
> him - it feels a bit inappropriate to poke around in the IDE config
> space for IRQ reasons... But anyone interested should take a look into
> the newest 5513 ide driver (in the bk tree).

It does not look right to me either to poke the IDE controller. Another
solution might be to parse the routing table and gather informations from
there. Example, the findings of 0x61,...,0x63 will tell us that we're
dealing with newer chipsets that uses those for values for the 3 OHCI and
the EHCI. The revision ID trick seems not effective, at least looking at
your machine with rev-id 0 that has 0x61..63. Martin, was the revision id
0, that you suggested to be handled with the old router, minded ?



- Davide


  parent reply	other threads:[~2003-05-27 22:16 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
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 [this message]
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.0305271519210.1362@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).