| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Mesa is the default libgbm provider, but does not yet have virtual/libgbm
in the PROVIDES list. This makes it difficult the change the dependency
to another recipes that provide only libgbm. Add virtual/libgbm to mesa
and TI's libgbm recipe, and change the dependency in qtbase.
Add gbm to qtbase PACKAGECONFIG on intel devices.
Task-number: QTBUG-57896
Change-Id: I491df7057e52f9e74dd87abf65e542eab2cd3f9e
Reviewed-by: Gatis Paeglis <gatis.paeglis@qt.io>
Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
|
| |
|
|
|
| |
Change-Id: Ic31ed346d6520b3bd6fc7a58e15a41e4496385c7
Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Prepending to IMAGE_CMD_ext3 in order to push files into the rootfs is
flaky for a couple of reasons. First, it is conceptually inconsistent
with the rest of the build system - files that go into the rootfs should
really by installed by packages through the regular mechanisms. Second,
and what prompted this patch, with several concurrent image generation
tasks this is just unsafe. I regularly experienced .tgz image generation
failures, as tar complained that the files changed from under it.
Since this is related to the grub-efi packaging on this particular device,
just package the microcode into the required initramfs in that recipe.
Change-Id: I4e037ddbb017d1764852310b0b77900cde260dd6
Reviewed-by: Gatis Paeglis <gatis.paeglis@qt.io>
|
| |
|
|
|
|
|
| |
License changed to GPLv3 + Commercial
Change-Id: I267c97216e717ed29071df064337e1bcf83de973
Reviewed-by: Kalle Viironen <kalle.viironen@theqtcompany.com>
|
|
|
meta-intel no longer has specific BSPs for each machine, but they
share a common BSP based on the architecture.
Change-Id: Ibbb7b8b2153103367168ea37d904ce23bc245108
Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
|
