Panda How to kernel 3 1 rcx

Introduction
Continuing Happy 20th Birthday Greetings to Linux!! The merge window for 3.1 is over and the 3.1-rc1 kernel has been released. Lots of work on the omap platforms and on pandaboard. Let's see what -rc1 has brought.

rc1
There is still an issue with the setting up of the wl12xx:

[   0.181457] error setting wl12xx data

The extremely simple workaround available for 3.0, moved to twl_common.c in -rc1, doesn't produce the working wlan as in 3.0. But applying that to the -rc2 code does result in a functional wl12xx driver.

More to come as these issue are investigated.

rc2
Yep, -rc2 is out and I haven't had the time to fiddle much with it as yet, on to -rc3. In short, -rc2 fixes some of the wl12xx issues, but still requires a patch to function. There is still an unresolved start up issue with wl12xx, in that sometimes it will work, sometimes, not. Same kernel, MLO, & u-boot and userspace.

rc3
-rc3 is out and there are no OMAP or Panda changes. However there is a boot issue with Panda as described here: https://lkml.org/lkml/2011/8/25/117

This issue has been resolved, so be sure to get this commit or later from git: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=69dd3d8e29e294caaf63eb5e8a72d250279f9e5f

rc4
-rc4 has been released and yet again there are no OMAP or Panda changes. The issue introduced in -rc3 noted above, has been resolved.

If you build the wl12xx driver as a module, and modprobe it, the wlan seems to start up fine every time, must be some sort of race when it is compiled into the kernel.

wlan12xx patch
This patch is necessary to resolve the issue noted in 3.0 and 3.1-rc1 above, however the code has moved to twl_common.c and so an new patch is presented here.

[[Media:0001a-omap4-pandaboard-wlan-fix.patch|0001a-omap4-pandaboard-wlan-fix.patch]]

Apply it like so: (from inside the kernel sources directory)

patch -p1 < 0001a-omap4-pandaboard-wlan-fix.patch

DVI Patch
This patch is necessary to make 720p resolution available.

[[Media:0003-omap4-pandaboard-dvi720p.patch|0003-omap4-pandaboard-dvi720p.patch]]

Apply it like so: (from inside the kernel sources directory)

patch -p1 < 0001-omap4-pandaboard-dvi720p.patch

Then use either of the following configs

make ARCH=arm omap2plus_defconfig or make ARCH=arm panda_dvi_defconfig

Compile as above.

I2C Patch
i2c character device driver

Ever since 2.6.38, the i2c character device driver support from user space has been broken for OMAP44xx. * A fix has been submitted for the linux-omap-2.6 branch, but it may be a while till it gets into an -rcx. See http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commit;h=39fe1a6fafe1e85c183379af9f3ceda7cd24bd65 for the commit. * A quick fix for this issue is available

Apply it like so: (from inside the kernel sources directory)

patch -p1 < Omap44xx-i2c-fix.patch

Compile as above.

Building
Building 3.1-rc1 or -rc2 is basically the same as How to build 2.6.38 kernel, but of course you need the 3.1-rc1/rc2 sources. The omap2plus_defconfig works and illustrates the wl12xx issue, with or without a patch to twl_common.c. [[Media:config.3.1-rc1.1|config.3.1-rc1.1]] works with the dvi patch and i2c patch.

Building 3.1-rc4 is a bit different if you want to have a working wlan.

In order to ensure that the wlan starts up consistently, it is recommended that the wl12xx driver be built as a module and started after the PandaBoard has booted.

Grab the 3.1-rc4 sources and use [[Media:config.3.1-rc4.1|config.3.1-rc4.1]] as the .config (this requires you patch the dvi & i2c as above)

Then compile loke so:

make ARCH=arm CROSS_COMPILE=Path_to_your/arm-2010q1/bin/arm-none-linux-gnueabi- uImage

Then compile the modules like so:

make ARCH=arm CROSS_COMPILE=/home/kenm/Panda/arm-2010q1/bin/arm-none-linux-gnueabi- modules

"Install" the modules to somewhere convenient:

make ARCH=arm CROSS_COMPILE=/home/kenm/Panda/arm-2010q1/bin/arm-none-linux-gnueabi- INSTALL_MOD_PATH=../testlib_omap modules_install

Copy lib/modules/3.1.0-rc4-dirty/ to your SD card (as root), boot up the Pandaboard.

fbtest on DVI Port
After booting run fbtest to see a nice test pattern from the dvi port.



Switching primary display to the HDMI port
Make sure that a monitor is plugged into the HDMI port before doing the following:

echo "1" > /sys/devices/platform/omapdss/display1/enabled echo "0" > /sys/devices/platform/omapdss/overlay0/enabled echo "tv" > /sys/devices/platform/omapdss/overlay0/manager echo "1" > /sys/devices/platform/omapdss/overlay0/enabled
 * 1) Enable HDMI
 * 1) Disable overlay0 (an overlay must be disabled before changing its properties)
 * 1) Set the manager of overlay0 to display1 which is HDMI
 * 1) Enable overlay0

And content on overlay 0 of primary lcd would be transferred to HDMI. It works similarly for all other overlay's.

Switching primary display to the DVI port
See: http://omappedia.org/wiki/Bootargs_for_enabling_display for lots of useful info on the display subsystem. Be aware that the display, manager and overlay numbers don't match the panda configuration.

Make sure that a monitor is plugged into the DVI port before doing the following:

echo "0" > /sys/devices/platform/omapdss/display1/enabled echo "0" > /sys/devices/platform/omapdss/overlay0/enabled echo "lcd2" > /sys/devices/platform/omapdss/overlay0/manager echo "1" > /sys/devices/platform/omapdss/overlay0/enabled
 * 1) Disable HDMI
 * 1) Disable overlay0 (an overlay must be disabled before changing its properties)
 * 1) Set the manager of overlay0 to display0 which is DVI
 * 1) Enable overlay0

The above commands should be run from the serial console and the cable should be in the destination port before running the commands.

fbtest on HDMI Port
Run fbtest to see a nice test pattern from the HDMI port.



i2cdetect
You can run i2cdetect and the results should look like this:

0 1  2  3  4  5  6  7  8  9  a  b  c  d  e  f 00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  40: -- -- -- -- -- -- -- -- UU UU UU UU -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  70: -- -- -- -- -- -- -- --
 * 1) i2cdetect -y -r 1

wlan
Run the following commands after the PandaBoard is booted:

modprobe wl12xx_sdio ifconfig wlan0 up iwconfig wlan0 essid "Your AccessPoint Name" udhcpc -i wlan0

If your network is set up to provide DHCP services, the PandaBoard will get all the "right stuff(tm)" and you will be able to access the Internet.

PING www.google.com (74.125.73.99): 56 data bytes 64 bytes from 74.125.73.99: seq=0 ttl=43 time=62.683 ms 64 bytes from 74.125.73.99: seq=1 ttl=43 time=54.077 ms 64 bytes from 74.125.73.99: seq=2 ttl=43 time=51.484 ms 64 bytes from 74.125.73.99: seq=3 ttl=43 time=54.108 ms
 * 1) ping www.google.com