From: Dave Jones <davej@redhat.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org,
Fedora Kernel Team <kernel-team@fedoraproject.org>,
Ben Hutchings <ben@decadent.org.uk>
Subject: Re: net: cdc_ncm, cdc_mbim: allow user to prefer NCM for backwards compatibility
Date: Thu, 16 May 2013 15:17:01 -0400 [thread overview]
Message-ID: <20130516191701.GC5805@redhat.com> (raw)
In-Reply-To: <87mwrueo9k.fsf@nemi.mork.no>
On Thu, May 16, 2013 at 09:08:23PM +0200, Bjørn Mork wrote:
> Yes, this is a very unfortunate side effect of the userspace/kernel
> split of the MBIM driver combined with the NCM/MBIM "backwards
> compatibility" setting. Which in itself is a bad idea, IMHO.
>
> I recommend all distros do the same as Debian: Set NCM as default until
> a userspace application with MBIM support is ready and packaged in the
> distro:
> http://anonscm.debian.org/viewvc/kernel/dists/trunk/linux/debian/patches/debian/cdc_ncm-cdc_mbim-use-ncm-by-default.patch
Thanks for the pointer. We'll pick that up for the Fedora 3.9 kernels.
Ben, does debian have a commits mailing list for kernel changes ?
> FWIW, I wish we would have thought about this issue before v3.8 was
> released. Then we could have made that patch the mainline default,
> without that being a userspace API change. But we didn't.
>
> The good news is that Aleksander has done some nice work on the MBIM
> support in ModemManager, so there is a good chance that the next release
> will make this problem go away.
good news indeed!
thanks.
Dave
next prev parent reply other threads:[~2013-05-16 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 18:25 net: cdc_ncm, cdc_mbim: allow user to prefer NCM for backwards compatibility Dave Jones
2013-05-16 19:08 ` Bjørn Mork
2013-05-16 19:17 ` Dave Jones [this message]
2013-05-16 19:23 ` Bjørn Mork
2013-05-16 19:35 ` Dave Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130516191701.GC5805@redhat.com \
--to=davej@redhat.com \
--cc=ben@decadent.org.uk \
--cc=bjorn@mork.no \
--cc=kernel-team@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).