From: Jean Delvare <khali@linux-fr.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: greg@kroah.com, linux-pci@atrey.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org,
"Mark M. Hoffman" <mhoffman@lightlink.com>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [-mm patch] drivers/pci/quirks.c: cleanup
Date: Sun, 7 Jan 2007 12:30:13 +0100 [thread overview]
Message-ID: <20070107123013.097c1f23.khali@linux-fr.org> (raw)
In-Reply-To: <20070105232913.GU20714@stusta.de>
Hi Adrian,
On Sat, 6 Jan 2007 00:29:13 +0100, Adrian Bunk wrote:
> While looking at the code, I also noted the following:
>
> quirk_sis_96x_compatible() is pretty useless since all it does is to set
> a static variable that is only used in a printk().
>
> quirk_sis_96x_compatible() was added with:
>
>
> 2003/05/13 13:48:50-07:00 mhoffman
> [PATCH] i2c: Add SiS96x I2C/SMBus driver
>
> This patch adds support for the SMBus of SiS96x south
> bridges. It is based on i2c-sis645.c from the lm sensors
> project, which never made it into an official kernel and
> was anyway mis-named.
>
> This driver works on my SiS 645/961 board vs w83781d.
>
>
> It's usage in
>
>
> static void __init quirk_sis_503_smbus(struct pci_dev *dev)
> {
> if (sis_96x_compatible)
> quirk_sis_96x_smbus(dev);
> }
>
>
> Was removed in
>
>
> Author: torvalds <torvalds>
> Date: Thu Oct 30 19:03:38 2003 +0000
>
> Stop SIS 96x chips from lying about themselves.
>
> Some machines with the SIS 96x southbridge have it set up
> to claim it is a SIS 503 chip. That breaks irq routing logic
> among other things. Fix it properly by making everybody aware
> of the duplicity.
>
>
> Was this intentional (and quirk_sis_96x_compatible() should be removed),
> or is this a bug that should be fixed?
I noticed this too in April 2006, see:
http://lists.lm-sensors.org/pipermail/lm-sensors/2006-April/016016.html
Quoting myself back then:
"The whole sis_96x_compatible stuff looks superfluous now. It was used
before 2.6.0-test10, but we could certainly get rid of it now."
I do not think there is a bug here, or someone would have complained by
now. Note though that I do not have a SiS-based motherboard to test on.
Mark may be able to help with testing.
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2007-01-07 11:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 4:13 [-mm patch] drivers/pci/quirks.c: cleanup Adrian Bunk
2006-12-19 8:52 ` Matthew Wilcox
2006-12-19 9:57 ` Adrian Bunk
2007-01-05 8:52 ` Jean Delvare
2007-01-05 23:29 ` Adrian Bunk
2007-01-07 11:30 ` Jean Delvare [this message]
2007-01-07 15:40 ` Mark M. Hoffman
2007-01-14 13:46 ` [-mm patch] remove quirk_sis_96x_compatible() Adrian Bunk
2007-01-14 15:22 ` Mark M. Hoffman
2007-01-07 15:44 ` [-mm patch] drivers/pci/quirks.c: cleanup Mark M. Hoffman
2007-01-08 11:10 ` Jean Delvare
2007-01-09 3:02 ` Mark M. Hoffman
2007-01-09 3:11 ` [PATCH 2.6.20-rc4] i2c/pci: fix sis96x smbus quirk once and for all Mark M. Hoffman
2007-01-09 13:17 ` [-mm patch] drivers/pci/quirks.c: cleanup Jean Delvare
2007-01-10 3:58 ` Mark M. Hoffman
2007-01-10 9:35 ` Jean Delvare
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=20070107123013.097c1f23.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=bunk@stusta.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=mhoffman@lightlink.com \
--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