From: Alan Cox <alan@redhat.com>
To: szepe@pinerecords.com (Tomas Szepe)
Cc: alan@redhat.com (Alan Cox), linux-kernel@vger.kernel.org
Subject: PATCH: fix sis_apic fix (was Re: Linux 2.5.49-ac1)
Date: Tue, 26 Nov 2002 07:20:11 -0500 (EST) [thread overview]
Message-ID: <200211261220.gAQCKBt07952@devserv.devel.redhat.com> (raw)
In-Reply-To: <20021126115614.GK29196@louise.pinerecords.com> from "Tomas Szepe" at Nov 26, 2002 12:56:14 PM
> > Your tree is corrupt, looks like flipped bits (its gone from 'a' to ^A)
>
> Naah, that's just me pasting text into joe and forgetting to fix it up
> afterwards. :)
Seems I screwed up that bit of the merge and pulled in the prototype not
final sis_apic bits. Apply this on top
--- include/asm-i386/io_apic.h~ 2002-11-26 12:39:26.000000000 +0000
+++ include/asm-i386/io_apic.h 2002-11-26 12:42:17.000000000 +0000
@@ -125,7 +125,8 @@
*/
static inline void io_apic_modify(unsigned int apic, unsigned int
reg, unsigned int value)
{
- if(apic_sis_bug)
+ extern int sis_apic_bug;
+ if(sis_apic_bug)
*IO_APIC_BASE(apic) = reg;
*(IO_APIC_BASE(apic)+4) = value;
}
--- drivers/pci/quirks.c~ 2002-11-26 12:43:57.000000000 +0000
+++ drivers/pci/quirks.c 2002-11-26 12:43:57.000000000 +0000
@@ -350,8 +350,9 @@
static void __init quirk_ioapic_rmw(struct pci_dev *dev)
{
+ extern int sis_apic_bug;
if(dev->devfn == 0 && dev->bus->number == 0)
- apic_sys_bug = 1;
+ sis_apic_bug = 1;
}
next prev parent reply other threads:[~2002-11-26 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 23:52 Linux 2.5.49-ac1 Alan Cox
2002-11-26 0:19 ` Russell King
2002-11-26 3:55 ` Tomas Szepe
2002-11-26 11:54 ` Alan Cox
2002-11-26 11:56 ` Tomas Szepe
2002-11-26 12:20 ` Alan Cox [this message]
2002-11-26 5:01 ` Linux 2.5.49-ac1 - mouse and keyboard issues Murray J. Root
2002-11-26 13:59 ` Linux 2.5.49-ac1 Adrian Bunk
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=200211261220.gAQCKBt07952@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.com \
/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
all inboxes | Powered by JetHome®