Hi,
I've not tried it with Cacko, but the same principle should apply.
The simplest, lowest propellor factor method I can think of getting you going is this:
1)Run the terminal/console app
2) Type (enter after each one)
su
3) Type:
cp /etc/pcmcia/bluetooth.conf /home/zaurus/Documents
then:
cp /etc/bluetooth/uart /home/zaurus/Documents
4) Hook your zaurus up to a PC/Mac, browse the internal disc, and use a text editor to edit the bluetooth.conf file. What you are looking for is a line that contains the product info string your card has. I suspect it's not there, or if it is, it is missing the underscore characters.
so you may find a pair of lines:
card "AmbiCom BT2000C Bluetooth CF Card"
version "AmbiCom BT2000C", "Bluetooth PC/CF Card", "", ""
then copy them and paste a new copy and edit it to read:
card "AmbiCom BT2000C Bluetooth CF Card"
version "AmbiCom_BT2000C", "Bluetooth_PC/CF_Card", ""
if there isn't one like that, just paste this one in.
5) Do the same again, but this time edit the 'uart' file.
You need to edit the Ambicom line to read
"AmbiCom_BT2000C", "Bluetooth_PC/CF_Card", "":/dev/ttyS3 bt2000c flow
6) Go back to the terminal app and type:
cp /home/zaurus/Documents/uart /etc/bluetooth/
cp /home/zaurus/Documents/bluetooth.conf /etc/pcmcia/
7) reboot
With a following wind, that should be you up and running, unless...
I may be having more luck due to the version of bluez i'm running. We install a repackaged version of:
bluez-zaurus_2.12-2.4.20-alpha4_arm.ipk (posted elsewhere on these forums)
Which definitely has stuff in it to support the BT2000-CF. Maybe that's the key? Or maybe Mr Maslovsky has included that (or better) in Cacko?