At 11:57 AM 10/23/2002 +0200, Oliver Neukum wrote:
It is easier to teach applications to use my ioctl. However that doesn't much matter because they won't learn it.Why would teaching applications your ioctl be harder than teaching them your customs procfs or driverfs file? From a coding point of view an ioctl on a file you do a lot of ioctls on anyway is far simpler than deducing a path to another file, opening it and writing an ASCII value into it. Which is racy by the way, unless you revalidate the file.
The proc entry is not meant for apps to use, it's meant for users. Since the apps won't adjust the shutter speed, I've given users a simple mechanism to do so.
Users will react much better to a special feature that uses a tool they already have and are familiar with (echo) than any custom app I can give them. Especially since this allows them to adjust shutter speed while looking at the image. A custom ioctl app would not.You are offering a nonstandard feature. It needs special support in any case. Those who can rig their own shell scripts can compile a simple C programm, too.
Leaving out the shutter speed will make the driver unusable in all but a small set of situations.While that is true, V4L2 is not here yet and won't come into 2.4. So I suggest that you leave out the shutter speed setting until it is clear whether V4L2 is in 2.6/3.0.
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
