Home
last modified time | relevance | path

Searched hist:"00 f43e51c5e77c3333784830305a2bbd4d55d2c0" (Results 1 – 5 of 5) sorted by relevance

/rk3399_rockchip-uboot/include/configs/
H A Dmx6sabreauto.h00f43e51c5e77c3333784830305a2bbd4d55d2c0 Mon Jul 10 18:59:12 UTC 2017 Fabio Estevam <fabio.estevam@nxp.com> mx6sabre: Use PARTUUID to specify the rootfs location

mx6sabre boards can run different kernel versions, such as NXP 4.1 or
mainline.

Currently the rootfs location is passed via mmcblk number and the
problem with this approach is that the mmcblk number for the eMMC
changes depending on the kernel version.

In order to avoid such issue, use UUID method to specify the rootfs
location.

Succesfully tested booting a NXP 4.1 and also a mainline kernel on a
mx6qsabresd and mx6dlsabreauto.

Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
H A Dmx6sabresd.h00f43e51c5e77c3333784830305a2bbd4d55d2c0 Mon Jul 10 18:59:12 UTC 2017 Fabio Estevam <fabio.estevam@nxp.com> mx6sabre: Use PARTUUID to specify the rootfs location

mx6sabre boards can run different kernel versions, such as NXP 4.1 or
mainline.

Currently the rootfs location is passed via mmcblk number and the
problem with this approach is that the mmcblk number for the eMMC
changes depending on the kernel version.

In order to avoid such issue, use UUID method to specify the rootfs
location.

Succesfully tested booting a NXP 4.1 and also a mainline kernel on a
mx6qsabresd and mx6dlsabreauto.

Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
H A Dmx6sabre_common.h00f43e51c5e77c3333784830305a2bbd4d55d2c0 Mon Jul 10 18:59:12 UTC 2017 Fabio Estevam <fabio.estevam@nxp.com> mx6sabre: Use PARTUUID to specify the rootfs location

mx6sabre boards can run different kernel versions, such as NXP 4.1 or
mainline.

Currently the rootfs location is passed via mmcblk number and the
problem with this approach is that the mmcblk number for the eMMC
changes depending on the kernel version.

In order to avoid such issue, use UUID method to specify the rootfs
location.

Succesfully tested booting a NXP 4.1 and also a mainline kernel on a
mx6qsabresd and mx6dlsabreauto.

Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
/rk3399_rockchip-uboot/configs/
H A Dmx6sabresd_defconfig00f43e51c5e77c3333784830305a2bbd4d55d2c0 Mon Jul 10 18:59:12 UTC 2017 Fabio Estevam <fabio.estevam@nxp.com> mx6sabre: Use PARTUUID to specify the rootfs location

mx6sabre boards can run different kernel versions, such as NXP 4.1 or
mainline.

Currently the rootfs location is passed via mmcblk number and the
problem with this approach is that the mmcblk number for the eMMC
changes depending on the kernel version.

In order to avoid such issue, use UUID method to specify the rootfs
location.

Succesfully tested booting a NXP 4.1 and also a mainline kernel on a
mx6qsabresd and mx6dlsabreauto.

Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
H A Dmx6sabreauto_defconfig00f43e51c5e77c3333784830305a2bbd4d55d2c0 Mon Jul 10 18:59:12 UTC 2017 Fabio Estevam <fabio.estevam@nxp.com> mx6sabre: Use PARTUUID to specify the rootfs location

mx6sabre boards can run different kernel versions, such as NXP 4.1 or
mainline.

Currently the rootfs location is passed via mmcblk number and the
problem with this approach is that the mmcblk number for the eMMC
changes depending on the kernel version.

In order to avoid such issue, use UUID method to specify the rootfs
location.

Succesfully tested booting a NXP 4.1 and also a mainline kernel on a
mx6qsabresd and mx6dlsabreauto.

Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>