© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Scott James Remnant wrote on 2008-04-24:
> ...
The statements about IEEE 1394 and about what the linux1394 stack does are... somewhat inaccurate. I won't comment further.
> Failing that, an interim solution would be if we could at least have some information
> from the kernel about _WHAT_ is connected on the firewire port when they are connected
> and disconnected, we don't even get that right now!
Wrong, you do get that. There are kobjects and uevents for each unit on each node, including the AV/C unit of a camcorder for example.
> If we had insert notification, with vendor and device ids inside the uevent, we could at
> least enable access on a "per known device" basis -- I'd still be nervous about raw1394
> though, since anyone can fake a device id pair.
Indeed; it doesn't make sense to use these uevents to change /dev/raw1394's ownership and permissions or ACL because the basic problems of
1.) ohci1394 having physical DMA enabled,
2.) /dev/raw1394 being used for all devices
don't go away. (Both of these issues are addressed by the new firewire stack.)