From: Alex Holland <ah160@student.cs.york.ac.uk>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Compile bluez-bluefw-1.0 fails
Date: Tue, 20 Apr 2004 10:28:08 +0100 [thread overview]
Message-ID: <200404201028.08718.ah160@student.cs.york.ac.uk> (raw)
In-Reply-To: <200404192121.31112.ah160@student.cs.york.ac.uk>
Well, booted up today and it worked! To be honest though, I consider
this to be a bad thing; it means it'll probably do the works
sometimes/doesn't work sometimes thing that bluez-bluefw did too.
Conclusion? Don't go near USB dongles with Broadcomm chipsets. I wish I
had a CSR.
Thanks for the help, anyway.
Alex Holland
Here's bits of dmesg and lsmod/usb, just in case it reveals anything:
---------------------------------------------------------------------
...blah...
Bluetooth: Broadcom Blutonium firmware driver ver 1.0
drivers/usb/core/usb.c: registered new driver bcm203x
Bluetooth: Core ver 2.4
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: HCI USB driver ver 2.5
drivers/usb/core/usb.c: registered new driver hci_usb
...blah...
Bluetooth: L2CAP ver 2.1
Bluetooth: L2CAP socket layer initialized
...blah...
Bluetooth: RFCOMM ver 1.2
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
-----------------------------------------------------------------------
Bus 001 Device 007: ID 0a5c:2001 Broadcom Corp.
-----------------------------------------------------------------------
rfcomm 34780 2
l2cap 21380 5 rfcomm
hci_usb 9664 6
bluetooth 43812 15 rfcomm,l2cap,hci_usb
bcm203x 4416 0
firmware_class 7616 1 bcm203x
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&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-04-20 9:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-18 21:21 [Bluez-users] Compile bluez-bluefw-1.0 fails Dirk Vornheder
2004-04-18 21:55 ` Marcel Holtmann
2004-04-19 8:35 ` Alex Holland
2004-04-19 10:23 ` Marcel Holtmann
2004-04-19 13:19 ` Alex Holland
2004-04-19 13:30 ` Marcel Holtmann
2004-04-19 13:41 ` Alex Holland
2004-04-19 13:54 ` Marcel Holtmann
2004-04-19 15:39 ` Alex Holland
2004-04-19 16:12 ` Marcel Holtmann
2004-04-19 17:22 ` Alex Holland
2004-04-19 17:52 ` Simone Gotti
2004-04-19 20:21 ` Alex Holland
2004-04-20 9:28 ` Alex Holland [this message]
2004-04-20 11:56 ` 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=200404201028.08718.ah160@student.cs.york.ac.uk \
--to=ah160@student.cs.york.ac.uk \
--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