From: Marcel Holtmann <marcel@holtmann.org>
To: Peter Favrholdt <pfavr@mip.sdu.dk>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] snd-bt-sco
Date: Thu, 01 Jul 2004 16:10:01 +0200 [thread overview]
Message-ID: <1088691001.4540.230.camel@pegasus> (raw)
In-Reply-To: <40E346A8.2050209@mip.sdu.dk>
Hi Peter,
> Well, I figured out I didn't have the /dev/snd/* device files
>
> So now it almost works. The headset seems connected. I can use alsamixer (and
> the volume buttons on the headset changes the volume in the mixer window).
> hciconfig shows data is flowing at a steady rate from the microphone:
>
> hci0: Type: USB
> BD Address: 00:0B:0D:20:79:21 ACL MTU: 339:4 SCO MTU: 64:0
> UP RUNNING PSCAN ISCAN
> RX bytes:8895374 acl:72 sco:329395 events:232 errors:0
> TX bytes:3768 acl:151 sco:0 commands:47 errors:0
>
> But no sound
and I am not sure that your USB dongle supports SCO over HCI. Show us
the output of "hciconfig -a" and "cat /proc/bus/usb/devices".
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-07-01 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 22:17 [Bluez-devel] snd-bt-sco Peter Favrholdt
2004-06-30 23:03 ` Peter Favrholdt
2004-07-01 14:10 ` Marcel Holtmann [this message]
2004-07-01 20:49 ` Peter Favrholdt
-- strict thread matches above, loose matches on Subject: below --
2004-12-09 17:34 Michael Zanetti
2004-12-09 21:28 ` Marcel Holtmann
2004-12-09 22:35 ` Brad Midgley
2004-12-09 22:57 ` Chris Boyle
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=1088691001.4540.230.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=pfavr@mip.sdu.dk \
/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.