* [Bluez-users] Re: bluetooth 1.2 and 2.0 dongles support
@ 2005-10-14 10:55 Esteban Monturus
2005-10-14 11:00 ` Marcel Holtmann
0 siblings, 1 reply; 2+ messages in thread
From: Esteban Monturus @ 2005-10-14 10:55 UTC (permalink / raw)
To: 'bluez-users@lists.sourceforge.net'
>Hi Esteban,
Hi Marcel,
>> I have some other questions about BlueZ I had forgotten to ask you, so
>> here they go:
>> 1. I would like to buy a 2.0+EDR dongle to use with BlueZ. I have visited
>> your "Bluetooth device features and revision information" page, but I
>> haven't found any one. Does BlueZ support Bluetooth 2.0+EDR?.
>yes. EDR is fully supported.
I have purchased Cellink BTA-6030 Class 1 Bluetooth 2.0 + EDR dongles
>> 2. I have a Cellink BTA-3120 dongle. Although Cellink says that it is
>> Bluetooth 1.2 compliant, when I use it with BlueZ, the HCI version I get
>> with hciconfig is 1.1. Is that wright?
>Send in the "hciconfig hci0 features" output.
EWS4:/ # hciconfig hci0 features
hci0: Type: USB
BD Address: 00:0A:94:11:77:F5 ACL MTU: 120:20 SCO MTU: 64:0
Features: 0xff 0xff 0x05 0x00 0x00 0x00 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park state> <RSSI> <channel quality> <SCO link> <HV2 packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <power control>
>> 3. I also have an old Belkin F8T001 dongle. When I plugged it BlueZ loaded
>> always some firmware stuff and it worked properly. My old version of BlueZ
>> had a bluez-bluefw-1.0-202 rpm packet. I think this is equivalent to the
>> new tarball bluez-firmware that I have downloaded from BlueZ's homepage and
>> installed, but the reality is that this dongle doesn't work anymore.
>Use bluez-firmware and the bcm203x kernel driver for the 2.6 kernels.
How do I use this driver? I have tried to load it with insmod and I get the following:
EWS4:~/paquetes_rpm # insmod /lib/modules/2.6.4-52-smp/kernel/drivers/bluetooth/bcm203x.ko
insmod: error inserting '/lib/modules/2.6.4-52-smp/kernel/drivers/bluetooth/bcm203x.ko': -1 Unknown symbol in module
At the same time the following lines appear in the /var/log/messages file:
Oct 14 12:38:07 EWS4 kernel: bcm203x: Unknown symbol release_firmware
Oct 14 12:38:07 EWS4 kernel: bcm203x: Unknown symbol request_firmware
>Regards
>Marcel
Esteban.
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: [Bluez-users] Re: bluetooth 1.2 and 2.0 dongles support
2005-10-14 10:55 [Bluez-users] Re: bluetooth 1.2 and 2.0 dongles support Esteban Monturus
@ 2005-10-14 11:00 ` Marcel Holtmann
0 siblings, 0 replies; 2+ messages in thread
From: Marcel Holtmann @ 2005-10-14 11:00 UTC (permalink / raw)
To: bluez-users
Hi Esteban,
> >> 2. I have a Cellink BTA-3120 dongle. Although Cellink says that it is
> >> Bluetooth 1.2 compliant, when I use it with BlueZ, the HCI version I get
> >> with hciconfig is 1.1. Is that wright?
>
> >Send in the "hciconfig hci0 features" output.
>
> EWS4:/ # hciconfig hci0 features
> hci0: Type: USB
> BD Address: 00:0A:94:11:77:F5 ACL MTU: 120:20 SCO MTU: 64:0
> Features: 0xff 0xff 0x05 0x00 0x00 0x00 0x00 0x00
> <3-slot packets> <5-slot packets> <encryption> <slot offset>
> <timing accuracy> <role switch> <hold mode> <sniff mode>
> <park state> <RSSI> <channel quality> <SCO link> <HV2 packets>
> <HV3 packets> <u-law log> <A-law log> <CVSD> <power control>
this is a Bluetooth 1.1 dongle.
> >> 3. I also have an old Belkin F8T001 dongle. When I plugged it BlueZ loaded
> >> always some firmware stuff and it worked properly. My old version of BlueZ
> >> had a bluez-bluefw-1.0-202 rpm packet. I think this is equivalent to the
> >> new tarball bluez-firmware that I have downloaded from BlueZ's homepage and
> >> installed, but the reality is that this dongle doesn't work anymore.
>
> >Use bluez-firmware and the bcm203x kernel driver for the 2.6 kernels.
>
> How do I use this driver? I have tried to load it with insmod and I get the following:
>
> EWS4:~/paquetes_rpm # insmod /lib/modules/2.6.4-52-smp/kernel/drivers/bluetooth/bcm203x.ko
> insmod: error inserting '/lib/modules/2.6.4-52-smp/kernel/drivers/bluetooth/bcm203x.ko': -1 Unknown symbol in module
>
> At the same time the following lines appear in the /var/log/messages file:
>
> Oct 14 12:38:07 EWS4 kernel: bcm203x: Unknown symbol release_firmware
> Oct 14 12:38:07 EWS4 kernel: bcm203x: Unknown symbol request_firmware
Load the firmware_class kernel module and place the firmware files
under /lib/firmware/
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-10-14 11:00 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-10-14 10:55 [Bluez-users] Re: bluetooth 1.2 and 2.0 dongles support Esteban Monturus
2005-10-14 11:00 ` Marcel Holtmann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox