[Galaxy Note 10.1 General] X-Stranger:
Well, there are some thoughts of rolling out something ready for use, but need to find time for this. But even having this done you will be still required to change some settings and be able to run a few utilities by yourself.

Okay, below is how to bring up WiFi and Bluetooth.

As soon as you boot to Linux, you need to get original wireless devices firmware from system partitions and compile "brcm_patchram_plus" utility from sources found on the Internet. I've already done this for you, so you can download it from attachment (you could also try the firmware files from "linux-firmware" package from your Linux distribution - hopefully it contains appropriate stuff). Unpack the content of firmware.tar.gz to /opt. There are 2 folders: wifi and bluez. So, to start WiFi first we need to load wireless module with proper parameters, then use "wpa_supplicant" (please install if you don't have it) to connect to hotspot:

insmod /lib/modules/3.0.31/kernel/drivers/net/wireless/bcmdhd/dhd.ko op_mode=0 firmware_path=/opt/wifi/bcmdhd_sta.bin nvram_path=/opt/wifi/nvram_net.txt_murata
ip link set wlan0 up
wpa_supplicant -B -i wlan0 -Dwext -c /etc/wpa_supplicant/wpa_supplicant.conf
ip addr add 192.168.1.33/24 dev wlan0
ip route add default via 192.168.1.1
echo "nameserver 8.8.8.8" > /etc/resolv.conf
echo "nameserver 8.8.4.4" >> /etc/resolv.conf

Those lines can be added to /etc/rc.local, so you'll get the network automatically connected on boot. Also, kernel module settings can be moved to /etc/modprobe.d/dhd.conf file. Please note that you should update network settings appropriately, and below is an example of /etc/wpa_supplicant/wpa_supplicant.conf file:

ctrl_interface=/var/run/wpa_supplicant
eapol_version=1

network={
ssid="HomeSweetHome"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
psk="p@ssw0rd"
}

If your hotspot provides DHCP service, you might want to use "dhcpcd" program to obtain IP address automatically, instead of setting it in script above.

Bluetooth is almost the same: we must load firmware file. But also a bit tricky: it does not work properly due to some problems with memory management, so we should use "valgrind" utility to make it running (please install it and "bluez" packages if you don't have it yet). The next thing - we need to get your bluetooth address file:

mount /dev/mmcblk0p3 /srv
cp -f /srv/bluetooth/bt_addr /opt/bluez/
umount /srv

Next run this:

nohup /opt/bluez/brcm_patchram_plus --bd_addr `cat /opt/bluez/bt_addr` --enable_hci --enable_lpm --no2bytes --tosleep 50000 --baudrate 4000000 --use_baudrate_for_download --patchram /opt/bluez/bcm4334.hcd --i2s=1,0,0,0 /dev/ttySAC0 >/dev/null 2>&1 &
nohup /usr/bin/valgrind /usr/sbin/bluetoothd --noplugin=mgmr >/dev/null 2>&1 &

This will load firmware with special settings and bring up bluetooth daemon via valgrind with "mgmr" module disabled. Those lines can be also added to /etc/rc.local (but for some reason it does not work for me from here, so every time I need to run in manually when want to use bluetooth). Now you can pair your wireless keyboard and mouse using "bluez-simple-agent" utility for example.

As for me, WiFi works stable, but bluetooth is buggy, and sometimes gave me kernel panic on system reboot. Probably this can be fixed with some kernel patches - feel free to post any if you are the expert in this ;)