Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 4 Mar 2003 16:25:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 4 Mar 2003 16:25:43 -0500 Received: from pc2-cwma1-4-cust86.swan.cable.ntl.com ([213.105.254.86]:23969 "EHLO irongate.swansea.linux.org.uk") by vger.kernel.org with ESMTP id ; Tue, 4 Mar 2003 16:25:42 -0500 Subject: Re: Displaying/modifying PCI device id tables via sysfs From: Alan Cox To: Kai Germaschewski Cc: Matt Domsch , Greg KH , jgarzik@pobox.com, Linux Kernel Mailing List , mochel@osdl.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1046817563.12231.2.camel@irongate.swansea.linux.org.uk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.1 (1.2.1-4) Date: 04 Mar 2003 22:39:23 +0000 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 879 Lines: 16 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/