From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Guillaume JUAN <guillaume.juan@sagemcom.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: n_gsm issues
Date: Wed, 1 Aug 2012 22:23:22 +0100 [thread overview]
Message-ID: <20120801222322.345d0bc2@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <440_1343835403_50194D0B_440_1588_1_OF108ABE84.7A08D19F-ONC1257A4D.00556998-C1257A4D.0055C11D@sagemcom.com>
> Who can I contact to discuss issues / submit fixes ?
This list and me more specifically.
> - When a virtual tty is closed from user-space, the operation is not fully
> synchronous: DISC requests can be sent on the DLCI after the system call
> has returned.
> This is because gsmtty_close does not wait for event DLCI_CLOSED after
> calling gsm_dlci_begin_close.
That one is intentional.
> - On line discipline attach, n_gsm use default settings that have no chance
> to match what I set in the modem
> and when I do the TIOCSETCONF ioctl to configure it correctly, this
> previous settings cause it to call gsm_cleanup_mux(), leading to delays and
> useless commands to the modem (that won't be answered).
We start in passive mode to tyr and avoid useless commands but could
certainly be improved.
> - The CLD command encoding is not strictly compliant with 3GPP 27.010
> The TLV built does not have any L byte, whereas it should have one
> indicating a zero length for the value field.
> The modem I use accept this variant but some may not.
What kernel verison is this ?
> This issue is the most disturbing for me, as I consequently can see no way
> to end mux session in a fully satisfying way.
Probably we need to split 'ldisc close' and 'ending a mux'
(eg have an ioctl for 'mux shutdown')
Alan
next prev parent reply other threads:[~2012-08-01 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 15:36 n_gsm issues Guillaume JUAN
2012-08-01 21:23 ` Alan Cox [this message]
2012-08-02 12:37 ` Réf. : " Guillaume JUAN
2012-08-03 13:42 ` Alan Cox
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=20120801222322.345d0bc2@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=guillaume.juan@sagemcom.com \
--cc=linux-serial@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