From: Lars Grunewaldt <lgw@dark-reality.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: Again: Problems with Dongle, Headset or btsco
Date: Mon, 24 Jan 2005 12:21:40 +0100 [thread overview]
Message-ID: <41F4DA44.6070608@dark-reality.de> (raw)
In-Reply-To: <41F4D1ED.6070502@webstuhl.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Marcel,
as it seems that those dongles seem not to work with the currect sco
implementation, what would you propose to debug this misfunction?
Maybe the hci_usb driver can be fixed or a workaround added for this
chipsets (I think they are buggy, not our implementation, but if there's
a simple workaround...)
best regards,
~ Lars
Ben Pezzei wrote:
| Hi
|
| Lars Grunewaldt schrieb:
|
|>
|> uhm, this is wrong. If you are using the "actual" btsco package from CVS
|> - - and you should be - it must record as signed 16 bit if I'm not
|> mistaken (possibly unsigned 16B, but in no case 8 bit)
|
|
| This worked neither
|
| Anyways, I just want to let you know that I kicked the Anycom
| Dongle and bought an D-Link DBT 120 Rev 4, et voila: Everything
| is working fine.
|
| Headset: Plantronics 2500
|
| tnx again for your help and congrats @ Developers
|
| greetings
| ben
|
|
|
|
| -------------------------------------------------------
| This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
| Tool for open source databases. Create drag-&-drop reports. Save time
| by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
| Download a FREE copy at http://www.intelliview.com/go/osdn_nl
| _______________________________________________
| Bluez-devel mailing list
| Bluez-devel@lists.sourceforge.net
| https://lists.sourceforge.net/lists/listinfo/bluez-devel
|
- --
Lars Grunewaldt
* software development
* multimedia design
skills: C/C++/Java/PHP/(X)HTML/Flash/audio/video
web: http://www.dark-reality.de
mail: lgw@dark-reality.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB9NpEQWC6DTWkDAoRApYwAJ0V/f3tlellTspUzas4S250FqlRJgCfZuRy
IuFYlvDUJWm5dCvrf8qLrjk=
=F9NV
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-01-24 11:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 11:44 [Bluez-devel] Again: Problems with Dongle, Headset or btsco Ben Pezzei
2005-01-21 13:07 ` Lars Grunewaldt
2005-01-21 16:08 ` Ben Pezzei
2005-01-21 17:04 ` Lars Grunewaldt
2005-01-21 17:14 ` mirko_3
2005-01-22 13:59 ` Ben Pezzei
2005-01-22 14:19 ` mirko_3
2005-01-22 14:40 ` ligi
2005-01-22 15:35 ` [Bluez-devel] " Paul Ionescu
2005-01-22 17:43 ` Ben Pezzei
2005-01-22 19:24 ` [Bluez-devel] " Paul Ionescu
2005-01-22 15:40 ` [Bluez-devel] " Sebastian Roth
2005-01-22 17:50 ` Ben Pezzei
2005-01-23 17:52 ` Lars Grunewaldt
2005-01-24 10:46 ` Ben Pezzei
2005-01-24 11:21 ` Lars Grunewaldt [this message]
2005-01-24 12:20 ` Marcel Holtmann
2005-02-02 5:00 ` [Bluez-devel] " Jesse Guardiani
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=41F4DA44.6070608@dark-reality.de \
--to=lgw@dark-reality.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