From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Matt Domsch <Matt_Domsch@dell.com>, Greg KH <greg@kroah.com>,
jgarzik@pobox.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
mochel@osdl.org
Subject: Re: Displaying/modifying PCI device id tables via sysfs
Date: 04 Mar 2003 22:39:23 +0000 [thread overview]
Message-ID: <1046817563.12231.2.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0303041414270.23375-100000@chaos.physics.uiowa.edu>
On Tue, 2003-03-04 at 20:22, Kai Germaschewski wrote:
> It shares one caveat with the approach above, i.e. struct pci_device_id
> has a field called "unsigned long driver_data", and as such is really hard
> to fill from userspace. I think in the common case it's not used and can
> be just set to zero, but if the driver e.g. expects it to point to a
> driver-private structure describing the device, you lose.
Lots of drivers will simply do the wrong thing if you do that. Version
equivalence is rather more important. Of course if you know what equivalence
you are claiming you can look it up in the table to get the pci_device_id
next prev parent reply other threads:[~2003-03-04 21:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 17:57 Displaying/modifying PCI device id tables via sysfs Matt Domsch
2003-03-03 18:25 ` Greg KH
2003-03-03 20:02 ` Alan Cox
2003-03-03 20:56 ` Matt Domsch
2003-03-04 0:31 ` Greg KH
2003-03-04 4:56 ` Matt Domsch
2003-03-04 14:10 ` Patrick Mochel
2003-03-04 20:22 ` Kai Germaschewski
2003-03-04 22:39 ` Alan Cox [this message]
2003-03-04 22:57 ` Jeff Garzik
2003-03-04 0:34 ` Jeff Garzik
2003-05-23 0:53 ` Rusty Russell
2003-05-24 0:37 ` Greg KH
2003-05-25 4:57 ` Rusty Russell
2003-05-23 2:27 Matt_Domsch
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=1046817563.12231.2.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Matt_Domsch@dell.com \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@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;
as well as URLs for NNTP newsgroup(s).