Vendor and model ids are available for PCI and USB devices, but I think you
can not assume that all busses have them and you dont gain anything if you
keep them separate (unless you want to interpret the fields of the device id).
In other words I would merge them into a single field.
> * serial number
> * content-cookie
> * topology-cookie
You need another field that contains a identifier for the bus or the scheme
of the device id, because different busses use different formats and you
cannot compare them.
You could also merge content-cookie and serial number because you will always
to interpret them together.
> I suppose these ID fields could also be used by a userspace tool to
> load/unload drivers as necessary.
There is a problem with that idea: you often cannot generate the device id
before the driver is available. Things like the content cookie and the serial
number must be created by the driver, at least in some cases. For example a
PCI ethernet card has a great serial number, its hardware address, but you
can only get it after the driver has been loaded.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/