public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin List-Petersen <martin@list-petersen.net>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Audio & Bluetooth
Date: Tue, 09 Nov 2004 02:05:52 +0000	[thread overview]
Message-ID: <1099965952.27159.7.camel@loke> (raw)
In-Reply-To: <1099956503.29330.35.camel@pegasus>

[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]

On Mon, 2004-11-08 at 23:28, Marcel Holtmann wrote:
> Hi Martin,
> 
> > > > I have a question: for my mobile I use an HAMA Bluetooth headset. If I 
> > > > buy a bluetooth PCMCIA card for my notebook, will I be able to use this 
> > > > headset with this card? recognized as a second soundcard? as a normal 
> > > > headset for my integrate soundcard? recognized by my software phone 
> > > > clients? If I buy an USB bluetooth device, would it be the same? better?
> > > 
> > > actually this is not an easy to answer question. First thing is that you
> > > should get a Bluetooth device with a CSR chip and at least HCI 16.x
> > > firmware on it. The second is that it must route the SCO traffic through
> > > the HCI and via a PCM. Then it should be possible.
> > 
> > How to identify version 16.x or higher ? hciconfig -a only gives a
> > hexadecimal value, that not really gives me get a clue on the firmware
> > version.
> > 
> > HCI Ver: 1.1 (0x1) HCI Rev: 0xbc LMP Ver: 1.1 (0x1) LMP Subver: 0xbc
> 
> you are kidding me? Use "hciconfig hci0 revision" or look at my webpage
> where most of the build ids are decoded.

Must be blind. Anyhow, i guess this doesn't sound good for sound:

# hciconfig hci0 revision
hci0:   Type: USB
        BD Address: 00:60:57:02:7F:E1 ACL MTU: 192:8  SCO MTU: 64:8
        HCI 12.7
        Chip version: BlueCore01b
        SCO mapping:  PCM

I have problems with no audio on this dongle. So i take it, that it
might be the oldish firmware.

Kind regards,
Martin List-Petersen


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-11-09  2:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08 18:59 [Bluez-users] Audio & Bluetooth administrator tootai
2004-11-08 19:31 ` Brad Midgley
2004-11-08 19:57 ` Marcel Holtmann
2004-11-08 22:56   ` Martin List-Petersen
2004-11-08 23:28     ` Marcel Holtmann
2004-11-09  2:05       ` Martin List-Petersen [this message]
2004-11-09  9:54         ` Peter Stephenson
2004-11-09 14:11       ` Timothy Murphy
2004-11-09 14:28         ` Marcel Holtmann
2004-11-09 14:47         ` Peter Stephenson
2004-11-10  0:56           ` Marcel Holtmann
2004-11-11 20:57   ` Martin List-Petersen
2004-11-11 21:27     ` Marcel Holtmann
2004-11-12  1:09       ` Martin List-Petersen
2004-11-12  1:26         ` Marcel Holtmann
2004-11-12  1:40           ` Martin List-Petersen

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=1099965952.27159.7.camel@loke \
    --to=martin@list-petersen.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox