From: "Udo A. Steinberg" <reality@delusion.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.6-ac4
Date: Mon, 16 Jul 2001 04:13:33 +0200 [thread overview]
Message-ID: <3B524DCD.3C6D6187@delusion.de> (raw)
In-Reply-To: <20010716004933.A18030@lightning.swansea.linux.org.uk> <3B524B36.A9F926CC@delusion.de>
"Udo A. Steinberg" wrote:
>
> Alan Cox wrote:
>
> > 2.4.6-ac4
> > o Update VIA southbridge bug fix to VIA provided (me)
> > workaround.
> > | Except we apply it even when no sblive is
> > | present
>
>
> I have a VIA 686a chipset and the workaround is being enabled nonetheless.
> I guess that's not quite correct. ac3 did the right thing, ac4 doesn't.
I kinda see why (relevant part of -ac4 patch):
The underlined piece won't ever execute, and the range doesn't reflect the
comment above.
+ p=pci_find_device(PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C686, NULL);
+ if(p!=NULL)
+ {
+ pci_read_config_byte(p, PCI_CLASS_REVISION, &rev);
+ /* 0x40 - 0x4f == 686B, 0x10 - 0x2f == 686A; thanks Dan Hollis
+ /* Check for buggy part revisions */
+ if (rev < 0x40 && rev > 0x42)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+ return;
+ }
+ else
+ {
+ p = pci_find_device(PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_8231, NULL);
+ if(p==NULL) /* No problem parts */
+ return;
+ pci_read_config_byte(p, PCI_CLASS_REVISION, &rev);
+ /* Check for buggy part revisions */
+ if (rev < 0x10 && rev > 0x12)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+ return;
+ }
next prev parent reply other threads:[~2001-07-16 2:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-15 23:49 Linux 2.4.6-ac4 Alan Cox
2001-07-16 0:20 ` David Ford
2001-07-16 0:49 ` David S. Miller
2001-07-16 2:02 ` Udo A. Steinberg
2001-07-16 2:13 ` Udo A. Steinberg [this message]
2001-07-16 11:16 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-07-16 11:58 Mikael Pettersson
2001-07-16 12:24 ` Xavier Bestel
2001-07-16 16:18 ` Xavier Bestel
2001-07-16 12:45 ` 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=3B524DCD.3C6D6187@delusion.de \
--to=reality@delusion.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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.