public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Guardiani <jesse@wingnet.net>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: Re: Again: Problems with Dongle, Headset or btsco
Date: Wed, 02 Feb 2005 00:00:56 -0500	[thread overview]
Message-ID: <ctpmok$otj$2@sea.gmane.org> (raw)
In-Reply-To: 1106569225.9269.64.camel@pegasus

Marcel Holtmann wrote:

> Hi Lars,
> 
>> 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...)
> 
> 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 confused by this response. I have a USB-240 dongle too. Does this mean
that a simple workaround is possible, or no?

-- 
Jesse Guardiani, Systems Administrator
WingNET Internet Services,
P.O. Box 2605 // Cleveland, TN 37320-2605
423-559-LINK (v)  423-559-5145 (f)
http://www.wingnet.net




-------------------------------------------------------
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-02-02  5:00 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
2005-01-24 12:20                   ` Marcel Holtmann
2005-02-02  5:00                     ` Jesse Guardiani [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='ctpmok$otj$2@sea.gmane.org' \
    --to=jesse@wingnet.net \
    --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