From: Hans Bausewein <hans@comerwell.xs4all.nl>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Broadcom Corporation (Firmware 105.105.074) USB dongle
Date: Sat, 30 Oct 2004 22:47:54 +0200 [thread overview]
Message-ID: <20041030204753.GA10315@comerwell.xs4all.nl> (raw)
In-Reply-To: <1099167789.6644.6.camel@notepaq>
On Sat, Oct 30, 2004 at 10:23:09PM +0200, Marcel Holtmann wrote:
>
> I don't think so, because this is some kind of init problem. You can try
> to set the quirk for your device 0a5c:2009 to HCI_BROKEN_ISOC only,
> because it seems that parts of it still work if you don't call reset.
Did this, but with same result. I only compiled 'hci_usb.c' and replaced the
'hci_usb.ko' since it's only a piece of implementation that changed. Must be
OK, I guess.
> Btw do you compiled your kernel with the CONFIG_BT_HCIUSB_SCO option? If
> yes, then try without it.
OK, maybe this is the problem. The Debian default was with
CONFIG_BT_HCIUSB_SCO=y, so I kept that.
Now I have to recompile everything, I guess.
It's compiling on the 2.8 GHz P4 machine at my work, now.
> The other thing is to change the init sequence of HCI commands and
> actually for this I must have this dongle at home. Think about donating
> it to me instead of returning it.
Maybe I'll buy another one for you, if I think it will work.
Hans
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-10-30 20:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-30 9:43 [Bluez-users] Broadcom Corporation (Firmware 105.105.074) USB dongle Hans Bausewein
2004-10-30 11:47 ` Marcel Holtmann
2004-10-30 12:44 ` Hans Bausewein
2004-10-30 13:41 ` Marcel Holtmann
2004-10-30 15:23 ` Hans Bausewein
2004-10-30 15:42 ` Marcel Holtmann
2004-10-30 15:57 ` Hans Bausewein
2004-10-30 16:10 ` Marcel Holtmann
2004-10-30 19:59 ` Hans Bausewein
2004-10-30 20:23 ` Marcel Holtmann
2004-10-30 20:47 ` Hans Bausewein [this message]
2004-11-02 21:40 ` Hans Bausewein
2004-11-02 21:58 ` Marcel Holtmann
2004-11-05 13:33 ` Hans Bausewein
2004-11-05 14:22 ` 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=20041030204753.GA10315@comerwell.xs4all.nl \
--to=hans@comerwell.xs4all.nl \
--cc=bluez-users@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