On Mon, May 13, 2002, David Brownell <[EMAIL PROTECTED]> wrote:
> > > We _have_ that protection because only device drivers that
> > > claim an interface, perhaps via probe(), are allowed to use
> > > that device.  To repeat:  the protection doesn't need to be
> > > explicit in the driver programming interfaces.
> > > 
> > > On the other hand, usbdevfs doesn't necessarily bother to
> > > claim interfaces when it makes control calls.  Since that's
> > > internal to usbcore, I don't think that undermines my point.
> > > It's already got its fingers in lots of places "real drivers"
> > > aren't allowed to go.
> > 
> > Actually, it does undermine your point. To make it work we need
> > reference counting.
> 
> Not in the _device driver_ programming interface though, just
> internal to the usbcore code (which includes usbfs).
> 
> Yes, I said that already.

Gotcha.

While I don't think we should make device driver programming more
complicated that it needs to be, especially for the common case, I
don't see why we should let device drivers access to reference
counting if they want to.

JE


_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to