On Thu, Mar 10, 2011 at 12:28 PM, BiX <bixt...@gmail.com> wrote: > Using Gingerbread on OMAP 3530 > > For WiFi: > > 1. Build rt73 as loadable module. > 2. Added BOARD_WLAN_TI_STA_DK_ROOT in BoardConfig.mk to build > wlan_loader. > 3. Placed rt73usb.ko, rt2x00lib.ko & rt2x00usb.ko in /system/lib/ > modules. > 4. Placed rt73.bin in /system/etc/firmware. > > Locat: > I/WifiHW ( 973): Loading WiFi Modules > E/WifiHW ( 973): Cannot find driver rt73usb in proc > I/WifiHW ( 973): insmod > I/WifiHW ( 973): insmod > I/WifiHW ( 973): insmod > D/Tethering( 973): wlan0 is not a tetherable iface, ignoring > E/wlan_loader( 1316): Cannot open eeprom image file <./nvs_map.bin>: > No such file or directory > E/wlan_loader( 1316): init_driver() failed > I/WifiHW ( 973): rmmod > E/Tethering( 973): attempting to remove unknown iface (wlan0), > ignoring > E/WifiService( 973): Failed to load Wi-Fi driver. > > For Bluetooth: > > 1. Build HCI USB and HCI UART for kernel. > 2. Add to BoardConfig.mk: > BOARD_HAVE_BLUETOOTH := true > 3. Remove from $ANDROID/system/bluetooth/bluedroid/bluetooth.c: > if (set_bluetooth_power(1) < 0) goto out; > > > Once Bluetooth is ticked, this message will keep repeating 'E/ > bluetooth_ScoSocket.cpp( 1035): accept_work socket() failed: Protocol > not supported'. > I can scan with hcitool scan but if I try to l2ping, I'll get 'Can't > create socket: Protocol not supported'. > > Logcat: > I/bluedroid( 972): Starting hciattach daemon > I/bluedroid( 972): Starting bluetoothd deamon > E/BluetoothEventLoop.cpp( 972): event_filter: Received signal > org.freedesktop.DBus:NameAcquired from /org/freedesktop/DBus > E/BluetoothEventLoop.cpp( 972): event_filter: Received signal > org.bluez.Adapter:PropertyChanged from /org/bluez/1309/hci0 > D/BluetoothService( 972): Bluetooth state 11 -> 12 > V/BluetoothEventRedirector( 1289): Received > android.bluetooth.adapter.action.STATE_CHANGED > E/BluetoothAudioGateway.cpp( 1035): Can't create RFCOMM socket > E/BT Audio Gateway( 1035): Could not set up listening socket, exiting > E/bluetooth_ScoSocket.cpp( 1035): accept_work socket() failed: > Protocol not supported
You need to enable these in your kernel, # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_HAMRADIO is not set # CONFIG_CAN is not set # CONFIG_IRDA is not set CONFIG_BT=y CONFIG_BT_L2CAP=y # CONFIG_BT_L2CAP_EXT_FEATURES is not set CONFIG_BT_SCO=y CONFIG_BT_RFCOMM=y CONFIG_BT_RFCOMM_TTY=y # CONFIG_BT_BNEP is not set CONFIG_BT_HIDP=y > Things added to my init.rc: > > # wifi > mkdir /system/etc/wifi 0770 wifi wifi > chmod 0770 /system/etc/wifi > chmod 0660 /system/etc/wifi/wpa_supplicant.conf > chown wifi wifi /system/etc/wifi/wpa_supplicant.conf > > #bluetooth power up/down interface > chown bluetooth bluetooth /sys/class/rfkill/rfkill0/type > chown bluetooth bluetooth /sys/class/rfkill/rfkill0/state > chmod 0660 /sys/class/rfkill/rfkill0/state > > setprop wifi.interface wlan0 > setprop wlan.driver.status ok > > service wlan_loader /system/bin/wlan_loader > disabled > oneshot > > service ifcfg_ralink /system/bin/ifconfig wlan0 up > disabled > oneshot > > service wpa_supplicant /system/bin/wpa_supplicant -dd -Dwext -iwlan0 - > c /system/etc/wifi/wpa_supplicant.conf > group system wifi inet > disabled > oneshot > > service dhcpcd /system/bin/logwrapper /system/bin/dhcpcd -d wlan0 > disabled > oneshot > #group system dhcp > > service hciattach /system/bin/hciattach -l > user root > # changing user to root from bluetooth is a potential security issue > # service hciattach_legacy is used instead of hciattach because, we > dont > # have nodes named ttyHS0 > group bluetooth net_bt_admin misc > disabled > oneshot > > on property:init.svc.wpa_supplicant=stopped > stop dhcpcd > > -- > unsubscribe: android-porting+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-porting > -- --Pavan Savoy -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting