From: "Riikka Jylhä" <jylhar@ac.tut.fi>
To: "'Marcel Holtmann'" <marcel@rvs.uni-bielefeld.de>
Cc: <bluez-users@lists.sourceforge.net>
Subject: RE: [Bluez-users] USB-drivers
Date: Mon, 4 Aug 2003 15:41:15 +0300 [thread overview]
Message-ID: <000201c35a85$b18576d0$ae2ae682@ac.tut.fi> (raw)
In-Reply-To: <1059999322.1747.95.camel@pegasus>
Thanks for your reply,
-----Original Message-----
> You need to apply a patch for using two ISOC URB's
> per TX and RX path.=20
Is this included in patch-2.4.21-mh2.gz. There is "Quirk for devices
with no ISOC endpoints" at the Changelog. There is ISOC mentioned but is
this the right patch or do I have to use the one I remember sawing
somewhere in the bluez-developers mail-archive?
> And the alternate configuration for the ISOC
> interface must be set correctly according to the voice setting.
How do I do that?
> At the moment this is only tested with CSR dongles, but I can play and
> record audio data with my headset in 8 and 16 bit quality. And it
seems
> that the BlueCore02 produces better audio than the BlueCore01b.
What audio formats are supported? Am I able to send .wav and .mp3
sounds?
> Using an UART based device is mostly no option, because the bandwith
is
> not enough for sending SCO packets over the HCI link. But it is
working
> with the 3Com and Xircom PCMCIA cards.
.. poor me only having TDK and Socket PCMCIA cards
> Regards
>
> Marcel
--
Riikka Jylh=E4
next prev parent reply other threads:[~2003-08-04 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 11:40 [Bluez-users] USB-drivers Riikka Jylhä
2003-08-04 12:15 ` Marcel Holtmann
2003-08-04 12:41 ` Riikka Jylhä [this message]
2003-08-04 12:56 ` Marcel Holtmann
2003-08-04 13:28 ` Steven Singer
2003-08-04 14:28 ` Marcel Holtmann
2003-08-05 12:38 ` Riikka Jylhä
2003-08-06 7:13 ` Riikka Jylhä
2003-08-06 11:18 ` 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='000201c35a85$b18576d0$ae2ae682@ac.tut.fi' \
--to=jylhar@ac.tut.fi \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@rvs.uni-bielefeld.de \
/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