Panda How to kernel 3 2 rcx - Revision history

KenMcGuire at 02:07, 19 February 2012

2012-02-19T02:07:01Z

KenMcGuire at 23:25, 24 December 2011

2011-12-24T23:25:03Z

RobDay: Fix some obvious typoes and update references to rc6. Probably more aesthetic fixes that can be done.

2011-12-21T22:54:50Z

Fix some obvious typoes and update references to rc6. Probably more aesthetic fixes that can be done.

KenMcGuire at 17:12, 17 December 2011

2011-12-17T17:12:36Z

Prpplague: /* PandaBoard-ES */

2011-12-13T17:17:10Z

‎PandaBoard-ES

KenMcGuire at 16:56, 10 December 2011

2011-12-10T16:56:10Z

Prpplague: /* Introduction */

2011-12-08T23:42:58Z

‎Introduction

KenMcGuire at 17:24, 3 December 2011

2011-12-03T17:24:49Z

KenMcGuire at 16:50, 24 November 2011

2011-11-24T16:50:12Z

KenMcGuire at 14:48, 17 November 2011

2011-11-17T14:48:57Z

@@ Line 15: / Line 15: @@
 where x is the release candidate version.
 == rc1 ==
@@ Line 115: / Line 119: @@
 [[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 152: / Line 156: @@
 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 39: / Line 39: @@
 There were no changes to PandaBoard related code in the -rc6 release. The same patches required for -rc1, -rc3, -rc4 & -rc5 work for the -rc6 sources, and the kernel works as well.
 == PandaBoard ES ==
@@ Line 81: / Line 85: @@
 == Building ==
-Building 3.2-rc1,3,4,5,6 is a bit different from previous How-To's if you want to have a working wlan.
+Building 3.2-rc1,3,4,5,6,7 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.2-rc1,3,4,5,6 sources and use [[Media:config.3.2-rc1.1|config.3.2-rc1.1]], [[Media:config.3.2-rc3.1|config.3.2-rc3.1]], [[Media:config.3.2-rc4.1|config.3.2-rc4.1]], [[Media:config.3.2-rc5.1|config.3.2-rc5.1]] or [[Media:config.3.2-rc6.1|config.3.2-rc6.1]] as the .config (you should apply all the above patches)
+Grab the 3.2-rc1,3,4,5,6,7 sources and use [[Media:config.3.2-rc1.1|config.3.2-rc1.1]], [[Media:config.3.2-rc3.1|config.3.2-rc3.1]], [[Media:config.3.2-rc4.1|config.3.2-rc4.1]], [[Media:config.3.2-rc5.1|config.3.2-rc5.1]], [[Media:config.3.2-rc6.1|config.3.2-rc6.1]] or [[Media:config.3.2-rc7.1|config.3.2-rc7.1]] as the .config (you should apply all the above patches)
 Then compile like so:
@@ Line 100: / Line 104: @@
 Copy lib/modules/3.2.0-rc1-dirty/ to your SD card (as root), boot up the Pandaboard.
-After 3.2-rc1, the kernel versioning was changed and the modules for -rc4,5,6 are now located in lib/modules/3.2.0-rc4-00002-gd3aebaf/ the last digits will change as the sources are edited, so your version numbers may differ.
+After 3.2-rc1, the kernel versioning was changed and the modules for -rc4,5,6,7 are now located in lib/modules/3.2.0-rc4-00002-gd3aebaf/ the last digits will change as the sources are edited, so your version numbers may differ.

@@ Line 1: / Line 1: @@
 == Introduction ==
-The merge window for 3.2 is over and the 3.2-rc1 kernel has been released.
+The merge window for 3.2 is over and we are currently at v3.2-rc6.
-Lots of work on the omap platforms and on pandaboard. Let's see
+Lots of work on the OMAP platforms and on Pandaboard. Let's see
-what -rc1 has brought.
+what the various release candidates have provided.
-you can download a tarball of the mainline kernel at http://kernel.org/
+You can download a tarball of the mainline kernel at http://kernel.org/
 or you can clone a copy of mainline kernel with:
@@ Line 14: / Line 14: @@
 </pre>
-where x is the release candidate version
+where x is the release candidate version.
 == rc1 ==
@@ Line 26: / Line 26: @@
 == rc3 ==
-There were no changes to OMAP or PandBoard related code in the -rc3 release. The same patches required for -rc1 work for the -rc3 sources, and the kernel works as does the -rc1.
+There were no changes to OMAP or PandaBoard related code in the -rc3 release. The same patches required for -rc1 work for the -rc3 sources, and the kernel works as does the -rc1.
 == rc4 ==
@@ Line 34: / Line 34: @@
 == rc5 ==
-There were no changes to OMAP or PandBoard related code in the -rc5 release. The same patches required for -rc1, -rc3 & -rc4 work for the -rc5 sources, and the kernel works as well.
+There were no changes to OMAP or PandaBoard related code in the -rc5 release. The same patches required for -rc1, -rc3 & -rc4 work for the -rc5 sources, and the kernel works as well.
 == rc6 ==
-There were no changes to PandBoard related code in the -rc6 release. The same patches required for -rc1, -rc3, -rc4 & -rc5 work for the -rc6 sources, and the kernel works as well.
+There were no changes to PandaBoard related code in the -rc6 release. The same patches required for -rc1, -rc3, -rc4 & -rc5 work for the -rc6 sources, and the kernel works as well.
-== PandaBoard-ES ==
+== PandaBoard ES ==
-There is now a PandaBoare-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 therefor the max clock frequency when running the OMAP4460 on the PandaBoard ES with the mainline kernel is 920MHz(same as the OMAP4430).
+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).

@@ Line 35: / Line 35: @@
 There were no changes to OMAP or PandBoard related code in the -rc5 release. The same patches required for -rc1, -rc3 & -rc4 work for the -rc5 sources, and the kernel works as well.
 == PandaBoard-ES ==
@@ Line 77: / Line 81: @@
 == Building ==
-Building 3.2-rc1,3,4,5 is a bit different from previous How-To's if you want to have a working wlan.
+Building 3.2-rc1,3,4,5,6 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.2-rc1,3,4,5 sources and use [[Media:config.3.2-rc1.1|config.3.2-rc1.1]], [[Media:config.3.2-rc3.1|config.3.2-rc3.1]], [[Media:config.3.2-rc4.1|config.3.2-rc4.1]] or [[Media:config.3.2-rc5.1|config.3.2-rc5.1]] as the .config (you should apply all the above patches)
+Grab the 3.2-rc1,3,4,5,6 sources and use [[Media:config.3.2-rc1.1|config.3.2-rc1.1]], [[Media:config.3.2-rc3.1|config.3.2-rc3.1]], [[Media:config.3.2-rc4.1|config.3.2-rc4.1]], [[Media:config.3.2-rc5.1|config.3.2-rc5.1]] or [[Media:config.3.2-rc6.1|config.3.2-rc6.1]] as the .config (you should apply all the above patches)
 Then compile like so:
@@ Line 96: / Line 100: @@
 Copy lib/modules/3.2.0-rc1-dirty/ to your SD card (as root), boot up the Pandaboard.
-After 3.2-rc1, the kernel versioning was changed and the modules for -rc4,5 are now located in lib/modules/3.2.0-rc4-00002-gd3aebaf/ the last digits will change as the sources are edited, so your version numbers may differ.
+After 3.2-rc1, the kernel versioning was changed and the modules for -rc4,5,6 are now located in lib/modules/3.2.0-rc4-00002-gd3aebaf/ the last digits will change as the sources are edited, so your version numbers may differ.

@@ Line 38: / Line 38: @@
 == PandaBoard-ES ==
-There is now a PandaBoare-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 MLO/u-boot/kernel be specifically crafted for the 4460. The thermal management is not in the mainline 4430 code as yet and could cause unwanted thermal problems. So BEWARE of running any code built for the non -ES PandaBoard on the -ES model.
+There is now a PandaBoare-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 therefor the max clock frequency when running the OMAP4460 on the PandaBoard ES with the mainline kernel is 920MHz(same as the OMAP4430).
 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.
 == wlan12xx patch ==

@@ Line 31: / Line 31: @@
 There were quite a few updates to OMAP code, but no PandaBoard related changes. The same patches required for -rc1 & -rc3 work for the -rc4 sources, and the kernel works as does the -rc1 & -rc3.
 == PandaBoard-ES ==
@@ Line 49: / Line 53: @@
 == DVI Patch ==
-This patch is necessary to make 720p resolution available. there is also a new selection in the .config file for DVI
+A patch is no longer necessary to make 720p resolution available. The DVI driver now reads the EDID and sets the resolution on bootup if the display is plugged into the DVI connector. If the display is not plugged in on bootup it will default to 640 x 480.
-−
-[[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
 == I2C Patch ==
@@ Line 79: / Line 77: @@
 == Building ==
-Building 3.2-rc1,3,4 is a bit different from previous How-To's if you want to have a working wlan.
+Building 3.2-rc1,3,4,5 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.2-rc1,3,4 sources and use [[Media:config.3.2-rc1.1|config.3.2-rc1.1]], [[Media:config.3.2-rc3.1|config.3.2-rc3.1]] or [[Media:config.3.2-rc4.1|config.3.2-rc4.1]] as the .config (you should apply all the above patches)
+Grab the 3.2-rc1,3,4,5 sources and use [[Media:config.3.2-rc1.1|config.3.2-rc1.1]], [[Media:config.3.2-rc3.1|config.3.2-rc3.1]], [[Media:config.3.2-rc4.1|config.3.2-rc4.1]] or [[Media:config.3.2-rc5.1|config.3.2-rc5.1]] as the .config (you should apply all the above patches)
 Then compile like so:
@@ Line 98: / Line 96: @@
 Copy lib/modules/3.2.0-rc1-dirty/ to your SD card (as root), boot up the Pandaboard.
-After 3.2-rc1, the kernel versioning was changed and the modules for -rc4 are now located in lib/modules/3.2.0-rc4-00002-gd3aebaf/ the last digits will change as the sources are edited, so your version numbers may differ.
+After 3.2-rc1, the kernel versioning was changed and the modules for -rc4,5 are now located in lib/modules/3.2.0-rc4-00002-gd3aebaf/ the last digits will change as the sources are edited, so your version numbers may differ.

@@ Line 11: / Line 11: @@
 There are no changes to OMAP or PandaBoard related code in the -rc2 release, or any fixes that would eliminate any of the patches required for -rc1, so we'll skip testing this release for a bit.
@@ Line 55: / Line 65: @@
 == Building ==
-Building 3.2-rc1 is a bit different from previous How-To's if you want to have a working wlan.
+Building 3.2-rc1,3 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.2-rc1 sources and use [[Media:config.3.2-rc1.1|config.3.2-rc1.1]] as the .config (you should apply all the above patchs)
+Grab the 3.2-rc1,3 sources and use [[Media:config.3.2-rc1.1|config.3.2-rc1.1]] or [[Media:config.3.2-rc3.1|config.3.2-rc3.1]] as the .config (you should apply all the above patches)
 Then compile like so:

@@ Line 8: / Line 8: @@
 There are several issues requiring new patches. The WL12xx driver needs newer firmware, and the same patch as used for 3.1. 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 latest 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.
+== rc2 ==
 == wlan12xx patch ==