From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] State of snd-bt-sco
Date: Sun, 28 Nov 2004 18:52:06 +0100 [thread overview]
Message-ID: <1101664326.18467.56.camel@pegasus> (raw)
In-Reply-To: <200411281307.43051.carlosarazevedo@netcabo.pt>
Hi Carlos,
> Is snd-bt-sco (from the CVS) currently working ? I can get btsco (the app) to
> connect to the headset
> (http://sourceforge.net/mailarchive/forum.php?thread_id=6030842&forum_id=1883)
> and get the following :
>
> Device is 1:0
> Voice setting: 0x0060
> RFCOMM channel 1 connected
> recieved AT+CKPD=200
> opened hwdep
> connected SCO channel
> Setting sco fd
> Done setting sco fd
> recieved AT+VGS=04
> Sending up speaker change 4
>
> but when I run aplay (aplay -D hw:1 prompt-copia1.wav) or arecord it exits
> with
>
> Playing WAVE 'prompt-copia1.wav' : Signed 16 bit Little Endian, Rate 8000 Hz,
> Mono
> aplay: pcm_write:1118: write error: Input/output error
>
> I've sprinkled the kernel driver with dprintks but apparently there is no data
> going from the SCO socket to the ALSA driver.
for me it is working. What is the output of "hciconfig -a"? What kernel
are you running and what Linux distribution do you use? Do you checked
with hcidump what packets are sent?
> By the way both in btsco and in the driver there's some structs and other
> variables declared inside the code (not at the top of the function). GCC
> 2.95.x doesn't like it, so it would be nice if they were moved upstream.
What about sending in a patch?
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-11-28 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 13:07 [Bluez-users] State of snd-bt-sco Carlos Azevedo
2004-11-28 16:31 ` Brad Midgley
2004-11-28 17:52 ` Marcel Holtmann [this message]
2004-11-28 22:10 ` [Bluez-users] Broadcomm usb dongle problems Moran
2004-11-29 1:32 ` Marcel Holtmann
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=1101664326.18467.56.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@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 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.