From: "Todd E. Johnson" <tejohnson@yahoo.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Re: 2.6.2 errors with DBT-120 (B2)
Date: Sat, 14 Feb 2004 09:18:17 -0500 [thread overview]
Message-ID: <402E2E29.7040207@yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 342 bytes --]
Thanks for the quick reply! Attached is the 'hciconfig -a' in
hciconfig.txt...
Bummer on the SCO support. I am looking forward to using it in an
embedded linux based telematics system for vehicle hands free
functionality. Anything I can do to help besides provide the 'hciconfig
-a' output?
Regards,
Todd E. Johnson
[-- Attachment #2: hciconfig.txt --]
[-- Type: text/plain, Size: 597 bytes --]
hci0: Type: USB
BD Address: 00:80:C8:1F:B0:1F ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:412 acl:0 sco:0 events:22 errors:0
TX bytes:579 acl:0 sco:0 commands:21 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'BlueZ (0)'
Class: 0x700408
Service Classes: Object Transfer, Audio, Telephony
Device Class: Audio/Video, Hands-free
HCI Ver: 1.1 (0x1) HCI Rev: 0x1bb LMP Ver: 1.1 (0x1) LMP Subver: 0x1bb
Manufacturer: Cambridge Silicon Radio (10)
next reply other threads:[~2004-02-14 14:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 14:18 Todd E. Johnson [this message]
2004-02-14 14:43 ` [Bluez-users] Re: 2.6.2 errors with DBT-120 (B2) Marcel Holtmann
2004-02-14 15:01 ` [Bluez-users] bcm203x module causes kernel panic on boot Alex Holland
2004-02-14 15:15 ` Marcel Holtmann
[not found] ` <402E4E02.9020600@yahoo.com>
2004-02-15 13:27 ` [Bluez-users] Re: 2.6.2 errors with DBT-120 (B2) Marcel Holtmann
2004-02-15 16:09 ` Todd E. Johnson
2004-02-15 16:20 ` Marcel Holtmann
2004-02-16 21:36 ` [Bluez-users] " Todd E. Johnson
2004-02-16 22:31 ` [Linux-usb-users] " Todd E. Johnson
2004-02-16 22:34 ` Todd E. Johnson
2004-02-18 14:25 ` [Bluez-users] " Todd E. Johnson
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=402E2E29.7040207@yahoo.com \
--to=tejohnson@yahoo.com \
--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