Marcel Holtmann <marcel@xxxxxxxxxxxx> writes: > I would be against this. You get USB_CDC_NOTIFY_NETWORK_CONNECTION, Not sure I do. Will have to verify that. But I guess you're right. > but > I prefer not to have ifconfig up execute any QMI commands. Can we please > run all of that in userspace. > > Same happens for devices like MBM already. You need to drive the AT > channel since otherwise you are not getting any connections. And the > LOWER_UP just signals the link. > > We are not putting any AT commands into the kernel either, so I rather > have QMI staying out of it. Especially since you will run into some > resource allocation issues with QMI and its services. That makes this > whole think even more complicated. At that point we need to put QMI as a > socket family in the kernel (similar to Phonet or CAIF). If you don't > want that, then lets leave all QMI out of the kernel. Damn, you are convincing :-) OK, this makes the job next to nothing. Rethinking this, I realized that the real reason I started putting all the QMI stuff in the driver was that I didn't see how I could export any sane interface to userspace. Now that that is sorted out, then there is no real reason to keep QMI in the kernel. Yes I know Dan and you know what you are doing and that I should just have shut up and listened. But I came to the correct conclusion in the end at least :-) Thanks for not giving up on me, both of you. Bjørn -- 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
