David Brownell wrote:
> Requiring write access isn't sufficient, in the case of
> multiple writers.
You can either trust a piece of driver software (and give
it write permission), or not, but still allow it to
find out what devices are on the bus, by giving it
only read permission.
A trusted driver is assumed to know about peculiarities
of the device it drives.
> APIs for that), I do expect to be able to write user mode
> code that works with power management policies, and so
> must be able to talk to hubs ... without clobbering what
> the kernel hub driver may be doing.
In that case it will become necessary to add ioctl's
that talk to the hub driver instead of directly accessing
the hub...
> Setting permissions, OK -- but my observation is that
> the current "read" permission doesn't match what "read"
> permission normally matches.
Depends on how you look at it. On the wire every transaction
is bidirectional, even though user data may be flowing
only in one direction.
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
