From: Davide Libenzi <davidel@xmailserver.org>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: SiS ISA bridge IRQ routing on 2.6 ...
Date: Wed, 29 Oct 2003 11:27:33 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.56.0310291124230.973@bigblue.dev.mdolabs.com> (raw)
In-Reply-To: <3F9F4841.2040904@cyberone.com.au>
On Wed, 29 Oct 2003, Nick Piggin wrote:
> >Linus, I saw that Marcelo merged Alan bits to fix the IRQ routing with the
> >newest SiS ISA bridges. To make it really short the ISA bridge inside the
> >SiS 85C503/5513 issue IRQ routing requests on 0x60, 0x61, 0x62 and 0x63
> >for the USB hosts and the current code does not handle them correctly.
> >2.6-test9 does not have those bits and the USB subsystem won't work w/out
> >that. Did Alan ever posted the patch for 2.6? If yes, did you simply miss
> >it or you have a particular reason to not merge it?
> >I really would like to remove the SiS IRQ patch from my to-apply-2.6
> >folder :)
> >
>
> Alan thought I should put SiS IRQ routing on the must-fix list.
> Doesn't mean it has to go in before 2.6.0, but if its common
> hardware and its in 2.4 without problems its probably a good idea.
Alan did not like my approach, so I'll let him post to Linus his work. If
he doesn't I'll post mine. The solution is trivial though and it works for
me as long as for many users that google'd about SiS+USB and asked me the
patch.
- Davide
next prev parent reply other threads:[~2003-10-29 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 3:45 SiS ISA bridge IRQ routing on 2.6 Davide Libenzi
2003-10-29 4:55 ` Nick Piggin
2003-10-29 19:27 ` Davide Libenzi [this message]
2003-10-29 23:11 ` Alan Cox
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.56.0310291124230.973@bigblue.dev.mdolabs.com \
--to=davidel@xmailserver.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
--cc=torvalds@osdl.org \
/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).