On 07/14/2013 07:58 PM, Otavio Salvador wrote:
On Sun, Jul 14, 2013 at 11:52 PM, Fabio Estevam <feste...@gmail.com> wrote:
Hi Otavio,
On Sun, Jul 14, 2013 at 11:44 PM, Otavio Salvador
<ota...@ossystems.com.br> wrote:
On Sun, Jul 14, 2013 at 11:40 PM, Fabio Estevam <feste...@gmail.com> wrote:
From: Fabio Estevam <fabio.este...@freescale.com>
mx6qsabrelite and nitrogen6q boards are hardware compatible, so let's avoid the
code duplication and only use the nitrogen6x source code to make board code
maintainance easier.
Tested booting a mainline device tree kernel on a mx6qsabrelite board.
Signed-off-by: Fabio Estevam <fabio.este...@freescale.com>
I think this is a huge improvement I am just not sure about the
environment preserving for sabrelite. I think most people using
sabrelite end using the U-Boot from SPI NOR.
I can't say whether SPI NOR or SD card is the most common medium for
storing the environment variables for sabrelite, but my main goal here
was to try to keep compability with existing code.
Currently mx6qsabrelite defines CONFIG_ENV_IS_IN_MMC, so I kept the
same here. This patch introduces no change in functional behaviour.
If we think CONFIG_ENV_IS_IN_xxx should be changed, then this is
something to be handled by a separate patch.
Agreed :-)
Reviewed-by: Otavio Salvador <ota...@ossystems.com.br>
+1
We should also add something to the README file though.
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
