From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] SCO over UART
Date: Wed, 24 Aug 2005 00:42:54 -0600 [thread overview]
Message-ID: <430C16EE.4090501@xmission.com> (raw)
In-Reply-To: <4305B185.2080604@umit.at>
David,
It doesn't seem to help anything...
# hcitool cmd 0x3f 0x001d 0x00
< HCI Command: ogf 0x3f, ocf 0x001d, plen 1
00
> HCI Event: 0x0e plen 4
07 1D FC 00
but then I haven't been able to confirm that I've done all the right
things to get btsco to work on gumstix.
This doesn't look right:
btsco v0.4a
Device is 0:0
Voice setting: 0x0060
RFCOMM channel 2 connected
speaker volume: 0 mic volume: 0
driver is in use
Can't connect SCO audio channel
: Device or resource busy
where the "driver is in use" message first appears when trying to play
music to the audio device.
Brad
David Bannach wrote:
> brad,
>
>> What is the ericsson command and how do you inject it into hci?
>>
>> Is the rok101008 similar in this respect to the rok104001? That's
>> what's on the gumstix.com board and I've been *very* interested in
>> getting sco working with this. I thought it couldn't be coaxed into
>> using hci.
>
>
> the command is "ericsson_set_sco_data_path". i found it in this document
> (only):
> http://www.vs.inf.ethz.ch/res/proj/smart-its/dl/ROK_101_007_revR1C-HCI_ericsson_specific.pdf
>
>
> i use hcitool for sending the command to the module, e.g. the following
> line will set the sco mapping to hci:
>
> hcitool cmd 0x3f 0x001d 0x00
>
> the rok101008 and rok104001 seem very similar. at least the command
> above returns a positive response on both devices. i did not notice
> differences of these devices so far. actually i want to get sco running
> on the rok104001 which is built into a qbic (pxa based wearable) but
> it's easier to try things with an external module attached to a notebook.
>
> i'm still having the problem that bluez does not send any sco data to
> the module. i'm really curious about your results.
>
> david
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-08-24 6:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 8:45 [Bluez-devel] SCO over UART David Bannach
2005-08-17 20:37 ` Brad Midgley
2005-08-19 10:16 ` David Bannach
2005-08-24 6:42 ` Brad Midgley [this message]
2005-09-07 8:14 ` David Bannach
2005-09-07 13:59 ` Brad Midgley
2005-09-14 9:47 ` David Bannach
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=430C16EE.4090501@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-devel@lists.sourceforge.net \
/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).