All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: ofono bug
Date: Tue, 06 Nov 2012 09:01:25 -0600	[thread overview]
Message-ID: <50992645.9060604@gmail.com> (raw)
In-Reply-To: <22bf93ea.1c0c0.13ad61e5931.Coremail.wujiangbo_1987@163.com>

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

Hi,

Just a gentle reminder not to top-post on this mailing list.

On 11/06/2012 08:27 AM, 吴江波 wrote:
> Hi,
> i already fix the bug, so i think this is the real bug.
> i set a callback fuc to GAtMux, and add status member for echo channel,
> when i find the channel active, it will call back the fuc, fuc check all
> channel is active, if all channel is active, continue to send AT
> commands you want.
>
>

It is pretty hard to follow what you mean here.  Can you send the actual 
fix as a patch? e.g. git send-email

>
>
>
> At 2012-11-06 22:23:21,"吴江波" <wujiangbo_1987@163.com> wrote:
>
>     Hi Denis Kenzior,
>     I find a bug about ofono, in src/ifx.c. The function
>     setup_internal_mux. if we modem use Mux in ofono code, ofono will
>     create six channel to send request. After we send AT commands, each
>     mux channel should be active that through send a little data and

To state this another way, we open the channel by sending the DLC 
establishment command.  This creates a mapping between that dlc number 
and a GIOChannel.

>     receive. In setup_internal_mux function it only set 10 millisecond
>     to do that, it manual think channel active while 10 millisecond. if
>     the modem don't response channel active in 10 millisecond, the

The T1 we negotiated during CMUX is 10ms, we assume that the channel 
establishment doesn't fail, however the timing might need to be relaxed 
a bit due to how long it might take the kernel to transmit.

>     sending AT commands don't dispatch to right channel. if you are

Sorry I don't follow this.  The sending will always dispatch to the 
right DLC since the DLC number is associated with the GIOChannel.

>     lucky, ofono will work well, but it don't guarantee. and also i have
>     the problem. ofono don't work well, it be cause by channel havn't
>     configure, ofono send AT comands. The GAtMux receive the response,
>     but GAtMux don't know which channel the response should be
>     dispatched. GAtMux will discard the right response, and the AT

Again, I don't follow.  The AT commands are coming on a particular DLC. 
  The DLC mapping is already established after g_at_mux_create_channel 
is called.

>     command will don't receive the response forever, it will case some
>     request timeout, and ofono think it have some problem it don't work.
>     any questions. then we open mux, ofono will create a new IOChannel,
>     the previously device IOChannel should remove from main context, but
>     ofono don't do that. why?

I don't understand the question, sorry.

Regards,
-Denis

      reply	other threads:[~2012-11-06 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-06 14:23 ofono bug =?unknown-8bit?b?5ZC05rGf5rOi?=
2012-11-06 14:27 ` bug =?unknown-8bit?b?5ZC05rGf5rOi?=
2012-11-06 15:01   ` Denis Kenzior [this message]

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=50992645.9060604@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.