summaryrefslogtreecommitdiff
path: root/conf/machine/phyflex-imx6-5.conf
AgeCommit message (Collapse)Author
2019-12-19i.mx6: change to generic path for barebox image nameMaik Otto
the barebox in PD20 will be have a parallel image build for unsigned, signed, usb signed and encrypted images. so the machines have been reworked to integrate this functionality with a generic barebox image name Signed-off-by: Maik Otto <m.otto@phytec.de> Signed-off-by: Stefan Müller-Klieser <s.mueller-klieser@phytec.de>
2019-09-06conf: machine: remove SUPPORTEDIMAGE variableNorbert Wesp
The definition of this combinations moved to the manifest. Signed-off-by: Norbert Wesp <n.wesp@phytec.de> Signed-off-by: Stefan Müller-Klieser <s.mueller-klieser@phytec.de>
2018-05-09machine: imx6: Add yogurt distro to SUPPORTEDIMAGEStefan Riedmueller
The naming pattern for the SUPPORTEDIMAGE meta data changed as it now also contains the distro. So yogurt was added to the SUPPORTEDIMAGE of all i.MX 6 boards that already had a supported image set. Signed-off-by: Stefan Riedmueller <s.riedmueller@phytec.de> Signed-off-by: Stefan Müller-Klieser <s.mueller-klieser@phytec.de>
2017-04-20machine: i.MX6: update DESCRIPTION fieldsStefan Müller-Klieser
We have entries at the layer index for our hardware. The DESCRIPTION field will be used to describe our boards. The important keywords have to be found here so that our boards get displayed online in a nice way. Signed-off-by: Stefan Müller-Klieser <s.mueller-klieser@phytec.de>
2016-11-29machines: imx6: refactor includes for UltraLite and Quad/DualLiteStefan Christ
The i.MX6 SoCs UltraLite and Quad/DualLite are quite different. Therefore split the configuration into two separate files 'phyimx6ul.inc' and 'phyimx6qdl.inc' and a common file 'phyimx6.inc'. This refactoring does not change the config variables of the machines. Tested with "bitbake -e". The only difference is the values of PREFERRED_PROVIDER_virtual/egl, .. for the i.MX6 UltraLite. Now it has the default values: PREFERRED_PROVIDER_virtual/egl="mesa" PREFERRED_PROVIDER_virtual/libgl="mesa" PREFERRED_PROVIDER_virtual/libgles2="mesa" PREFERRED_PROVIDER_virtual/libgles1="mesa" Signed-off-by: Stefan Lengfeld <s.lengfeld@phytec.de> Signed-off-by: Stefan Müller-Klieser <s.mueller-klieser@phytec.de>
2016-10-06MACHINE_FEATURES: renameStefan Müller-Klieser
- wlan to wifi, upstream compliant - touchscreen to resistivetouch, correction Signed-off-by: Stefan Müller-Klieser <s.mueller-klieser@phytec.de>
2016-06-03machine: imx6: don't use _append for SOC_FAMILYStefan Christ
Now bitbake does not need two parsing passes to resolve the value of variable SOC_FAMILY. This will avoid problems when the barebox environment handling is reworked. Signed-off-by: Stefan Christ <s.christ@phytec.de> Signed-off-by: Stefan Müller-Klieser <s.mueller-klieser@phytec.de>
2016-05-09machines: imx6: update machine info from databaseStefan Müller-Klieser
Signed-off-by: Stefan Müller-Klieser <s.mueller-klieser@phytec.de>
2015-10-20conf: [imx6]: refactor KBUILD_DEFCONFIGStefan Christ
The kernel defconfig is the same for all i.MX6 machines. Move the definition to the general include file phyimx6.inc. The AM335x machine configuration does the same. Signed-off-by: Stefan Christ <s.christ@phytec.de> Signed-off-by: Stefan Müller-Klieser <s.mueller-klieser@phytec.de>
2015-09-25barebox.inc: remove BAREBOX_DEFAULT_ENV handlingStefan Christ
The machine specific variable BAREBOX_DEFAULT_ENV contains the path to the default environment in the barebox source tree. It's only used when no other environments machineenv, boardenv and commonenv is used. It's only a fallback mechanism. In the first case, when machineenv, boardenv or commonenv is defined, the variable BAREBOX_DEFAULT_ENV is not used and no files are added to the environment from the internal barebox default environment. In the second case, when machineenv, boardenv and commonenv are not defined, the variable BAREBOX_DEFAULT_ENV _is_ used and the path to the internal barebox environment is added to the config parameter CONFIG_DEFAULT_ENVIRONMENT_PATH instead of the machineenv, boardenv or commonenv paths. But the internal barebox environment in source tree in folders arch/arm/boards/phytec-som-am335x/defaultenv-physom-am335x/ and arch/arm/boards/phytec-phyflex-imx6/defaultenv-phyflex-imx6/ is nevertheless used, because our device init functions in board.c have the code lines like defaultenv_append_directory(defaultenv_physom_am335x); Signed-off-by: Stefan Christ <s.christ@phytec.de> Signed-off-by: Stefan Müller-Klieser <s.mueller-klieser@phytec.de>
2015-09-15i.MX6: machine: Add SOC_FAMILY appendStefan Christ
Introduce the same board specific SOC_FAMILY as for the AM335x machines. The i.MX6 SOC_FAMILYs are phyboard-alcor-imx6, phyboard-mira-imx6, phyboard-subra-imx6, phycard-imx6 and phyflex-imx6 Now every i.MX6 machine is in the SOC_FAMILY 'mx6' and in the SOC_FAMILY 'mx6q' or 'mx6dl' and in one of the board specific SOC_FAMILYs from above. Signed-off-by: Stefan Christ <s.christ@phytec.de> Signed-off-by: Stefan Müller-Klieser <s.mueller-klieser@phytec.de>
2015-08-05linux: switch to linux-yocto includeStefan Müller-Klieser
We want to be more mainline conform. As it is now possible to use the yocto kernel recipes with a standard kernel, we switch to this recipe to reduce maintainance by dropping the legacy kernel recipe. Signed-off-by: Stefan Müller-Klieser <s.mueller-klieser@phytec.de>
2015-04-24conf: machine: add phy(flex|card)-imx6 machinesStefan Christ
Add a couple of standard and non-standard phyFLEX-i.MX6 and phyCARD-i.MX6 RAM variants and append the necessary COMAPTIBLE_MACHINE lines in the barebox and linux-mainline recipe. Signed-off-by: Stefan Christ <s.christ@phytec.de>