| Age | Commit message (Collapse) | Author |
|---|
|
Use "Yocto Project Compatible" in place of "compliance" as suggested
by Jeffrey Osier Mixon.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
The link has changed on the yoctoproject website, updating the URL
in the BSP layer READMEs.
This fixes the bug:
[Yocto #3730]
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
Add links in the readme so that one can find on the Internet
further details of the platforms supported by this BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
The WEBTITLE will be used to publish the BSP on the Yocto Project Website.
And adding the Yocto Project Compliance information for the 1.3 release.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
BSP maintainership for following BSPs is now transitioned from Tom to Nitin
sugarbay, emenlow, crownbay, jasperforest, chiefriver
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
The gst-ffmpeg recipe in oe-core had LICENSE_FLAGS added to make it
"commercial", so to avoid build errors the BSPs that use it (via the
gst-va-intel VA_FEATURE) should only include it if the user has added
"commercial" to LICENSE_FLAGS_WHITELIST when building.
This adds a conditional to detect that, along with a NOTE in the
README to explain the need for the flag.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
This layer provides support for Ivy Bridge + Panther Point Intel systems.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
Nitin A Kamble
Tom Zanussi