On Fri, May 22, 2009 at 10:06, Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx> wrote:
> Would it work if I implement the discussed aggregate fw_device attribute
> (i.e. the concatenation of significant attributes of all children) and send
> an KOBJ_CHANGE event when units were recreated? Do change events trigger
> the necessary actions to update ownership and ACL?
Yes, that sounds fine.
> One other thing which I forgot yesterday:
>
> We actually already have an attribute which exists when an fw_device
> KOBJ_ADD event happens and includes information about all children. However,
> it is a binary blob (config_rom, a dump of the device description from which
> also ATTR{specifier_id} and ATTR{version} are derived; format is defined in
> IEEE 1212, contents defined in various higher level protocol specs) --- and
> since the firewire-core has a config ROM parser anyway, we do not really
> want to duplicate this parser in userspace for basic purposes like setting
> device file ownership/ ACLs/ symlinks and the likes.
That sounds like the USB "descriptors" file. Yes, it would be nice if
we can have that in an easily readable format in syfs without the need
for a parser.
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
