public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Grunewaldt <lgw@dark-reality.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] bluetooth headset - connects but no audio
Date: Wed, 26 Jan 2005 12:41:33 +0100	[thread overview]
Message-ID: <41F781ED.2050704@dark-reality.de> (raw)
In-Reply-To: <41F74AC1.3010605@fastwebnet.it>

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

WiseLYNX wrote:
| | | I'll do some more experiments on my own, and I'll let you know if I
| | | understand something.
| |
| | Would be great. Good luck! I'm out of ideas :(
|
| alas, you where right. it was just a dongle issue - my friend's works
| perfectly. my misfortune in buying hardware strikes back :(
|
| is there any way to "fix" the problem?
|

I asked Marcel on this list, but I did not understand his answer...:

| the Silicon Wave chips are not the best ones. They have problems and it
| seems that they are not going to fix them. Mostly because they sell ROM
| chips are these ones can't be updated by a newer firmware. However if
| this is the problem with SCO packets and handle 0 then the hci_usb
| driver should simply drop these frames, because they are not valid SCO
| payload.

...?

I'm not sure if he means that there are to many packages recieved now,
or that the packages are dropped because of the 0 handle. I think that
might be hot-fixable somehow, at least for one connection. Of course
this is ugly, but if it's optional just to make this broken chipsets work?

best regards,
~  Lars



- --
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

iD8DBQFB94HsQWC6DTWkDAoRAroNAJ9E6fkzvN6D+gMJ8yz7FoDt+ks6LQCglOaY
RcQ4UuGEIc2hhazxyQUbphU=
=/OYs
-----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

      reply	other threads:[~2005-01-26 11:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-19 10:41 [Bluez-devel] bluetooth headset - connects but no audio WiseLYNX
2005-01-19 12:22 ` Lars Grunewaldt
2005-01-19 11:55   ` WiseLYNX
2005-01-19 13:54     ` Lars Grunewaldt
2005-01-19 13:27       ` WiseLYNX
2005-01-19 15:26         ` Lars Grunewaldt
2005-01-19 14:08       ` WiseLYNX
2005-01-19 17:27         ` Lars Grunewaldt
2005-01-19 21:52           ` WiseLYNX
2005-01-20  1:40             ` Lars Grunewaldt
2005-01-20 10:23               ` WiseLYNX
2005-01-20 13:12                 ` Lars Grunewaldt
2005-01-26  7:46                   ` WiseLYNX
2005-01-26 11:41                     ` Lars Grunewaldt [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=41F781ED.2050704@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