Open Source Telephony
 help / color / mirror / Atom feed
From: Clement Viel <vielclement@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 2/3] sim800: add documentation and modify AUTHORS file
Date: Sat, 03 Nov 2018 00:36:26 +0100	[thread overview]
Message-ID: <20181102233626.GB6943@turing> (raw)
In-Reply-To: <2552d5a0-6bfc-26c8-14f0-ee93b8ea8f03@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2197 bytes --]

Hi Denis,

On Thu, Nov 01, 2018 at 09:48:24AM -0500, Denis Kenzior wrote:
> Hi Clement,
> 
> On 10/15/2018 12:27 PM, Clement Viel wrote:
> >---
> >  AUTHORS              |  1 +
> 
> Please don't include AUTHORS changes.  One of the maintainers will take care
> of it.
> 
> >  doc/sim800-modem.txt | 11 +++++++++++
> >  2 files changed, 12 insertions(+)
> >  create mode 100644 doc/sim800-modem.txt
> >
> >diff --git a/AUTHORS b/AUTHORS
> >index 2d360e6..a8362c8 100644
> >--- a/AUTHORS
> >+++ b/AUTHORS
> >@@ -138,3 +138,4 @@ Florent Beillonnet <florent.beillonnet@gmail.com>
> >  Martin Hundebøll <martin@geanix.com>
> >  Julien Tournier <tournier.julien@gmail.com>
> >  Nandini Rebello <nandini.rebello@intel.com>
> >+Clement Viel <vielclement@gmail.com>
> >diff --git a/doc/sim800-modem.txt b/doc/sim800-modem.txt
> >new file mode 100644
> >index 0000000..7220cb8
> >--- /dev/null
> >+++ b/doc/sim800-modem.txt
> >@@ -0,0 +1,11 @@
> >+SIM800 modem usage
> >+===================
> >+
> >+To enable SIM800 module support you need to put the following
> >+udev rule into appropriate file in /{etc,lib}/udev/rules.d:
> >+
> >+KERNEL=="ttyS2", ENV{OFONO_DRIVER}="sim800"
> >+
> >+Sim800 driver code is merged with sim900's. So, to add modifications to sim800 driver, sim900.c file must be edited
> >+accordingly.
> >+To differentiate the two modems, developpers must use the "modem_type"
> >field of sim900_data
> typo
> 
> structure.
> >
> 
> Also, we can't have people hand-editing driver code to distinguish between
> one device and another.  You've already went to the trouble of creating a
> separate sim800 driver (which I do not think is the right approach at all),
> why not take advantage of that fact with an appropriate probe() function or
> something?

These indications were targeting developpers to warn them about the fact that sim800 and sim900 drivers are merged.
I'll remove these lines

> 
> Anyway, I still think you should be querying +CGMM or ATI or whatever to
> figure out the modem model automatically and not rely on the user to set
> this up.

Yep this will be done.

> Regards,
> -Denis

Regards
Clem

  reply	other threads:[~2018-11-02 23:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15 17:27 [PATCH 1/3] sim800: add support for sim800 modem Clement Viel
2018-10-15 17:27 ` [PATCH 2/3] sim800: add documentation and modify AUTHORS file Clement Viel
2018-11-01 14:48   ` Denis Kenzior
2018-11-02 23:36     ` Clement Viel [this message]
2018-10-15 17:27 ` [PATCH 3/3] sim800: add udev detection Clement Viel
2018-10-31 15:16 ` [PATCH 1/3] sim800: add support for sim800 modem =?unknown-8bit?q?Cl=C3=A9ment?= VIEL
2018-11-01 14:53 ` Denis Kenzior
2018-11-02 23:31   ` Clement Viel
  -- strict thread matches above, loose matches on Subject: below --
2018-10-03 13:28 Clement Viel
2018-10-03 13:28 ` [PATCH 2/3] sim800: add documentation and modify AUTHORS file Clement Viel

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=20181102233626.GB6943@turing \
    --to=vielclement@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