On Wed, Jan 19, 2005 at 12:38:31PM -0600, Brian King wrote:
Greg KH wrote:
On Wed, Jan 19, 2005 at 06:13:57PM +0100, Christoph Hellwig wrote:
I think the hardware_version, firmware_version, rom_version and driver_version don't belong into the FC transport class, there's nothign specific to FC or even SCSI specific in them.
Then put them in the individual driver (not the driver_version one though, that belongs as a MODULE_VERSION() paramater).
If you want these attributes talk to Greg about fiding a place in the common driver model code for them.
No, they don't belong there either, sorry :)
How about at an attribute on the pci object?
It is a pci specific attribute? If so, I'll add it to the pci core. Otherwise you are free to add it yourself to the pci device in your pci driver to that location.
I won't argue that it is a pci specific attribute, since there are plenty of devices out there that have firmware that are not pci devices, such as scsi disks. This just seems like too common of an attribute to have each driver doing their own thing. The options as I see them are:
1. scsi_host class 2. pci core 3. driver unique
-- Brian King eServer Storage I/O IBM Linux Technology Center - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
