From: Stephan von Krawczynski <skraw@ithnet.com>
To: Justin Cormack <justin@street-vision.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: APIC with SIS
Date: Thu, 9 Jan 2003 17:59:15 +0100 [thread overview]
Message-ID: <20030109175915.1c9dd425.skraw@ithnet.com> (raw)
In-Reply-To: <1042130749.25527.5.camel@lotte>
On 09 Jan 2003 16:45:44 +0000
Justin Cormack <justin@street-vision.com> wrote:
> > > Current ACPI is on sourceforge. The SIS APIC workaround bits haven't yet
> > > been backported to 2.4, so you either do the backport or wait 8)
> >
> > Ok, so I took ACPI from sf and voila: it works now! I took the patch for
> > 2.4.20 and it does fine. Are there chances to include this in the
> > mainstream? Without my SIS-based motherboards do not work at all with
> > shared interrupts (which you actually cannot prevent due to lacking bios
> > support for pci-irq mapping).
> >
> > BTW: I tried 2.4.21-pre[1-3] and none did work, of course.
>
> You may be able to disable the APIC in the BIOS. One of my new Sis
> boards gave this option and it is an ok workaround for now at least.
Unfortunately it is not. Shared interrupts do _not_ work with APIC disabled.
They _only_ work with APIC enabled in BIOS _and_ APIC support patch from sf.
I tested every other combination and none did work.
--
Regards,
Stephan
next prev parent reply other threads:[~2003-01-09 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 16:08 APIC with SIS Stephan von Krawczynski
2002-12-30 17:02 ` Alan Cox
2002-12-30 16:33 ` Stephan von Krawczynski
2002-12-30 17:18 ` Alan Cox
2003-01-09 16:09 ` Stephan von Krawczynski
[not found] ` <1042130749.25527.5.camel@lotte>
2003-01-09 16:59 ` Stephan von Krawczynski [this message]
[not found] ` <1042131701.25527.8.camel@lotte>
2003-01-09 17:42 ` Stephan von Krawczynski
2003-01-09 18:44 ` 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=20030109175915.1c9dd425.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=justin@street-vision.com \
--cc=linux-kernel@vger.kernel.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 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.