From: Marcel Holtmann <marcel@holtmann.org>
To: Hans Bausewein <hans@comerwell.xs4all.nl>
Cc: 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:23:09 +0200 [thread overview]
Message-ID: <1099167789.6644.6.camel@notepaq> (raw)
In-Reply-To: <20041030195917.GA10109@comerwell.xs4all.nl>
Hi Hans,
> > actually there must be a secret within the init sequence of the commands
> > and you should try a clean 2.6.9 vanilla kernel with the -mh3 patch.
>
> same results
>
> p2:~# hciconfig dev hci0 up
> Can't init device hci0. Device or resource busy(16)
>
> And then I plugged in the other MSI (CSR) dongle: still works fine.
>
> > I think I will get this dongle working, but I need it at home for further
> > testing and I stopped buying Bluetooth dongles by myself. If you believe
> > it or not, I have enough of them ;)
>
> I think about returning it to the shop and buying the Cambridge-based
> dongle. Let me know if I can try anything. I'll have it until tuesday, at
> least.
>
> Would it help to turn on CONFIG_BT_HCIUSB_DEBUG and examine log ?
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.
Btw do you compiled your kernel with the CONFIG_BT_HCIUSB_SCO option? If
yes, then try without it.
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.
Regards
Marcel
-------------------------------------------------------
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:23 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 [this message]
2004-10-30 20:47 ` Hans Bausewein
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=1099167789.6644.6.camel@notepaq \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=hans@comerwell.xs4all.nl \
/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.