LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: SDiZ <sdiz@sdiz.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][BLUETOOTH] add HCI_BROKEN_ISOC for 0e5e:6622 (bugzilla #9027)
Date: Tue, 19 Feb 2008 21:55:45 +0100	[thread overview]
Message-ID: <AC57C59C-2B98-44F5-A408-05BBC11C08B9@holtmann.org> (raw)
In-Reply-To: <47B315CA.4080600@sdiz.net>

Hi,

>>>>> This patch fix bugzilla #9027.
>>>>> ``Syslog flooded with "hci_scodata_packet: hci0 SCO packet for  
>>>>> unknown
>>>>> connection handle 92" message"
>>>>>
>>>>> see http://bugzilla.kernel.org/show_bug.cgi?id=9027
>>>>>
>>>>>
>>>> when we get the content of /proc/bus/usb/devices for this one. Do  
>>>> you
>>>> have the manufacturer name of it or at least an idea which kind of
>>>> device this is. Check "hciconfig hci0 version".
>>>>
>>>>
>>> It have no text on the chips and package, so I don't know the
>>> manufacturer name.
>>>
>>
>> and what about "hciconfig hci0 version"?
>>
> hci0: Type: USB
> BD Address: 11:11:11:11:11:11 ACL MTU: 672:3 SCO MTU: 48:1
> HCI Ver: 2.0 (0x3) HCI Rev: 0x1f4 LMP Ver: 2.0 (0x3) LMP Subver: 0x1f4
> Manufacturer: CONWISE Technology Corporation Ltd (66)

this is really a broken device. Please update your comment in your  
patch and re-sent it. The comment should read

/* CONWISE Technology based adapters with buggy SCO support */

And also put the entry right after the RTX Telecom one.

Regards

Marcel


  reply	other threads:[~2008-02-19 20:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13  3:40 SDiZ
2008-02-13  6:02 ` David Miller
2008-02-13 10:31 ` Marcel Holtmann
2008-02-13 15:34   ` SDiZ
2008-02-13 15:40     ` Marcel Holtmann
2008-02-13 16:07       ` SDiZ
2008-02-19 20:55         ` Marcel Holtmann [this message]
2008-02-19  2:14       ` SDiZ

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=AC57C59C-2B98-44F5-A408-05BBC11C08B9@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sdiz@sdiz.net \
    --subject='Re: [PATCH][BLUETOOTH] add HCI_BROKEN_ISOC for 0e5e:6622 (bugzilla #9027)' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).