Alan,
Alan Stern <[EMAIL PROTECTED]> wrote on 06/28/2006 07:09:12 AM:
> On Tue, 27 Jun 2006, Martin Rubli wrote:
>
> > As an example, the tree structure could look something like this
(slightly
> > simplified):
> >
> > /sys/class/video4linux/video0/
> > |
> > |--extension_units/
> > |
> > |--{00000000-0000-0000-000000000001}/
> > |--{12345678-1234-1234-abcdefabcdef}/
>
> If you decide to go this route, _please_ don't use those Windows-style
> GUID thingies as filenames. A filename should not include any shell
> meta-characters. Omitting the '{' and '}' would help; replacing the
> meaningless numbers with meaningful English words would help even more.
I can see your point and leaving out the brackets is certainly a good idea.
But there's no reasonable way to have meaningful words instead of GUIDs.
The reason for the whole extension interface is to provide access to
extension units that the UVC driver itself doesn't know about.
Such extension units are defined by device manufacturers and don't even
need to have proper names. And even if we were to allow applications to
register with an English name when they enable raw mode, I doubt that
UNIT_VENDORXYZ_EX3 or extunit_04 would be very useful to anyone. On the
contrary, apps will look for units in the 'extensions' by their GUID for
lack of a name specification.
That being said, there will be reasonable names (and/or symlinks) wherever
possible, so that you could access .../controls/brightness/cur instead of
.../controls/ctrl001/cur for example.
Cheers,
Martin
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
