> > A model of one simple file to be opened per device _is_ simpler
> > than a number of files to control various settings.
> > Plus, how do you control permissions on that thing ?
>
> The driver controls the initial permissions. I think it will be up to
> userspace to control them after that.
You'll let a single device's settings have differing permissions
and ownership?
That is ... astonishing and complex.
(I am running out of fitting adjectives. I should look for my dictionary.)
> > Next I'd like to see a lock for attributes and making implementing
> > open mandatory. After that the interfaces should be basically
> > useable, but still I don't think it's for general consumption, ever.
>
> Why should open be mandatory? What do you want to do in open()?
Proper reference counting and locking. A single read or write interface
is terrible with respect to locking against disconnect. There's a reason
you have to open a file before you read it. Without that the greatest
majority of drivers will get using driverfs wrong.
Regards
Oliver
-------------------------------------------------------
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
