linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ajay <ajay.kv@globaledgesoft.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: L2CAP Flush_Timeout  Error
Date: Wed, 03 Oct 2012 01:51:23 +0530	[thread overview]
Message-ID: <506B4CC3.1010203@globaledgesoft.com> (raw)
In-Reply-To: <506B4479.3050105@globaledgesoft.com>



> On Tue, Oct 02, 2012 at 11:48:56PM +0530, Ajay wrote:
>> Hi,
>>      Im currently working in an A2DP stuff, where i noticed an error.
>> Here i wanted to monitor the flushed packets due to timeout.
>>
>>   I used the  l2test code for my testing purpose
>>
>>                On client side   "l2test  -R  -S <bdadddr> "
>>                and i set the flush timeout as 100 (opts.flush_to = 100)
>>
>>         But  later  when i print the getsockopt value of flush_to, it
>> was showing some default value (65532)  harcoded at kernel side.
>
> Try the patch in this thread.
>
> Best regards
> Andrei Emeltchenko
>

    Thanks for your patch , its working fine. Now even  if i set the
flush_timeout = 5 , i couldnt  able to see any packets missing at the
receiver side . Here in the sender  side  im giving proper sequence
number, and these same sequence is getting at the receiver side . i
doubted even though its flushing , controller is doing some
retransmission job...please help . My kernel is 2.6.39 , and im using
BASIC MODE of transmission. so shall i change it to STEAMING MODE ????

-- 
  Thanks & regards

AJAY KV
8892753703



      reply	other threads:[~2012-10-02 20:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 18:18 L2CAP Flush_Timeout Error Ajay
2012-10-08  9:09 ` [PATCH] Bluetooth: Allow to set flush timeout Andrei Emeltchenko
2012-10-08  9:11 ` L2CAP Flush_Timeout Error Andrei Emeltchenko
2012-10-02 19:46   ` Ajay
2012-10-02 20:21     ` Ajay [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=506B4CC3.1010203@globaledgesoft.com \
    --to=ajay.kv@globaledgesoft.com \
    --cc=linux-bluetooth@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;
as well as URLs for NNTP newsgroup(s).