Hi Alex, > > what is the reason to have an extra kernel driver for this and not use > > the USB library and send me a patch for another transport layer for > > OpenOBEX? > > Well, it just didn't occur to me. :) Plus, the WMC specification lists > plenty of other interfaces, which either are in the kernel already (ACM > modems, ethernet) or will be there sooner or later (voice, device > management, firmware upgrades) when the gadgets appear on the market. So > keeping the obex interface out of kernel would be then inconsistent. By > the way, they're all pretty similar to obex, so with a little tweaking the > driver could support them all.
I don't buy your point. From what I know is that OBEX only needs bulk transfers and these can be used very easy through the USB library. The big advantage using the USB library is that you also support OBEX over USB for FreeBSD and MacOS X at the same time with the same code. Think about that, because this is not about inconsistence. Use the interface that fits the best and from my view this is not a kernel driver. Regards Marcel ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
