Temp meta-intel release notes - Revision history

Nitinkamble at 21:13, 13 May 2013

2013-05-13T21:13:55Z

← Older revision		Revision as of 21:13, 13 May 2013
Line 7:		Line 7:
	* LTSI Kernel: The v1.4 release of the meta-intel BSPs now also include LTSI enabled v3.4 kernel recipes along with the default (v3.8.4) linux-yocto kernel recipes.		* LTSI Kernel: The v1.4 release of the meta-intel BSPs now also include LTSI enabled v3.4 kernel recipes along with the default (v3.8.4) linux-yocto kernel recipes.

	* ~~Emenlow~~ BSP has been changed to use EMGD graphics driver stack in place of the earlier Poulsbo Graphics Driver Stack.		* The emenlow BSP has been changed to use the Intel EMGD graphics driver stack in place 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 emenlow-noemgd BSP has been created which uses fully open source gma500 graphics driver stack.
Line 13:		Line 13:
	* 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 meta-intel BSPs using the Intel EMGD graphics stack, namely crownbay, emenlow, fri2 and sys940x~~, the EMGD graphics driver stack has been upgraded from v1.14 to the latest, v1.16~~.		* The EMGD graphics driver stack has been upgraded from v1.14 to the latest, v1.16 for all the meta-intel BSPs using the Intel EMGD graphics stack, namely crownbay, emenlow, fri2 and sys940x.

	* All the meta-intel BSPs using Intel Linux graphics stack, namely sugarbay, chiefriver and nuc, now utilize the version 2012Q4 of the Intel Linux Graphics Stack.		* All the meta-intel BSPs using Intel Linux graphics stack, namely sugarbay, chiefriver and nuc, now utilize the version 2012Q4 of the Intel Linux Graphics Stack.
Line 21:		Line 21:
	* The method of specifying BSP Video Acceleration configuration has been changed in this release. Instead of using the VA_FEATURES variable a new variable named MACHINE_HWCODECS is used to specify which video codecs to include in the generated image.		* The method of specifying BSP Video Acceleration configuration has been changed in this release. Instead of using 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 default kernel recipe which is Linux-yocto 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		* 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

Nitinkamble at 20:56, 13 May 2013

2013-05-13T20:56:36Z

← Older revision		Revision as of 20:56, 13 May 2013
Line 5:		Line 5:
	== New Features and 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 of the meta-intel BSPs now also include LTSI enabled v3.4 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.		* Emenlow BSP has been changed to use EMGD graphics driver stack in place 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 emenlow-noemgd BSP has been created which uses fully open source gma500 graphics driver stack.
Line 13:		Line 13:
	* 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~~ namely crownbay, ~~emenow~~, fri2 & sys940x, the EMGD graphics driver stack has been upgraded from v1.14 to the latest, v1.16.		* For all meta-intel BSPs using the Intel EMGD graphics stack, namely crownbay, emenlow, fri2 and 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.		* All the meta-intel BSPs using Intel Linux graphics stack, namely sugarbay, chiefriver and nuc, now utilize the version 2012Q4 of the Intel Linux Graphics Stack.

			* For 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 using the VA_FEATURES variable a new variable named MACHINE_HWCODECS is used to specify which video codecs to include in the generated image.		* The method of specifying BSP Video Acceleration configuration has been changed in this release. Instead of using the VA_FEATURES variable a new variable named MACHINE_HWCODECS is used to specify which video codecs to include in the generated image.
Line 27:		Line 29:
	* v3.8 of real time kernel recipes (linux-yocto-rt_v3.8) are 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.8 of real time kernel recipes (linux-yocto-rt_v3.8) are 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~~.		* As part of the BSP retirement process, the Cedartrail BSP has been retired from the Yocto Project as of this 1.4 release. But the 1.3 version of the BSP is still available and maintained with critical bug fixes.

Nitinkamble at 20:42, 13 May 2013

2013-05-13T20:42:23Z

← Older revision		Revision as of 20:42, 13 May 2013
Line 17:		Line 17:
	* 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.		* 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.		* The method of specifying BSP Video Acceleration configuration has been changed in this release. Instead of using 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.

Nitinkamble at 20:41, 13 May 2013

2013-05-13T20:41:26Z

← Older revision		Revision as of 20:41, 13 May 2013
Line 25:		Line 25:
	* 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.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		* v3.8 of real time kernel recipes (linux-yocto-rt_v3.8) are 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.		* 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.

Nitinkamble at 20:40, 13 May 2013

2013-05-13T20:40:03Z

← Older revision		Revision as of 20:40, 13 May 2013
Line 32:		Line 32:
	== Known Issues ==		== 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.		* [Bug #4180] 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.

Nitinkamble at 20:38, 13 May 2013

2013-05-13T20:38:18Z

← Older revision		Revision as of 20:38, 13 May 2013
Line 27:		Line 27:
	* 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		* 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		* 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.
	supported going forward.


	== Known Issues ==		== 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		* 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.
	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.

Nitinkamble at 20:37, 13 May 2013

2013-05-13T20:37:48Z

← Older revision		Revision as of 20:37, 13 May 2013
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.

Nitinkamble at 20:27, 13 May 2013

2013-05-13T20:27:12Z

← Older revision		Revision as of 20:27, 13 May 2013
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 know issues for this release of the Yocto Project.
	Features and updates		Features and updates

	= Features & Updates =		== Features & 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.
Line 21:		Line 21:
	nuc, sugarbay, sys940x, sys940x-noemgd		nuc, sugarbay, sys940x, sys940x-noemgd

	= 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 platrom, it is observed that some of the USB devices were getting automatically suspended 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.

Nitinkamble: Created page with "== Release Notes == Following are features, updates, and know issues for this release of the Yocto Project. Features and updates = Features & Updates = * LTSI Kernel: The v1.4..."

2013-05-13T20:26:48Z

Created page with "== Release Notes == Following are features, updates, and know issues for this release of the Yocto Project. Features and updates = Features & Updates = * LTSI Kernel: The v1.4..."

New page

== Release Notes ==

Following are features, updates, and know issues for this release of the Yocto Project.
Features and updates

= Features & 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.
* 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.
* A new emenlow-noemgd BSP has been created which uses fully open source gma500 graphics stack.
* 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.
* 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.
* 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
* 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

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