path: root/meta-yocto-bsp/recipes-graphics
AgeCommit message (Collapse)Author
2021-07-29meta-poky/meta-yocto-bsp: Convert to new override syntaxRichard Purdie
This converts the two layers to the new override syntax. This was done using <oe-core>/scripts/contrib/ <this-layer> with no manual fixes. (From meta-yocto rev: 387eab70f343966267c2a68746aea1bbb8525191) Signed-off-by: Richard Purdie <>
2019-03-02meta-yocto-bsp: Disable the glamor acceleration for the beagleboneKevin Hao
In the commit ec6d61cbddc3 ("mesa: enable native and nativesdk variants"), the gallium is enabled for the mesa. Since we use the modesetting driver for the Xorg on the beagleboard and the glamor acceleration method is enabled by the modesetting driver, the gallium DRI driver will be used after this commit. But the gallium DRI driver only support 32bpp and we choose to use 16bpp on beaglebone in commit e7434c17b4b3 ("meta-yocto-bsp: workaround the X malfunction on beaglebone"), the mismatch between them causes the malfunction of the Xorg. I have hacked the kernel to enable the 32bpp for the beagllebone, but it has the following issues: 1. The color is abnormal. 2. The Xorg hang occasionally. 3. The performance of using glamor acceleration based on gallium is pretty bad. So I choose to disable the glamor on this board. (From meta-yocto rev: b7a995856c58b507a521a55dcf94bee75804e81c) Signed-off-by: Kevin Hao <> Signed-off-by: Richard Purdie <>
2017-11-11beaglebone-yocto: rename beaglebone machine to beaglebone-yoctoJoshua Lock
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 <> Signed-off-by: Richard Purdie <>
2017-04-11meta-yocto-bsp: workaround the X malfunction on beagleboneKevin Hao
After the change in kernel commit a291b6b3d287 ("ARM: dts: am335x-boneblack: Add blue-and-red-wiring -property to LCDC node"), the pixel format we support for 32bit bpp has been changed from XRGB8888 to XBGR8888. But the fbdev created by modesetting driver use the XRGB8888 format by default, this causes the X malfunction. There is no easy way to adjust the pixel format of the fbdev created by the modesetting driver. So we create a xorg.conf to use the 16bit bpp to work around this issue. [YOCTO #11267] (From meta-yocto rev: 1ef8a9584298a8745a28c0c92fa3ecbf92ffe494) Signed-off-by: Kevin Hao <> Signed-off-by: Richard Purdie <>
2014-03-31Drop beagleboard, replaced by beagleboneRichard Purdie
(From meta-yocto rev: b125761e5e31fc506f7b5b87308850cd573ab1b6) Signed-off-by: Richard Purdie <>
2013-08-28atom-pc: Purge straggling configuration filesDarren Hart
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 <> Signed-off-by: Richard Purdie <>
2013-08-28meta-yocto-bsp: Add genericx86-64 machineDarren Hart
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 <> Cc: Ross Burton <> Cc: Tom Zanussi <> Cc: Bruce Ashfield <> Signed-off-by: Richard Purdie <>
2013-07-31genericx86: add new BSPRoss Burton
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 <> Signed-off-by: Saul Wold <> Signed-off-by: Richard Purdie <>
2013-05-29xserver-xf86-config: re-enable AutoAddDevices for beagleboardPaul Eggleton
This was added quite a long time ago because of poor interactions between HAL and the X server when it came to enabling input devices. HAL is long gone and I think it's safe to say we don't need to disable this any longer, especially as it gets in the way of being able to plug in the keyboard/mouse after boot. (This has already effectively been removed for the other BSPs in meta-yocto-bsp). Fixes [YOCTO #1823]. (From meta-yocto rev: 214bc44e119ca808e59d28a21a6626c6f8e03cf7) Signed-off-by: Paul Eggleton <> Signed-off-by: Richard Purdie <>
2013-03-04xserver-xf86-config: atom-pc doesn't need a xorg.confRoss Burton
Replace xorg.conf with an empty file so it doesn't get installed, as atom-pc can auto-detect the hardware. (From meta-yocto rev: 3f47e2bc61e564dfc179ef29ded43411e1a40b5a) Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <>
2012-12-06mesa: remove atom-pc specific overridesRoss Burton
These bbappends were used so that atom-pc would prefer mesa-dri over mesa-xlib. We don't have mesa-xlib anymore, so these are not required. (From meta-yocto rev: bf7e83a980e9df664d79c94fff31189b5abb04ca) Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <>
2012-09-05meta-yocto: Split into distro and bsp componentsRichard Purdie
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 <>