From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH v4 4/4] udev: add Telit UC864-G and update udev rules
Date: Mon, 13 Jun 2011 04:28:43 -0500 [thread overview]
Message-ID: <4DF5D84B.4030607@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1106140956070.30119@entw48>
[-- Attachment #1: Type: text/plain, Size: 2103 bytes --]
Hi Bernhard,
>> In theory you can use $GPSNMUN to enable GPS reporting on Ports 1 and 4
>> which seem to be fully functional. However, it does look like on my
>> UC864-G, port #3 is used for the GPS stream. Port #1 doesn't seem to
>> respond to anything.
>>
>
> I just tried the following at my modem:
>
> AT$GPSNMUN=1,1,1,1,1,1,1
> AT$GPSP=1
>
> Which enables the GPS reporting on Ports 1 and 4 and adds $GPSNMUN: at
> the beginning of every GPS report e.g.
>
> $GPSNMUN: $GPVTG,,T,,M,,N,,K*4E
>
> Which would be easy to catch from ofono.
>
> In my opinion the problem about this is that the GPS atom needs to be
> loaded for every telit modem, then try AT$GPSNMUN=1,1,1,1,1,1,1 and wait
> for the response. If the response is an error the atom knows that the
> modem does not support GPS. Could this check/enable also be added to a
> part of the telit plugin?
>
> The udev approach has the benifet to be able to do
>
> if (HasGPS)
> ... = ofono_location_reporting_create(...);
>
> or something like that at the telit plugin.
>
I agree that your proposed approach is the right one.
>>
>> Yes and no. ofono_modem_create has two modes of operation, one where a
>> known unique id is given. This can come for example from the serial
>> number of the USB device. Some manufacturers provide this information
>> properly, others do not. If you cannot trust the USB serial ID, then
>> giving a NULL parameter to ofono_modem_create will tell oFono to
>> generate a unique id itself. Your path will then look like /telit2 or
>> something like that.
>
> Ah, ok then the patch is fine I think and I like to get it reviewed :)
>
> But I can alter the patch to only search for the modem device and add
> the GPS check later to the telit plugin or the GPS atom, if you like.
>
Patch has been reviewed, however we might have to examine whether we
need to tweak the udev rules for this serial number / modem path stuff
to work properly. Marcel will have to take a look as I'm lost in that
part of the udev plugin.
Regards,
-Denis
next prev parent reply other threads:[~2011-06-13 9:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 15:18 [PATCH v4 1/4] network-registration.c: add telit support Bernhard.Guillon
2011-06-06 22:52 ` Denis Kenzior
2011-06-08 15:18 ` [PATCH v4 2/4] Add basic Telit UC864-G support: Bernhard.Guillon
2011-06-08 9:29 ` Denis Kenzior
2011-06-14 8:42 ` Bernhard Guillon
2011-06-09 10:26 ` Marcel Holtmann
2011-06-08 15:18 ` [PATCH v4 3/4] atmodem/vendor.h: add OFONO_VENDOR_TELIT Bernhard.Guillon
2011-06-06 22:51 ` Denis Kenzior
2011-06-08 15:18 ` [PATCH v4 4/4] udev: add Telit UC864-G and update udev rules Bernhard.Guillon
2011-06-08 15:32 ` Bernhard Guillon
2011-06-06 23:25 ` Denis Kenzior
2011-06-10 8:32 ` Bernhard Guillon
2011-06-08 8:32 ` Denis Kenzior
2011-06-14 8:34 ` Bernhard Guillon
2011-06-13 9:28 ` Denis Kenzior [this message]
2011-06-15 9:12 ` Bernhard Guillon
2011-06-13 9:04 ` Denis Kenzior
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=4DF5D84B.4030607@gmail.com \
--to=denkenz@gmail.com \
--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