From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: linux-wireless@vger.kernel.org, netdev@xanatos,
linux-usb@vger.kernel.org
Cc: "Ismail, Rahman" <abdul.r.ismail@intel.com>,
"Wallick, Stephanie S" <stephanie.s.wallick@intel.com>
Subject: Mobile Broadband Interface Model (MBIM) support?
Date: Fri, 24 May 2013 10:09:15 -0700 [thread overview]
Message-ID: <20130524170915.GA15788@xanatos> (raw)
Do we have support for the new extensions for USB communication devices
that use the Mobile Broadband Interface Model (MBIM) spec?
http://www.usb.org/developers/devclass_docs/MBIM10Errata1.zip
The spec was released pretty recently, which is why I'm asking on the
mailing lists, rather than digging around the kernel tree for a driver.
Sarah Sharp
next reply other threads:[~2013-05-24 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 17:09 Sarah Sharp [this message]
2013-05-24 18:10 ` Mobile Broadband Interface Model (MBIM) support? Sarah Sharp
2013-05-25 0:11 ` Dan Williams
2013-05-24 18:14 ` Bjørn Mork
2013-05-24 19:08 ` Bjørn Mork
2013-05-24 19:31 ` Bjørn Mork
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=20130524170915.GA15788@xanatos \
--to=sarah.a.sharp@linux.intel.com \
--cc=abdul.r.ismail@intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@xanatos \
--cc=stephanie.s.wallick@intel.com \
/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).