From: =?unknown-8bit?q?Bj=C3=B8rn?= Mork <bjorn@mork.no>
To: ofono@ofono.org
Subject: Re: [PATCH 7/8] sierra: Support CDMA modems
Date: Wed, 06 Mar 2013 10:43:27 +0100 [thread overview]
Message-ID: <87boawoocg.fsf@nemi.mork.no> (raw)
In-Reply-To: <20130305221538.GL11149@alittletooquiet.net>
[-- Attachment #1: Type: text/plain, Size: 2230 bytes --]
Forest Bond <forest@alittletooquiet.net> writes:
> On Tue, Mar 05, 2013 at 10:45:15PM +0100, Bjørn Mork wrote:
>> Forest Bond <forest@alittletooquiet.net> writes:
>>
>> > Anyway, I notice that one of the ports appears to be QCDM. It appears that QCDM
>> > support is partially implemented in oFono? But I don't know QCDM at all. Can
>> > we use it to do netreg?
>>
>> What kind of Sierra device is this? And what vid is it using?
>
> Well, I'm really after a few devices:
>
> * Sierra Wireless USB 598 (Sprint/Telus branded)
> * Sierra Wireless MC5728V (Feeney Wireless Skyus 3G)
>
> The 598 has VID 0025. I think the Skyus 3G does, too (at least in some
> configurations), but I don't have one in front of me to check. In any case it
> is a very similar part to the 598. All I have to test with right now is a Telus
> demo device (with no service :/) as my other parts were returned to their
> respective owners some time ago.
>
>> I ask because I have only seen QCDM ports active on Sierra devices
>> in firmware modes with rmnet/qmi_wwan interfaces. In which case you
>> should have QMI support.
>
> I couldn't get qmicli to do anything with any of the ports, but test-qcdm (from
> the ModemManager source tree) seems to like talking to the last port.
>
>> > If not, I could probably implement (partial) CnS support at some point. I'm
>> > just not sure I will have time to do it right away.
>>
>> And those modes do not have any CnS ports.
>
> These parts definitely have CnS ports. We've used CnS for an unrelated project
> with all of these devices.
>
> In all, I think the ports are as follows:
>
> 1. AT commands
> 2. CnS
> 3. NMEA 0183 (GPS)
> 4. QCDM
>
> WRT #3, I remember seeing what looked like NMEA a while back using a Sprint
> part. WRT #4 I've only ever tested the Telus part.
>
> What do you think?
Thanks. I think you are right. Learning something new every day.
Until know I thought they had a clear split between "Qualcomm" and
"Sierra" protocols, but these devices obviously do a mix. Is the NMEA
port Sierra style (enabled using the SetNmea control message) or
Qualcomm style (enabled by writing "$GPS_START" to the port)?
Bjørn
next prev parent reply other threads:[~2013-03-06 9:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 19:31 [PATCH 0/8] Sierra Wireless CDMA modem support Forest Bond
2012-12-28 19:34 ` [PATCH 1/8] sierramodem: Add skeleton for Sierra Wireless modem driver Forest Bond
2012-12-28 19:34 ` [PATCH 2/8] sierramodem: Add skeleton cdma netreg driver Forest Bond
2012-12-31 2:11 ` Denis Kenzior
2012-12-28 19:35 ` [PATCH 3/8] sierramodem: Add ERI parsing functions Forest Bond
2012-12-31 2:19 ` Denis Kenzior
2012-12-28 19:35 ` [PATCH 4/8] sierramodem: Report network registration status Forest Bond
2012-12-31 2:26 ` Denis Kenzior
2012-12-28 19:35 ` [PATCH 5/8] sierra: Create GPRS context in post_sim function Forest Bond
2012-12-31 2:39 ` Denis Kenzior
2012-12-28 19:36 ` [PATCH 6/8] sierra: Initialize GSM error reporting separately Forest Bond
2012-12-31 2:40 ` Denis Kenzior
2012-12-28 19:36 ` [PATCH 7/8] sierra: Support CDMA modems Forest Bond
2012-12-31 2:34 ` Denis Kenzior
2013-03-04 16:48 ` Forest Bond
2013-03-04 23:03 ` Denis Kenzior
2013-03-05 19:36 ` Forest Bond
2013-03-05 20:52 ` Denis Kenzior
2013-03-05 21:45 ` =?unknown-8bit?q?Bj=C3=B8rn?= Mork
2013-03-05 22:15 ` Forest Bond
2013-03-06 9:43 ` =?unknown-8bit?q?Bj=C3=B8rn?= Mork [this message]
2013-03-06 13:36 ` Forest Bond
2012-12-28 19:36 ` [PATCH 8/8] udevng: Support single-interface sierra devices Forest Bond
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=87boawoocg.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=ofono@ofono.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