From: Marcel Holtmann <marcel@holtmann.org>
To: sreevani medhahal <sreevani.medhahal@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Disconnect eSCO link from Command line
Date: Wed, 28 Jan 2009 10:57:47 +0100 [thread overview]
Message-ID: <1233136667.2139.1.camel@violet> (raw)
In-Reply-To: <c2a31c480901280137y33faa44fm975c63f5ae2ab514@mail.gmail.com>
Hi Sreevani,
> >> After the headset has created the eSCO link. The Profile Tuning
> >> Suite asks for Closing the Audio Connection from AG. Is there any
> >> command line utiility to disable the eSCO link & not the service level
> >> connection(ACL).[The eSCO link is visible on giving hcitool con ]
> >
> > not that I know of except hcitool cmd ;)
> >
> I tried modifying hcitool.c function cmd_dc by changing type of link
> to ESCO_LINK(instead of ACL_LINK). i got the error as disconnect
> failed operation not permitted.
> > You should also not be sheeting with sending a HCI command when it comes
> > to PTS tests. You program has to be able to disconnect eSCO by itself.
> >
> BlueZ is getting sco_connect result as Connection timed out. but where
> as when i list the connections using hcitool con, i see that there is
> a eSCO link.
you might wanna try bluetooth-testing.git since the SCO/eSCO connection
reject patch might do exactly what you expect here.
Regards
Marcel
next prev parent reply other threads:[~2009-01-28 9:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 5:16 Disconnect eSCO link from Command line sreevani medhahal
2009-01-28 5:39 ` Marcel Holtmann
2009-01-28 9:37 ` sreevani medhahal
2009-01-28 9:57 ` Marcel Holtmann [this message]
2009-01-28 8:23 ` Johan Hedberg
2009-01-28 9:42 ` sreevani medhahal
2009-01-28 11:25 ` Johan Hedberg
2009-01-30 9:57 ` sreevani medhahal
2009-01-30 12:18 ` sreevani medhahal
2009-02-01 16:57 ` Marcel Holtmann
2009-02-01 16:56 ` Marcel Holtmann
2009-02-03 6:04 ` sreevani medhahal
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=1233136667.2139.1.camel@violet \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sreevani.medhahal@gmail.com \
/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.