> >>I have not checked the audio driver. I guess drivers need to be written
> >>for OBEX & other new goodies defined in the standard.
> >>
> >>
> >Presumably you can do at least the OBEX stuff in userspace. I think that there
> >is an project working on this (OpenOBEX?).
> >
> You are correct, the OBEX stuff can be done in userspace. However a USB
> driver and interface will still be needed to provide access to the pipe.
Not necessarily. You could use libusb on top of usb[dev]fs.
> According to the usb-wmcd spec, the OBEX interface is the same as the
> ACM but with a few simplifications. It might be possible to adapt the
> ACM driver so it can also handle the OBEX case & present an interface
> eg. ttyOBEXn. In this scenario, I guess new major/minor device numbers
> would be needed? Or maybe use the same major device number but allocate
> ranges of minors for ttyACM & ttyOBEX.
>
> Or any other ideas?
A cursory look into OpenOBEX leads me to the conclusion that it supports
OBEX over IP, IrDA and Bluetooth. The core infrastructure assumes that
OBEX packets are sent over sockets.
So you either do some surgery to OpenOBEX or you write a kernel driver
that exports the OBEX stuff as a network driver, not a tty.
Regards
Oliver
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
