On 09/19/2012 11:22 AM, Otavio Salvador wrote:
On Wed, Sep 19, 2012 at 3:08 PM, Robert Nelson<robertcnel...@gmail.com> wrote:
On Wed, Sep 19, 2012 at 1:00 PM, Otavio Salvador
<ota...@ossystems.com.br> wrote:
On Wed, Sep 19, 2012 at 2:57 PM, Robert Nelson<robertcnel...@gmail.com> wrote:
On Wed, Sep 19, 2012 at 10:13 AM, Otavio Salvador
<ota...@ossystems.com.br> wrote:
OpenEmbedded has change partitioning layout of generated image so it
does not raise warnings during the boot regarding unkown partition
being used for U-Boot.
Signed-off-by: Otavio Salvador<ota...@ossystems.com.br>
---
include/configs/mx6qsabrelite.h | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/include/configs/mx6qsabrelite.h b/include/configs/mx6qsabrelite.h
index 72d0154..0d5fd40 100644
--- a/include/configs/mx6qsabrelite.h
+++ b/include/configs/mx6qsabrelite.h
@@ -141,12 +141,10 @@
#define CONFIG_EXTRA_ENV_SETTINGS \
"script=boot.scr\0" \
"uimage=uImage\0" \
- "console=ttymxc1\0" \
- "fdt_high=0xffffffff\0" \
- "initrd_high=0xffffffff\0" \
Your going to need fdt_high/initrd_high for when using linux device tree's...
I am not against keeping it but it is not used right now.
It may not be used in openembedded, but device tree is the only option
for a pure mainline kernel for this board, so it's needed. ;)
No problem, I can rebase and remove this change.
Hi Otavio,
It seems that this path of trying to configure the "right" set of default
options seems like a bit of a goose chase.
Isn't using 'mkenvimage' in OE a better route? That way, the environment can
change with the userspace decision.
Regards,
Eric
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
