From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] headset neo-507 not working with bluefritz 2.0
Date: Sun, 08 May 2005 22:29:53 -0600 [thread overview]
Message-ID: <427EE741.5000002@xmission.com> (raw)
In-Reply-To: <427D5693.6070501@gmx.de>
Michael
Everything looks right but the bluetooth adapter may not be ideal. We
mostly have seen success using CSR based adapters and I'm not sure this
one is known to work with btsco.
Brad
> hci0: Type: USB
> BD Address: 00:04:0E:89:BC:7F ACL MTU: 120:20 SCO MTU: 64:0
> UP RUNNING PSCAN ISCAN INQUIRY AUTH
> RX bytes:128 acl:0 sco:0 events:16 errors:0
> TX bytes:313 acl:0 sco:0 commands:16 errors:0
> Features: 0xff 0xff 0x05 0x00 0x00 0x00 0x00 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: RSWITCH HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Name: 'BlueZ leeloo (0)'
> Class: 0x100100
> Service Classes: Object Transfer
> Device Class: Computer, Uncategorized
> HCI Ver: 1.1 (0x1) HCI Rev: 0x2005 LMP Ver: 1.1 (0x1) LMP
> Subver: 0x1805
> Manufacturer: AVM Berlin (31)
>
>
> hciconfig hci0 revision:
> hci0: Type: USB
> BD Address: 00:04:0E:89:BC:7F ACL MTU: 120:20 SCO MTU: 64:0
> Unknown type
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-05-09 4:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-08 0:00 [Bluez-devel] headset neo-507 not working with bluefritz 2.0 Michael Tede
2005-05-09 4:29 ` Brad Midgley [this message]
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=427EE741.5000002@xmission.com \
--to=bmidgley@xmission.com \
--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 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.