summaryrefslogtreecommitdiffstats
path: root/conf
Commit message (Collapse)AuthorAgeFilesLines
...
* rmc: Add recipe and bbclass for RMC featureJianxun Zhang2016-08-031-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | RMC Feature is based on RMC project, systemd-boot, EFI installer to enable a single generic image, built for multiple platforms, automatically applies customization and quirks specific to a type of boards at runtime. In another word, you will see a single image behaves differently and intelligently according to the type of board it is running on. To Enable this feature: add the two lines in conf file: DISTRO_FEATURES_append = " rmc" EFI_PROVIDER = "rmc-systemd-boot" Based on Saul Wold's initial work on a feature switch, RMC patches in systemd-boot, installer and gnu-efi aren't built unless the feature is enabled. For a supported board, this feature can : () show and boot with board-specific boot entries in boot menu in live-boot and post-installation. () apply a kernel cmdline fragment to the end of cmdline to boot Linux kernel. This is effective for any boot entry user chooses in boot menu. () create directory and deploy files only for the type of the running board to target's file systems. What left on target after installation is just same as the result from installing a conventional image customized for a single type of hardware. To add support of new boards, a new variable RMC_BOARD_DATA_DIRS is the interface to developers. How-to information will be provided with examples in following patches. Signed-off-by: Jianxun Zhang <jianxun.zhang@linux.intel.com> Reviewed-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
* quark: Switch gummiboot to systemd-bootJianxun Zhang2016-07-281-1/+1
| | | | | | | | | | | | | The systemd-boot is the old gummiboot merged into systemd project. We have enabled systemd-boot as a standalone EFI bootloader in OE, also with updated wic plugin to support specifying "systemd-boot" as bootloader in wks files. Assuming these are good enough to replace gummiboot for quark, this change does it. Signed-off-by: Jianxun Zhang <jianxun.zhang@linux.intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
* intel-common-pkgarch: Set common PACKAGE_ARCH for linux-yocto-tinyTom Zanussi2016-05-271-0/+1
| | | | | | | The linux-yocto-tiny metadata assumes the common PACKAGE_ARCH but without this is actually machine-specific and broken. Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
* conf/machine/README: RemoveTom Zanussi2016-04-291-39/+0
| | | | | | | All content has been moved to the top-level README. Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
* conf/machine/intel-*: Add rootwait to APPEND variablesCalifornia Sullivan2016-04-263-3/+3
| | | | | | | | | | | | | | | | When using the init-install-efi.sh scripts from oe-core to install to a USB stick, we do not get the "rootwait" kernel command line option. Without the rootwait option we get a kernel panic when attempting to boot from the installed USB stick. This patch adds rootwait to the kernel command line of all intel-* MACHINEs as a temporary workaround. This could potentially impact boot times with devices that do not require it, but in testing with a Silverjaw lure and SSD on a MinnowBoard Max, it did not have a noticable impact. Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
* machine: add i915 firmware to initramfs for intel-core* MACHINEsCalifornia Sullivan2016-03-292-0/+4
| | | | | | | | | Skylake and Broxton graphics require firmware blobs to run properly. The firmware must be built into the initramfs since the i915 driver is built into the kernel and won't have rootfs access on initialization. Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
* meta-intel.inc: Update INTRD to INITRD_LIVESaul Wold2016-03-031-1/+1
| | | | | | | | This address a boot issue based on using the new bootimg code that makes a distiction between Live and VM type of image so they can co-exisit. Signed-off-by: Saul Wold <sgw@linux.intel.com>
* machine: move PREFERRED_VERSION/PREFERRED_PROVIDER to meta-intel.incCalifornia Sullivan2016-02-224-9/+3
| | | | | | | This information is the same across all meta-intel supported MACHINEs, so we can move it to a shared location. Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
* machine: update PREFERRED_VERSION to 4.4 for intel-core* and intel-quarkCalifornia Sullivan2016-02-223-3/+3
| | | | | | This makes us use the new 4.4 kernel by default. Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
* gma500_gfx: Avoid inserting gma500_gfx module for certain devicesAlejandro Hernandez2016-02-191-0/+2
| | | | | | | | | | | | | | | | The gma500_gfx driver will match certain devices on which it causes incorrect functionality, we want to avoid inserting this module, basicallly blacklist it for specific hardware, but still allow it to work on other hardware by default; usually when we have an already working system, using udev rules would do the job, but since we are building it, it is impossible to blacklist a driver when a certain udev rule matches, since rootfs isn't writeable at this point during boot time, the solution is to use modprobe install, which runs a certain command instead of inserting a matching module this command needs to insert the module manually afterwards and have a flag --ignore-install so it doesn't create an infinite loop executing itself everytime it wants to insert the module, busybox's modprobe doesnt provide this functionality, so a small hack had to be used to avoid the infite loop instead. Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
* intel-core2-32: fix SERIAL_CONSOLES lineSaul Wold2015-11-021-1/+1
| | | | | | This should be SERIAL_CONSOLES with ; setting between baud and device. Signed-off-by: Saul Wold <sgw@linux.intel.com>
* conf: Add a direct path to common recipesJoonas Lahtinen2015-10-271-1/+1
| | | | | | | | | | | | | | | | By adding the direct path to recipes in common directories we allow upper layers to further extend the recipes. Without the patch the extending recipes look like this: require common/recipes-foo/bar/baz.inc With this patch the include can be written like in other layers: require recipes-foo/bar/baz.inc Signed-off-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
* intel-quark-common: Add no-asm config to opensslSaul Wold2015-10-021-0/+1
| | | | | | | This causes the build to not use Assembly code which contains invalid CMOV instructions. Signed-off-by: Saul Wold <sgw@linux.intel.com>
* meta-intel: meta-romley BSP retirement from YP 2.0WU CHIA CHUAN2015-09-301-1/+0
| | | | | | | | | | | | | | | | | | | | Remove meta-romley BSP layer from meta-intel master branch which is targeting for YP 2.0. A heads-up email was sent to the meta-intel mailing list for requesting any feedback regarding retirement of these BSP. Since there is no concern, we assume that it is agreed upon and thus this patch to retire the BSP. The "MAINTAINERS file" and "conf/machine/README file" are updated to reflect removal of the BSP. We expect intel-corei7-64 machine is continued to be used to support the platform and dpdk recipe under meta-romley is now supported under meta-isg/common/recipes-extended/dpdk. Signed-off-by: WU CHIA CHUAN <chia.chuan.wu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
* intel-quark-common: disable padlock codeSaul Wold2015-09-161-1/+5
| | | | | | | | The padlock code is a subset of x86 hardware acceleration code. It uses the cmov instruction which is invalid on Quark based hardware, so we disable this code. Signed-off-by: Saul Wold <sgw@linux.intel.com>
* intel-core2-32: Allow for multiple tty console typesSaul Wold2015-08-281-2/+2
| | | | | | | Adding the ttyPCH0 will allow of the platforms that have the EG20T Hardware to get both kernel console output and login prompt. Signed-off-by: Saul Wold <sgw@linux.intel.com>
* Remove older platform specific BSPsSaul Wold2015-08-281-1/+1
| | | | | | | | | | The intel-core* BSPs supercede these older BSPs therefore it's time to remove these older platform specific bsps. Bump LAYERVERSION to 3 to allow the Autobuilder to know that these BSPs have been removed. Signed-off-by: Saul Wold <sgw@linux.intel.com>
* intel-quark: add CFLAGS for kernel to no use lock prefixSaul Wold2015-08-191-0/+3
| | | | | | | | The kernel needs to have the EXTRA_CFLAGS based via a variable as it does not pick up the CLFAGS from the tune file. Quark based kernel should not use the lock prefix. Signed-off-by: Saul Wold <sgw@linux.intel.com>
* intel-quark: use the 4.1 linux-yocto kernelSaul Wold2015-08-191-6/+2
| | | | | | Use the 4.1 kernel which is now the default in oe-core Signed-off-by: Saul Wold <sgw@linux.intel.com>
* intel-core*: use the 4.1 linux-yocto kernelSaul Wold2015-08-192-2/+2
| | | | | | Use the 4.1 kernel which is now the default in oe-core Signed-off-by: Saul Wold <sgw@linux.intel.com>
* intel-quark: Introduce new BSP for Quark/X1000 SOCSaul Wold2015-07-082-0/+35
| | | | | | | This new BSP is for the Quark/X1000 and related series that need the limited no-lock-prefix. Signed-off-by: Saul Wold <sgw@linux.intel.com>
* intel-corei7-64: add nfc machine featureCristian Iorga2015-06-011-1/+1
| | | | | | | | | add support for the generic NFC stack Partial fix for [YOCTO #7451]. Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
* intel-core2-32: add nfc machine featureCristian Iorga2015-06-011-1/+1
| | | | | | | | | add support for the generic NFC stack Partial fix for [YOCTO #7451]. Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
* intel-core*: use gstreamer-vaapi-1.0 directly instead of gst-va-intelRoss Burton2015-02-272-2/+2
| | | | | | | | No need for a layer of indirection when that layer only has one option. Previously with EMGD there was a choice, but not anymore. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Darren Hart <dvhart@linux.intel.com>
* meta-intel.inc: Remove kernel customization for poky-lsb imagesNitin A Kamble2015-02-241-3/+0
| | | | | | | This is handled in oe-core now, remove the redundant code. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Darren Hart <dvhart@linux.intel.com>
* Update LSB preferred version to 3.14 LTSIDarren Hart2015-02-201-1/+1
| | | | | | | LSB images prefer to build with LTSI. Update to 3.14, now that 3.10 has been removed. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
* intel-core*: Prefer 3.19 for the Intel common BSPsDarren Hart2015-02-202-2/+2
| | | | | | | Now that 3.17 has been removed and linux-yocto-3.19 is available, set the preferred version to 3.19. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
* intel-microcode: Add ability to filter microcodeNitin A Kamble2014-10-211-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | The microcode data file released by Intel has microcode for many Intel processors, which by default all get installed onto the target image. In some situations it may desirable to choose microcode for only a selected processor or processors. This change provides an easier way to filter and select only the microcode of interest for BSPs from recipe space. A new variable, UCODE_FILTER_PARAMETERS, is introduced, which can be defined to contain parameters to the iucode_tool which will filter the microcode of interest for the BSP under consideration. More information on the iucode-tool parameters is available here: http://manned.org/iucode-tool. This filtering makes the generated microcode files very machine-specific, hence making the recipe machine-specific. BSPs using the common Intel kernel will not be using the filtered microcode, and will be able to share the intel-microcode packages with the common Intel package arch for the recipe. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Acked-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
* intel-corei7-64: Add intel-ucode to MACHINE_FEATURESNitin A Kamble2014-10-211-0/+1
| | | | | | | | Enable the Intel microcode feature for this BSP. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Acked-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
* intel-core2-32: Add intel-ucode to MACHINE_FEATURESNitin A Kamble2014-10-211-0/+1
| | | | | | | | Enable the Intel microcode feature for this BSP. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Acked-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
* meta-intel: Add new intel-ucode MACHINE_FEATURENitin A Kamble2014-10-211-3/+3
| | | | | | | | | | | | | | | | | With this change, Intel microcode support can be enabled or disabled for any BSP by controlling the MACHINE_FEATURES variable. Any BSP from the meta-intel layer can enable Intel microcode loading support by adding the following line in the machine configuration. MACHINE_FEATURES += "intel-ucode" This change keeps the intel-microcode feature disabled by default; it can however be enabled as an "opt-in" feature via the MACHINE_FEATURES variable. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
* meta-intel.inc: Use LTSI kernel for poky-lsb imagesNitin A Kamble2014-10-211-0/+3
| | | | | | | | v3.10 is now the latest LTSI kernel. Use it for all the poky-lsb images, so that it gets validation in the QA cycles. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
* layer.conf: Avoid conflicts with sub-layersNitin A Kamble2014-10-011-1/+1
| | | | | | | | | | | | | | | The layer priority is getting ignored because the same set of files are visible in the meta-intel layer as well as any of its sub layers. The layer pattern for recipe files is changed from "^${LAYERDIR}/" to "^${LAYERDIR}/common" to stop unintentionally including the sub-layer recipe files in the meta-intel layer. Fixes Bug: [YOCTO #6552] Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
* intel-corei7-64: Use the v3.17 kernel by defaultNitin A Kamble2014-09-301-1/+1
| | | | | | | | The linux-yocto_3.17 recipe is available for this BSP. Make it the default kernel for this BSP. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
* intel-core2-32: Use the v3.17 kernel by defaultNitin A Kamble2014-09-301-1/+1
| | | | | | | | The linux-yocto_3.17 recipe is available for this BSP. Make it the default kernel for this BSP. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
* layer.conf: Bumping LAYERVERSIONElizabeth Flanagan2014-09-181-1/+1
| | | | | | | | As we've retired some BSPs we'll need to bump LAYERVERSION so that the autobuilder does not fail out on them. Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
* intel-corei7-64.conf: include the AMT daemon in the imagesNitin A Kamble2014-09-181-1/+1
| | | | | | | | Some of the platforms supported by the intel-corei7-64 BSP have AMT feature on the platform. Enable it so that it can get utilized with this BSP. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Acked-by: Darren Hart <dvhart@linux.intel.com>
* Remove all the changes related to the proprietary EMGD graphics driverNitin A Kamble2014-09-172-13/+0
| | | | | | | | As all the EMGD based BSPs have been retired, there is no need for the proprietary EMGD support in the meta-intel layer. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
* meta-intel BSPs: enable microcode loading support for imagesNitin A Kamble2014-09-041-0/+7
| | | | | | | | For the BSPs using the meta-intel.inc file enable the early boot-time kernel as well as the user space microcode loading support. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
* meta-intel.inc: Enable ASPEED Tech Graphic CardOng Boon Leong2014-05-091-0/+2
| | | | | | | | | This is to enable ASPEED Technology graphic card that is bundled inside certain Intel customer reference board. Signed-off-by: Ong Boon Leong <boon.leong.ong@intel.com> Acked-By: Nitin A Kamble <nitin.a.kamble@intel.com>
* intel-common: Specify linux-yocto and cleanup orderDarren Hart2014-04-292-4/+6
| | | | | | | | | In keeping with the other BSPs in meta-intel, specify the PREFERRED_PROVIDER and the PREFERRED_VERSION for the linux-yocto kernel to 3.14. Move the assignments below the required includes in keeping with the rest of meta-intel. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
* intel-common: Set common PACKAGE_ARCH for linux-yocto-rtDarren Hart2014-04-091-0/+1
| | | | | | | | The linux-yocto/meta support is now available for the intel-core* machines and the preempt-rt kernel. Enable the common PACKAGE_ARCH in intel-common-pkgarch.inc. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
* intel-corei7-64: change the default kernel to v3.14Nitin A Kamble2014-04-041-1/+1
| | | | | | Use the latest linux-yocto kernel for the intel-corei7-64 BSP. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
* intel-core2-32: change the default kernel to v3.14Nitin A Kamble2014-04-041-1/+1
| | | | | | Use the latest linux-yocto kernel for the intel-core2-32 BSP. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
* Remove chiefriver, sys940x & n450 BSPsNitin A Kamble2014-03-271-0/+4
| | | | | | | | | | | | | | | | | | Configuration for the chiefriver, sys940x, sys940x-noemgd, n450 BSPs are deleted. The consolidated BSPs viz intel-corei7-64 and intel-core2-32 support these boards. As part of the usual retirement process, a heads-up email was sent to the meta-intel mailing list requesting any feedback regarding retirement of these BSPs. The community did not had any concerning feedback to reconsider the retirement decision. The MAINTAINERS file and the layer version of the meta-intel layer are updated to reflect removal of the BSPs. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> CC: Darren Hart <dvhart@linux.intel.com> Reviewed-by: Darren Hart <dvhart@linux.intel.com>
* intel-core*: Set kernel provider with conditional assignmentDarren Hart2014-03-172-2/+2
| | | | | | | | | | The PREFERRED_PROVIDER_virtual/kernel was assigned with = instead of ?=, preventing the user from overriding the setting with something like linux-yocto-rt. Use ?=. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Reported-by: Teemu Keskinarkaus <Teemu.Keskinarkaus@Maximatecc.com> Cc: Tom Zanussi <tom.zanussi@intel.com>
* intel-common: Add nuc to the READMEDarren Hart2014-03-141-0/+1
| | | | | | | | | Both the Ivy Bridge and Haswell nuc systems are covered supported by the intel-corei7-64 BSP. The HDMI audio requires manual configuration which is handled by a machine-specific script in the nuc BSP. A general solution to this sort of problem is in the works. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
* intel-common: Add a READMEDarren Hart2014-03-121-0/+39
| | | | | | | | | | | Add a README describing the intel-core* (intel-common) BSPs and the Linux kernel package architecture. Includes a list of currently tested BSPs compatible with the intel-common BSPs. Update the top-level README with a reference to this new README for the intel-common BSPs. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
* intel-core*: Add common MACHINE_* valuesDarren Hart2014-03-112-0/+16
| | | | | | | | Add common values for the various MACHINE_ variables, derived from the existing BSPs in meta-intel. Include EFI and PCBIOS, 3G and wifi support, and video decoding. Include the linux-firmware package. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
* intel-core*: Add default serial consoleDarren Hart2014-03-112-0/+8
| | | | | | | | For the intel-common BSPs, assume a default serial console of ttyS0 at 115200 BAUD. This will ensure the configuration is in place and is easy to find and modify on the resulting images. Signed-off-by: Darren Hart <dvhart@linux.intel.com>