On Sun, Mar 27, 2005 at 04:27:24PM -0500, Adam Belay wrote: > > extern int device_create_file(struct device *device, struct device_attribute > > * entry); > > and delete them (e.g. in ->remove) using > > extern void device_remove_file(struct device * dev, struct device_attribute > > * attr); > > > > and there's also > > > > extern int driver_create_file(struct device_driver *, struct > > driver_attribute *); > > extern void driver_remove_file(struct device_driver *, struct > > driver_attribute *); > > > > > > Dominik > > Yes, I'm aware of these functions but they pollute the bus level > namespace. I'm interested in reactions to this alternative approach. I > wanted to explore the possibility of making a device driver instance a > separate component with its own individual state and relationships. To be honest, I don't consider this to be a pollution of the "bus" namespace, but I fear that having two different places for somewhat similar, or even equal, data adds unneeded complexity to the driver model. In what specific instances has the current design limited or obstructed your intentions? Dominik
