On 11/23/07, Chris Frey <[EMAIL PROTECTED]> wrote:
> I know the configuration exists, since the same code works when
> the usb_storage module is not loaded.
>
> I've always assumed that this conflict is a fundamental issue when
> two programs try to access the same USB device (even if one is a kernel
> module).  If I'm wrong, I'd love for someone to show me how to do
> it right.

According to LDD3 chapter 13 (http://lwn.net/Kernel/LDD3/), multiple
configuration devices are rare, and interfaces can be claimed by
separate drivers (i.e. I have a Logitech webcam with a mic in it, and
an ALSA driver handles the mic while the quickcam module handles the
video).  This implies that you should see if the default configuration
(or some other one) supports both mass storage and syncing interfaces,
and then code Barry to co-exist with the mass storage driver by only
claiming the interface(s) you need.

I might not be understanding the situation correctly, I haven't looked
at any USB related code yet and I'm only somewhat familiar with these
concepts so far, so I apologize if the above paragraph is useless.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Reply via email to