Bluetooth kernel modules successfully built!
Thanks for your clarification, I stand corrected. That should teach me about assuming... I'll see what I can do, but it's not easy without a testing device 
@Tornankan & akeake: (I'll continue in English since I know there's a a few ppl watching this thread from .fi, and they may be interested too). Thanks for your work so far! I will leave the actual GPS software work up to you to experiment with (if/when we get that far), and concentrate on the actual Bluetooth support myself. Without you, I never would have gotten around to it however, so thanks again!
I've had some luck compiling Bluetooth support as modules. They all load properly now (I had to patch the source since one kernel symbol was not exported, this seems to be a well-known bug). Personally, I feel the most exciting news is that the kernel modules I compiled work at all and load without complaining, that opens up a lot of possibilities... But, back on topic:
I have tested loading the modules with no bad side effects, but of course this is experimental work (backup everything as usual...). I've uploaded the kernel modules for Bluetooth support + device specific drivers together with a really simple scripts that just loads all of them, and logs output so we can see if the bluetooth dongle is found. (The script looks like this, if anyone wonders. Very basic.)
Right now I have no bluetooth USB dongle available (will have to look for it later), but it would be useful if you who have one would test this. Basically, I'm hopinh the kernel will find the bluetooth adapter as the driver loads. There is no user interface yet to do actual pairing, should it work. Also, userland modifications will be needed (bluetoothd missing for instance). But, if this part works the rest should be OK, I think.
So, some simple steps to perform to help me test (nothing you do here is permanent - if it crashes, just do the usual reset and you should be fine):
- Download twk-bt-kernel-modules.zip
- Unpack the zip file. Inside is a folder called "btmod".
- Connect the M7/7CK100 to the computer (USB) and copy the entire folder to the internal flash disk (not sdcard, since the script uses /flash). No "firmware flashing", just normal file copy!
- (Safely) disconnect the tablet from the computer
- Connect Bluetooth USB "dongle"
- Start a shell (Betterterm)
- Type: su + enter to become root
- Type: busybox sh /flash/btmod/loadmods.sh + enter
- Some text appears (end of the kernel log).
- Done! 
Connect the tablet to the computer again, and check the flash drive. 3 files have been created:
- bt-insmod.log: This should be empty (0 bytes). If not, please post the contents!
- dmesg-system.log: The kernel log before any modules were loaded. There may be a hint in this at the last lines when you plugged the BT dongle in. Not very interesting, for now.
- bt-dmesg.log: This is also the kernel log, but only stuff from the bluetooth subsystem modules + driver modules loading. It's the same displayed at the shell prompt. It looks like this when no bluetooth dongle is attached while executing the script:
Kod:
[147] Bluetooth: Core ver 2.11
[147] NET: Registered protocol family 31
[147] Bluetooth: HCI device and connection manager initialized
[147] Bluetooth: HCI socket layer initialized
[147] Bluetooth: L2CAP ver 2.9
[147] Bluetooth: L2CAP socket layer initialized
[147] Bluetooth: BNEP (Ethernet Emulation) ver 1.2
[147] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[147] Bluetooth: Broadcom Blutonium firmware driver ver 1.1
[147] usbcore: registered new interface driver bcm203x
[147] Bluetooth: BlueFRITZ! USB driver ver 1.1
[147] usbcore: registered new interface driver bfusb
[148] Bluetooth: Digianswer Bluetooth USB driver ver 0.9
[148] usbcore: registered new interface driver bpa10x
[148] Bluetooth: HCI USB driver ver 2.9
[148] usbcore: registered new interface driver hci_usb
If your output differs (except for the [xxx]), something was probably found. Please post output! If not, please list the brand and model of the bluetooth USB stick you are testing. Also check the later part of dmesg-system.log for hints.
I'll update when I have something new.. And, as always: All help is very welcome!
Have fun for now 
EDIT: I forgot to log output from "lsmod" in the script, to verify modules in fact did load. You can type it manually from the prompt after running the script. To send output to a file, execute something like "lsmod > /flash/lsmod.log"
You should see something like this:
Kod:
# lsmod
hci_usb 12380 0 - Live 0xbf02c000
bpa10x 6308 0 - Live 0xbf029000
bfusb 9956 0 - Live 0xbf025000
bcm203x 4804 0 - Live 0xbf022000
hidp 14912 0 - Live 0xbf01d000
bnep 11104 0 - Live 0xbf019000
l2cap 31204 2 hidp,bnep, Live 0xbf010000
bluetooth 52196 6 hci_usb,bpa10x,bfusb,hidp,bnep,l2cap, Live 0xbf002000
wlan 1600 0 - Live 0xbf000000
#