path: root/meta-yocto-bsp/recipes-bsp
AgeCommit message (Collapse)AuthorFilesLines
2021-07-29meta-poky/meta-yocto-bsp: Convert to new override syntaxRichard Purdie2-2/+2
This converts the two layers to the new override syntax. This was done using <oe-core>/scripts/contrib/convert-overrides.py <this-layer> with no manual fixes. (From meta-yocto rev: 387eab70f343966267c2a68746aea1bbb8525191) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-21gma500-gfx-check: Update licence to match changes in OE-CoreRichard Purdie1-1/+1
Match SPDX licence name changes in OE-Core. (From meta-yocto rev: 4acb5d2a9e77b8f426fa2370a9a71b9df8c7c3e7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-11-11beaglebone-yocto: rename beaglebone machine to beaglebone-yoctoJoshua Lock1-0/+0
The beaglebone BSP provided in this layer is a reference implementation usingonly mainline components available in core Yocto Project layers, whereas Texas Instruments maintain a full-featured BSP in the meta-ti layer. Rename the reference machine to prevent namespace collisions with the version maintained by the SoC vendor. [YOCTO #12326] (From meta-yocto rev: e32882938eca7f50548deab84dab78b4aef31b95) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-18gma500-gfx-check: Fixes infinite calling to modprobe gma500_gfxAlejandro Hernandez2-1/+5
The previous script caused an infinite call to modprobe gma500_gfx on certain situations, this fixes a typo and uses a new flag to avoid the infinite loop (From meta-yocto rev: 9a341596fd0cdf892e125b2eead7b5e334a590b4) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-07formfactor: add machconfig for BeagleboneMaxin B. John1-0/+3
We need machconfig file to automatically choose between physical and virtual keyboards. [YOCTO #9027] (From meta-yocto rev: 8ce98b75163c75ef74cb2d25fb01de9c4553ad9e) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-19formfactor: remove unused beagleboard configurationMaxin B. John1-3/+0
Clean up formfactor configuration for beagleboard (since only beaglebone machine definition exists). (From meta-yocto rev: 5118e5ee292df6f2f44a4b066b384ce8f1e59e3d) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-19alsa-state: remove beagleboard configurationMaxin B. John2-657/+0
Purging beagleboard related configuration (since only beaglebone machine definition exists). (From meta-yocto rev: 7740d956a9ba559674a27405761564ee96cfb8e3) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-11-25gma500_gfx: Avoid inserting gma500_gfx module for certain devicesAlejandro Hernandez3-0/+31
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 doesnt create an infinite loop executing itself everytime it wants to insert the module, busybox's modprobe doesn't provide this functionality, so a small hack had to be used to avoid the infite loop instead. (From meta-yocto rev: 70c143767a8b63921e668a62ac463b3a6b8c6132) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-28atom-pc: Purge straggling configuration filesDarren Hart1-6/+0
A few atom-pc configuration files escaped the last purge of atom-pc. Clean them up. (From meta-yocto rev: f26d99ffb2c67b310d4c46627932dc3f8aefad96) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-28meta-yocto-bsp: Add genericx86-64 machineDarren Hart1-0/+6
Duplicate the genericx86 machine, but select x86_64 tunables and use the common-pc-64 linux-yocto KMACHINE and config. This has been boot tested with core-image-sato on a Lenovo x220 (Core-i5) and a Supermicro MBD-X8DTL-iF-O (dual-socket Xeon 5680). (From meta-yocto rev: 9b7db7ded0e6b7f5c0cd3ab7fbb0bce4112407da) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Ross Burton <ross.burton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-07-31genericx86: add new BSPRoss Burton1-0/+6
This BSP aims to support "most" contemporary x86 hardware. It's a direct copy of atom-pc initially. (From meta-yocto rev: 1a73ef79e16d0cbcd60fa3ad9854dbc121e3282d) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-05meta-yocto: Split into distro and bsp componentsRichard Purdie5-0/+667
Now we have settled on best practises and compliance criteria, bring meta-yocto into compliance by separating out the hardware support components into meta-yocto-bsp leaving policy configuration in meta-yocto. Also rename the meta-yocto scripts directory to OE-Core can be a clearly isolated component in poky. (From meta-yocto rev: eac90e27a032ea23d9a4f35c7eef8b1940c80e22) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>