Panda How to kernel 3 5 rcx - Revision history

KenMcGuire at 16:21, 16 July 2012

2012-07-16T16:21:47Z

KenMcGuire at 15:59, 8 July 2012

2012-07-08T15:59:29Z

KenMcGuire at 14:46, 1 July 2012

2012-07-01T14:46:53Z

KenMcGuire at 14:32, 1 July 2012

2012-07-01T14:32:19Z

KenMcGuire at 01:43, 1 July 2012

2012-07-01T01:43:15Z

KenMcGuire at 18:17, 25 June 2012

2012-06-25T18:17:04Z

Chris81: /* rc1 */

2012-06-04T19:19:20Z

‎rc1

Chris81: widow /* Introduction */

2012-06-04T19:14:38Z

widow - ‎Introduction

KenMcGuire at 19:26, 3 June 2012

2012-06-03T19:26:51Z

KenMcGuire at 19:08, 3 June 2012

2012-06-03T19:08:23Z

@@ Line 31: / Line 31: @@
 Several OMAP4 related changes, but not much, Closing in on the release according to Linus.
@@ Line 68: / Line 82: @@
 == Building ==
-Building 3.5-rc1/rc4/rc5/rc6 is fairly straight forward.
+Building 3.5-rc1/rc4/rc5/rc6/rc7 is fairly straight forward.
-Grab the 3.5-rc1/4/5/6 sources and use [[Media:config.3.5-rc1.1|config.3.5-rc1.1]], [[Media:config.3.5-rc4.1|config.3.5-rc4.1]], [[Media:config.3.5-rc5.1|config.3.5-rc5.1]] or [[Media:config.3.5-rc6.1|config.3.5-rc6.1]] as the .config
+Grab the 3.5-rc1/4/5/6/7 sources and use [[Media:config.3.5-rc1.1|config.3.5-rc1.1]], [[Media:config.3.5-rc4.1|config.3.5-rc4.1]], [[Media:config.3.5-rc5.1|config.3.5-rc5.1]], [[Media:config.3.5-rc6.1|config.3.5-rc6.1]] or [[Media:config.3.5-rc7.1|config.3.5-rc7.1]] as the .config
-The 3.5-rc1/4/5/6 .config enables Sound builtin and wl12xx as a single module. The builtin sound works, as does HDMI sound. Note that the HDMI monitor must be plugged in and enabled for the HDMI sound to work.
+The 3.5-rc1/4/5/6/7 .config enables Sound builtin and wl12xx as a single module. The builtin sound works, as does HDMI sound. Note that the HDMI monitor must be plugged in and enabled for the HDMI sound to work.
 Then compile like so:
@@ Line 81: / Line 95: @@
 === CPU Frequency Control ===
-The 3.5-rc5/6 .config also enables SmartReflex as well as OMAP frequency scaling. Default governor is set to performance so the CPU will come up at 1008MHz.
+The 3.5-rc5/6/7 .config also enables SmartReflex as well as OMAP frequency scaling. Default governor is set to performance so the CPU will come up at 1008MHz.
 Display the current cpu frequency.

@@ Line 27: / Line 27: @@
 -rc5 does not have any OMAP or PandaBoard specific changes.
 The WL12xx driver on a PandaBoard 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.
 With the modules built in, operation is not consistent. The PandaBoard ES does not need the patch.
 == PandaBoard ES ==
@@ Line 53: / Line 58: @@
 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 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 a 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.
 In -rc1 there is an issue with wl12xx_sdio building as a module, so the recommended way (as implememted in the .config) is to build wl12xx as a single module which includes wl12xx, wl12xx_sdio and wl12xx_core. This can then be modprobed on either PandaBoard (with patch) or PandaBoard ES.
@@ Line 58: / Line 67: @@
 == Building ==
-The 3.5-rc1/4/5 .config enables Sound builtin and wl12xx as a single module. The builtin sound works, as does HDMI sound. Note that the HDMI monitor must be plugged in and enabled for the HDMI sound to work.
+Building 3.5-rc1/rc4/rc5/rc6 is fairly straight forward.
 Then compile like so:
@@ Line 71: / Line 81: @@
 === CPU Frequency Control ===
-The 3.5-rc5 .config also enables SmartReflex as well as OMAP frequency scaling. Default governor is set to performance so the CPU will come up at 1008MHz.
+The 3.5-rc5/6 .config also enables SmartReflex as well as OMAP frequency scaling. Default governor is set to performance so the CPU will come up at 1008MHz.
 Display the current cpu frequency.

@@ Line 72: / Line 72: @@
 The 3.5-rc5 .config also enables SmartReflex as well as OMAP frequency scaling. Default governor is set to performance so the CPU will come up at 1008MHz.
 Display the current cpu frequency.
@@ Line 81: / Line 77: @@
   # cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
   1008000
 The cpu governor seems to work, and on 4430 get stats, but not on 4460 ie. all zeros.

@@ Line 81: / Line 81: @@
   # cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
   1008000
 === i2cdetect ===

@@ Line 23: / Line 23: @@
 -rc4 has a few omap4 related changes, but nothing specific to the PandaBoard.
@@ Line 54: / Line 58: @@
 == Building ==
-Building 3.5-rc1/rc4 is fairly straight forward.
+Building 3.5-rc1/rc4/rc5 is fairly straight forward.
-Grab the 3.5-rc1/4 sources and use [[Media:config.3.5-rc1.1|config.3.5-rc1.1]] or [[Media:config.3.5-rc4.1|config.3.5-rc4.1]] as the .config
+The 3.5-rc1/4/5 .config enables Sound builtin and wl12xx as a single module. The builtin sound works, as does HDMI sound. Note that the HDMI monitor must be plugged in and enabled for the HDMI sound to work.
-−
-The 3.5-rc1/4 .config enables Sound builtin and wl12xx as a single module. The builtin sound works, as does HDMI sound. Note that the HDMI monitor must be plugged in and enabled for the HDMI sound to work.
 Then compile like so:
@@ Line 66: / Line 69: @@
 == Testing ==
 === i2cdetect ===

@@ Line 19: / Line 19: @@
 Many changes in OMAP and Panda specific code since 3.4 was released. The HDMI, DVI interfaces both work under certain circumstances and properly read the EDID info from the monitor. HDMI sound is now functional. Changes to the WLAN code continue, and WLAN does function as well under the proper circumstances.
@@ Line 50: / Line 54: @@
 == Building ==
-Building 3.5-rc1 is fairly straight forward.
+Building 3.5-rc1/rc4 is fairly straight forward.
-Grab the 3.5-rc1 sources and use [[Media:config.3.5-rc1.1|config.3.5-rc1.1]] as the .config
+Grab the 3.5-rc1/4 sources and use [[Media:config.3.5-rc1.1|config.3.5-rc1.1]] or [[Media:config.3.5-rc4.1|config.3.5-rc4.1]] as the .config
-The 3.5-rc1 .config enables Sound builtin and wl12xx as a single module. The builtin sound works, as does HDMI sound.
+The 3.5-rc1/4 .config enables Sound builtin and wl12xx as a single module. The builtin sound works, as does HDMI sound. Note that the HDMI monitor must be plugged in and enabled for the HDMI sound to work.
 Then compile like so:
@@ Line 95: / Line 99: @@
 bytes from 74.125.73.99: seq=2 ttl=43 time=51.484 ms
 bytes from 74.125.73.99: seq=3 ttl=43 time=54.108 ms
 === USB Performance ===

@@ Line 18: / Line 18: @@
 === rc1 ===
-Many changes in OMAP and Panda specific code since 3.4 was released. The HDMI, DVI interfaces both work and under certain circumstances and properly read the EDID info from the monitor. HDMI sound is now functional. Changes to the WLAN code continue, and WLAN does function as well under the proper circumstances.
+Many changes in OMAP and Panda specific code since 3.4 was released. The HDMI, DVI interfaces both work under certain circumstances and properly read the EDID info from the monitor. HDMI sound is now functional. Changes to the WLAN code continue, and WLAN does function as well under the proper circumstances.
-The WL12xx driver on a PandaBoard 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.
+The WL12xx driver on a PandaBoard 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.
 With the modules built in, operation is not consistent. The PandaBoard ES does not need the patch.

@@ Line 1: / Line 1: @@
 == Introduction ==
-Kernel 3.5 merge widow has closed and 3.5-rc1 has been released.
+Kernel 3.5 merge window has closed and 3.5-rc1 has been released.
 You can download a tarball of the mainline kernel at http://kernel.org/

@@ Line 38: / Line 38: @@
   patch -p1 < 0001a-omap4-pandaboard-wlan-fix.patch
 The latest wlan firmware is available from git: git://git.kernel.org/?p=linux/kernel/git/firmware/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 returned. 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.
+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 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 a 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.
@@ Line 78: / Line 82: @@
 Run the following commands after the PandaBoard is booted:
-  modprobe wl12xx    ** only if you built the wl12xx drivers as modules
+  modprobe wl12xx    ** only if you built the wl12xx drivers a module as recommended
   ifconfig wlan0 up
   iwconfig wlan0 essid "Your AccessPoint Name"

@@ Line 9: / Line 9: @@
 git clone http://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
 cd linux
-git checkout v3.5-rc1
+git checkout v3.5-rcx
 </pre>
 ''' Important Note '''
-There has been a lot of work done on the HDMI interface and its related driver omapdrm. Between kernel 3.1 and 3.2-rc1 enough changed so that the Testing section on the HDMI interface is no longer correct. The hdmi init functions are no longer in arch/arm/mach_omap2/board-omap4panda.c. When this situation stabilises, the HDMI testing section below will be updated.
+There has been a lot of work done on the HDMI interface and its related driver omapdrm. Between kernel 3.1 and 3.2-rc1 enough changed so that the Testing section on the HDMI interface has been removed from this How-To. The HDMI testing section below will return when the code stabilises.
 === rc1 ===
-''' The following seems to be only true for the PandaBoard ES. Tests with a PandaBoard EA3 confirm that the patch is still needed '''
+Many changes in OMAP and Panda specific code since 3.4 was released. The HDMI, DVI interfaces both work and under certain circumstances and properly read the EDID info from the monitor. HDMI sound is now functional. Changes to the WLAN code continue, and WLAN does function as well under the proper circumstances.
-=== rc4 ===
+The WL12xx driver on a PandaBoard 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.
+With the modules built in, operation is not consistent. The PandaBoard ES does not need the patch.
-resolve nebulous 'Error setting wl12xx data' fix to PandaBoard. "This should be fixed properly for the next merge window so we don't
-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 was  merged into the release codebase.
-−
-=== rc7 ===
-−
 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.
-The race issue that required building as a module has returned and with the modules built in, operation is not consistant.
 == PandaBoard ES ==
@@ Line 41: / Line 31: @@
 == wlan12xx patch ==
-This patch is still necessary to resolve the issue noted in 3.0, 3.1 and 3.2, the code was moved to twl_common.c.
+This patch is still necessary to resolve the issue noted in 3.2 and earlier
 [[Media:0001a-omap4-pandaboard-wlan-fix.patch|0001a-omap4-pandaboard-wlan-fix.patch]]
@@ Line 49: / Line 39: @@
   patch -p1 < 0001a-omap4-pandaboard-wlan-fix.patch
-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 latest wlan firmware is available from git: git://git.kernel.org/?p=linux/kernel/git/firmware/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 returned. 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.
@@ Line 55: / Line 46: @@
 == Building ==
-Building 3.3 is fairly straight forward.
+Building 3.5-rc1 is fairly straight forward.
-Grab the 3.3 sources and use [[Media:config.3.3.1|config.3.3.1]] as the .config
+Grab the 3.5-rc1 sources and use [[Media:config.3.5-rc1.1|config.3.5-rc1.1]] as the .config
-The 3.3 .config enables Sound builtin and wl12xx as modules. The builtin sound does not presently work, but the enabled configuration allows USB sound devices, which function properly.
+The 3.5-rc1 .config enables Sound builtin and wl12xx as a single module. The builtin sound works, as does HDMI sound.
 Then compile like so:
@@ Line 67: / Line 58: @@
 == Testing ==
 === i2cdetect ===
@@ Line 136: / Line 79: @@
   modprobe wl12xx    ** only if you built the wl12xx drivers as modules
   ifconfig wlan0 up
   iwconfig wlan0 essid "Your AccessPoint Name"