[U-Boot] [PATCH 1/3] mx53loco: Change default environment to cope with OE changes
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 otavio@ossystems.com.br --- include/configs/mx53loco.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/configs/mx53loco.h b/include/configs/mx53loco.h index 8cbaf08..fcd6b44 100644 --- a/include/configs/mx53loco.h +++ b/include/configs/mx53loco.h @@ -120,8 +120,8 @@ "script=boot.scr\0" \ "uimage=uImage\0" \ "mmcdev=0\0" \ - "mmcpart=2\0" \ - "mmcroot=/dev/mmcblk0p3 rw\0" \ + "mmcpart=1\0" \ + "mmcroot=/dev/mmcblk0p2 rw\0" \ "mmcrootfstype=ext3 rootwait\0" \ "mmcargs=setenv bootargs console=ttymxc0,${baudrate} " \ "root=${mmcroot} " \
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 otavio@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" \ + "console=ttymxc1\0" \ "mmcdev=0\0" \ - "mmcpart=2\0" \ - "mmcroot=/dev/mmcblk0p3 rootwait rw\0" \ + "mmcpart=1\0" \ + "mmcroot=/dev/mmcblk0p2 rootwait rw\0" \ "mmcargs=setenv bootargs console=${console},${baudrate} " \ "root=${mmcroot}\0" \ "loadbootscript=" \
On Wed, Sep 19, 2012 at 10:13 AM, Otavio Salvador otavio@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 otavio@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...
Regards,
On Wed, Sep 19, 2012 at 2:57 PM, Robert Nelson robertcnelson@gmail.com wrote:
On Wed, Sep 19, 2012 at 10:13 AM, Otavio Salvador otavio@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 otavio@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.
Fabio, do you prefer me to keep it or remove?
On Wed, Sep 19, 2012 at 1:00 PM, Otavio Salvador otavio@ossystems.com.br wrote:
On Wed, Sep 19, 2012 at 2:57 PM, Robert Nelson robertcnelson@gmail.com wrote:
On Wed, Sep 19, 2012 at 10:13 AM, Otavio Salvador otavio@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 otavio@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. ;)
Regards,
On Wed, Sep 19, 2012 at 3:08 PM, Robert Nelson robertcnelson@gmail.com wrote:
On Wed, Sep 19, 2012 at 1:00 PM, Otavio Salvador otavio@ossystems.com.br wrote:
On Wed, Sep 19, 2012 at 2:57 PM, Robert Nelson robertcnelson@gmail.com wrote:
On Wed, Sep 19, 2012 at 10:13 AM, Otavio Salvador otavio@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 otavio@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.
On 09/19/2012 11:22 AM, Otavio Salvador wrote:
On Wed, Sep 19, 2012 at 3:08 PM, Robert Nelsonrobertcnelson@gmail.com wrote:
On Wed, Sep 19, 2012 at 1:00 PM, Otavio Salvador otavio@ossystems.com.br wrote:
On Wed, Sep 19, 2012 at 2:57 PM, Robert Nelsonrobertcnelson@gmail.com wrote:
On Wed, Sep 19, 2012 at 10:13 AM, Otavio Salvador otavio@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 Salvadorotavio@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
On Wed, Sep 19, 2012 at 8:40 PM, Eric Nelson eric.nelson@boundarydevices.com wrote:
On 09/19/2012 11:22 AM, Otavio Salvador wrote:
On Wed, Sep 19, 2012 at 3:08 PM, Robert Nelsonrobertcnelson@gmail.com wrote:
On Wed, Sep 19, 2012 at 1:00 PM, Otavio Salvador otavio@ossystems.com.br wrote:
On Wed, Sep 19, 2012 at 2:57 PM, Robert Nelsonrobertcnelson@gmail.com wrote:
On Wed, Sep 19, 2012 at 10:13 AM, Otavio Salvador otavio@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 Salvadorotavio@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.
I sort of agree; do you use 2 or 3 partitions in this case?
Isn't using 'mkenvimage' in OE a better route? That way, the environment can change with the userspace decision.
In fact in OE we have a patch for it. Usually we don't call mkenvimage for it but I like the idea to add this feature there later.
Hi Otavio,
On 09/19/2012 04:51 PM, Otavio Salvador wrote:
On Wed, Sep 19, 2012 at 8:40 PM, Eric Nelson eric.nelson@boundarydevices.com wrote:
On 09/19/2012 11:22 AM, Otavio Salvador wrote:
On Wed, Sep 19, 2012 at 3:08 PM, Robert Nelsonrobertcnelson@gmail.com wrote:
On Wed, Sep 19, 2012 at 1:00 PM, Otavio Salvador otavio@ossystems.com.br wrote:
On Wed, Sep 19, 2012 at 2:57 PM, Robert Nelsonrobertcnelson@gmail.com wrote:
On Wed, Sep 19, 2012 at 10:13 AM, Otavio Salvador otavio@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 Salvadorotavio@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.
I sort of agree; do you use 2 or 3 partitions in this case?
Or 1 or 9?
I'm actually not kidding here. The current Freescale Android image (R13.4-Beta) actually does want 9 partitions for a bunch of stuff like a 'recovery' partition, a 'vendor' partition, etc.
Or even 0? Windows users have been known to use SD cards straight out of the box with no partition table.
In short, this is something that can't be solved in the general case, so I think it's best for the main-line U-Boot code to not try and provide policy, only functionality.
To that end, we've tried to standardize on something simple: the presence of a file named '6q_bootscript' on one of the SD cards that can handle these sorts of userspace details: http://boundarydevices.com/u-boot-conventions-for-i-mx6-nitrogen6x-and-sabre...
This allows all of the userspace bits to go into the userspace filesystem, but still allows machine-specific like the type of display connected to be saved in the environment.
Using this approach, you can load kernel(s) or RAM disks from anywhere that U-Boot can reach without re-compiling U-Boot.
Isn't using 'mkenvimage' in OE a better route? That way, the environment can change with the userspace decision.
In fact in OE we have a patch for it. Usually we don't call mkenvimage for it but I like the idea to add this feature there later.
The best part of doing it in OE is that the same commit should be able to update both the environment variables (or boot script) and the parts which depend on it (like creation of the filesystem image(s)).
Regards,
Eric
On Wed, Sep 19, 2012 at 9:58 PM, Eric Nelson eric.nelson@boundarydevices.com wrote:
On 09/19/2012 04:51 PM, Otavio Salvador wrote:
I sort of agree; do you use 2 or 3 partitions in this case?
Or 1 or 9?
I'm actually not kidding here. The current Freescale Android image (R13.4-Beta) actually does want 9 partitions for a bunch of stuff like a 'recovery' partition, a 'vendor' partition, etc.
Or even 0? Windows users have been known to use SD cards straight out of the box with no partition table.
In short, this is something that can't be solved in the general case, so I think it's best for the main-line U-Boot code to not try and provide policy, only functionality.
I agree; but mainline could have defaults that works at least for usual U-Boot hacker. That's why I asked how many you use.
To that end, we've tried to standardize on something simple: the presence of a file named '6q_bootscript' on one of the SD cards that can handle these sorts of userspace details:
http://boundarydevices.com/u-boot-conventions-for-i-mx6-nitrogen6x-and-sabre...
This allows all of the userspace bits to go into the userspace filesystem, but still allows machine-specific like the type of display connected to be saved in the environment.
Using this approach, you can load kernel(s) or RAM disks from anywhere that U-Boot can reach without re-compiling U-Boot.
This is indeed nice.
Isn't using 'mkenvimage' in OE a better route? That way, the environment can change with the userspace decision.
In fact in OE we have a patch for it. Usually we don't call mkenvimage for it but I like the idea to add this feature there later.
The best part of doing it in OE is that the same commit should be able to update both the environment variables (or boot script) and the parts which depend on it (like creation of the filesystem image(s)).
Yes; I will work in a generic way for it in OE ... I like the idea and also see the added value for the flexibility.
After MX23 I will focus on this ;-) (or Marek kills me :P)
This doesn't solve the question:
Better to have 2 or 3 partition layout by default in mainline?
Hi Octavio,
On 09/19/2012 06:15 PM, Otavio Salvador wrote:
On Wed, Sep 19, 2012 at 9:58 PM, Eric Nelson eric.nelson@boundarydevices.com wrote:
On 09/19/2012 04:51 PM, Otavio Salvador wrote:
I sort of agree; do you use 2 or 3 partitions in this case?
Or 1 or 9?
I'm actually not kidding here. The current Freescale Android image (R13.4-Beta) actually does want 9 partitions for a bunch of stuff like a 'recovery' partition, a 'vendor' partition, etc.
Or even 0? Windows users have been known to use SD cards straight out of the box with no partition table.
In short, this is something that can't be solved in the general case, so I think it's best for the main-line U-Boot code to not try and provide policy, only functionality.
I agree; but mainline could have defaults that works at least for usual U-Boot hacker. That's why I asked how many you use.
To that end, we've tried to standardize on something simple: the presence of a file named '6q_bootscript' on one of the SD cards that can handle these sorts of userspace details:
http://boundarydevices.com/u-boot-conventions-for-i-mx6-nitrogen6x-and-sabre...
This allows all of the userspace bits to go into the userspace filesystem, but still allows machine-specific like the type of display connected to be saved in the environment.
Using this approach, you can load kernel(s) or RAM disks from anywhere that U-Boot can reach without re-compiling U-Boot.
This is indeed nice.
Isn't using 'mkenvimage' in OE a better route? That way, the environment can change with the userspace decision.
In fact in OE we have a patch for it. Usually we don't call mkenvimage for it but I like the idea to add this feature there later.
The best part of doing it in OE is that the same commit should be able to update both the environment variables (or boot script) and the parts which depend on it (like creation of the filesystem image(s)).
Yes; I will work in a generic way for it in OE ... I like the idea and also see the added value for the flexibility.
After MX23 I will focus on this ;-) (or Marek kills me :P)
This doesn't solve the question:
Better to have 2 or 3 partition layout by default in mainline?
I suspect that this question isn't for me, since I'm not sure which userspace(s) we're targeting.
Heck, I didn't know that OE was still kicking... I kinda had the impression that Yocto had taken it over ;)
Regards,
Eric
On Wed, Sep 19, 2012 at 10:29 PM, Eric Nelson eric.nelson@boundarydevices.com wrote:
On 09/19/2012 06:15 PM, Otavio Salvador wrote:
On Wed, Sep 19, 2012 at 9:58 PM, Eric Nelson eric.nelson@boundarydevices.com wrote:
The best part of doing it in OE is that the same commit should be able to update both the environment variables (or boot script) and the parts which depend on it (like creation of the filesystem image(s)).
Yes; I will work in a generic way for it in OE ... I like the idea and also see the added value for the flexibility.
After MX23 I will focus on this ;-) (or Marek kills me :P)
This doesn't solve the question:
Better to have 2 or 3 partition layout by default in mainline?
I suspect that this question isn't for me, since I'm not sure which userspace(s) we're targeting.
Heck, I didn't know that OE was still kicking... I kinda had the impression that Yocto had taken it over ;)
Yocto is an unbrealla project which has OE-Core and bitbake plus meta-yocto merged in Poky. The markering is all done for Yocto but OE is live there ;-)
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 otavio@ossystems.com.br --- include/configs/mx6qsabresd.h | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/include/configs/mx6qsabresd.h b/include/configs/mx6qsabresd.h index 448ce28..793427a 100644 --- a/include/configs/mx6qsabresd.h +++ b/include/configs/mx6qsabresd.h @@ -74,11 +74,9 @@ "script=boot.scr\0" \ "uimage=uImage\0" \ "console=ttymxc0\0" \ - "fdt_high=0xffffffff\0" \ - "initrd_high=0xffffffff\0" \ "mmcdev=0\0" \ - "mmcpart=2\0" \ - "mmcroot=/dev/mmcblk0p3 rootwait rw\0" \ + "mmcpart=1\0" \ + "mmcroot=/dev/mmcblk1p2 rootwait rw\0" \ "mmcargs=setenv bootargs console=${console},${baudrate} " \ "root=${mmcroot}\0" \ "loadbootscript=" \
participants (3)
-
Eric Nelson -
Otavio Salvador -
Robert Nelson