From: Maximilian Michel <michel@docomolab-euro.com>
To: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>, max@3max.de
Subject: Re: [Bluez-users] zeevo acer dongle
Date: Thu, 31 Jul 2003 12:09:20 +0200 [thread overview]
Message-ID: <3F28EAD0.6050209@docomolab-euro.com> (raw)
In-Reply-To: <1059640831.1832.84.camel@pegasus>
Marcel Holtmann wrote:
> Hi Maximilian,
>
>
>>T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
>>D: Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS= 8 #Cfgs= 1
>>P: Vendor=0b7a ProdID=07d0 Rev= 1.34
>>S: SerialNumber=3EC08003i
>>C:* #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr=100mA
>>I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
>>E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=1ms
>>E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
>>E: Ad=03(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
>>I: If#= 1 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)
>
>
> and this is what I mean. They don't read the H:2 spec. and push out an
> invalid product, because at least it must have this entry:
>
> I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
> E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
>
> You can use one of my patches with this changelog entry
>
> - Quirk for devices with no ISOC endpoints
>
> or you disable SCO support for the hci_usb driver at compile time.
>
> Regards
>
> Marcel
>
>
>
OK, compiling with latest patch with quirk helped, can use the dongle now.
But I think, I can never user voice with this dongle as it would need
sco support?
Thanks,
Maximilian
next prev parent reply other threads:[~2003-07-31 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 15:06 [Bluez-users] zeevo acer dongle Maximilian Michel
2003-07-30 22:17 ` Marcel Holtmann
2003-07-31 8:23 ` Maximilian Michel
2003-07-31 8:40 ` Marcel Holtmann
2003-07-31 10:09 ` Maximilian Michel [this message]
2003-07-31 10:34 ` Marcel Holtmann
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=3F28EAD0.6050209@docomolab-euro.com \
--to=michel@docomolab-euro.com \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@rvs.uni-bielefeld.de \
--cc=max@3max.de \
/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.