New Bluetooth Drivers, For Sharp ROMs using 2.4.18 kernel Options

[tumnus]

I've finally got around to updating the Bluetooth BlueZ driver ipk.

This is only for Sharp ROMs and variants of Sharp ROMs, excluding Cacko ROMs, that use the 2.4.18 kernel. So for example this includes Sharp ROMs on SL-5500, SL-5600, SL-6000, SL-C850, but NOT SL-3000.

Here's some of the improvements:

• Ambicom BT2000C Support. Thanks to tetron for spotting this had been included in the latest drivers. EDIT: Actually it doesn't look like this is working
• Socket Card Rev G Support without requiring the extra bluez-csr-serial ipk. Thanks to maslovsky for sorting this out
• Hopefully Dlink, Mavin, Billionton, BrainBoxes, and Dell cards should all be supported 'out of the box'
• Should work 'out of the box' on the SL-6000. (It moves /etc/pcmcia.bm3.conf out of the way on installation and back again on removal) Thanks to DrWowe for spotting what was wrong previously
• EDIT: Included hci_usb driver would should allow SL-6000L owners to use USB Bluetooth dongles with the appropriate USB cable.

EDIT: The PAN profile should be working now as I resolved a kernel module problem.

Before installing the new ipk, backup your files under /etc/bluetooth and /etc/pcmcia/peers. Then you can easily restore them after installing the new ipk. (You will need to run '/etc/rc.d/init.d/bluetooth restart' after restoring rfcomm.conf and hcid.conf)

Also uninstall all bluez packages before installing this one, including the bluez-csr-serial, which is no longer required with the new package.

So here is the new ipk (Note: the 1st, 3rd and 4th underscores [_] in the filename need to be changed to dashes [-] after downloading):

This post has been edited by tumnus: Feb 28 2005, 08:26 AM

Attached File(s)

 bluez_zaurus_2.13_2.4.18_alpha3_arm.ipk ( 310.9K ) Number of downloads: 3135

 

[pakman]

Hi Tumnus,

Finally got around to trying the new bluez-zaurus packages, and it works! I deinstalled the old bluez-zaurus, susp-resume-bluez and bluez-csr-serial packages (after carefully making copies of all the files involved so I wouldn't lose my hacks - I used 'ipkg files ...' to help with this).

I installed the new bluez-zaurus package, copied my previous /etc/bluetooth/rfcomm.conf and /etc/bluetooth/hcid.conf back, and everything worked! (Pairings were still OK because this procedure doesn't touch /etc/bluetooth/link_key.) The name of the card now correctly appears when inserted or when I tap the eject icon. More importantly, when the Z is suspended, I only have to do a 'cardctl resume', and after a second or two, 'hciconfig' shows that the interface is up again - this is a real advance over the previous state of affairs where the interface stayed obstinately down unless I did '/etc/rc.d/init.d/bluetooth stop' followed by '/etc/rc.d/init.d/bluetooth start' . Unlike sornett, I didn't have to do an eject/insert to get this to work.

I haven't tried the new susp-resume scripts yet, because being paranoid I would rather leave the card suspended and explicitly enable it when I need it My own scripts are pretty trivial now - a one-liner to start using the card, and a couple of lines to shut down any running PAN's before suspending the card when I have finished.

Many thanks to you and Maslovsky for sorting this out,
P.