Letux Kernel

Wireless

You are looking at an old revision of the page Wireless. This revision was created by Christoph Mair.

Table of Content

How to configure wireless interfaces (UMTS, WLAN, Bluetooth)

WLAN

is configured as SDIO card "mmc1".

Driver: Marvel 8686 (libertas) Firmware: sd8686.bin

Power and Reset

echo "255" >/sys/class/leds/tca6507:6/brightness # activate reset
echo "2800000" >/sys/devices/platform/reg-virt-consumer.4/max_microvolts
echo "2800000" >/sys/devices/platform/reg-virt-consumer.4/min_microvolts
echo "normal" >/sys/devices/platform/reg-virt-consumer.4/mode
echo "0" >/sys/class/leds/tca6507:6/brightness # release reset

Disable power:

echo "255" >/sys/class/leds/tca6507:6/brightness # activate reset
echo "0" >/sys/devices/platform/reg-virt-consumer.4/max_microvolts

Configure

Driver should be loaded automatically after enabling power. If not, run

depmod -a
modprobe libertas_sdio
FIXME: we need to notify the MMC driver to detect MMC1

Then:

iwconfig wlan0 
ifconfig wlan0 up
iwlist wlan0 scan

Create an ad-hoc network

On the phone run:

ifconfig wlan0 up
iwconfig wlan0 mode ad-hoc essid GTA04 enc off channel 6
ifconfig wlan0 10.1.1.1

On a laptop run:

ifconfig wlan0 up
iwconfig wlan0 mode ad-hoc essid GTA04 enc off
ifconfig wlan0 10.1.1.2

Now they should be connected. To verify this try to ping each other.

The call to iwconfig will search for a network with the specified essid and join it. If none is found, a new one will be created. You can check if the devices are connected to the same network by comparing the cell address which can be displayed with 'iwconfig wlan0'.

Depending on the chipsets the syntax may be slightly different. Try 'enc none' if 'off' does not work.

Bluetooth

is accessed through UART1 (/dev/ttyS0).

Enable power

see section WLAN above (power is shared)

Configure

Attach to UART1 as HCI interface

hciattach -n -s 115200 /dev/ttyS0 any 115200 flow & sleep 2
hciconfig -a
hciconfig hci0 up; sleep 2
hciconfig hci0 name GTA04
hcitool dev
hcitool scan

WWAN

is connected to the internal HS-USB. Use lsusb to identify.

Needs Option HSO-kernel driver module.