| Age | Commit message (Collapse) | Author |
|---|
|
As the machine were not using UBOOT_CONFIG, the first step was to
convert the recipe to use the variable. After that, the mfgtool
variant is added.
Change-Id: I73ab7cdaef1d85cfd7cb3e3d650aed09682be2f4
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
3.10.17-1.0.0-beta changed the imx6sl-evk.dts file to work with
EPDC but as a consequence it breaks CSI function as its pins
are shared. A new imx6sl-evk-csi.dts file has been add to
allow use of CSI in case it is desired.
Signed-off-by: Lauren Post <lauren.post@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Change-Id: I0b511a73923a5876a960f427e165bc28c6cd7a44
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Change-Id: I8225e52de382a20de05b8255574892fd63ffc002
Signed-off-by: Lauren Post <lauren.post@freescale.com>
|
|
ENGR00277895: dts: ARM: imx6: add ldo-enable dts files
Currently, we use different dts files to support ldo-bypass or ldo-enable, then
we need add both dts files for the boards which can support ldo-bypass mode(all
boards support ldo-enable at least). So for below boards we need add ldo-enable
dts file so that we can use this to easily support ldo-enable mode:
1)mx6q-sabresd board: ldo-bypass dts->mx6q-sabresd.dtb,
ldo-enable dts->mx6q-sabresd-ldo.dtb
2)mx6q-sabresd board: ldo-bypass dts->mx6dl-sabresd.dtb,
ldo-enable dts->mx6dl-sabresd-ldo.dtb
3)mx6sl-evk board: ldo-bypass dts->mx6sl-evk.dtb,
ldo-enable dts->mx6sl-evk-ldo.dtb
Change-Id: I997bf896a3d3fde482fe9c120a92c16d49817adb
Signed-off-by: Lauren Post <lauren.post@freescale.com>
|
|
Include vendor name to machine name
Fix machine name
Include SOC
Fix description
Change-Id: Icab97b5de6f1bf02af778d026abd9e3365a523cf
Signed-off-by: Daiane Angolini <daiane.angolini@freescale.com>
|
|
The SOC_FAMILY uses the MACHINEOVERRIDES and it evaluates from left to
right. In this case, the most SoC specific value needs to be kept in
the right so it take precedence.
This has been catch when finding out why i.MX6SL EVK where using the
wrong value as entry point, and this was the root cause.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Change-Id: I8e5b3d6b31267f6cfcfe11be9a7aa4d6a5fdfec0
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Add machine definition for Freescale i.MX6SL EVK board
Change-Id: I696ca2dc1705d2095afbf2f16c62ed79404966ad
Signed-off-by: Daiane Angolini <daiane.angolini@freescale.com>
|
Otavio Salvador
Lauren Post
Daiane Angolini