summaryrefslogtreecommitdiff
path: root/conf/machine/phyboard-mira-imx6-3.conf
AgeCommit message (Collapse)Author
2016-02-26barebox: imx6: env: add PEB-WLBT-01 (wifi) supportStefan Christ
Add support for expansion board PEB-WLBT-01 for phyBOARD-MIRA-i.MX6 to barebox environment Signed-off-by: Stefan Christ <s.christ@phytec.de> Signed-off-by: Stefan Müller-Klieser <s.mueller-klieser@phytec.de>
2015-12-14machine: imx6: use module and board article numberStefan Christ
The module and board article numbers contain more information (if you know how to decode them) than the article number of the bundle. Use them instead. Signed-off-by: Stefan Christ <s.christ@phytec.de> 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-12Add new phyboard-mira machinesChristian Hemp
Add the machine phyboard-mira-imx6-3 and phyboard-mira-imx6-4 and remove the old prototype machines phyboard-mira-imx6-1 and phyboard-mira-imx6-2. phyboard-mira-imx6-3: Full featured MIRA with: - phyCORE-i.MX6 Quad 1GB RAM - 1Gbit Ethernet - mPCIe - CAN - HDMI - Camera (VM-010 mono) - UART3 - SD - USB - USB otg phyboard-mira-imx6-4: Low Cost MIRA with: - phyCORE-i.MX6 SOLO 256MB RAM - 10/100 Mbit Ethernet - HDMI - SD - USB - USB otg Signed-off-by: Christian Hemp <c.hemp@phytec.de> Conflicts: conf/machine/phyboard-mira-imx6-3.conf conf/machine/phyboard-mira-imx6-4.conf Signed-off-by: Stefan Müller-Klieser <s.mueller-klieser@phytec.de>