Temp meta-intel release notes: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
No edit summary
Line 1: Line 1:
= Release Notes =
= Release Notes =


Following are features, updates, and know issues for this release of the Yocto Project.
Following are features, updates, and known issues for this v1.4 release of the meta-intel layer of the Yocto Project.
Features and updates


== Features & Updates ==
== New Features and Updates ==


* LTSI Kernel: The v1.4 release is the 1st release for Yocto Project meta-intel BSPs which provides LTSI enabled (v3.4) Linux kernel recipes along with the default (v3.8.4) linux-yocto kernel recipes.
* LTSI Kernel: The v1.4 release is the 1st release for Yocto Project meta-intel BSPs which provides LTSI enabled (v3.4) Linux kernel recipes along with the default (v3.8.4) linux-yocto kernel recipes.
* As part of the standard BSP retirement process, the cedartrail BSP has been retired from the Yocto Project as of this 1.4 release. Also note that the last, 1.3 version of the cedartrail BSP is still fully
 
supported going forward.
* Emenlow BSP is been changed to use EMGD graphics driver stack instead of the earlier Poulsbo Graphics Driver Stack.
* Emenlow BSP is been changed to use EMGD graphics driver stack instead of the earlier Poulsbo Graphics Driver Stack.
* A new emenlow-noemgd BSP has been created which uses fully open source gma500 graphics stack.
 
* A new emenlow-noemgd BSP has been created which uses fully open source gma500 graphics driver stack.
 
* A new nuc BSP has been created to support Intel’s Next Unit of Computing platforms.
* A new nuc BSP has been created to support Intel’s Next Unit of Computing platforms.
* For all the emgd based BSPs viz crownbay, emenow, fri2 & sys940x the EMGD graphics driver stack has been upgraded from v1.14 to the latest v1.16.
 
* For different hardware platforms supported by the fri2-noemgd BSP, X is enabled by using the fbdev X driver in place of the earlier vesa X driver.
* For all the emgd based BSPs namely crownbay, emenow, fri2 & sys940x, the EMGD graphics driver stack has been upgraded from v1.14 to the latest, v1.16.
* The method of specifying BSP Video Acceleration configuration is changed now. Instead of the VA_FEATURES var a new variable named MACHINE_HWCODECS is used to specify which video codecs to include in the image.
 
* In the fri2-noemgd BSP, X is enabled for different supported hardware platforms, by using the fbdev X driver in place of the earlier vesa X driver.
 
* The method of specifying BSP Video Acceleration configuration has been changed in this release. Instead of the VA_FEATURES variable a new variable named MACHINE_HWCODECS is used to specify which video codecs to include in the generated image.
 
* For all the meta-Intel BSPs the Linux-yocto kernel (default kernel) is updated to v3.8.4.
* For all the meta-Intel BSPs the Linux-yocto kernel (default kernel) is updated to v3.8.4.
* New Linux-yocto-dev kernel recipes, which are used for development of the next kernel are now provided for these meta-intel BSPs: chiefriver, crownbay, crownbay-noemgd, emenlow, emenlow-noemgd, fri2, fri2-noemgd, jasperforest, nuc, sugarbay, sys940x, sys940x-noemgd  
 
* Real time kernel recipes, linux-yocto-rt_v3.4 are now provided for these meta-intel BSPs: chiefriver, crownbay,  crownbay-noemgd, crystalforest, emenlow, emenlow-noemgd, fri2, fri2-noemgd, jasperforest, n450, nuc, sugarbay, sys940x, sys940x-noemgd
* New Linux-yocto-dev kernel recipes, which are used for development of the next kernel are now provided for these meta-intel BSPs: chiefriver, crownbay, crownbay-noemgd, emenlow, emenlow-noemgd, fri2, fri2-noemgd, jasperforest, nuc, sugarbay, sys940x, sys940x-noemgd
* Real time kernel recipes, linux-yocto-rt_v3.8 is now provided for these meta-intel BSPs: chiefriver, crownbay, crownbay-noemgd, emenlow, emenlow-noemgd, fri2, fri2-noemgd, jasperforest, n450,
 
nuc,  sugarbay, sys940x, sys940x-noemgd
* v3.4 of real time kernel recipes (linux-yocto-rt_v3.4) are now provided for these meta-intel BSPs: chiefriver, crownbay,  crownbay-noemgd, crystalforest, emenlow, emenlow-noemgd, fri2, fri2-noemgd, jasperforest, n450, nuc, sugarbay, sys940x, sys940x-noemgd
 
* v3.8 of real time kernel recipes (linux-yocto-rt_v3.8) is now provided for these meta-intel BSPs: chiefriver, crownbay, crownbay-noemgd, emenlow, emenlow-noemgd, fri2, fri2-noemgd, jasperforest, n450, nuc,  sugarbay, sys940x, sys940x-noemgd
 
* As part of the standard BSP retirement process, the cedartrail BSP has been retired from the Yocto Project as of this 1.4 release. Also note that the last, 1.3 version of the cedartrail BSP is still fully
supported going forward.
 


== Known Issues ==
== Known Issues ==
* USB devices auto disabling:  On the Sugarbay platrom, it is observed that some of the USB devices were getting automatically suspended within few seconds of inactivity. A workaround for this
 
* USB devices auto disabling:  On the Sugarbay platform, it is observed that some of the USB devices were getting automatically disabled within few seconds of inactivity. A workaround for this
issue is: pass boot parameter usbcore.autosuspend=-1 to the kernel, which avoids this auto suspension. This issue is observed with the v3.8.4 kernel, and may also show on other hardware
issue is: pass boot parameter usbcore.autosuspend=-1 to the kernel, which avoids this auto suspension. This issue is observed with the v3.8.4 kernel, and may also show on other hardware
platforms.
platforms.

Revision as of 20:37, 13 May 2013

Release Notes

Following are features, updates, and known issues for this v1.4 release of the meta-intel layer of the Yocto Project.

New Features and Updates

  • LTSI Kernel: The v1.4 release is the 1st release for Yocto Project meta-intel BSPs which provides LTSI enabled (v3.4) Linux kernel recipes along with the default (v3.8.4) linux-yocto kernel recipes.
  • Emenlow BSP is been changed to use EMGD graphics driver stack instead of the earlier Poulsbo Graphics Driver Stack.
  • A new emenlow-noemgd BSP has been created which uses fully open source gma500 graphics driver stack.
  • A new nuc BSP has been created to support Intel’s Next Unit of Computing platforms.
  • For all the emgd based BSPs namely crownbay, emenow, fri2 & sys940x, the EMGD graphics driver stack has been upgraded from v1.14 to the latest, v1.16.
  • In the fri2-noemgd BSP, X is enabled for different supported hardware platforms, by using the fbdev X driver in place of the earlier vesa X driver.
  • The method of specifying BSP Video Acceleration configuration has been changed in this release. Instead of the VA_FEATURES variable a new variable named MACHINE_HWCODECS is used to specify which video codecs to include in the generated image.
  • For all the meta-Intel BSPs the Linux-yocto kernel (default kernel) is updated to v3.8.4.
  • New Linux-yocto-dev kernel recipes, which are used for development of the next kernel are now provided for these meta-intel BSPs: chiefriver, crownbay, crownbay-noemgd, emenlow, emenlow-noemgd, fri2, fri2-noemgd, jasperforest, nuc, sugarbay, sys940x, sys940x-noemgd
  • v3.4 of real time kernel recipes (linux-yocto-rt_v3.4) are now provided for these meta-intel BSPs: chiefriver, crownbay, crownbay-noemgd, crystalforest, emenlow, emenlow-noemgd, fri2, fri2-noemgd, jasperforest, n450, nuc, sugarbay, sys940x, sys940x-noemgd
  • v3.8 of real time kernel recipes (linux-yocto-rt_v3.8) is now provided for these meta-intel BSPs: chiefriver, crownbay, crownbay-noemgd, emenlow, emenlow-noemgd, fri2, fri2-noemgd, jasperforest, n450, nuc, sugarbay, sys940x, sys940x-noemgd
  • As part of the standard BSP retirement process, the cedartrail BSP has been retired from the Yocto Project as of this 1.4 release. Also note that the last, 1.3 version of the cedartrail BSP is still fully

supported going forward.


Known Issues

  • USB devices auto disabling: On the Sugarbay platform, it is observed that some of the USB devices were getting automatically disabled within few seconds of inactivity. A workaround for this

issue is: pass boot parameter usbcore.autosuspend=-1 to the kernel, which avoids this auto suspension. This issue is observed with the v3.8.4 kernel, and may also show on other hardware platforms.