This bug is a placeholder for 1.3 BSP-related work to be handed off (from Tom to Nitin). In general, we want to move all the meta-intel BSPs to the new kernel version every cycle. For crownbay, there are actually two BSPs to worry about, crownbay and crownbay-noemgd. There is also the added complication that for crownbay, EMGD also needs to be changed/upgraded to match the new kernel. Note also that a new EMGD version may also entail changes to userspace components, so all in all, there may be several interdependent and entwined tasks. See bug 2542 for more details on EMGD and possible strategies for making all these changes together. As for the kernel itself, the work basically entails modifying the kernel recipes and machine configuration to upgrade to the new kernel, along with verifying that all the kernel configuration related to the BSP in the meta branch of the 3.4 kernel repo exists and has been properly enabled. Note that with 2-point kernel version jumps e.g. 3.2 -> 3.4, the underlying kernel options may have changed and may no longer apply and therefore the corresponding features may no longer exist or their contents may have changed, etc. Moving a BSP to a new kernel therefore entails testing all the functionality to make sure nothing's regressed.
This is co-dependent on upgrading emgd to 3.4 - you can start with the -noemgd version and upgrade that to 3.4, which should be relatively straightforward. Once that's done, you can move on to the 3.4 crownbay and get the upgraded emgd 3.4 working on it.
Marking as P2 and medium as it is required for release, but not for M2. Also moving to M3 as it is intertwined with 2542 and Nitin will not be 100% available for M2.
I tried moving crownbay bsp to v3.4 kernel. I notice that in v3.4 kernel has major changes in the DRM interface. And the latest EMGD driver v1.14 is still based on 2.6.39, which makes the emgd driver incompatible with the v3.4 kernel. I am trying to get some information from the EMGD driver people if there is a newer driver which will work with v3.4 kernel.
We need to be using what's in the EMGD release tarball, which means adapting the kernel source to work with the current Yocto kernel release, whatever that is. You should be able to base your work off the current set of changes for that already in the Yocto emgd 1.10 branch, which brings the 2.6.39 emgd kernel source to 3.2. Judging from how easily the emenlow moved to 3.4, you might not actually have much work to do to get this working.
a commit went in for this into meta-intel layer: commit ae59294054e8b7cd23c8ea9789cdecd000480af6 Author: Nitin A Kamble <nitin.a.kamble@intel.com> Date: Thu Jun 28 18:32:00 2012 -0700 crownbay: add recipe extension for linux-yocto-3.4 Add emgd branch info in git src_uri At build time, the emgd-1.14 branch is merged with the crownbay bsp kernel source branch to get emgd kernel driver's support. Reference it in the src_uri, and its commit-id to be used, so that any changes in the emgd branch will not affect build unknowingly. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Tested-by: Tom Zanussi <tom.zanussi@intel.com>
Setting to Verified - Fixed. Tested with crownbay version: root@crownbay:~# cat /etc/version 201208090703