Panda How to kernel 3 3 rcx - Revision history

KenMcGuire at 00:49, 13 March 2012

2012-03-13T00:49:06Z

KenMcGuire at 00:39, 13 March 2012

2012-03-13T00:39:12Z

Bgamari: Add note about UART crash with devicetree

2012-03-01T21:24:42Z

Add note about UART crash with devicetree

KenMcGuire at 02:03, 19 February 2012

2012-02-19T02:03:17Z

KenMcGuire at 01:07, 19 February 2012

2012-02-19T01:07:59Z

KenMcGuire at 17:31, 3 February 2012

2012-02-03T17:31:37Z

KenMcGuire: Created page with "== Introduction == The merge window for 3.3 is over and we are currently at v3.3-rc1. Lots of work on the OMAP platforms and on Pandaboard. Let's see what the various release can..."

2012-01-23T00:14:29Z

Created page with "== Introduction == The merge window for 3.3 is over and we are currently at v3.3-rc1. Lots of work on the OMAP platforms and on Pandaboard. Let's see what the various release can..."

New page

== Introduction ==
The merge window for 3.3 is over and we are currently at v3.3-rc1.
Lots of work on the OMAP platforms and on Pandaboard. Let's see
what the various release candidates have provided.

You can download a tarball of the mainline kernel at http://kernel.org/

or you can clone a copy of mainline kernel with:

<pre>
git clone http://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
cd linux
git checkout v3.3-rcx
</pre>

where x is the release candidate version.

== rc1 ==

The WLAN still requires a patch. The WL12xx driver needs current firmware, and the same patch as used for 3.1 and 3.2 works. When the driver isn't happy, the error messages are somewhat less than useful, however the drivers/firmware are being constantly improved and it would not be a good idea to have the driver support anything but the latest firmware. Still a work in progress.

== PandaBoard ES ==

There is now a PandaBoard ES http://pandaboard.org/content/pandaboard-es which includes an OMAP 4460 at up to 1.2GHz. Several important differences make it important (at the present time) that the [[PandaBoard_ES_uboot_howto| MLO/u-boot be specifically crafted for the 4460]]. The thermal management is not in the mainline 4430 code as yet and therefore the max clock frequency when running the OMAP4460 on the PandaBoard ES with the mainline kernel is 920MHz(same as the OMAP4430).

== wlan12xx ==
The latest wlan firmware is available from git: git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git just copy the contents of the ti-connectivity folder to /lib/firmware/ti-connectivity.

This patch is still necessary to resolve the issue noted in 3.0, 3.1 and 3.2.

[[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

== I2C Patch ==
i2c character device driver patch that has been necessary is no longer required, and the issues from kernel 3.2 have been resolved.

== Building ==
Building 3.3-rc1 is a bit different from previous How-To's 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.3-rc1 sources and use [[Media:config.3.3-rc1.1|config.3.3-rc1.1]] as the .config (you should apply the above patch)

This .config enables Sound so the resulting kernel will be a bit bigger than previously.

Then compile like 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.3.0-rc1-dirty/ to your SD card (as root), boot up the Pandaboard.

== Testing ==

=== fbtest on DVI Port ===

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

[[File:fbtest.jpg|240px]]

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

# Enable HDMI
echo "1" > /sys/devices/platform/omapdss/display1/enabled

# Disable overlay0 (an overlay must be disabled before changing its properties)
echo "0" > /sys/devices/platform/omapdss/overlay0/enabled

# Set the manager of overlay0 to display1 which is HDMI
echo "tv" > /sys/devices/platform/omapdss/overlay0/manager

# Enable overlay0
echo "1" > /sys/devices/platform/omapdss/overlay0/enabled

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:

# Disable HDMI
echo "0" > /sys/devices/platform/omapdss/display1/enabled

# Disable overlay0 (an overlay must be disabled before changing its properties)
echo "0" > /sys/devices/platform/omapdss/overlay0/enabled

# Set the manager of overlay0 to display0 which is DVI
echo "lcd2" > /sys/devices/platform/omapdss/overlay0/manager

# Enable overlay0
echo "1" > /sys/devices/platform/omapdss/overlay0/enabled

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.

[[File:fbtest2.jpg|240px]]

=== i2cdetect ===

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

# i2cdetect -y -r 1
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: -- -- -- -- -- -- -- --

=== 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
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

=== USB Performance ===

Insert a USB memory stick into one of the usb ports

Run dmesg to see what sdx the stick was recognised as, then:

hdparam -tT /dev/sdx

If you did this on a kernel without the patch you will see some improvement, if you run the same command on a desktop Linux system, with the same USB memory stick, the PandaBoard's speed should roughly be the same.

[[Category:PandaBoard]]

@@ Line 46: / Line 46: @@
 The WL12xx driver still needs the same patch as used for 3.1 and 3.2. when the driver isn't happy, the error messages are somewhat less than useful, however the drivers/firmware are being constantly improved and it would not be a good idea to have the driver support anything but the latest firmware.
 == PandaBoard ES ==
@@ Line 64: / Line 65: @@
 The latest wlan firmware is available from git: git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git just copy the contents of the ti-connectivity folder to /lib/firmware/ti-connectivity.
-The patch is no longer necessary for the PandaBoard ES but does not seem to hurt if applied. In addition, the race issue that required building as a module has been resolved. As part of the code cleanup, the wl12xx and wl12xx_sdio drivers no longer depend on each other. This creates an issue with systems that do not use udev or mdev (with as somewhat fiddly & slow script) to load MODALIAS drivers. The quick solution is to modprobe both, the order no longer matters. Just modprobing wl12xx_sdio will no longer automatically load wl12xx. For this How To, we will build the drivers into the kernel.
+The patch is no longer necessary for the PandaBoard ES but does not seem to hurt if applied. In addition, the race issue that required building as a module has returned as of -rc2. As part of the code cleanup, the wl12xx and wl12xx_sdio drivers no longer depend on each other. This creates an issue with systems that do not use udev or mdev (with as somewhat fiddly & slow script) to load MODALIAS drivers. The quick solution is to modprobe both, the order no longer matters. Just modprobing wl12xx_sdio will no longer automatically load wl12xx. It is suggested that these 2 drivers be built as modules.
 == I2C Patch ==

@@ Line 20: / Line 20: @@
 == rc1 ==
 The WLAN no longer requires a patch! The WL12xx driver needs current firmware. When the driver isn't happy, the error messages are somewhat less than useful, however the drivers/firmware are being constantly improved and it would not be a good idea to have the driver support anything but the latest firmware. Still a work in progress.
@@ Line 38: / Line 40: @@
 Devicetree-enabled kernels crash during boot due to the UART driver (http://www.spinics.net/lists/linux-omap/msg64921.html). A patch has been proposed and should be merged before release.
 == PandaBoard ES ==
@@ Line 44: / Line 52: @@
 == wlan12xx ==
 The latest wlan firmware is available from git: git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git just copy the contents of the ti-connectivity folder to /lib/firmware/ti-connectivity.
-The patch is no longer necessary to resolve the issue noted in 3.0, 3.1 and 3.2. In addition, the race issue that required building as a module has been resolved. As part of the code cleanup, the wl12xx and wl12xx_sdio drivers no longer depend on each other. This creates an issue with systems that do not use udev or mdev (with as somewhat fiddly & slow script) to load MODALIAS drivers. The quick solution is to modprobe both, the order no longer matters. Just modprobing wl12xx_sdio will no longer automatically load wl12xx. For this How To, we will build the drivers into the kernel.
+The patch is no longer necessary for the PandaBoard ES but does not seem to hurt if applied. In addition, the race issue that required building as a module has been resolved. As part of the code cleanup, the wl12xx and wl12xx_sdio drivers no longer depend on each other. This creates an issue with systems that do not use udev or mdev (with as somewhat fiddly & slow script) to load MODALIAS drivers. The quick solution is to modprobe both, the order no longer matters. Just modprobing wl12xx_sdio will no longer automatically load wl12xx. For this How To, we will build the drivers into the kernel.
 == I2C Patch ==

← Older revision		Revision as of 21:24, 1 March 2012
Line 37:		Line 37:
	issue error messages merely because a driver is not configured."		issue error messages merely because a driver is not configured."

		+	Devicetree-enabled kernels crash during boot due to the UART driver (http://www.spinics.net/lists/linux-omap/msg64921.html). A patch has been proposed and should be merged before release.

	== PandaBoard ES ==		== PandaBoard ES ==

@@ Line 15: / Line 15: @@
 where x is the release candidate version.
 == rc1 ==
@@ Line 21: / Line 24: @@
 == rc2 ==
 No PandaBoard changes, and with no patches required this is an easy release to build.
 == rc3 ==
+Skipped due to the HDMI changes which cropped up in 3.2-rc1
 == rc4 ==
 == PandaBoard ES ==
@@ Line 46: / Line 55: @@
 Grab the 3.3-rc1 or 3.3-rc2 sources and use [[Media:config.3.3-rc1.1|config.3.3-rc1.1]] or [[Media:config.3.3-rc2.1|config.3.3-rc2.1]] as the .config
-The 3.3-rc1 .config enables Sound builtin and wl12xx as modules and the 3.3-rc2 enables Sound and the wl12xx drivers builtin, so the resulting kernel will be a bit bigger than previously.
+The 3.3-rc1 .config enables Sound builtin and wl12xx as modules and the 3.3-rc2 enables Sound and the wl12xx drivers builtin, so the resulting kernel will be a bit bigger than previously. The builtin sound does not presently work, but the enabled configuration allows USB sound devices, which function properly.
 Then compile like so:
@@ Line 60: / Line 69: @@
 [[File:fbtest.jpg|240px]]
-=== Switching primary display to the HDMI port ===
+=== Switching primary display to the HDMI port  --> Currently not functional <-- ===
 Make sure that a monitor is plugged into the HDMI port before doing the following:
@@ Line 97: / Line 106: @@
 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 ===
+=== fbtest on HDMI Port --> Currently not functional <-- ===
 Run fbtest to see a nice test pattern from the HDMI port.

@@ Line 1: / Line 1: @@
 == Introduction ==
-The merge window for 3.3 is over and we are currently at v3.3-rc2.
+The merge window for 3.3 is over and we are currently at v3.3-rc4.
 Lots of work on the OMAP platforms and on Pandaboard as well as the wl12xx wlan driver . Let's see
 what the various release candidates have provided.
@@ Line 22: / Line 22: @@
 == rc2 ==
 No PandaBoard changes, and with no patches required this is an easy release to build.
 == PandaBoard ES ==

@@ Line 1: / Line 1: @@
 == Introduction ==
-The merge window for 3.3 is over and we are currently at v3.3-rc1.
+The merge window for 3.3 is over and we are currently at v3.3-rc2.
-Lots of work on the OMAP platforms and on Pandaboard. Let's see
+Lots of work on the OMAP platforms and on Pandaboard as well as the wl12xx wlan driver . Let's see
 what the various release candidates have provided.
@@ Line 18: / Line 18: @@
 == rc1 ==
-The WLAN still requires a patch. The WL12xx driver needs current firmware, and the same patch as used for 3.1 and 3.2 works. When the driver isn't happy, the error messages are somewhat less than useful, however the drivers/firmware are being constantly improved and it would not be a good idea to have the driver support anything but the latest firmware. Still a work in progress.
+The WLAN no longer requires a patch! The WL12xx driver needs current firmware. When the driver isn't happy, the error messages are somewhat less than useful, however the drivers/firmware are being constantly improved and it would not be a good idea to have the driver support anything but the latest firmware. Still a work in progress.
 == PandaBoard ES ==
 There is now a PandaBoard ES http://pandaboard.org/content/pandaboard-es which includes an OMAP 4460 at up to 1.2GHz. Several important differences make it important (at the present time) that the [[PandaBoard_ES_uboot_howto| MLO/u-boot be specifically crafted for the 4460]]. The thermal management is not in the mainline 4430 code as yet and therefore the max clock frequency when running the OMAP4460 on the PandaBoard ES with the mainline kernel is 920MHz(same as the OMAP4430).
 == wlan12xx ==
 The latest wlan firmware is available from git: git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git just copy the contents of the ti-connectivity folder to /lib/firmware/ti-connectivity.
-This patch is still necessary to resolve the issue noted in 3.0, 3.1 and 3.2.
+The patch is no longer necessary to resolve the issue noted in 3.0, 3.1 and 3.2. In addition, the race issue that required building as a module has been resolved. As part of the code cleanup, the wl12xx and wl12xx_sdio drivers no longer depend on each other. This creates an issue with systems that do not use udev or mdev (with as somewhat fiddly & slow script) to load MODALIAS drivers. The quick solution is to modprobe both, the order no longer matters. Just modprobing wl12xx_sdio will no longer automatically load wl12xx. For this How To, we will build the drivers into the kernel.
-−
-[[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
 == I2C Patch ==
@@ Line 40: / Line 36: @@
 == Building ==
-Building 3.3-rc1 is a bit different from previous How-To's if you want to have a working wlan.
+Building 3.3-rc1 or -rc2 is fairly straight forward.
-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.3-rc1 or 3.3-rc2 sources and use [[Media:config.3.3-rc1.1|config.3.3-rc1.1]] or [[Media:config.3.3-rc2.1|config.3.3-rc2.1]] as the .config
-Grab the 3.3-rc1 sources and use [[Media:config.3.3-rc1.1|config.3.3-rc1.1]] as the .config (you should apply the above patch)
+The 3.3-rc1 .config enables Sound builtin and wl12xx as modules and the 3.3-rc2 enables Sound and the wl12xx drivers builtin, so the resulting kernel will be a bit bigger than previously.
-−
-This .config enables Sound so the resulting kernel will be a bit bigger than previously.
 Then compile like so:
   make ARCH=arm CROSS_COMPILE=Path_to_your/arm-2010q1/bin/arm-none-linux-gnueabi- uImage
 == Testing ==
@@ Line 133: / Line 116: @@
 Run the following commands after the PandaBoard is booted:
-  modprobe wl12xx_sdio
+ modprobe wl12xx    ** only if you built the wl12xx drivers as modules
   ifconfig wlan0 up
   iwconfig wlan0 essid "Your AccessPoint Name"