Yocto Project - User contributions [en]

Meta-intel-2.0-dizzy-1.7 release planning

2014-10-08T16:17:32Z

Nitinkamble: /* related reference */

=== For reference here is the Yocto Project 1.7 release schedule===
* YP 1.7 M4 RC2 Build/QA test : Oct 8 – Oct 14
* YP 1.7 M4 RC3 Build/QA test : Oct 15 – Oct 21
* YP 1.7 M4 RC4 Build/QA test : Oct 22 – Oct 28
* YP 1.7 Release Final Publish : Oct 29 – Oct 31

=== Meta-intel 2.0 release schedule ===
* Meta-intel-2.0-dizzy-1.7 RC2 Build/QA test: Oct 8 – Oct 14
* Meta-intel-2.0-dizzy-1.7 RC3 Build/QA test: Oct 15 – Oct 21
* Meta-intel-2.0-dizzy-1.7 RC4 Build/QA test: Oct 22 – Oct 28
* Meta-intel-2.0-dizzy-1.7 RC5 Build/QA test: Oct 29 – Nov 4
* Meta-intel-2.0-dizzy-1.7 Release : Nov 5 – Nov 11

=== Remaining tasks for the meta-intel release ===
* Release branch and tags for QA use - Darren/Tom
* Per RC meta-intel build and QA test - Alex & IoTG team
* Kernel srcrev updates for all the BSPs - Bruce, Nitin & IoTG team
* Microcode commits - Nitin
* Machine setup tool commits - Nitin
* Follow the release process. Includes making BSP tar balls, Publishing of the BSPs, YP compatible certification, Release Notes - Michael + other
* Important bugs to fix before the release:
** bug #6162 - Bruce

=== Related reference material ===
* [[Yocto Release Engineering]]
* [[Meta-intel Release Process]]

Meta-intel-2.0-dizzy-1.7 release planning

2014-10-08T16:17:02Z

Nitinkamble: /* Remaining tasks for the meta-intel release */

=== For reference here is the Yocto Project 1.7 release schedule===
* YP 1.7 M4 RC2 Build/QA test : Oct 8 – Oct 14
* YP 1.7 M4 RC3 Build/QA test : Oct 15 – Oct 21
* YP 1.7 M4 RC4 Build/QA test : Oct 22 – Oct 28
* YP 1.7 Release Final Publish : Oct 29 – Oct 31

=== Meta-intel 2.0 release schedule ===
* Meta-intel-2.0-dizzy-1.7 RC2 Build/QA test: Oct 8 – Oct 14
* Meta-intel-2.0-dizzy-1.7 RC3 Build/QA test: Oct 15 – Oct 21
* Meta-intel-2.0-dizzy-1.7 RC4 Build/QA test: Oct 22 – Oct 28
* Meta-intel-2.0-dizzy-1.7 RC5 Build/QA test: Oct 29 – Nov 4
* Meta-intel-2.0-dizzy-1.7 Release : Nov 5 – Nov 11

=== Remaining tasks for the meta-intel release ===
* Release branch and tags for QA use - Darren/Tom
* Per RC meta-intel build and QA test - Alex & IoTG team
* Kernel srcrev updates for all the BSPs - Bruce, Nitin & IoTG team
* Microcode commits - Nitin
* Machine setup tool commits - Nitin
* Follow the release process. Includes making BSP tar balls, Publishing of the BSPs, YP compatible certification, Release Notes - Michael + other
* Important bugs to fix before the release:
** bug #6162 - Bruce

=== related reference ===
* [[Yocto Release Engineering]]
* [[Meta-intel Release Process]]

Meta-intel-2.0-dizzy-1.7 release planning

2014-10-08T16:15:01Z

Nitinkamble:

Meta-intel-2.0-dizzy-1.7 release planning

2014-10-08T16:14:42Z

Nitinkamble: Created page with "=== For reference here is the Yocto Project 1.7 release schedule=== * YP 1.7 M4 RC2 Build/QA test : Oct 8 – Oct 14 * YP 1.7 M4 RC3 Build/QA test : Oct 15 – Oct 21 * YP 1.7 M4..."

Main Page

2014-10-08T16:05:59Z

Nitinkamble: /* Current Project Status and Schedule */

== Welcome to the Yocto Project Wiki! ==
=== Current Project Status and Schedule ===
* [[Yocto 1.7 Status]]
* [[Yocto 1.7 Schedule]]
* [[1.7 qa run history]]
* [[1.7 QA Status]]
* [[meta-intel-2.0-dizzy-1.7 release planning]]

=== Main Wiki Sections ===
* [[Planning and Governance]]
* [[Community Guidelines]]
* [[Yocto Release Engineering | Yocto Project Release Engineering]]
* [[Processes and Activities]]
** [[YoctoCalendar]]
* [[Projects]]
* [[Yocto Interest Groups]]
* [[FAQ]]
* [[How do I]]
* [[Contributors]]
* [[Training]]
* [[Testopia]] - The Yocto Project's community-opened test case management platform
* [[Toaster]] - the web interface | [[Web UI]] - The design plans for the new Web UI

== Other resources ==
* [http://yoctoproject.org Yocto Project Front Page]

Meta-intel Release Process

2014-10-08T16:02:19Z

Nitinkamble: /* meta-intel BSP release version scheme */

meta-intel releases happen with the same cadence that poky releases happen, though the actual release may be staggered with respect to the associated poky release. We now attempt to co-release with poky, or at least have everything ready to co-release, but the actual release decision may dictate that we don't actually co-release. The meta-intel release may also be staggered simply because meta-intel needs the extra time to stabilize against the associated poky release.

This pages attempts to capture the meta-intel release process as it exists - it isn't meant to be an official or binding document.

Also, this process only addresses the BSPs built and released by the Yocto Autobuilder team, and tested by the Yocto QA team - it doesn't address the release process for any BSPs that are managed outside of that process, such as the ISG BSPs, which may be built using a separate autobuilder and tested by ISG, i.e. which have their own release process, though their metadata may exist within the meta-intel and linux-yocto repositories.

=== Overall Responsibilities ===

The meta-intel repository consists of a set of BSPs and some common metadata. Because those BSPs each have separate owners, we can't make a blanket assertion that all those BSPs will be released as part of a meta-intel release. It would be nice to be able to do so, but in reality, different groups of maintainers may decide to do separate releases. As such. this section only describes the perceived responsibilities of the maintainers for the set of BSPs controlled by the Yocto team.

The Yocto Project Program Manager has the ultimate responsibility for coordinating the various BSP owners and managing the overall meta-intel release.

* Basically the BSP maintainer(s) are responsible for tracking the release milestones and making sure the BSPs are up-to-date and releasable with respect to the poky release. This includes all recipe upgrades and bugfixes intended to go into the release.
* At each release candidate, the autobuilder team generates the images passes them on to QA for testing.
* QA tests and provides feedback on how the BSPs meet the release criteria.
* The BSP maintainer(s) fix any problems found by QA, and the cycle repeats itself in the next RC cycle, until all BSPs can be released.

Once the BSPs are ready to be released from the BSP maintainer's and QA team standpoint, the autobuilder team generates release tarballs for each BSP and makes them available to the Yocto website maintainers for availability as downloads on the Yocto website.
* The yocto website maintainers make the tarballs available from pages containing the release notes for each BSP, along with test reports and image verification status for each (see sections below for details).
* Any problems not fixed by the BSP maintainers need to be noted by the maintainer and sent to the website maintainer and Yocto documentation maintainer as 'Layer-specific Notes' to be appended to each affected BSP's release notes (see below).

=== Basic Process ===
Even though exceptions may occur for some BSPs, this is the basic process we use to release all meta-intel BSPs:

* All meta-intel BSPs will be build along with each Yocto Project milestone release candidates. Then QA will follow and results will be integrated with the full pass QA report.
* Bugs will be fixed/handled by maintainers or others.
* Within the first week after Yocto Project major release, RC1 for meta-intel BSPs will be built and tested.
* Within the second week after Yocto Project major release, RC2 for meta-intel BSPs will be built and tested.
* meta-intel BSPs will be released by the end of the third week after Yocto Project major release.

=== Branch and Tag Management ===

The autobuilder maintainers are the only ones who can create new branches and release tags in meta-intel, and will do so when necessary as required to generate the infrastructure needed for a release.
* Once a new branch is created for the release, the meta-intel maintainer(s) will add new commits to both master and the release branch up until the time of release (as appropriate - some patches may only be intended for master or the release)

=== meta-intel BSP directory naming convention ===

All directories for meta-intel BSPs should be named in the format of:

meta-platform[-cpu][-crb]

Note: CPU name and CRB name are optional if the BSP supports more than 1 CPU or CRB

=== meta-intel BSP release version scheme ===

Starting with the poky v1.6.1 release in July 2014, meta-intel BSPs started following a new version scheme. With the new scheme meta-intel BSP tarballs get the meta-intel layer version string, along with the compatible poky layer release name and version needed for the BSP. For example in July 2014 the crownbay-noemgd BSP was released as crownbay-noemgd-1.0-daisy-1.6.1 as seen here [https://www.yoctoproject.org/downloads/bsps/daisy161/crown-bay-0 YP BSP link]

The new format for releasing meta-intel BSPs is

<BSP Name>-<meta intel layer version in the major.minor format>-<the poky release name and version compatible for this BSP>
For Example: crownbay-noemgd-1.0-daisy-1.6.1

Note that meta-intel BSPs will generally be compatible with subsequent dot release of the poky layer, because the dot release are for bug fixes, and they do not add new features.

==== Incrementing meta-intel BSP version ====

The major part of the meta-intel layer BSP version is incremented for every major release of Yocto Project release. For the new BSP releases made for the poky dot releases, or new BSP releases which do not change the requirement of the compatible poky release, the minor part of the meta-intel layer version is incremented to denote it as a dot release.

=== Release Notes ===

Currently, the 'release notes' for a BSP consist of the information found on the web page for the BSP in the 'Downloads' section for the BSP, and essentially consists of the BSP's README along with a 'Layer-Specific Notes' section, which is tacked on to the end of the page.

* The Yocto documentation and website maintainers will be responsible for the content of the BSP pages and will ask the BSP maintainer(s) for any additional information needed for a particular BSP
* Normally the only thing needed from the BSP maintainer(s) are the 'Layer-Specific Notes' for a BSP, which the BSP maintainers should supply to the documentation and website maintainers unsolicited as part of the release process.
** Any layer-specific notes that affect multiple or all BSPs should be attached to each BSP separately in the 'Layer-Specific Notes' section.
* The title used for the BSP on the website is retrieved by the documentation and website maintainers from the BSP's WEBTITLE field in the BSP's machine.conf, and should therefore reflect accurately how the BSP is identified on the website. This may be a string defined by marketing, and should at least be approved by marketing.

=== Testing ===

According to the Yocto Project compliance requirements, no meta-intel BSP can be released without testing data. The webpage for each BSP must contain a link to the testing data generated for every image contained in a released BSP. For the BSPs tested by Yocto QA, the QA test report should be the one linked to for those BSPs.

=== Image Verification ===

For every BSP image contained in a tarball released on the Yocto website, it must be verified that the image can be independently generated from scratch (including downloads) using the released metadata.

Customers must (and have, and will) be able to verify that the images contained in the release tarball can in fact be generated from the combination of the metadata contained in the BSP tarball and the set of packages downloaded by the build (from a scratch build) process to create those images.

In practice, this means that the autobuilder maintainer needs to supply the settings required to generate the BSP to the person verifiying the image. If the release tarball is generated by some other process, the BSP maintainer needs to supply that information.
* Note that all images released on the website must contain a time-limited kernel and this must be taken into account when verifying the image.

Meta-intel Release Process

2014-10-08T15:58:47Z

Nitinkamble: /* meta-intel BSP directory naming convention */

meta-intel releases happen with the same cadence that poky releases happen, though the actual release may be staggered with respect to the associated poky release. We now attempt to co-release with poky, or at least have everything ready to co-release, but the actual release decision may dictate that we don't actually co-release. The meta-intel release may also be staggered simply because meta-intel needs the extra time to stabilize against the associated poky release.

This pages attempts to capture the meta-intel release process as it exists - it isn't meant to be an official or binding document.

Also, this process only addresses the BSPs built and released by the Yocto Autobuilder team, and tested by the Yocto QA team - it doesn't address the release process for any BSPs that are managed outside of that process, such as the ISG BSPs, which may be built using a separate autobuilder and tested by ISG, i.e. which have their own release process, though their metadata may exist within the meta-intel and linux-yocto repositories.

=== Overall Responsibilities ===

The meta-intel repository consists of a set of BSPs and some common metadata. Because those BSPs each have separate owners, we can't make a blanket assertion that all those BSPs will be released as part of a meta-intel release. It would be nice to be able to do so, but in reality, different groups of maintainers may decide to do separate releases. As such. this section only describes the perceived responsibilities of the maintainers for the set of BSPs controlled by the Yocto team.

The Yocto Project Program Manager has the ultimate responsibility for coordinating the various BSP owners and managing the overall meta-intel release.

* Basically the BSP maintainer(s) are responsible for tracking the release milestones and making sure the BSPs are up-to-date and releasable with respect to the poky release. This includes all recipe upgrades and bugfixes intended to go into the release.
* At each release candidate, the autobuilder team generates the images passes them on to QA for testing.
* QA tests and provides feedback on how the BSPs meet the release criteria.
* The BSP maintainer(s) fix any problems found by QA, and the cycle repeats itself in the next RC cycle, until all BSPs can be released.

Once the BSPs are ready to be released from the BSP maintainer's and QA team standpoint, the autobuilder team generates release tarballs for each BSP and makes them available to the Yocto website maintainers for availability as downloads on the Yocto website.
* The yocto website maintainers make the tarballs available from pages containing the release notes for each BSP, along with test reports and image verification status for each (see sections below for details).
* Any problems not fixed by the BSP maintainers need to be noted by the maintainer and sent to the website maintainer and Yocto documentation maintainer as 'Layer-specific Notes' to be appended to each affected BSP's release notes (see below).

=== Basic Process ===
Even though exceptions may occur for some BSPs, this is the basic process we use to release all meta-intel BSPs:

* All meta-intel BSPs will be build along with each Yocto Project milestone release candidates. Then QA will follow and results will be integrated with the full pass QA report.
* Bugs will be fixed/handled by maintainers or others.
* Within the first week after Yocto Project major release, RC1 for meta-intel BSPs will be built and tested.
* Within the second week after Yocto Project major release, RC2 for meta-intel BSPs will be built and tested.
* meta-intel BSPs will be released by the end of the third week after Yocto Project major release.

=== Branch and Tag Management ===

The autobuilder maintainers are the only ones who can create new branches and release tags in meta-intel, and will do so when necessary as required to generate the infrastructure needed for a release.
* Once a new branch is created for the release, the meta-intel maintainer(s) will add new commits to both master and the release branch up until the time of release (as appropriate - some patches may only be intended for master or the release)

=== meta-intel BSP directory naming convention ===

All directories for meta-intel BSPs should be named in the format of:

meta-platform[-cpu][-crb]

Note: CPU name and CRB name are optional if the BSP supports more than 1 CPU or CRB

=== meta-intel BSP release version scheme ===

Starting with the poky v1.6.1 release in July 2014, meta-intel BSPs started following a new version scheme. With the new scheme meta-intel BSPs get the meta-intel layer version string, along with the compatible poky release name and version needed for the BSP. For example in July 2014 the crownbay-noemgd BSP was relelased as crownbay-noemgd-1.0-daisy-1.6.1 as seen here [https://www.yoctoproject.org/downloads/bsps/daisy161/crown-bay-0 YP BSP link]

The new format for releasing meta-intel BSPs is

<BSP Name>-<meta intel layer version in the major.minor format>-<the poky release name and version compatible for this BSP>
For Example: crownbay-noemgd-1.0-daisy-1.6.1

Note that meta-intel BSPs will generally be compatible with subsequent dot release of the poky layer, because the dot release are for bug fixes, and they do not add new features.

==== Incrementing meta-intel BSP version ====

The major part of the meta-intel layer BSP version is incremented for every major release of Yocto Project release. For the new BSP releases made for the poky dot releases, or new BSP releases which do not change the requirement of the oldest poky release, the minor part of the meta-intel layer version is incremented to denote it as a dot release.

=== Release Notes ===

Currently, the 'release notes' for a BSP consist of the information found on the web page for the BSP in the 'Downloads' section for the BSP, and essentially consists of the BSP's README along with a 'Layer-Specific Notes' section, which is tacked on to the end of the page.

* The Yocto documentation and website maintainers will be responsible for the content of the BSP pages and will ask the BSP maintainer(s) for any additional information needed for a particular BSP
* Normally the only thing needed from the BSP maintainer(s) are the 'Layer-Specific Notes' for a BSP, which the BSP maintainers should supply to the documentation and website maintainers unsolicited as part of the release process.
** Any layer-specific notes that affect multiple or all BSPs should be attached to each BSP separately in the 'Layer-Specific Notes' section.
* The title used for the BSP on the website is retrieved by the documentation and website maintainers from the BSP's WEBTITLE field in the BSP's machine.conf, and should therefore reflect accurately how the BSP is identified on the website. This may be a string defined by marketing, and should at least be approved by marketing.

=== Testing ===

According to the Yocto Project compliance requirements, no meta-intel BSP can be released without testing data. The webpage for each BSP must contain a link to the testing data generated for every image contained in a released BSP. For the BSPs tested by Yocto QA, the QA test report should be the one linked to for those BSPs.

=== Image Verification ===

For every BSP image contained in a tarball released on the Yocto website, it must be verified that the image can be independently generated from scratch (including downloads) using the released metadata.

Customers must (and have, and will) be able to verify that the images contained in the release tarball can in fact be generated from the combination of the metadata contained in the BSP tarball and the set of packages downloaded by the build (from a scratch build) process to create those images.

In practice, this means that the autobuilder maintainer needs to supply the settings required to generate the BSP to the person verifiying the image. If the release tarball is generated by some other process, the BSP maintainer needs to supply that information.
* Note that all images released on the website must contain a time-limited kernel and this must be taken into account when verifying the image.

Bugs Assigned to Nitin

2014-09-09T16:31:38Z

Nitinkamble:

Bugs Assigned to Nitin

2014-09-09T16:27:07Z

Nitinkamble:

{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|hardware=!(MinnowBoard Max, MinnowBoard)
|to=nitin.a.kamble@intel.com
|from=nitin.a.kamble@intel.com
|cc=nitin.a.kamble@intel.com
|columns=id,summary,severity,priority,milestone,to,from,status,whiteboard
|sort=milestone
|noresultsmessage="No matching bugs found."
|total=summary
}}

Bugs Assigned to Nitin

2014-09-09T16:25:29Z

Nitinkamble:

{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|hardware=!(MinnowBoard Max, MinnowBoard)
|to=nitin.a.kamble@intel.com
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=milestone
|noresultsmessage="No matching bugs found."
|total=summary
}}

== All tasks I'm cc'd or I have created and not assigned to me ==
{{#bugzilla:
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=!nitin.a.kamble@intel.com
|from=nitin.a.kamble@intel.com
|cc=nitin.a.kamble@intel.com
}}

Bugs Assigned to Nitin

2014-09-09T16:21:04Z

Nitinkamble:

{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|hardware=!(MinnowBoard Max, MinnowBoard)
|to=nitin.a.kamble@intel.com
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|group=milestone
|noresultsmessage="No matching bugs found."
|total=summary
}}

== All tasks I'm cc'd or I have created and not assigned to me ==
{{#bugzilla:
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=!nitin.a.kamble@intel.com
|from=nitin.a.kamble@intel.com
|cc=nitin.a.kamble@intel.com
}}

Bugs Assigned to Nitin

2014-09-09T16:19:06Z

Nitinkamble:

Bugs Assigned to Nitin

2014-09-09T16:18:11Z

Nitinkamble:

{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|hardware=!(MinnowBoard Max, MinnowBoard)
|to=nitin.a.kamble@intel.com
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=!milestone
|noresultsmessage="No matching bugs found."
|total=summary
}}

== All tasks I'm cc'd or I have created and not assigned to me ==
{{#bugzilla:
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=!nitin.a.kamble@intel.com
|from=nitin.a.kamble@intel.com
|cc=nitin.a.kamble@intel.com
}}

Bugs Assigned to Nitin

2014-09-09T16:16:56Z

Nitinkamble:

{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|hardware=!(MinnowBoard Max, MinnowBoard)
|to=nitin.a.kamble@intel.com
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=!milestone
|noresultsmessage="No matching bugs found."
|total=summary
}}

== All tasks I'm cc'd or I have created and not assigned to me ==
{{#bugzilla:columns=+to,+from
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=!nitin.a.kamble@intel.com
|from=nitin.a.kamble@intel.com
|cc=nitin.a.kamble@intel.com
}}

Bugs Assigned to Nitin

2014-09-09T16:15:50Z

Nitinkamble:

{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|hardware=!(MinnowBoard Max, MinnowBoard)
|to=nitin.a.kamble@intel.com
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=!milestone
|noresultsmessage="No matching bugs found."
|total=summary
}}

== All tasks I'm cc'd or I have created and not assigned to me ==
{{#bugzilla:columns=+to,+from
|to=!nitin.a.kamble@intel.com
|from=nitin.a.kamble@intel.com
|cc=nitin.a.kamble@intel.com
}}

Bugs Assigned to Nitin

2014-09-09T16:09:55Z

Nitinkamble:

Bugs Assigned to Nitin

2014-09-09T16:09:01Z

Nitinkamble:

{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|hardware=!(MinnowBoard Max, MinnowBoard)
|owner=nitin.a.kamble@intel.com
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=priority
|noresultsmessage="No matching bugs found."
|total=summary
}}

Bugs Assigned to Nitin

2014-09-09T16:05:24Z

Nitinkamble:

{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|hardware=!(MinnowBoard Max, MinnowBoard)
|owner="Nitin Kamble"
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=priority
|noresultsmessage="No matching bugs found."
|total=summary
}}

Bugs Assigned to Nitin

2014-09-09T16:04:43Z

Nitinkamble:

{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|hardware=!(MinnowBoard Max, MinnowBoard)
|owner=Nitin Kamble
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=priority
|noresultsmessage="No matching bugs found."
|total=summary
}}

Bugs Assigned to Nitin

2014-09-09T16:04:03Z

Nitinkamble: Created page with "{{#bugzilla: |status=!(RESOLVED,VERIFIED,CLOSED) |hardware=!(MinnowBoard Max, MinnowBoard) |owner=nitin.a.kamble@intel.com |columns=id,summary,severity,priority,milestone..."

Nitin

2014-09-09T16:01:16Z

Nitinkamble: Created page with "== Nitin's Pages == * Bugs Assigned to Nitin"

== Nitin's Pages ==

* [[Bugs Assigned to Nitin]]

Last Known Good Commits for meta-intel

2014-04-25T01:16:08Z

Nitinkamble:

This page may not be uptodate at all the times. To get the latest status contact Nitin Kamble.

Yocto Project Repositories, Branches & Commits:
* poky.git:
** master+work commit 87650bb9aa4fe2bacf9e4486a66c3ebd5851df21
** master: commit 57e8d56a6b63942b616a1e6dd894fd4ea7b409cf
** Additional commits over master:
87650bb linux-yocto-3.14: point srcuri to local repo
* meta-intel.git
** master+work commit eaa294bd980a7d9fd3468a6df2258b3dc60da4d9
** master: commit db84acfc8d9ed8dccd4a79de39fee337bc729662
** Additional commits over master:
eaa294b 3.14: kernel recipes: use the local branch HEADS

BSP Status
* sugarbay:
** Date: 2014-04-23-Wednesday-23-09-16
** poky repo: master: commit 57e8d56a6b63942b616a1e6dd894fd4ea7b409cf
** poky repo: master+work commit 87650bb9aa4fe2bacf9e4486a66c3ebd5851df21
** meta-intel: master: commit db84acfc8d9ed8dccd4a79de39fee337bc729662
** meta-intel: master+work commit eaa294bd980a7d9fd3468a6df2258b3dc60da4d9
** kernel version:linux-yocto-3.14.0+gitAUTOINC+44f9bf45ec_144595ef62-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 41m 5s

* nuc:
** Date: 2014-04-23-Wednesday-23-09-16
** poky repo: master: commit 57e8d56a6b63942b616a1e6dd894fd4ea7b409cf
** poky repo: master+work commit 87650bb9aa4fe2bacf9e4486a66c3ebd5851df21
** meta-intel: master: commit db84acfc8d9ed8dccd4a79de39fee337bc729662
** meta-intel: master+work commit eaa294bd980a7d9fd3468a6df2258b3dc60da4d9
** kernel version:linux-yocto-3.14.0+gitAUTOINC+44f9bf45ec_144595ef62-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 32m 13s

* jasperforest:
** Date: 2014-04-23-Wednesday-23-09-16
** poky repo: master: commit 57e8d56a6b63942b616a1e6dd894fd4ea7b409cf
** poky repo: master+work commit 87650bb9aa4fe2bacf9e4486a66c3ebd5851df21
** meta-intel: master: commit db84acfc8d9ed8dccd4a79de39fee337bc729662
** meta-intel: master+work commit eaa294bd980a7d9fd3468a6df2258b3dc60da4d9
** kernel version:linux-yocto-3.14.0+gitAUTOINC+44f9bf45ec_144595ef62-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 23m 15s

* crownbay:
** Date: 2014-04-23-Wednesday-23-09-16
** poky repo: master: commit 57e8d56a6b63942b616a1e6dd894fd4ea7b409cf
** poky repo: master+work commit 87650bb9aa4fe2bacf9e4486a66c3ebd5851df21
** meta-intel: master: commit db84acfc8d9ed8dccd4a79de39fee337bc729662
** meta-intel: master+work commit eaa294bd980a7d9fd3468a6df2258b3dc60da4d9
** kernel version:linux-yocto-3.10.35+gitAUTOINC+b6e58b33dd_cee957655f-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 42m 19s

* emenlow:
** Date: 2014-04-23-Wednesday-23-09-16
** poky repo: master: commit 57e8d56a6b63942b616a1e6dd894fd4ea7b409cf
** poky repo: master+work commit 87650bb9aa4fe2bacf9e4486a66c3ebd5851df21
** meta-intel: master: commit db84acfc8d9ed8dccd4a79de39fee337bc729662
** meta-intel: master+work commit eaa294bd980a7d9fd3468a6df2258b3dc60da4d9
** kernel version:linux-yocto-3.10.35+gitAUTOINC+b6e58b33dd_cee957655f-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 26m 50s

* crownbay-noemgd:
** Date: 2014-04-23-Wednesday-23-09-16
** poky repo: master: commit 57e8d56a6b63942b616a1e6dd894fd4ea7b409cf
** poky repo: master+work commit 87650bb9aa4fe2bacf9e4486a66c3ebd5851df21
** meta-intel: master: commit db84acfc8d9ed8dccd4a79de39fee337bc729662
** meta-intel: master+work commit eaa294bd980a7d9fd3468a6df2258b3dc60da4d9
** kernel version:linux-yocto-3.14.0+gitAUTOINC+44f9bf45ec_144595ef62-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 26m 8s

* emenlow-noemgd:
** Date: 2014-04-23-Wednesday-23-09-16
** poky repo: master: commit 57e8d56a6b63942b616a1e6dd894fd4ea7b409cf
** poky repo: master+work commit 87650bb9aa4fe2bacf9e4486a66c3ebd5851df21
** meta-intel: master: commit db84acfc8d9ed8dccd4a79de39fee337bc729662
** meta-intel: master+work commit eaa294bd980a7d9fd3468a6df2258b3dc60da4d9
** kernel version:linux-yocto-3.14.0+gitAUTOINC+44f9bf45ec_144595ef62-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 26m 50s

* fri2:
** Date: 2014-04-23-Wednesday-23-09-16
** poky repo: master: commit 57e8d56a6b63942b616a1e6dd894fd4ea7b409cf
** poky repo: master+work commit 87650bb9aa4fe2bacf9e4486a66c3ebd5851df21
** meta-intel: master: commit db84acfc8d9ed8dccd4a79de39fee337bc729662
** meta-intel: master+work commit eaa294bd980a7d9fd3468a6df2258b3dc60da4d9
** kernel version:linux-yocto-3.10.35+gitAUTOINC+b6e58b33dd_cee957655f-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 26m 5s

* fri2-noemgd:
** Date: 2014-04-23-Wednesday-23-09-16
** poky repo: master: commit 57e8d56a6b63942b616a1e6dd894fd4ea7b409cf
** poky repo: master+work commit 87650bb9aa4fe2bacf9e4486a66c3ebd5851df21
** meta-intel: master: commit db84acfc8d9ed8dccd4a79de39fee337bc729662
** meta-intel: master+work commit eaa294bd980a7d9fd3468a6df2258b3dc60da4d9
** kernel version:linux-yocto-3.14.0+gitAUTOINC+44f9bf45ec_144595ef62-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 26m 28s

* intel-core2-32:
** Date: 2014-04-23-Wednesday-23-09-16
** poky repo: master: commit 57e8d56a6b63942b616a1e6dd894fd4ea7b409cf
** poky repo: master+work commit 87650bb9aa4fe2bacf9e4486a66c3ebd5851df21
** meta-intel: master: commit db84acfc8d9ed8dccd4a79de39fee337bc729662
** meta-intel: master+work commit eaa294bd980a7d9fd3468a6df2258b3dc60da4d9
** kernel version:linux-yocto-3.14.0+gitAUTOINC+44f9bf45ec_144595ef62-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 34m 30s

* intel-corei7-64:
** Date: 2014-04-23-Wednesday-23-09-16
** poky repo: master: commit 57e8d56a6b63942b616a1e6dd894fd4ea7b409cf
** poky repo: master+work commit 87650bb9aa4fe2bacf9e4486a66c3ebd5851df21
** meta-intel: master: commit db84acfc8d9ed8dccd4a79de39fee337bc729662
** meta-intel: master+work commit eaa294bd980a7d9fd3468a6df2258b3dc60da4d9
** kernel version:linux-yocto-3.14.0+gitAUTOINC+44f9bf45ec_144595ef62-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 25m 30s

Last Known Good Commits for meta-intel

2014-03-14T01:48:07Z

Nitinkamble:

This page tracks the last poky and meta-intel commits that were verified to build and boot into sato for each meta-intel BSP.

This BSP health status is updated weekly by Nitin A Kamble <nitin.a.kamble@intel.com>

Yocto Project Repositories, Branches & Commits:

Yocto Project Repositories, Branches & Commits:
* poky.git:
** master+work commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** master: commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** Additional commits over master:
* meta-intel.git
** master+work commit 82bf35e54a224f4692aa8eabc569a0b756504f69
** master: commit a5b790da02f657bae8f32d817fc391e2c67fd3a9
** Additional commits over master:
6b0ea03 sys940x: linux-yocto_3.10: update git branch SRCREVs
42ed65a sugarbay: linux-yocto_3.10: update git branch SRCREVs
403fe2e nuc: linux-yocto_3.10: update git branch SRCREVs
984f94e jasperforest: linux-yocto_3.10: update git branch SRCREVs
9ac57db fri2: linux-yocto_3.10: update git branch SRCREVs
427b023 emenlow: linux-yocto_3.10: update git branch SRCREVs
0b8e156 crownbay: linux-yocto_3.10: update git branch SRCREVs
8a4be95 chiefriver: linux-yocto_3.10: update git branch SRCREVs

BSP Status
* sugarbay:
** Date: 2014-03-12-Wednesday-13-17-01
** poky repo: master: commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** poky repo: master+work commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** meta-intel: master: commit a5b790da02f657bae8f32d817fc391e2c67fd3a9
** meta-intel: master+work commit 82bf35e54a224f4692aa8eabc569a0b756504f69
** kernel version:linux-yocto-3.10.32+gitAUTOINC+6e0e756d51_78afd3095c-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 56m 10s

* nuc:
** Date: 2014-03-12-Wednesday-13-17-01
** poky repo: master: commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** poky repo: master+work commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** meta-intel: master: commit a5b790da02f657bae8f32d817fc391e2c67fd3a9
** meta-intel: master+work commit 82bf35e54a224f4692aa8eabc569a0b756504f69
** kernel version:linux-yocto-3.10.32+gitAUTOINC+6e0e756d51_78afd3095c-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 1h 19m 13s

* jasperforest:
** Date: 2014-03-12-Wednesday-13-17-01
** poky repo: master: commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** poky repo: master+work commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** meta-intel: master: commit a5b790da02f657bae8f32d817fc391e2c67fd3a9
** meta-intel: master+work commit 82bf35e54a224f4692aa8eabc569a0b756504f69
** kernel version:linux-yocto-3.10.32+gitAUTOINC+6e0e756d51_78afd3095c-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 26m 1s

* crownbay:
** Date: 2014-03-12-Wednesday-13-17-01
** poky repo: master: commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** poky repo: master+work commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** meta-intel: master: commit a5b790da02f657bae8f32d817fc391e2c67fd3a9
** meta-intel: master+work commit 82bf35e54a224f4692aa8eabc569a0b756504f69
** kernel version:linux-yocto-3.10.32+gitAUTOINC+6e0e756d51_78afd3095c-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 1h 0m 36s

* chiefriver:
** Date: 2014-03-12-Wednesday-13-17-01
** poky repo: master: commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** poky repo: master+work commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** meta-intel: master: commit a5b790da02f657bae8f32d817fc391e2c67fd3a9
** meta-intel: master+work commit 82bf35e54a224f4692aa8eabc569a0b756504f69
** kernel version:linux-yocto-3.10.32+gitAUTOINC+6e0e756d51_78afd3095c-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 25m 18s

* emenlow:
** Date: 2014-03-12-Wednesday-13-17-01
** poky repo: master: commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** poky repo: master+work commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** meta-intel: master: commit a5b790da02f657bae8f32d817fc391e2c67fd3a9
** meta-intel: master+work commit 82bf35e54a224f4692aa8eabc569a0b756504f69
** kernel version:linux-yocto-3.10.32+gitAUTOINC+6e0e756d51_78afd3095c-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 31m 36s

* crownbay-noemgd:
** Date: 2014-03-12-Wednesday-13-17-01
** poky repo: master: commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** poky repo: master+work commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** meta-intel: master: commit a5b790da02f657bae8f32d817fc391e2c67fd3a9
** meta-intel: master+work commit 82bf35e54a224f4692aa8eabc569a0b756504f69
** kernel version:linux-yocto-3.10.32+gitAUTOINC+6e0e756d51_78afd3095c-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 30m 50s

* emenlow-noemgd:
** Date: 2014-03-12-Wednesday-13-17-01
** poky repo: master: commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** poky repo: master+work commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** meta-intel: master: commit a5b790da02f657bae8f32d817fc391e2c67fd3a9
** meta-intel: master+work commit 82bf35e54a224f4692aa8eabc569a0b756504f69
** kernel version:linux-yocto-3.10.32+gitAUTOINC+6e0e756d51_78afd3095c-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 31m 50s

* fri2:
** Date: 2014-03-12-Wednesday-13-17-01
** poky repo: master: commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** poky repo: master+work commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** meta-intel: master: commit a5b790da02f657bae8f32d817fc391e2c67fd3a9
** meta-intel: master+work commit 82bf35e54a224f4692aa8eabc569a0b756504f69
** kernel version:linux-yocto-3.10.32+gitAUTOINC+6e0e756d51_78afd3095c-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 27m 44s

* fri2-noemgd:
** Date: 2014-03-12-Wednesday-13-17-01
** poky repo: master: commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** poky repo: master+work commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** meta-intel: master: commit a5b790da02f657bae8f32d817fc391e2c67fd3a9
** meta-intel: master+work commit 82bf35e54a224f4692aa8eabc569a0b756504f69
** kernel version:linux-yocto-3.10.32+gitAUTOINC+6e0e756d51_78afd3095c-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 28m 24s

* sys940x:
** Date: 2014-03-12-Wednesday-13-17-01
** poky repo: master: commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** poky repo: master+work commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** meta-intel: master: commit a5b790da02f657bae8f32d817fc391e2c67fd3a9
** meta-intel: master+work commit 82bf35e54a224f4692aa8eabc569a0b756504f69
** kernel version:linux-yocto-3.10.32+gitAUTOINC+6e0e756d51_78afd3095c-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 27m 42s

* sys940x-noemgd:
** Date: 2014-03-12-Wednesday-13-17-01
** poky repo: master: commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** poky repo: master+work commit 5f05bdda0bf3f9fadf287a0632c2fa697380273f
** meta-intel: master: commit a5b790da02f657bae8f32d817fc391e2c67fd3a9
** meta-intel: master+work commit 82bf35e54a224f4692aa8eabc569a0b756504f69
** kernel version:linux-yocto-3.10.32+gitAUTOINC+6e0e756d51_78afd3095c-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 28m 15s

Last Known Good Commits for meta-intel

2014-02-13T23:49:06Z

Nitinkamble:

This page tracks the last poky and meta-intel commits that were verified to build and boot into sato for each meta-intel BSP.

This BSP health status is updated weekly by Nitin A Kamble <nitin.a.kamble@intel.com>

Yocto Project Repositories, Branches & Commits:

Builds: 11 succeeded, 5 failed.

Yocto Project Repositories, Branches & Commits:
* poky.git:
** master+work commit 16888c8b31b3936a8a1007472feee95b70112db3
** master: commit b70a10ca3ee4a0add90d387e2c8288e531aaa47c
** Additional commits over master:
16888c8 Revert "linux-yocto-dev: a temp fix for build IRQ issue"
6e5c227 linux-yocto-dev: a temp fix for build IRQ issue
* meta-intel.git
** master+work commit cbfea853e2e3af4aed3061bf09ae3b4a657065af
** master: commit 49b97a90ea3bce2a61a8578cface01f32a97e2b3
** Additional commits over master:
cbfea85 Revert "gstreamer-vaapi recipes : updates to v 5.8"
4028cfb gstreamer-vaapi recipes : updates to v 5.8
b4d7e1e libxrandr recipe of version 1.2.3
317f18f xrandr-1.2.3 recipe

BSP Status
* qemux86:
** Date: 2014-02-12-Wednesday-13-26-04
** poky repo: master: commit b70a10ca3ee4a0add90d387e2c8288e531aaa47c
** poky repo: master+work commit 16888c8b31b3936a8a1007472feee95b70112db3
** meta-intel: master: commit 49b97a90ea3bce2a61a8578cface01f32a97e2b3
** meta-intel: master+work commit cbfea853e2e3af4aed3061bf09ae3b4a657065af
** kernel version:linux-yocto-dev-3.13++gitAUTOINC+4217f8c61f_889c6bec6b-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 1h 1m 19s

* genericx86:
** Date: 2014-02-12-Wednesday-13-26-04
** poky repo: master: commit b70a10ca3ee4a0add90d387e2c8288e531aaa47c
** poky repo: master+work commit 16888c8b31b3936a8a1007472feee95b70112db3
** meta-intel: master: commit 49b97a90ea3bce2a61a8578cface01f32a97e2b3
** meta-intel: master+work commit cbfea853e2e3af4aed3061bf09ae3b4a657065af
** kernel version:linux-yocto-3.10.25+gitAUTOINC+713abc0efa_79af968f2f-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 57m 17s

* genericx86-64:
** Date: 2014-02-12-Wednesday-13-26-04
** poky repo: master: commit b70a10ca3ee4a0add90d387e2c8288e531aaa47c
** poky repo: master+work commit 16888c8b31b3936a8a1007472feee95b70112db3
** meta-intel: master: commit 49b97a90ea3bce2a61a8578cface01f32a97e2b3
** meta-intel: master+work commit cbfea853e2e3af4aed3061bf09ae3b4a657065af
** kernel version:linux-yocto-3.10.25+gitAUTOINC+713abc0efa_79af968f2f-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 55m 45s

* sugarbay:
** Date: 2014-02-12-Wednesday-13-26-04
** poky repo: master: commit b70a10ca3ee4a0add90d387e2c8288e531aaa47c
** poky repo: master+work commit 16888c8b31b3936a8a1007472feee95b70112db3
** meta-intel: master: commit 49b97a90ea3bce2a61a8578cface01f32a97e2b3
** meta-intel: master+work commit cbfea853e2e3af4aed3061bf09ae3b4a657065af
** kernel version:linux-yocto-dev-3.12.0+gitAUTOINC+4217f8c61f_889c6bec6b-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 59m 2s

* nuc:
** Date: 2014-02-12-Wednesday-13-26-04
** poky repo: master: commit b70a10ca3ee4a0add90d387e2c8288e531aaa47c
** poky repo: master+work commit 16888c8b31b3936a8a1007472feee95b70112db3
** meta-intel: master: commit 49b97a90ea3bce2a61a8578cface01f32a97e2b3
** meta-intel: master+work commit cbfea853e2e3af4aed3061bf09ae3b4a657065af
** kernel version:linux-yocto-dev-3.13++gitAUTOINC+4217f8c61f_889c6bec6b-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 1h 24m 42s

* jasperforest:
** Date: 2014-02-12-Wednesday-13-26-04
** poky repo: master: commit b70a10ca3ee4a0add90d387e2c8288e531aaa47c
** poky repo: master+work commit 16888c8b31b3936a8a1007472feee95b70112db3
** meta-intel: master: commit 49b97a90ea3bce2a61a8578cface01f32a97e2b3
** meta-intel: master+work commit cbfea853e2e3af4aed3061bf09ae3b4a657065af
** kernel version:linux-yocto-dev-3.13++gitAUTOINC+4217f8c61f_889c6bec6b-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 32m 32s

* crownbay:
** Date: 2014-02-12-Wednesday-13-26-04
** poky repo: master: commit b70a10ca3ee4a0add90d387e2c8288e531aaa47c
** poky repo: master+work commit 16888c8b31b3936a8a1007472feee95b70112db3
** meta-intel: master: commit 49b97a90ea3bce2a61a8578cface01f32a97e2b3
** meta-intel: master+work commit cbfea853e2e3af4aed3061bf09ae3b4a657065af
** kernel version:linux-yocto-3.10.19+gitAUTOINC+d9cd83c029_a9ec82e355-r0
** Build Status: Build failed
** Testing Status:
Time taken = 0h 19m 37s

* chiefriver:
** Date: 2014-02-12-Wednesday-13-26-04
** poky repo: master: commit b70a10ca3ee4a0add90d387e2c8288e531aaa47c
** poky repo: master+work commit 16888c8b31b3936a8a1007472feee95b70112db3
** meta-intel: master: commit 49b97a90ea3bce2a61a8578cface01f32a97e2b3
** meta-intel: master+work commit cbfea853e2e3af4aed3061bf09ae3b4a657065af
** kernel version:linux-yocto-dev-3.13++gitAUTOINC+4217f8c61f_889c6bec6b-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 27m 27s

* emenlow:
** Date: 2014-02-12-Wednesday-13-26-04
** poky repo: master: commit b70a10ca3ee4a0add90d387e2c8288e531aaa47c
** poky repo: master+work commit 16888c8b31b3936a8a1007472feee95b70112db3
** meta-intel: master: commit 49b97a90ea3bce2a61a8578cface01f32a97e2b3
** meta-intel: master+work commit cbfea853e2e3af4aed3061bf09ae3b4a657065af
** kernel version:linux-yocto-3.10.19+gitAUTOINC+d9cd83c029_a9ec82e355-r0
** Build Status: Build failed
** Testing Status:
Time taken = 0h 18m 59s

* crownbay-noemgd:
** Date: 2014-02-12-Wednesday-13-26-04
** poky repo: master: commit b70a10ca3ee4a0add90d387e2c8288e531aaa47c
** poky repo: master+work commit 16888c8b31b3936a8a1007472feee95b70112db3
** meta-intel: master: commit 49b97a90ea3bce2a61a8578cface01f32a97e2b3
** meta-intel: master+work commit cbfea853e2e3af4aed3061bf09ae3b4a657065af
** kernel version:linux-yocto-dev-3.13++gitAUTOINC+4217f8c61f_889c6bec6b-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 35m 33s

* emenlow-noemgd:
** Date: 2014-02-12-Wednesday-13-26-04
** poky repo: master: commit b70a10ca3ee4a0add90d387e2c8288e531aaa47c
** poky repo: master+work commit 16888c8b31b3936a8a1007472feee95b70112db3
** meta-intel: master: commit 49b97a90ea3bce2a61a8578cface01f32a97e2b3
** meta-intel: master+work commit cbfea853e2e3af4aed3061bf09ae3b4a657065af
** kernel version:linux-yocto-dev-3.13++gitAUTOINC+4217f8c61f_889c6bec6b-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 36m 31s

* fri2:
** Date: 2014-02-12-Wednesday-13-26-04
** poky repo: master: commit b70a10ca3ee4a0add90d387e2c8288e531aaa47c
** poky repo: master+work commit 16888c8b31b3936a8a1007472feee95b70112db3
** meta-intel: master: commit 49b97a90ea3bce2a61a8578cface01f32a97e2b3
** meta-intel: master+work commit cbfea853e2e3af4aed3061bf09ae3b4a657065af
** kernel version:linux-yocto-3.10.19+gitAUTOINC+d9cd83c029_a9ec82e355-r0
** Build Status: Build failed
** Testing Status:
Time taken = 0h 19m 37s

* fri2-noemgd:
** Date: 2014-02-12-Wednesday-13-26-04
** poky repo: master: commit b70a10ca3ee4a0add90d387e2c8288e531aaa47c
** poky repo: master+work commit 16888c8b31b3936a8a1007472feee95b70112db3
** meta-intel: master: commit 49b97a90ea3bce2a61a8578cface01f32a97e2b3
** meta-intel: master+work commit cbfea853e2e3af4aed3061bf09ae3b4a657065af
** kernel version:linux-yocto-dev-3.13++gitAUTOINC+4217f8c61f_889c6bec6b-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 30m 32s

* sys940x:
** Date: 2014-02-12-Wednesday-13-26-04
** poky repo: master: commit b70a10ca3ee4a0add90d387e2c8288e531aaa47c
** poky repo: master+work commit 16888c8b31b3936a8a1007472feee95b70112db3
** meta-intel: master: commit 49b97a90ea3bce2a61a8578cface01f32a97e2b3
** meta-intel: master+work commit cbfea853e2e3af4aed3061bf09ae3b4a657065af
** kernel version:linux-yocto-3.10.19+gitAUTOINC+d9cd83c029_a9ec82e355-r0
** Build Status: Build failed
** Testing Status:
Time taken = 0h 19m 10s

* sys940x-noemgd:
** Date: 2014-02-12-Wednesday-13-26-04
** poky repo: master: commit b70a10ca3ee4a0add90d387e2c8288e531aaa47c
** poky repo: master+work commit 16888c8b31b3936a8a1007472feee95b70112db3
** meta-intel: master: commit 49b97a90ea3bce2a61a8578cface01f32a97e2b3
** meta-intel: master+work commit cbfea853e2e3af4aed3061bf09ae3b4a657065af
** kernel version:linux-yocto-dev-3.13++gitAUTOINC+4217f8c61f_889c6bec6b-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 29m 47s

* minnow:
** Date: 2014-02-12-Wednesday-13-26-04
** poky repo: master: commit b70a10ca3ee4a0add90d387e2c8288e531aaa47c
** poky repo: master+work commit 16888c8b31b3936a8a1007472feee95b70112db3
** meta-intel: master: commit 49b97a90ea3bce2a61a8578cface01f32a97e2b3
** meta-intel: master+work commit cbfea853e2e3af4aed3061bf09ae3b4a657065af
** kernel version:linux-yocto-3.10.25+gitAUTOINC+4d658aa580_79af968f2f-r0
** Build Status: Build failed
** Testing Status:

Last Known Good Commits for meta-intel

2014-01-28T19:07:12Z

Nitinkamble:

This page tracks the last poky and meta-intel commits that were verified to build and boot into sato for each meta-intel BSP.

This BSP health status is updated weekly by Nitin A Kamble <nitin.a.kamble@intel.com>

Yocto Project Repositories, Branches & Commits:

* poky.git:
** master+work commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** master: commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** Additional commits over master:
* meta-intel.git
** master+work commit 80a906c8aa3458c88ae6deb86e30f5e1826f0a69
** master: commit d8c1d14f9e0a87a0b4357b8764a0df40cc22f789
** Additional commits over master:
80a906c emgd-driver-bin: preserves the package stripping logic
129a5ab libxrandr recipe of version 1.2.3
15a324d xrandr-1.2.3 recipe
8899da2 sys940x-noemgd: linux-yocto-dev: update to use poky srcrevs
b684fb7 fri2-noemgd: linux-yocto-dev: update to use poky srcrevs
f65b821 emenlow-noemgd: linux-yocto-dev: update to use poky srcrevs
d331363 crownbay-noemgd: linux-yocto-dev: update to use poky srcrevs
54020c7 sugarbay: linux-yocto-dev: update to use poky srcrevs
059bff2 nuc: linux-yocto-dev: update to use poky srcrevs
e91dd92 jasperforest: linux-yocto-dev: update to use poky srcrevs
2b60785 chiefriver dev kernel update
722136d chiefriver: linux-yocto-dev: update to use poky srcrevs
053baea chiefriver: linux-yocto-dev: update srcrevs to v3.12.0
313c979 sugarbay: linux-yocto-dev: update srcrevs to v3.12.0

BSP Status
* qemux86:
** Date: 2014-01-27-Monday-16-47-16
** poky repo: master: commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** poky repo: master+work commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** meta-intel: master: commit d8c1d14f9e0a87a0b4357b8764a0df40cc22f789
** meta-intel: master+work commit 80a906c8aa3458c88ae6deb86e30f5e1826f0a69
** kernel version:linux-yocto-dev-3.10++gitAUTOINC+0580cffb6f_7446bf268c-r0
** Build Status: Build succeeded
** Testing Status:

* genericx86:
** Date: 2014-01-27-Monday-16-47-16
** poky repo: master: commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** poky repo: master+work commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** meta-intel: master: commit d8c1d14f9e0a87a0b4357b8764a0df40cc22f789
** meta-intel: master+work commit 80a906c8aa3458c88ae6deb86e30f5e1826f0a69
** kernel version:linux-yocto-3.10.19+gitAUTOINC+f47ea28445_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* genericx86-64:
** Date: 2014-01-27-Monday-16-47-16
** poky repo: master: commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** poky repo: master+work commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** meta-intel: master: commit d8c1d14f9e0a87a0b4357b8764a0df40cc22f789
** meta-intel: master+work commit 80a906c8aa3458c88ae6deb86e30f5e1826f0a69
** kernel version:linux-yocto-3.10.19+gitAUTOINC+f47ea28445_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* sugarbay:
** Date: 2014-01-27-Monday-16-47-16
** poky repo: master: commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** poky repo: master+work commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** meta-intel: master: commit d8c1d14f9e0a87a0b4357b8764a0df40cc22f789
** meta-intel: master+work commit 80a906c8aa3458c88ae6deb86e30f5e1826f0a69
** kernel version:linux-yocto-dev-3.10++gitAUTOINC+0580cffb6f_7446bf268c-r0
** Build Status: Build succeeded
** Testing Status:

* nuc:
** Date: 2014-01-27-Monday-16-47-16
** poky repo: master: commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** poky repo: master+work commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** meta-intel: master: commit d8c1d14f9e0a87a0b4357b8764a0df40cc22f789
** meta-intel: master+work commit 80a906c8aa3458c88ae6deb86e30f5e1826f0a69
** kernel version:linux-yocto-dev-3.10++gitAUTOINC+0580cffb6f_7446bf268c-r0
** Build Status: Build succeeded
** Testing Status:

* jasperforest:
** Date: 2014-01-27-Monday-16-47-16
** poky repo: master: commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** poky repo: master+work commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** meta-intel: master: commit d8c1d14f9e0a87a0b4357b8764a0df40cc22f789
** meta-intel: master+work commit 80a906c8aa3458c88ae6deb86e30f5e1826f0a69
** kernel version:linux-yocto-dev-3.10++gitAUTOINC+0580cffb6f_7446bf268c-r0
** Build Status: Build succeeded
** Testing Status:

* crownbay:
** Date: 2014-01-27-Monday-16-47-16
** poky repo: master: commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** poky repo: master+work commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** meta-intel: master: commit d8c1d14f9e0a87a0b4357b8764a0df40cc22f789
** meta-intel: master+work commit 80a906c8aa3458c88ae6deb86e30f5e1826f0a69
** kernel version:linux-yocto-3.10.19+gitAUTOINC+d9cd83c029_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* chiefriver:
** Date: 2014-01-27-Monday-16-47-16
** poky repo: master: commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** poky repo: master+work commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** meta-intel: master: commit d8c1d14f9e0a87a0b4357b8764a0df40cc22f789
** meta-intel: master+work commit 80a906c8aa3458c88ae6deb86e30f5e1826f0a69
** kernel version:linux-yocto-dev-3.10++gitAUTOINC+0580cffb6f_7446bf268c-r0
** Build Status: Build succeeded
** Testing Status:

* emenlow:
** Date: 2014-01-27-Monday-16-47-16
** poky repo: master: commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** poky repo: master+work commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** meta-intel: master: commit d8c1d14f9e0a87a0b4357b8764a0df40cc22f789
** meta-intel: master+work commit 80a906c8aa3458c88ae6deb86e30f5e1826f0a69
** kernel version:linux-yocto-3.10.19+gitAUTOINC+d9cd83c029_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* crownbay-noemgd:
** Date: 2014-01-27-Monday-16-47-16
** poky repo: master: commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** poky repo: master+work commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** meta-intel: master: commit d8c1d14f9e0a87a0b4357b8764a0df40cc22f789
** meta-intel: master+work commit 80a906c8aa3458c88ae6deb86e30f5e1826f0a69
** kernel version:linux-yocto-3.10.19+gitAUTOINC+d9cd83c029_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* emenlow-noemgd:
** Date: 2014-01-27-Monday-16-47-16
** poky repo: master: commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** poky repo: master+work commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** meta-intel: master: commit d8c1d14f9e0a87a0b4357b8764a0df40cc22f789
** meta-intel: master+work commit 80a906c8aa3458c88ae6deb86e30f5e1826f0a69
** kernel version:linux-yocto-3.10.19+gitAUTOINC+d9cd83c029_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* fri2:
** Date: 2014-01-27-Monday-16-47-16
** poky repo: master: commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** poky repo: master+work commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** meta-intel: master: commit d8c1d14f9e0a87a0b4357b8764a0df40cc22f789
** meta-intel: master+work commit 80a906c8aa3458c88ae6deb86e30f5e1826f0a69
** kernel version:linux-yocto-3.10.19+gitAUTOINC+d9cd83c029_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* fri2-noemgd:
** Date: 2014-01-27-Monday-16-47-16
** poky repo: master: commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** poky repo: master+work commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** meta-intel: master: commit d8c1d14f9e0a87a0b4357b8764a0df40cc22f789
** meta-intel: master+work commit 80a906c8aa3458c88ae6deb86e30f5e1826f0a69
** kernel version:linux-yocto-3.10.19+gitAUTOINC+d9cd83c029_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* sys940x:
** Date: 2014-01-27-Monday-16-47-16
** poky repo: master: commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** poky repo: master+work commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** meta-intel: master: commit d8c1d14f9e0a87a0b4357b8764a0df40cc22f789
** meta-intel: master+work commit 80a906c8aa3458c88ae6deb86e30f5e1826f0a69
** kernel version:linux-yocto-3.10.19+gitAUTOINC+d9cd83c029_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* sys940x-noemgd:
** Date: 2014-01-27-Monday-16-47-16
** poky repo: master: commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** poky repo: master+work commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** meta-intel: master: commit d8c1d14f9e0a87a0b4357b8764a0df40cc22f789
** meta-intel: master+work commit 80a906c8aa3458c88ae6deb86e30f5e1826f0a69
** kernel version:linux-yocto-3.10.19+gitAUTOINC+d9cd83c029_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* minnow:
** Date: 2014-01-27-Monday-16-47-16
** poky repo: master: commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** poky repo: master+work commit 1b636173ca88e5ccca1992f9a12367a1189fa674
** meta-intel: master: commit d8c1d14f9e0a87a0b4357b8764a0df40cc22f789
** meta-intel: master+work commit 80a906c8aa3458c88ae6deb86e30f5e1826f0a69
** kernel version:linux-yocto-3.10.17+gitAUTOINC+4a04774a65_c03195ed6e-r0
** Build Status: Build succeeded

Last Known Good Commits for meta-intel

2014-01-09T19:27:38Z

Nitinkamble:

This page tracks the last poky and meta-intel commits that were verified to build and boot into sato for each meta-intel BSP.

This BSP health status is updated weekly by Nitin A Kamble <nitin.a.kamble@intel.com>

Yocto Project Repositories, Branches & Commits:
* poky.git:
** master+work commit f4ae4399140ef61bafdd9223583a249279959ae1
** master: commit f4ae4399140ef61bafdd9223583a249279959ae1
** Additional commits over master:
* meta-intel.git
** master+work commit c37936116b60c66c40fe77f421a4bd66dbe4d9ea
** master: commit f707b6c67909ccd84cb2070bdc15777573833461
** Additional commits over master:
c379361 sugarbay: linux-yocto-3.10: enable the webcam feature
e5fe027 sugarbay: linux-yocto-dev: update the webcam feature name
5d51014 chiefriver: make linux-yocto-dev as the default kernel
ad2a4b1 chiefriver: linux-yocto-dev: update srcrevs to v3.12.0
ab9331b sugarbay: make linux-yocto-dev as the default kernel
d5ebaff sugarbay: linux-yocto-dev: update srcrevs to v3.12.0

BSP Status
* qemux86:
** Date: 2014-01-07-Tuesday-13-34-23
** poky repo: master: commit f4ae4399140ef61bafdd9223583a249279959ae1
** poky repo: master+work commit f4ae4399140ef61bafdd9223583a249279959ae1
** meta-intel: master: commit f707b6c67909ccd84cb2070bdc15777573833461
** meta-intel: master+work commit c37936116b60c66c40fe77f421a4bd66dbe4d9ea
** kernel version:linux-yocto-3.10.19+gitAUTOINC+18b8c6c3d9_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* genericx86:
** Date: 2014-01-07-Tuesday-13-34-23
** poky repo: master: commit f4ae4399140ef61bafdd9223583a249279959ae1
** poky repo: master+work commit f4ae4399140ef61bafdd9223583a249279959ae1
** meta-intel: master: commit f707b6c67909ccd84cb2070bdc15777573833461
** meta-intel: master+work commit c37936116b60c66c40fe77f421a4bd66dbe4d9ea
** kernel version:linux-yocto-3.10.19+gitAUTOINC+18b8c6c3d9_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* genericx86-64:
** Date: 2014-01-07-Tuesday-13-34-23
** poky repo: master: commit f4ae4399140ef61bafdd9223583a249279959ae1
** poky repo: master+work commit f4ae4399140ef61bafdd9223583a249279959ae1
** meta-intel: master: commit f707b6c67909ccd84cb2070bdc15777573833461
** meta-intel: master+work commit c37936116b60c66c40fe77f421a4bd66dbe4d9ea
** kernel version:linux-yocto-3.10.19+gitAUTOINC+18b8c6c3d9_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 49m 11s

* sugarbay:
** Date: 2014-01-07-Tuesday-13-34-23
** poky repo: master: commit f4ae4399140ef61bafdd9223583a249279959ae1
** poky repo: master+work commit f4ae4399140ef61bafdd9223583a249279959ae1
** meta-intel: master: commit f707b6c67909ccd84cb2070bdc15777573833461
** meta-intel: master+work commit c37936116b60c66c40fe77f421a4bd66dbe4d9ea
** kernel version:linux-yocto-3.10.19+gitAUTOINC+18b8c6c3d9_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* nuc:
** Date: 2014-01-07-Tuesday-13-34-23
** poky repo: master: commit f4ae4399140ef61bafdd9223583a249279959ae1
** poky repo: master+work commit f4ae4399140ef61bafdd9223583a249279959ae1
** meta-intel: master: commit f707b6c67909ccd84cb2070bdc15777573833461
** meta-intel: master+work commit c37936116b60c66c40fe77f421a4bd66dbe4d9ea
** kernel version:linux-yocto-3.10.19+gitAUTOINC+18b8c6c3d9_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* jasperforest:
** Date: 2014-01-07-Tuesday-13-34-23
** poky repo: master: commit f4ae4399140ef61bafdd9223583a249279959ae1
** poky repo: master+work commit f4ae4399140ef61bafdd9223583a249279959ae1
** meta-intel: master: commit f707b6c67909ccd84cb2070bdc15777573833461
** meta-intel: master+work commit c37936116b60c66c40fe77f421a4bd66dbe4d9ea
** kernel version:linux-yocto-3.10.19+gitAUTOINC+18b8c6c3d9_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* crownbay:
** Date: 2014-01-07-Tuesday-13-34-23
** poky repo: master: commit f4ae4399140ef61bafdd9223583a249279959ae1
** poky repo: master+work commit f4ae4399140ef61bafdd9223583a249279959ae1
** meta-intel: master: commit f707b6c67909ccd84cb2070bdc15777573833461
** meta-intel: master+work commit c37936116b60c66c40fe77f421a4bd66dbe4d9ea
** kernel version:linux-yocto-3.10.19+gitAUTOINC+18b8c6c3d9_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* chiefriver:
** Date: 2014-01-07-Tuesday-13-34-23
** poky repo: master: commit f4ae4399140ef61bafdd9223583a249279959ae1
** poky repo: master+work commit f4ae4399140ef61bafdd9223583a249279959ae1
** meta-intel: master: commit f707b6c67909ccd84cb2070bdc15777573833461
** meta-intel: master+work commit c37936116b60c66c40fe77f421a4bd66dbe4d9ea
** kernel version:linux-yocto-3.10.19+gitAUTOINC+18b8c6c3d9_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* emenlow:
** Date: 2014-01-07-Tuesday-13-34-23
** poky repo: master: commit f4ae4399140ef61bafdd9223583a249279959ae1
** poky repo: master+work commit f4ae4399140ef61bafdd9223583a249279959ae1
** meta-intel: master: commit f707b6c67909ccd84cb2070bdc15777573833461
** meta-intel: master+work commit c37936116b60c66c40fe77f421a4bd66dbe4d9ea
** kernel version:linux-yocto-3.10.19+gitAUTOINC+18b8c6c3d9_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* crownbay-noemgd:
** Date: 2014-01-07-Tuesday-13-34-23
** poky repo: master: commit f4ae4399140ef61bafdd9223583a249279959ae1
** poky repo: master+work commit f4ae4399140ef61bafdd9223583a249279959ae1
** meta-intel: master: commit f707b6c67909ccd84cb2070bdc15777573833461
** meta-intel: master+work commit c37936116b60c66c40fe77f421a4bd66dbe4d9ea
** kernel version:linux-yocto-3.10.19+gitAUTOINC+18b8c6c3d9_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* emenlow-noemgd:
** Date: 2014-01-07-Tuesday-13-34-23
** poky repo: master: commit f4ae4399140ef61bafdd9223583a249279959ae1
** poky repo: master+work commit f4ae4399140ef61bafdd9223583a249279959ae1
** meta-intel: master: commit f707b6c67909ccd84cb2070bdc15777573833461
** meta-intel: master+work commit c37936116b60c66c40fe77f421a4bd66dbe4d9ea
** kernel version:linux-yocto-3.10.19+gitAUTOINC+18b8c6c3d9_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* fri2:
** Date: 2014-01-07-Tuesday-13-34-23
** poky repo: master: commit f4ae4399140ef61bafdd9223583a249279959ae1
** poky repo: master+work commit f4ae4399140ef61bafdd9223583a249279959ae1
** meta-intel: master: commit f707b6c67909ccd84cb2070bdc15777573833461
** meta-intel: master+work commit c37936116b60c66c40fe77f421a4bd66dbe4d9ea
** kernel version:linux-yocto-3.10.19+gitAUTOINC+18b8c6c3d9_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* fri2-noemgd:
** Date: 2014-01-07-Tuesday-13-34-23
** poky repo: master: commit f4ae4399140ef61bafdd9223583a249279959ae1
** poky repo: master+work commit f4ae4399140ef61bafdd9223583a249279959ae1
** meta-intel: master: commit f707b6c67909ccd84cb2070bdc15777573833461
** meta-intel: master+work commit c37936116b60c66c40fe77f421a4bd66dbe4d9ea
** kernel version:linux-yocto-3.10.19+gitAUTOINC+18b8c6c3d9_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* sys940x:
** Date: 2014-01-07-Tuesday-13-34-23
** poky repo: master: commit f4ae4399140ef61bafdd9223583a249279959ae1
** poky repo: master+work commit f4ae4399140ef61bafdd9223583a249279959ae1
** meta-intel: master: commit f707b6c67909ccd84cb2070bdc15777573833461
** meta-intel: master+work commit c37936116b60c66c40fe77f421a4bd66dbe4d9ea
** kernel version:linux-yocto-3.10.19+gitAUTOINC+18b8c6c3d9_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* sys940x-noemgd:
** Date: 2014-01-07-Tuesday-13-34-23
** poky repo: master: commit f4ae4399140ef61bafdd9223583a249279959ae1
** poky repo: master+work commit f4ae4399140ef61bafdd9223583a249279959ae1
** meta-intel: master: commit f707b6c67909ccd84cb2070bdc15777573833461
** meta-intel: master+work commit c37936116b60c66c40fe77f421a4bd66dbe4d9ea
** kernel version:linux-yocto-3.10.19+gitAUTOINC+18b8c6c3d9_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

* minnow:
** Date: 2014-01-07-Tuesday-13-34-23
** poky repo: master: commit f4ae4399140ef61bafdd9223583a249279959ae1
** poky repo: master+work commit f4ae4399140ef61bafdd9223583a249279959ae1
** meta-intel: master: commit f707b6c67909ccd84cb2070bdc15777573833461
** meta-intel: master+work commit c37936116b60c66c40fe77f421a4bd66dbe4d9ea
** kernel version:linux-yocto-3.10.19+gitAUTOINC+18b8c6c3d9_a9ec82e355-r0
** Build Status: Build succeeded
** Testing Status:

Last Known Good Commits for meta-intel

2013-12-12T20:45:41Z

Nitinkamble:

This page tracks the last poky and meta-intel commits that were verified to build and boot into sato for each meta-intel BSP.

This BSP health status is updated weekly by Nitin A Kamble <nitin.a.kamble@intel.com>

Yocto Project Repositories, Branches & Commits:
* poky.git:
** master+work commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** master: commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** Additional commits over master:
* meta-intel.git
** tzanussi/mut commit 2626430dad3a0b7d07fbef859b1fe44417b85114
** master: commit a649e92498d234f2d0d52f3da5a85bdc87296c23
** Additional commits over master:
2626430 sugarbay: linux-yocto_3.10: change the feature for webcam

BSP Status
* qemux86:
** Date: 2013-12-02-Monday-10-25-34
** poky repo: master: commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** poky repo: master+work commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** meta-intel: master: commit a649e92498d234f2d0d52f3da5a85bdc87296c23
** meta-intel: tzanussi/mut commit 2626430dad3a0b7d07fbef859b1fe44417b85114
** kernel version:linux-yocto-3.10.19+gitAUTOINC+4011fe80ae_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* genericx86:
** Date: 2013-12-02-Monday-10-25-34
** poky repo: master: commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** poky repo: master+work commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** meta-intel: master: commit a649e92498d234f2d0d52f3da5a85bdc87296c23
** meta-intel: tzanussi/mut commit 2626430dad3a0b7d07fbef859b1fe44417b85114
** kernel version:linux-yocto-3.10.19+gitAUTOINC+4011fe80ae_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* genericx86-64:
** Date: 2013-12-02-Monday-10-25-34
** poky repo: master: commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** poky repo: master+work commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** meta-intel: master: commit a649e92498d234f2d0d52f3da5a85bdc87296c23
** meta-intel: tzanussi/mut commit 2626430dad3a0b7d07fbef859b1fe44417b85114
** kernel version:linux-yocto-3.10.19+gitAUTOINC+4011fe80ae_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* sugarbay:
** Date: 2013-12-02-Monday-10-25-34
** poky repo: master: commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** poky repo: master+work commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** meta-intel: master: commit a649e92498d234f2d0d52f3da5a85bdc87296c23
** meta-intel: tzanussi/mut commit 2626430dad3a0b7d07fbef859b1fe44417b85114
** kernel version:linux-yocto-3.10.19+gitAUTOINC+4011fe80ae_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Pass

* nuc:
** Date: 2013-12-02-Monday-10-25-34
** poky repo: master: commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** poky repo: master+work commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** meta-intel: master: commit a649e92498d234f2d0d52f3da5a85bdc87296c23
** meta-intel: tzanussi/mut commit 2626430dad3a0b7d07fbef859b1fe44417b85114
** kernel version:linux-yocto-3.10.19+gitAUTOINC+4011fe80ae_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Pass

* jasperforest:
** Date: 2013-12-02-Monday-10-25-34
** poky repo: master: commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** poky repo: master+work commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** meta-intel: master: commit a649e92498d234f2d0d52f3da5a85bdc87296c23
** meta-intel: tzanussi/mut commit 2626430dad3a0b7d07fbef859b1fe44417b85114
** kernel version:linux-yocto-3.10.19+gitAUTOINC+4011fe80ae_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Pass

* crownbay:
** Date: 2013-12-02-Monday-10-25-34
** poky repo: master: commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** poky repo: master+work commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** meta-intel: master: commit a649e92498d234f2d0d52f3da5a85bdc87296c23
** meta-intel: tzanussi/mut commit 2626430dad3a0b7d07fbef859b1fe44417b85114
** kernel version:linux-yocto-3.10.19+gitAUTOINC+4011fe80ae_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Pass

* chiefriver:
** Date: 2013-12-02-Monday-10-25-34
** poky repo: master: commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** poky repo: master+work commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** meta-intel: master: commit a649e92498d234f2d0d52f3da5a85bdc87296c23
** meta-intel: tzanussi/mut commit 2626430dad3a0b7d07fbef859b1fe44417b85114
** kernel version:linux-yocto-3.10.19+gitAUTOINC+4011fe80ae_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Pass

* emenlow:
** Date: 2013-12-02-Monday-10-25-34
** poky repo: master: commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** poky repo: master+work commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** meta-intel: master: commit a649e92498d234f2d0d52f3da5a85bdc87296c23
** meta-intel: tzanussi/mut commit 2626430dad3a0b7d07fbef859b1fe44417b85114
** kernel version:linux-yocto-3.10.19+gitAUTOINC+4011fe80ae_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Pass

* crownbay-noemgd:
** Date: 2013-12-02-Monday-10-25-34
** poky repo: master: commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** poky repo: master+work commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** meta-intel: master: commit a649e92498d234f2d0d52f3da5a85bdc87296c23
** meta-intel: tzanussi/mut commit 2626430dad3a0b7d07fbef859b1fe44417b85114
** kernel version:linux-yocto-3.10.19+gitAUTOINC+4011fe80ae_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Pass

* emenlow-noemgd:
** Date: 2013-12-02-Monday-10-25-34
** poky repo: master: commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** poky repo: master+work commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** meta-intel: master: commit a649e92498d234f2d0d52f3da5a85bdc87296c23
** meta-intel: tzanussi/mut commit 2626430dad3a0b7d07fbef859b1fe44417b85114
** kernel version:linux-yocto-3.10.19+gitAUTOINC+4011fe80ae_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Pass

* fri2:
** Date: 2013-12-02-Monday-10-25-34
** poky repo: master: commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** poky repo: master+work commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** meta-intel: master: commit a649e92498d234f2d0d52f3da5a85bdc87296c23
** meta-intel: tzanussi/mut commit 2626430dad3a0b7d07fbef859b1fe44417b85114
** kernel version:linux-yocto-3.10.19+gitAUTOINC+4011fe80ae_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* fri2-noemgd:
** Date: 2013-12-02-Monday-10-25-34
** poky repo: master: commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** poky repo: master+work commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** meta-intel: master: commit a649e92498d234f2d0d52f3da5a85bdc87296c23
** meta-intel: tzanussi/mut commit 2626430dad3a0b7d07fbef859b1fe44417b85114
** kernel version:linux-yocto-3.10.19+gitAUTOINC+4011fe80ae_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* sys940x:
** Date: 2013-12-02-Monday-10-25-34
** poky repo: master: commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** poky repo: master+work commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** meta-intel: master: commit a649e92498d234f2d0d52f3da5a85bdc87296c23
** meta-intel: tzanussi/mut commit 2626430dad3a0b7d07fbef859b1fe44417b85114
** kernel version:linux-yocto-3.10.19+gitAUTOINC+4011fe80ae_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* sys940x-noemgd:
** Date: 2013-12-02-Monday-10-25-34
** poky repo: master: commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** poky repo: master+work commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** meta-intel: master: commit a649e92498d234f2d0d52f3da5a85bdc87296c23
** meta-intel: tzanussi/mut commit 2626430dad3a0b7d07fbef859b1fe44417b85114
** kernel version:linux-yocto-3.10.19+gitAUTOINC+4011fe80ae_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* minnow:
** Date: 2013-12-02-Monday-10-25-34
** poky repo: master: commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** poky repo: master+work commit a17ffbdbb7d142a94ef842a32b749b18e2e7f0a1
** meta-intel: master: commit a649e92498d234f2d0d52f3da5a85bdc87296c23
** meta-intel: tzanussi/mut commit 2626430dad3a0b7d07fbef859b1fe44417b85114
** kernel version:linux-yocto-3.10.19+gitAUTOINC+4011fe80ae_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

Last Known Good Commits for meta-intel

2013-12-02T18:18:14Z

Nitinkamble:

Last Known Good Commits for meta-intel

2013-11-16T02:56:16Z

Nitinkamble:

This page tracks the last poky and meta-intel commits that were verified to build and boot into sato for each meta-intel BSP.

This BSP health status is updated weekly by Nitin A Kamble <nitin.a.kamble@intel.com>

Yocto Project Repositories, Branches & Commits:
* poky.git:
** master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** Additional commits over master:

* meta-intel.git
** tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** master: commit b74b419f08a040b5170addda5d17026e8c50290f
** Additional commits over master:
f5c2786 sys940x: Remove mesa PREFERRED_VERSION
1019ab5 emenlow: Remove mesa PREFERRED_VERSION
a317a41 fri2: Remove mesa PREFERRED_VERSION
3b26dd3 crownbay: Remove mesa PREFERRED_VERSION
06623c9 sys940x: linux-yocto-3.10: update kernel srcrevs
fedc707 sugarbay: linux-yocto-3.10: update kernel srcrevs
b374a53 nuc: linux-yocto-3.10: update kernel srcrevs
b21b1a1 jasperforest: linux-yocto-3.10: update kernel srcrevs
f195013 fri2: linux-yocto-3.10: update kernel srcrevs
c96b19c emenlow: linux-yocto-3.10: update kernel srcrevs
c328ab8 crownbay: linux-yocto-3.10: update kernel srcrevs
bee6a25 chiefriver: linux-yocto-3.10: update kernel srcrevs
e7a1f88 emgd-driver-bin: add missing GLchar typedef to gl2.h
ccc27af gstreamer-vaapi: add 0.5.6
678e42b libva-intel-driver: upgrade to 1.2.1
a9f02ff mesa: remove, mesa-gl is used with EMGD now

BSP Status
* qemux86:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* genericx86:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* genericx86-64:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* sugarbay:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Success

* nuc:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Success

* jasperforest:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Success

* crownbay:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Success

* chiefriver:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Success

* emenlow:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Success

* crownbay-noemgd:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Success

* emenlow-noemgd:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Success

* fri2:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* fri2-noemgd:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* sys940x:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* sys940x-noemgd:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

Last Known Good Commits for meta-intel

2013-11-16T02:55:51Z

Nitinkamble:

This page tracks the last poky and meta-intel commits that were verified to build and boot into sato for each meta-intel BSP.

This BSP health status is updated weekly by Nitin A Kamble <nitin.a.kamble@intel.com>

Yocto Project Repositories, Branches & Commits:
* poky.git:
** master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** Additional commits over master:
* meta-intel.git
** tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** master: commit b74b419f08a040b5170addda5d17026e8c50290f
** Additional commits over master:
f5c2786 sys940x: Remove mesa PREFERRED_VERSION
1019ab5 emenlow: Remove mesa PREFERRED_VERSION
a317a41 fri2: Remove mesa PREFERRED_VERSION
3b26dd3 crownbay: Remove mesa PREFERRED_VERSION
06623c9 sys940x: linux-yocto-3.10: update kernel srcrevs
fedc707 sugarbay: linux-yocto-3.10: update kernel srcrevs
b374a53 nuc: linux-yocto-3.10: update kernel srcrevs
b21b1a1 jasperforest: linux-yocto-3.10: update kernel srcrevs
f195013 fri2: linux-yocto-3.10: update kernel srcrevs
c96b19c emenlow: linux-yocto-3.10: update kernel srcrevs
c328ab8 crownbay: linux-yocto-3.10: update kernel srcrevs
bee6a25 chiefriver: linux-yocto-3.10: update kernel srcrevs
e7a1f88 emgd-driver-bin: add missing GLchar typedef to gl2.h
ccc27af gstreamer-vaapi: add 0.5.6
678e42b libva-intel-driver: upgrade to 1.2.1
a9f02ff mesa: remove, mesa-gl is used with EMGD now

BSP Status
* qemux86:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* genericx86:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* genericx86-64:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* sugarbay:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Success

* nuc:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Success

* jasperforest:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Success

* crownbay:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Success

* chiefriver:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Success

* emenlow:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Success

* crownbay-noemgd:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Success

* emenlow-noemgd:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status: Success

* fri2:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* fri2-noemgd:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* sys940x:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

* sys940x-noemgd:
** Date: 2013-11-15-Friday-18-52-01
** poky repo: master: commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** poky repo: master+work commit e1e1ee5ebfa7a7d21f9426764135fd772a8ed7b5
** meta-intel: master: commit b74b419f08a040b5170addda5d17026e8c50290f
** meta-intel: tzanussi/mut commit f5c2786e7ca190308523379706130e0c2be793c9
** kernel version:linux-yocto-3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0
** Build Status: Build succeeded
** Testing Status:

Last Known Good Commits for meta-intel

2013-11-01T23:55:08Z

Nitinkamble:

This page tracks the last poky and meta-intel commits that were verified to build and boot into sato for each meta-intel BSP.

This BSP health status is updated weekly by Nitin A Kamble <nitin.a.kamble@intel.com>

BSP Status
* sugarbay:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status: Good

* nuc:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status: Good

* jasperforest:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status: Good

* crownbay:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status: Good

* chiefriver:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status: Good

* emenlow:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status: Good

* crownbay-noemgd:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status: Good

* emenlow-noemgd:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status: Good

* fri2:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 35m 58s

* fri2-noemgd:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status:

* sys940x:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status:

* sys940x-noemgd:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status:

Last Known Good Commits for meta-intel

2013-11-01T22:41:22Z

Nitinkamble:

This page tracks the last poky and meta-intel commits that were verified to build and boot into sato for each meta-intel BSP.

This BSP health status is updated weekly by Nitin A Kamble <nitin.a.kamble@intel.com>

BSP Status
* sugarbay:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status:

* nuc:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status:

* jasperforest:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status:

* crownbay:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status:

* chiefriver:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status:

* emenlow:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status:

* crownbay-noemgd:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status:

* emenlow-noemgd:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status:

* fri2:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status:
Time taken = 0h 35m 58s

* fri2-noemgd:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status:

* sys940x:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status:

* sys940x-noemgd:
** Date: 2013-10-30-Wednesday-10-31-35
** poky repo: master: commit 5e427966756700e596740778f16b96d03e8568c8
** meta-intel: master: commit 82567949e049ce466c6e0b1422ce1ecaef069e3d
** kernel version:linux-yocto-3.10.11+gitAUTOINC+452f0679ea_3f6c8243ed-r0
** Build Status: Build succeeded
** Testing Status:

Guidelines for contributing to meta-intel layer

2013-10-28T16:00:05Z

Nitinkamble:

Note: This page is "Work in Progress", it is not finalized yet.

= meta-intel Layer Information =
git repository location:
* git://git.yoctoproject.org/meta-intel

Mailing List:
* List email address: meta-intel@yoctoproject.org
* How to subscribe : https://lists.yoctoproject.org/listinfo/meta-intel

= Guidelines for sending commits to meta-intel =
Please follow general guidelines for contributing to Yocto Project. Here are some of the links.
* [[Community Guidelines]]
* [[Contribution_Guidelines|Contribution Guidelines]]
* [[Recipe & Patch Style Guide]]
* [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html The Yocto Project Development Manual]

= Guidelines for submitting BSPs to meta-intel =
1st follow these general BSP developer's guides:
* [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html Board Support Packages (BSP) - Developer's Guide]
* [http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html Yocto Project Linux Kernel Development Manual]
* To save everybodies time, please make sure you can meet these expectations before submitting a BSP for meta-intel layer

= Expectations for up-streaming a BSP in meta-intel layer =
To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.

===1. Make sure the BSP is functioning well at all the times ===
Sometimes dependent layers such as oecore introduce changes which can break layers and BSPs depending on it. The maintainer of the BSP need to regularly validate the BSP with the latest dependent layers, to make sure it is still functioning properly.

Check this link showing status of the various meta-intel BSPs kept up to date: [https://wiki.yoctoproject.org/wiki/Last_Known_Good_Commits_for_meta-intel Last Known Good Commits for meta-intel]

===2. Prepare the BSP for release with every meta-intel release ===
This involves these things:
* tag the commit of the release in the meta-intel repository
* Get the "Yocto Project Compatibile" certification for the BSP from here: https://www.yoctoproject.org/webform/yocto-project-compatible-registration
* Build the binary images of the BSP with the meta_tlk layer, and make sure commercial licenses are turned off while building.
* Provide the built release tarball of the BSP to the release engineer for releasing to Yocto Project BSP release area

= Review process for sending commits and BSPs to meta-intel layer =
* All the commits for meta-intel layer must go through the meta-intel mailing list.
* The changes should be sent as individual commits. There are scripts available to prepare and send patches for review. Check http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#how-to-submit-a-change
* Do not send tarballs of code for review.

= Guidelines for releasing BSPs =
* [[Third_Party_BSP_Release_Process | Third Party BSP Release Guidelines]]

Guidelines for contributing to meta-intel layer

2013-10-28T15:59:35Z

Nitinkamble:

Note: This page is "Work in Progress", it is not finalized yet.

= meta-intel Layer Information =
git repository location:
* git://git.yoctoproject.org/meta-intel

Mailing List:
* List email address: meta-intel@yoctoproject.org
* How to subscribe : https://lists.yoctoproject.org/listinfo/meta-intel

= Guidelines for sending commits to meta-intel =
Please follow general guidelines for contributing to Yocto Project. Here are some of the links.
* [[Community Guidelines]]
* [[Contribution_Guidelines|Contribution Guidelines]]
* [[Recipe & Patch Style Guide]]
* [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html The Yocto Project Development Manual]

= Guidelines for submitting BSPs to meta-intel =
1st follow these general BSP developer's guides:
* [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html Board Support Packages (BSP) - Developer's Guide]
* [http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html Yocto Project Linux Kernel Development Manual]
* To save everybodies time, please make sure you can meet these expectations before submitting a BSP for meta-intel layer

= Expectations for up-streaming a BSP in meta-intel layer =
To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.

===1 Make sure the BSP is functioning well at all the times ===
Sometimes dependent layers such as oecore introduce changes which can break layers and BSPs depending on it. The maintainer of the BSP need to regularly validate the BSP with the latest dependent layers, to make sure it is still functioning properly.

Check this link showing status of the various meta-intel BSPs kept up to date: [https://wiki.yoctoproject.org/wiki/Last_Known_Good_Commits_for_meta-intel Last Known Good Commits for meta-intel]

===2 Prepare the BSP for release with every meta-intel release ===
This involves these things:
* tag the commit of the release in the meta-intel repository
* Get the "Yocto Project Compatibile" certification for the BSP from here: https://www.yoctoproject.org/webform/yocto-project-compatible-registration
* Build the binary images of the BSP with the meta_tlk layer, and make sure commercial licenses are turned off while building.
* Provide the built release tarball of the BSP to the release engineer for releasing to Yocto Project BSP release area

= Review process for sending commits and BSPs to meta-intel layer =
* All the commits for meta-intel layer must go through the meta-intel mailing list.
* The changes should be sent as individual commits. There are scripts available to prepare and send patches for review. Check http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#how-to-submit-a-change
* Do not send tarballs of code for review.

= Guidelines for releasing BSPs =
* [[Third_Party_BSP_Release_Process | Third Party BSP Release Guidelines]]

Guidelines for contributing to meta-intel layer

2013-10-28T15:58:30Z

Nitinkamble:

Note: This page is "Work in Progress", it is not finalized yet.

= meta-intel Layer Information =
git repository location:
* git://git.yoctoproject.org/meta-intel

Mailing List:
* List email address: meta-intel@yoctoproject.org
* How to subscribe : https://lists.yoctoproject.org/listinfo/meta-intel

= Guidelines for sending commits to meta-intel =
Please follow general guidelines for contributing to Yocto Project. Here are some of the links.
* [[Community Guidelines]]
* [[Contribution_Guidelines|Contribution Guidelines]]
* [[Recipe & Patch Style Guide]]
* [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html The Yocto Project Development Manual]

= Guidelines for submitting BSPs to meta-intel =
1st follow these general BSP developer's guides:
* [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html Board Support Packages (BSP) - Developer's Guide]
* [http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html Yocto Project Linux Kernel Development Manual]
* To save everybodies time, please make sure you can meet these expectations before submitting a BSP for meta-intel layer

= Expectations for up-streaming a BSP in meta-intel layer =
To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.

==1 Make sure the BSP is functioning well at all the times ==
Sometimes dependent layers such as oecore introduce changes which can break layers and BSPs depending on it. The maintainer of the BSP need to regularly validate the BSP with the latest dependent layers, to make sure it is still functioning properly.

Check this link showing status of the various meta-intel BSPs kept up to date: [https://wiki.yoctoproject.org/wiki/Last_Known_Good_Commits_for_meta-intel Last Known Good Commits for meta-intel]

==2 Prepare the BSP for release with every meta-intel release ==
This involves these things:
* tag the commit of the release in the meta-intel repository
* Get the "Yocto Project Compatibile" certification for the BSP from here: https://www.yoctoproject.org/webform/yocto-project-compatible-registration
* Build the binary images of the BSP with the meta_tlk layer, and make sure commercial licenses are turned off while building.
* Provide the built release tarball of the BSP to the release engineer for releasing to Yocto Project BSP release area

= Review process for sending commits and BSPs to meta-intel layer =
* All the commits for meta-intel layer must go through the meta-intel mailing list.
* The changes should be sent as individual commits. There are scripts available to prepare and send patches for review. Check http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#how-to-submit-a-change
* Do not send tarballs of code for review.

= Guidelines for releasing BSPs =
* [[Third_Party_BSP_Release_Process | Third Party BSP Release Guidelines]]

Guidelines for contributing to meta-intel layer

2013-10-28T15:54:16Z

Nitinkamble: /* 2 Prepare the BSP for release with every meta-intel release */

= meta-intel Layer Information =
git repository location:
* git://git.yoctoproject.org/meta-intel

Mailing List:
* List email address: meta-intel@yoctoproject.org
* How to subscribe : https://lists.yoctoproject.org/listinfo/meta-intel

= Guidelines for sending commits to meta-intel =
Please follow general guidelines for contributing to Yocto Project. Here are some of the links.
* [[Community Guidelines]]
* [[Contribution_Guidelines|Contribution Guidelines]]
* [[Recipe & Patch Style Guide]]
* [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html The Yocto Project Development Manual]

= Guidelines for submitting BSPs to meta-intel =
1st follow these general BSP developer's guides:
* [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html Board Support Packages (BSP) - Developer's Guide]
* [http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html Yocto Project Linux Kernel Development Manual]
* To save everybodies time, please make sure you can meet these expectations before submitting a BSP for meta-intel layer

= Expectations for up-streaming a BSP in meta-intel layer =
To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.

==1 Make sure the BSP is functioning well at all the times ==
Sometimes dependent layers such as oecore introduce changes which can break layers and BSPs depending on it. The maintainer of the BSP need to regularly validate the BSP with the latest dependent layers, to make sure it is still functioning properly.

Check this link showing status of the various meta-intel BSPs kept up to date: [https://wiki.yoctoproject.org/wiki/Last_Known_Good_Commits_for_meta-intel Last Known Good Commits for meta-intel]

==2 Prepare the BSP for release with every meta-intel release ==
This involves these things:
* tag the commit of the release in the meta-intel repository
* Get the "Yocto Project Compatibile" certification for the BSP from here: https://www.yoctoproject.org/webform/yocto-project-compatible-registration
* Build the binary images of the BSP with the meta_tlk layer, and make sure commercial licenses are turned off while building.
* Provide the built release tarball of the BSP to the release engineer for releasing to Yocto Project BSP release area

= Review process for sending commits and BSPs to meta-intel layer =
* All the commits for meta-intel layer must go through the meta-intel mailing list.
* The changes should be sent as individual commits. There are scripts available to prepare and send patches for review. Check http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#how-to-submit-a-change
* Do not send tarballs of code for review.

= Guidelines for releasing BSPs =
* [[Third_Party_BSP_Release_Process | Third Party BSP Release Guidelines]]

Guidelines for contributing to meta-intel layer

2013-10-28T15:53:32Z

Nitinkamble:

= meta-intel Layer Information =
git repository location:
* git://git.yoctoproject.org/meta-intel

Mailing List:
* List email address: meta-intel@yoctoproject.org
* How to subscribe : https://lists.yoctoproject.org/listinfo/meta-intel

= Guidelines for sending commits to meta-intel =
Please follow general guidelines for contributing to Yocto Project. Here are some of the links.
* [[Community Guidelines]]
* [[Contribution_Guidelines|Contribution Guidelines]]
* [[Recipe & Patch Style Guide]]
* [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html The Yocto Project Development Manual]

= Guidelines for submitting BSPs to meta-intel =
1st follow these general BSP developer's guides:
* [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html Board Support Packages (BSP) - Developer's Guide]
* [http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html Yocto Project Linux Kernel Development Manual]
* To save everybodies time, please make sure you can meet these expectations before submitting a BSP for meta-intel layer

= Expectations for up-streaming a BSP in meta-intel layer =
To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.

==1 Make sure the BSP is functioning well at all the times ==
Sometimes dependent layers such as oecore introduce changes which can break layers and BSPs depending on it. The maintainer of the BSP need to regularly validate the BSP with the latest dependent layers, to make sure it is still functioning properly.

Check this link showing status of the various meta-intel BSPs kept up to date: [https://wiki.yoctoproject.org/wiki/Last_Known_Good_Commits_for_meta-intel Last Known Good Commits for meta-intel]

==2 Prepare the BSP for release with every meta-intel release ==
This involves these things:
* git tag the commit of the release
* Get the "Yocto Project Compatibile" certification for the BSP from here: https://www.yoctoproject.org/webform/yocto-project-compatible-registration
* Build the binary images of the BSP with the meta_tlk layer, and make sure commercial licenses are turned off while building.
* Provide the built release tarball of the BSP to the release engineer for releasing to Yocto Project BSP release area

= Review process for sending commits and BSPs to meta-intel layer =
* All the commits for meta-intel layer must go through the meta-intel mailing list.
* The changes should be sent as individual commits. There are scripts available to prepare and send patches for review. Check http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#how-to-submit-a-change
* Do not send tarballs of code for review.

= Guidelines for releasing BSPs =
* [[Third_Party_BSP_Release_Process | Third Party BSP Release Guidelines]]

Guidelines for contributing to meta-intel layer

2013-10-28T15:51:31Z

Nitinkamble:

= meta-intel Layer Information =
git repository location:
* git://git.yoctoproject.org/meta-intel

Mailing List:
* List email address: meta-intel@yoctoproject.org
* How to subscribe : https://lists.yoctoproject.org/listinfo/meta-intel

= Guidelines for sending commits to meta-intel =
Please follow general guidelines for contributing to Yocto Project. Here are some of the links.
* [[Community Guidelines]]
* [[Contribution_Guidelines|Contribution Guidelines]]
* [[Recipe & Patch Style Guide]]
* [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html The Yocto Project Development Manual]

= Guidelines for submitting BSPs to meta-intel =
1st follow these general BSP developer's guides:
* [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html Board Support Packages (BSP) - Developer's Guide]
* [http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html Yocto Project Linux Kernel Development Manual]
* To save everybodies time, please make sure you can meet these expectations before submitting a BSP for meta-intel layer

= Expectations for up-streaming a BSP in meta-intel layer =
To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.

==1 Make sure the BSP is functioning well at all the times ==
Sometimes dependent layers such as oecore introduce changes which can break layers and BSPs depending on it. The maintainer of the BSP need to regularly validate the BSP with the latest dependent layers, to make sure it is still functioning properly.

Check this link showing status of the various meta-intel BSPs kept up to date:
[https://wiki.yoctoproject.org/wiki/Last_Known_Good_Commits_for_meta-intel Last Known Good Commits for meta-intel]

==2 Prepare the BSP for release with every meta-intel release ==
This involves these things:
* git tag the commit of the release
* Get the "Yocto Project Compatibile" certification for the BSP from here: https://www.yoctoproject.org/webform/yocto-project-compatible-registration
* Build the binary images of the BSP with the meta_tlk layer, and make sure commercial licenses are turned off while building.
* Provide the built release tarball of the BSP to the release engineer for releasing to Yocto Project BSP release area

= Review process for sending commits and BSPs to meta-intel layer =
* All the commits for meta-intel layer must go through the meta-intel mailing list.
* The changes should be sent as individual commits. There are scripts available to prepare and send patches for review. Check http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#how-to-submit-a-change
* Do not send tarballs of code for review.

= Guidelines for releasing BSPs =
* [[Third_Party_BSP_Release_Process | Third Party BSP Release Guidelines]]

Guidelines for contributing to meta-intel layer

2013-10-28T15:50:16Z

Nitinkamble:

== meta-intel Layer Information ==
git repository location:
* git://git.yoctoproject.org/meta-intel

Mailing List:
* List email address: meta-intel@yoctoproject.org
* How to subscribe : https://lists.yoctoproject.org/listinfo/meta-intel

== Guidelines for sending commits to meta-intel ==
Please follow general guidelines for contributing to Yocto Project. Here are some of the links.
* [[Community Guidelines]]
* [[Contribution_Guidelines|Contribution Guidelines]]
* [[Recipe & Patch Style Guide]]
* [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html The Yocto Project Development Manual]

== Guidelines for submitting BSPs to meta-intel ==
1st follow these general BSP developer's guides:
* [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html Board Support Packages (BSP) - Developer's Guide]
* [http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html Yocto Project Linux Kernel Development Manual]
* To save everybodies time, please make sure you can meet these expectations before submitting a BSP for meta-intel layer

== Expectations for up-streaming a BSP in meta-intel layer ==
To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.

===1 Make sure the BSP is functioning well at all the times ===
Sometimes dependent layers such as oecore introduce changes which can break layers and BSPs depending on it. The maintainer of the BSP need to regularly validate the BSP with the latest dependent layers, to make sure it is still functioning properly.

Check this link showing status of the various meta-intel BSPs kept up to date:
[https://wiki.yoctoproject.org/wiki/Last_Known_Good_Commits_for_meta-intel Last Known Good Commits for meta-intel]

===2 Prepare the BSP for release with every meta-intel release ===
This involves these things:
* git tag the commit of the release
* Get the "Yocto Project Compatibile" certification for the BSP from here: https://www.yoctoproject.org/webform/yocto-project-compatible-registration
* Build the binary images of the BSP with the meta_tlk layer, and make sure commercial licenses are turned off while building.
* Provide the built release tarball of the BSP to the release engineer for releasing to Yocto Project BSP release area

== Review process for sending commits and BSPs to meta-intel layer ==
* All the commits for meta-intel layer must go through the meta-intel mailing list.
* The changes should be sent as individual commits. There are scripts available to prepare and send patches for review. Check http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#how-to-submit-a-change
* Do not send tarballs of code for review.

== Guidelines for releasing BSPs ==
* [[Third_Party_BSP_Release_Process | Third Party BSP Release Guidelines]]

Expectations for up-streaming a BSP in meta-intel layer

2013-10-28T15:48:50Z

Nitinkamble: Blanked the page

Processes and Activities

2013-10-25T00:40:20Z

Nitinkamble:

Welcome to the Processes and Activities Page!

* [[Contribution Guidelines]]
* [[Recipe & Patch Style Guide]]
* [[Distro Tracking]]
* [[Best Known Methods (BKMs) for Package Updating]]
* [[Working Behind a Network Proxy]]
* [[SDK Generator]]
* [[QA]]
* [[Kernel]]
* [[Core]]
* [[Bugzilla Configuration and Bug Tracking]]
* [[Bug Triage]]
* [[Yocto Point-Release Development Workflow]]
* [[Yocto Release Engineering]]
* [[Performance]]
* [[Security]]
* [[PAM Integration]]
* [[Program Management Plan]]
* [[Enable sstate cache]]
* [[Image Recipes]]
* [[Community Statistics]]
* Guidelines for contributing to meta-intel layer

Expectations for up-streaming a BSP in meta-intel layer

2013-10-25T00:34:25Z

Nitinkamble:

To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.

==1 Make sure the BSP is functioning well at all the times ==
Sometimes dependent layers such as oecore introduce changes which can break layers and BSPs depending on it. The maintainer of the BSP need to regularly validate the BSP with the latest dependent layers, to make sure it is still functioning properly.

Check this link showing status of the various meta-intel BSPs kept up to date:
[https://wiki.yoctoproject.org/wiki/Last_Known_Good_Commits_for_meta-intel Last Known Good Commits for meta-intel]

==2 Prepare the BSP for release with every meta-intel release ==
This involves these things:
* git tag the commit of the release
* Get the "Yocto Project Compatibile" certification for the BSP from here: https://www.yoctoproject.org/webform/yocto-project-compatible-registration
* Build the binary images of the BSP with the meta_tlk layer, and make sure commercial licenses are turned off while building.
* Provide the built release tarball of the BSP to the release engineer for releasing to Yocto Project BSP release area
*

Expectations for up-streaming a BSP in meta-intel layer

2013-10-25T00:33:20Z

Nitinkamble:

Expectations for up-streaming a BSP in meta-intel layer

2013-10-25T00:32:18Z

Nitinkamble:

To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.

==1 Make sure the BSP is functioning well at all the times ==
Sometimes dependent layers such as oecore introduce changes which can break other layers like meta-intel, and BSPs within it. The maintainer of the BSP need to continuously validate the BSP with the latest dependent layers, to make sure it is still functioning properly.

Check this link showing status of the various meta-intel BSPs kept up to date:
[https://wiki.yoctoproject.org/wiki/Last_Known_Good_Commits_for_meta-intel Last Known Good Commits for meta-intel]

==2 Prepare the BSP for release with every meta-intel release ==
This involves these things:
* git tag the commit of the release
* Get the "Yocto Project Compatibile" certification for the BSP from here: https://www.yoctoproject.org/webform/yocto-project-compatible-registration
* Build the binary images of the BSP with the meta_tlk layer, and make sure commercial licenses are turned off while building.
* Provide the built release tarball of the BSP for releasing to Yocto Project BSP release area
*

Expectations for up-streaming a BSP in meta-intel layer

2013-10-25T00:31:39Z

Nitinkamble: /* 1 Make sure the BSP is functioning well at all the times */

To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.

==1 Make sure the BSP is functioning well at all the times ==
Sometimes dependent layers such as oecore introduce changes which can break other layers like meta-intel, and BSPs within it. The maintainer of the BSP need to continuously validate the BSP with the latest dependent layers, to make sure it is still functioning properly.

Check this link showing status of the various meta-intel BSPs kept up to date:
[https://wiki.yoctoproject.org/wiki/Last_Known_Good_Commits_for_meta-intel|Last Known Good Commits for meta-intel]

==2 Prepare the BSP for release with every meta-intel release ==
This involves these things:
* git tag the commit of the release
* Get the "Yocto Project Compatibile" certification for the BSP from here: https://www.yoctoproject.org/webform/yocto-project-compatible-registration
* Build the binary images of the BSP with the meta_tlk layer, and make sure commercial licenses are turned off while building.
* Provide the built release tarball of the BSP for releasing to Yocto Project BSP release area
*

Expectations for up-streaming a BSP in meta-intel layer

2013-10-25T00:29:39Z

Nitinkamble:

To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.

==1 Make sure the BSP is functioning well at all the times ==
Sometimes dependent layers such as oecore introduce changes which can break other layers like meta-intel, and BSPs within it. The maintainer of the BSP need to continuously validate the BSP with the latest dependent layers, to make sure it is still functioning properly

==2 Prepare the BSP for release with every meta-intel release ==
This involves these things:
* git tag the commit of the release
* Get the "Yocto Project Compatibile" certification for the BSP from here: https://www.yoctoproject.org/webform/yocto-project-compatible-registration
* Build the binary images of the BSP with the meta_tlk layer, and make sure commercial licenses are turned off while building.
* Provide the built release tarball of the BSP for releasing to Yocto Project BSP release area
*

Expectations for up-streaming a BSP in meta-intel layer

2013-10-25T00:29:22Z

Nitinkamble:

To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.

==# Make sure the BSP is functioning well at all the times ==
Sometimes dependent layers such as oecore introduce changes which can break other layers like meta-intel, and BSPs within it. The maintainer of the BSP need to continuously validate the BSP with the latest dependent layers, to make sure it is still functioning properly

==# Prepare the BSP for release with every meta-intel release ==
This involves these things:
* git tag the commit of the release
* Get the "Yocto Project Compatibile" certification for the BSP from here: https://www.yoctoproject.org/webform/yocto-project-compatible-registration
* Build the binary images of the BSP with the meta_tlk layer, and make sure commercial licenses are turned off while building.
* Provide the built release tarball of the BSP for releasing to Yocto Project BSP release area
*

Expectations for up-streaming a BSP in meta-intel layer

2013-10-25T00:27:46Z

Nitinkamble:

To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.

* Make sure the BSP is functioning well at all the times. Sometimes dependent layers such as oecore introduce changes which can break other layers like meta-intel, and BSPs within it. The maintainer of the BSP need to continuously validate the BSP with the latest dependent layers, to make sure it is still functioning properly
* Prepare the BSP for release with every meta-intel release. This involves these things
** git tag the commit of the release
** Get the "Yocto Project Compatibile" certification for the BSP from here: https://www.yoctoproject.org/webform/yocto-project-compatible-registration
** Build the binary images of the BSP with the meta_tlk layer, and make sure commercial licenses are turned off while building.
** Provide the built release tarball of the BSP for releasing to Yocto Project BSP release area
**

Expectations for up-streaming a BSP in meta-intel layer

2013-10-25T00:27:24Z

Nitinkamble: Created page with "To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations. * Make sure the BSP is functioning well at all the times...."

To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.

* Make sure the BSP is functioning well at all the times. Sometimes dependent layers such as oecore introduce changes which can break other layers like meta-intel, and BSPs within it. The maintainer of the BSP need to continuously validate the BSP with the latest dependent layers, to make sure it is still functioning properly
* Prepare the BSP for release with every meta-intel release. This involves these things
** git tag the commit of the release
** Get the "Yocto Project Compatibile" certification from here: https://www.yoctoproject.org/webform/yocto-project-compatible-registration
** Build the binary images of the BSP with the meta_tlk layer, and make sure commercial licenses are turned off while building.
** Provide the built release tarball of the BSP for releasing to Yocto Project BSP release area
**

Guidelines for contributing to meta-intel layer

2013-10-25T00:17:35Z

Nitinkamble: