From: "Robert J.Dunlop" <rjd@xyzzy.clara.co.uk>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: stelian.pop@fr.alcove.com, m.ashley@unsw.edu.au,
jun1m@mars.dti.ne.jp, t-kinjo@tc4.so-net.ne.jp,
tridge@valinux.com, linux-kernel@vger.kernel.org
Subject: Re: PATCH: linux-2.4.7-pre3/drivers/char/sonypi.c would hang some non-Sony notebooks
Date: Sun, 8 Jul 2001 10:42:55 +0100 [thread overview]
Message-ID: <20010708104255.B1441@xyzzy.clara.co.uk> (raw)
In-Reply-To: <20010707180414.A3456@adam.yggdrasil.com>
In-Reply-To: <20010707180414.A3456@adam.yggdrasil.com>; from adam@yggdrasil.com on Sun, Jul 08, 2001 at 09:30:44AM +0100
Hi,
First off, it works for me on my VAIO PCG-Z600NE.
On Sun, Jul 08, 2001 at 09:30:44AM +0100, Adam J. Richter wrote:
> The pci_device_id tables in linux-2.4.7-pre3/drivers/char/sonypi.c
> claims that the driver wants to be loaded on all computers that have
> an that have a PCI device with vendor id PCI_VENDOR_ID_INTEL and
...
> "lspci -v" on my Sony Vaio Picturebook, I see that, while none of the
> PCI devices have Sony's vendor ID, a number of them have Sony's
> vendor ID as their subsystem vendor ID's. So, I have implemented the
Just a niggle however. This still isn't a very good test to finding a
Sony laptop. What'll happen on machines that have any sort of Sony
plugin device ?
How's about we test for a machine that has a host bridge with the Sony
subvendor ID, rather than any device.
WARNING!! untested code.
static int __init sonypi_init_module(void) {
struct pci_dev *dev;
if ((dev = pci_find_class(PCI_CLASS_BRIDGE_HOST << 8, NULL)) == NULL)
return -ENODEV; /* Bizzare. No host bridge */
if (dev->subsystem_vendor != PCI_VENDOR_ID_SONY)
return -ENODEV; /* Not a Sony machine */
return pci_module_init(&sonypi_driver);
}
I guess this'll still pickup Sony desktops.
Perhaps we need a survey of lspci -nv results for sony and non-sony
machines ?
--
Bob Dunlop
rjd@xyzzy.clara.co.uk
www.xyzzy.clara.co.uk
next prev parent reply other threads:[~2001-07-08 9:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-08 1:04 Adam J. Richter
2001-07-08 9:42 ` Robert J.Dunlop [this message]
2001-07-08 10:51 ` arjan
2001-07-09 9:43 ` Stelian Pop
2001-07-09 10:39 ` Alan Cox
2001-07-09 13:31 ` Stelian Pop
2001-07-08 10:26 Adam J. Richter
2001-07-08 16:46 ` Robert J.Dunlop
2001-07-09 7:52 ` Alexander Griesser
2001-07-09 9:35 ` Stelian Pop
2001-07-09 12:54 Adam J. Richter
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=20010708104255.B1441@xyzzy.clara.co.uk \
--to=rjd@xyzzy.clara.co.uk \
--cc=adam@yggdrasil.com \
--cc=jun1m@mars.dti.ne.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=m.ashley@unsw.edu.au \
--cc=stelian.pop@fr.alcove.com \
--cc=t-kinjo@tc4.so-net.ne.jp \
--cc=tridge@valinux.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®