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 18:10:11 +0200 [thread overview]
Message-ID: <1099152611.16247.23.camel@pegasus> (raw)
In-Reply-To: <20041030155712.GA9715@comerwell.xs4all.nl>
Hi Hans,
> > > > > Kernel 2.6.10rc1 + patch is compiling now...
> > > >
> > > > Does it work? If yes, send in the output from "hciconfig -a".
> > >
> > > No, down, no m
> > >
> > > hci0: Type: USB
> > > BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
> > > DOWN
> > > RX bytes:0 acl:0 sco:0 events:0 errors:0
> > > TX bytes:0 acl:0 sco:0 commands:0 errors:0
> > > Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> > > Packet type: DM1 DH1 HV1
> > > Link policy:
> > > Link mode: SLAVE ACCEPT
> > >
> > > p2:/var/log# hciconfig dev hci0 up
> > > Can't init device hci0. Device or resource busy(16)
> >
> > This is funny. Actually it should work fine with that patch. I included
> > it into 2.6.9-mh3 that I put out some minutes ago. Please try it again.
> >
> > Maybe you wanna try to play with other combinations of the HCI_RESET and
> > HCI_BROKEN_ISOC quirks.
>
> It may be something else. I'll first try an unpatched kernel with the same
> settings. The previous results were with the standard Debian kernel.
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. 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 ;)
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 16:10 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 [this message]
2004-10-30 19:59 ` Hans Bausewein
2004-10-30 20:23 ` Marcel Holtmann
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=1099152611.16247.23.camel@pegasus \
--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.