On Wed, Oct 06, 2010 at 08:50:18AM +0300, Arnaud Mandy wrote: > ext Greg KH wrote: > >On Tue, Oct 05, 2010 at 05:33:07PM +0300, Arnaud Mandy wrote: > >>Introduces a new f_mtp.c function driver that allows > >>implementation of Media Transfer Protocol stack via userspace. > >>It uses a dedicated character driver u_mtp to implement the user space > >>file i/o interface. > > > >Didn't upstream reject this type of interface and logic? > > I know that upstream rejected the patches. > The idea was that upstream do not want another character device > driver else than u_serial. > So we decided that we can integrate the previous u_char as a > dedicated mtp charater device driver. > So we do not have 2 different character device driver in for > gadgets, as recommended by upstream, if I remember right. I thought this could still be done in userspace using gadgetfs, like the PTP gadget code works. Or is there something keeping that from being possible? > > Why are you > >trying to get this into meego instead? > > > > I wasn't trying to snick this anywhere else than through linux-usb. > I just wanted to get some review from some people from in meego > which are interested in that. My appologies, I originally thought you only sent this to the meego-kernel list, and I've been constantly harping on people to send stuff there upstream, and you did send it to linux-usb at the same time. But it still looked like you expected the meego project to take these patches, which you should have explained. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
