public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick <Nick.Thomas@Uni-Bielefeld.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] hello
Date: Mon, 29 Nov 2004 13:37:24 +0100	[thread overview]
Message-ID: <41AB1804.8070807@Uni-Bielefeld.de> (raw)
In-Reply-To: <1101694796.9527.13.camel@pegasus>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


|
| check with "hciconfig hci0 revision" (as root) for the setting of
| the SCO routing. I think it is set to PCM.

you were right:

(0:1)root@Muramasa:~$ hciconfig hci0 revision
hci0:   Type: USB
~        BD Address: 00:60:57:02:95:FE ACL MTU: 192:8  SCO MTU: 64:8
~        HCI 12.7
~        Chip version: BlueCore01b
~        SCO mapping:  PCM

so, is that the way it should be?


~    ,nick

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBqxgE40bmwXROfRURAvqRAKDsXeO6wiHySifzPpDzAh8sIOBT6ACeJELH
cVbkAU1OiN0vPgXBjvcpzpg=
=lamt
-----END PGP SIGNATURE-----



-------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-11-29 12:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-29  1:57 [Bluez-devel] hello Nick
2004-11-29  2:19 ` Marcel Holtmann
2004-11-29 12:37   ` Nick [this message]
2004-11-29 12:44     ` Marcel Holtmann
2004-11-29 12:51       ` Simon Vogl
2004-11-29 15:58         ` Nick
2004-11-29 13:30           ` Simon Vogl

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=41AB1804.8070807@Uni-Bielefeld.de \
    --to=nick.thomas@uni-bielefeld.de \
    --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