Skip to contentSkip to conversation

OMAP4: speed up booting on Pandaboard

PATCH New Sergiy Kibrik 4 participants 10 messages Nov 4, 2010 – Nov 15, 2010 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 OMAP4: speed up booting on Pandaboard

Improved default config for OMAP4 Pandaboard for faster boot:

	-reduced environment size to speed up memory initialization;
	-USB TTY driver turned off;
	-tweaked blob load address to avoid image relocation (according to default uImage load address);
---
 include/configs/omap4_panda.h |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)
include/configs/omap4_panda.h +4 -4
index 74defab..5aba424 100644
@@ -62,10 +62,10 @@
 
 /*
  * Size of malloc() pool
- * Total Size Environment - 256k
+ * Total Size Environment - 2k
  * Malloc - add 256k
  */
-#define CONFIG_ENV_SIZE			(256 << 10)
+#define CONFIG_ENV_SIZE			(256 << 4)
 #define CONFIG_SYS_MALLOC_LEN		(CONFIG_ENV_SIZE + (256 << 10))
 						/* initial data */
 /* Vector Base */
@@ -117,7 +117,7 @@
 
 /* USB device configuration */
 #define CONFIG_USB_DEVICE		1
-#define CONFIG_USB_TTY			1
+#undef CONFIG_USB_TTY
 #define CONFIG_SYS_CONSOLE_IS_IN_ENV	1
 
 /* Flash */
@@ -146,7 +146,7 @@
 #define CONFIG_ENV_OVERWRITE
 
 #define CONFIG_EXTRA_ENV_SETTINGS \
-	"loadaddr=0x82000000\0" \
+	"loadaddr=0x80007FC0\0" \
 	"console=ttyS2,115200n8\0" \
 	"usbtty=cdc_acm\0" \
 	"vram=16M\0" \
Signature · 1 line
1.7.0.4
#1 lore raw

PATCH 1/1 OMAP4: speed up booting on Pandaboard

Sergiy Kibrik wrote, on 11/04/2010 05:38 AM:

Quoted 3 lines

Improved default config for OMAP4 Pandaboard for faster boot:

	-reduced environment size to speed up memory initialization;
	-USB TTY driver turned off;

Do we really want to do this?

Quoted 3 lines
	-tweaked blob load address to avoid image relocation (according to default uImage load address);

What kind of savings did we get? I am guessing we have some time x savings..

Quoted 9 lines
---
  include/configs/omap4_panda.h |    8 ++++----
  1 files changed, 4 insertions(+), 4 deletions(-)
include/configs/omap4_panda.h +0 -0
index 74defab..5aba424 100644

include/configs/omap4_panda.h line 68

Quoted 9 lines
include/configs/omap4_panda.h +2 -2
@@ -62,10 +62,10 @@
 
  /*
   * Size of malloc() pool
- * Total Size Environment - 256k
+ * Total Size Environment - 2k
   * Malloc - add 256k
   */
-#define CONFIG_ENV_SIZE			(256<<  10)
+#define CONFIG_ENV_SIZE			(256<<  4)

/me likes the change, but not sure how it saves boot time.

include/configs/omap4_panda.h line 120

Quoted 9 lines
include/configs/omap4_panda.h +1 -1
  #define CONFIG_SYS_MALLOC_LEN		(CONFIG_ENV_SIZE + (256<<  10))
  						/* initial data */
  /* Vector Base */
@@ -117,7 +117,7 @@
 
  /* USB device configuration */
  #define CONFIG_USB_DEVICE		1
-#define CONFIG_USB_TTY			1
+#undef CONFIG_USB_TTY

do we need to have the undef? it might be better to just drop the define perhaps? what impact do we have on boot time with this change?

include/configs/omap4_panda.h line 149

Quoted 9 lines
include/configs/omap4_panda.h +1 -1
  #define CONFIG_SYS_CONSOLE_IS_IN_ENV	1
 
  /* Flash */
@@ -146,7 +146,7 @@
  #define CONFIG_ENV_OVERWRITE
 
  #define CONFIG_EXTRA_ENV_SETTINGS \
-	"loadaddr=0x82000000\0" \
+	"loadaddr=0x80007FC0\0" \

btw, Dumb question: how did we decide on this address? building from kernel.org, I see System.map @ c0004000 ==> 80004000

when I do make uImage,
/bin/bash /home/nmenon/Src/opensource/linux-2.6/scripts/mkuboot.sh -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n 'Linux-2.6.37-rc1-00005-gd88c092'

Regards,
Nishanth Menon

#8 lore raw

PATCH 1/1 OMAP4: speed up booting on Pandaboard

In reply to a message not in the archive

Forgot to copy list on my reply!

---------- Forwarded message ----------
From: Steve Sakoman <[email protected]>
Date: Thu, Nov 4, 2010 at 11:09 AM
Subject: Re: [U-Boot] [PATCH] OMAP4: speed up booting on Pandaboard
To: Sergiy Kibrik <[email protected]>

Quoted 2 lines · Sergiy Kibrik

Improved default config for OMAP4 Pandaboard for faster boot:
? ? ? ?-reduced environment size to speed up memory initialization;

How much time does this save? ?I think shrinking to 2K might be a bit extreme, how about 4K?

Quoted 1 line

? ? ? ?-USB TTY driver turned off;

Not sure I agree with this. ?I think it might be useful to leave USB gadget support in, since there are those who might prefer a USB console over the serial port.

However if others disagree, I have this comment: ?If you are going to turn off the gadget, why not remove the USB driver too?

Quoted 1 line

? ? ? ?-tweaked blob load address to avoid image relocation (according to default uImage load address);

I don't think this does what you think it does! ?Unless I am horribly mistaken, the loadaddr address environment variable has nothing to do with relocation! ?It is the address typically used to store data when you do a fatload, tftp, bootp, etc.

Steve

Quoted 48 lines

---
?include/configs/omap4_panda.h | ? ?8 ++++----
?1 files changed, 4 insertions(+), 4 deletions(-)

include/configs/omap4_panda.h +0 -0
index 74defab..5aba424 100644
@@ -62,10 +62,10 @@
 

?/*
?* Size of malloc() pool
- * Total Size Environment - 256k
+ * Total Size Environment - 2k
?* Malloc - add 256k
?*/

include/configs/omap4_panda.h +1 -1
-#define CONFIG_ENV_SIZE ? ? ? ? ? ? ? ? ? ? ? ?(256 << 10)
+#define CONFIG_ENV_SIZE ? ? ? ? ? ? ? ? ? ? ? ?(256 << 4)

?#define CONFIG_SYS_MALLOC_LEN ? ? ? ? ?(CONFIG_ENV_SIZE + (256 << 10)) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?/* initial data */ ?/* Vector Base */

include/configs/omap4_panda.h +0 -0
@@ -117,7 +117,7 @@
 

?/* USB device configuration */
?#define CONFIG_USB_DEVICE ? ? ? ? ? ? ?1

include/configs/omap4_panda.h +1 -1
-#define CONFIG_USB_TTY ? ? ? ? ? ? ? ? 1
+#undef CONFIG_USB_TTY

?#define CONFIG_SYS_CONSOLE_IS_IN_ENV ? 1

?/* Flash */

include/configs/omap4_panda.h +0 -0
@@ -146,7 +146,7 @@

?#define CONFIG_ENV_OVERWRITE

?#define CONFIG_EXTRA_ENV_SETTINGS \
- ? ? ? "loadaddr=0x82000000\0" \
+ ? ? ? "loadaddr=0x80007FC0\0" \
? ? ? ?"console=ttyS2,115200n8\0" \
? ? ? ?"usbtty=cdc_acm\0" \
? ? ? ?"vram=16M\0" \
--
1.7.0.4

_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

#2 lore raw

PATCH 1/1 OMAP4: speed up booting on Pandaboard

In reply to Nishanth Menon
Quoted 5 lines · Nishanth Menon

Sergiy Kibrik wrote, on 11/04/2010 05:38 AM:

Quoted 3 lines

Improved default config for OMAP4 Pandaboard for faster boot:

    -reduced environment size to speed up memory initialization;
    -USB TTY driver turned off;

Do we really want to do this?

well, Pandaboard has serial port. It can be used instead of usbtty

Quoted 7 lines
Quoted 4 lines

-tweaked blob load address to avoid image relocation (according to
default uImage load address);

What kind of savings did we get? I am guessing we have some time x savings..

reducing ENV_SIZE saves ~0.2 s.
turning off usbtty saves ~0.2 s.
changing loadaddr saves about a second. As shown my measurements, all introduced changes save about 1.3 - 1.5 seconds.

Quoted 11 lines
Quoted 11 lines
---
  include/configs/omap4_panda.h |    8 ++++----
  1 files changed, 4 insertions(+), 4 deletions(-)
include/configs/omap4_panda.h +0 -0
index 74defab..5aba424 100644
@@ -62,10 +62,10 @@
 
Quoted 9 lines

include/configs/omap4_panda.h

Quoted 8 lines
include/configs/omap4_panda.h +2 -2
  /*
   * Size of malloc() pool
- * Total Size Environment - 256k
+ * Total Size Environment - 2k
   * Malloc - add 256k
   */
-#define CONFIG_ENV_SIZE            (256<<  10)
+#define CONFIG_ENV_SIZE            (256<<  4)

/me likes the change, but not sure how it saves boot time.

again, it's about 0.2 seconds

Quoted 6 lines
Quoted 6 lines
include/configs/omap4_panda.h +0 -0
  #define CONFIG_SYS_MALLOC_LEN        (CONFIG_ENV_SIZE + (256<<  10))
                          /* initial data */
  /* Vector Base */
@@ -117,7 +117,7 @@
 
Quoted 6 lines

include/configs/omap4_panda.h line 120

Quoted 4 lines
include/configs/omap4_panda.h +1 -1
  /* USB device configuration */
  #define CONFIG_USB_DEVICE        1
-#define CONFIG_USB_TTY            1
+#undef CONFIG_USB_TTY

do we need to have the undef? it might be better to just drop the define perhaps? what impact do we have on boot time with this change?

if someone wants to turn usbtty again, he can simply #define variable again, in case we drop the whole line it may be slightly harder to find out proper variable in the code and then #define it all over again. I just thought keeping it will clarify config in some way.

Quoted 13 lines

include/configs/omap4_panda.h line 149

Quoted 10 lines
include/configs/omap4_panda.h +1 -1
  #define CONFIG_SYS_CONSOLE_IS_IN_ENV    1
 
  /* Flash */
@@ -146,7 +146,7 @@
  #define CONFIG_ENV_OVERWRITE
 
  #define CONFIG_EXTRA_ENV_SETTINGS \
-    "loadaddr=0x82000000\0" \
+    "loadaddr=0x80007FC0\0" \

btw, Dumb question: how did we decide on this address? building from kernel.org, I see System.map @ c0004000 ==> 80004000

Quoted 5 lines

when I do make uImage,
/bin/bash /home/nmenon/Src/opensource/linux-2.6/scripts/mkuboot.sh -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n 'Linux-2.6.37-rc1-00005-gd88c092'

0x80007FC0 is kernel load address (0x80008000) minus size of u-boot header (64 bytes). So load address is exactly the same as image address inside loaded blob, and we avoid memmoving kernel to it's load address.

-regards,
Sergey

#3 lore raw

PATCH 1/1 OMAP4: speed up booting on Pandaboard

Sergiy Kibrik wrote, on 11/05/2010 08:35 AM:

Quoted 8 lines · Nishanth Menon
Quoted 5 lines

Sergiy Kibrik wrote, on 11/04/2010 05:38 AM:

Quoted 3 lines

Improved default config for OMAP4 Pandaboard for faster boot:

     -reduced environment size to speed up memory initialization;
     -USB TTY driver turned off;

Do we really want to do this?

well, Pandaboard has serial port. It can be used instead of usbtty

how about all those folks who dont have a serial cable handy instead would like to power the board + see the terminal over usb?

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

-tweaked blob load address to avoid image relocation (according to
default uImage load address);

Quoted 8 lines
Quoted 3 lines

What kind of savings did we get? I am guessing we have some time x savings..

reducing ENV_SIZE saves ~0.2 s.
turning off usbtty saves ~0.2 s.
changing loadaddr saves about a second. As shown my measurements, all introduced changes save about 1.3 - 1.5 seconds.

for what? getting to u-boot shell prompt? if so, I wonder how it does it actually happen.

Quoted 22 lines
Quoted 12 lines
Quoted 12 lines
---
   include/configs/omap4_panda.h |    8 ++++----
   1 files changed, 4 insertions(+), 4 deletions(-)
include/configs/omap4_panda.h +0 -0
index 74defab..5aba424 100644
@@ -62,10 +62,10 @@
 
Quoted 9 lines

include/configs/omap4_panda.h

Quoted 8 lines
include/configs/omap4_panda.h +2 -2
   /*
    * Size of malloc() pool
- * Total Size Environment - 256k
+ * Total Size Environment - 2k
    * Malloc - add 256k
    */
-#define CONFIG_ENV_SIZE            (256<<   10)
+#define CONFIG_ENV_SIZE            (256<<   4)

/me likes the change, but not sure how it saves boot time.

Quoted 1 line

again, it's about 0.2 seconds

surprised how changing env saves 0.2 seconds - apologies, I dont have a panda on hand at the moment to do some actual tests with the board and patch :(

Quoted 14 lines
Quoted 7 lines
Quoted 7 lines
include/configs/omap4_panda.h +0 -0
   #define CONFIG_SYS_MALLOC_LEN        (CONFIG_ENV_SIZE + (256<<   10))
                           /* initial data */
   /* Vector Base */
@@ -117,7 +117,7 @@
 
Quoted 6 lines

include/configs/omap4_panda.h line 120

Quoted 4 lines
include/configs/omap4_panda.h +1 -1
   /* USB device configuration */
   #define CONFIG_USB_DEVICE        1
-#define CONFIG_USB_TTY            1
+#undef CONFIG_USB_TTY

do we need to have the undef? it might be better to just drop the define perhaps? what impact do we have on boot time with this change?

Quoted 2 lines

if someone wants to turn usbtty again, he can simply #define variable again, in case we drop the whole line it may be slightly harder to find out

proper

Quoted 2 lines

variable in the code and then #define it all over again. I just thought keeping it will clarify config in some way.

adding a comment will help
/* enable this to get tty over usb */

Quoted 13 lines
Quoted 13 lines

include/configs/omap4_panda.h line 149

Quoted 10 lines
include/configs/omap4_panda.h +1 -1
   #define CONFIG_SYS_CONSOLE_IS_IN_ENV    1
 
   /* Flash */
@@ -146,7 +146,7 @@
   #define CONFIG_ENV_OVERWRITE
 
   #define CONFIG_EXTRA_ENV_SETTINGS \
-    "loadaddr=0x82000000\0" \
+    "loadaddr=0x80007FC0\0" \

btw, Dumb question: how did we decide on this address? building from kernel.org, I see System.map @ c0004000 ==> 80004000

Quoted 6 lines
Quoted 5 lines

when I do make uImage,
/bin/bash /home/nmenon/Src/opensource/linux-2.6/scripts/mkuboot.sh -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n 'Linux-2.6.37-rc1-00005-gd88c092'

0x80007FC0 is kernel load address (0x80008000) minus size of u-boot header (64 bytes). So load address is exactly the same as image address inside loaded blob, and we avoid memmoving kernel to it's load address.

thanks for the clarification -> it might be good for us to come up with something a bit more automated as you can, in theory run mkuboot.sh with a different address.

Signature · 2 lines
Regards,
Nishanth Menon
#4 lore raw

PATCH 1/1 OMAP4: speed up booting on Pandaboard

Quoted 11 lines · Nishanth Menon

Sergiy Kibrik wrote, on 11/05/2010 08:35 AM:

Quoted 8 lines · Nishanth Menon
Quoted 5 lines

Sergiy Kibrik wrote, on 11/04/2010 05:38 AM:

Quoted 3 lines

Improved default config for OMAP4 Pandaboard for faster boot:

     -reduced environment size to speed up memory initialization;
     -USB TTY driver turned off;

Do we really want to do this?

well, Pandaboard has serial port. It can be used instead of usbtty

how about all those folks who dont have a serial cable handy instead would like to power the board + see the terminal over usb?

you're right, it can be the reason not to touch usbtty now.

Quoted 10 lines
Quoted 10 lines
Quoted 9 lines
Quoted 6 lines

-tweaked blob load address to avoid image relocation (according to
default uImage load address);

What kind of savings did we get? I am guessing we have some time x savings..

Quoted 8 lines
Quoted 5 lines

reducing ENV_SIZE saves ~0.2 s.
turning off usbtty saves ~0.2 s.
changing loadaddr saves about a second. As shown my measurements, all introduced changes save
about 1.3 - 1.5 seconds.

for what? getting to u-boot shell prompt? if so, I wonder how it does it actually happen.

no, not getting shell, but jumping to kernel. But even in case of getting shell, why we have to wait 1 more second?

Quoted 22 lines
Quoted 22 lines
Quoted 21 lines
Quoted 11 lines
---
   include/configs/omap4_panda.h |    8 ++++----
   1 files changed, 4 insertions(+), 4 deletions(-)
include/configs/omap4_panda.h +0 -0
index 74defab..5aba424 100644

include/configs/omap4_panda.h line 68

Quoted 9 lines
include/configs/omap4_panda.h +2 -2
@@ -62,10 +62,10 @@
 
   /*
    * Size of malloc() pool
- * Total Size Environment - 256k
+ * Total Size Environment - 2k
    * Malloc - add 256k
    */
-#define CONFIG_ENV_SIZE            (256<<   10)
+#define CONFIG_ENV_SIZE            (256<<   4)

/me likes the change, but not sure how it saves boot time.

Quoted 5 lines
Quoted 1 line

again, it's about 0.2 seconds

surprised how changing env saves 0.2 seconds - apologies, I dont have a panda on hand at the moment to do some actual tests with the board and patch :(

I guess it's because of memory initializaion issues in mem_malloc_init(), and because of 256k environment it takes longer to do memset.

Quoted 19 lines
Quoted 16 lines
Quoted 9 lines
Quoted 9 lines
include/configs/omap4_panda.h +0 -0
   #define CONFIG_SYS_MALLOC_LEN        (CONFIG_ENV_SIZE + (256<<  
 10))
                           /* initial data */
   /* Vector Base */
include/configs/omap4_panda.h +0 -0
@@ -117,7 +117,7 @@
 
Quoted 6 lines

include/configs/omap4_panda.h line 120

Quoted 4 lines
include/configs/omap4_panda.h +1 -1
   /* USB device configuration */
   #define CONFIG_USB_DEVICE        1
-#define CONFIG_USB_TTY            1
+#undef CONFIG_USB_TTY

do we need to have the undef? it might be better to just drop the define perhaps? what impact do we have on boot time with this change?

Quoted 3 lines

if someone wants to turn usbtty again, he can simply #define variable again,
in case we drop the whole line it may be slightly harder to find out

Quoted 6 lines

proper

Quoted 2 lines

variable in the code and then #define it all over again. I just thought keeping it will clarify config in some way.

adding a comment will help
/* enable this to get tty over usb */

THX, I'l do that.

Quoted 18 lines
Quoted 18 lines
Quoted 18 lines

include/configs/omap4_panda.h line 149

Quoted 10 lines
include/configs/omap4_panda.h +1 -1
   #define CONFIG_SYS_CONSOLE_IS_IN_ENV    1
 
   /* Flash */
@@ -146,7 +146,7 @@
   #define CONFIG_ENV_OVERWRITE
 
   #define CONFIG_EXTRA_ENV_SETTINGS \
-    "loadaddr=0x82000000\0" \
+    "loadaddr=0x80007FC0\0" \

btw, Dumb question: how did we decide on this address? building from kernel.org, I see System.map @ c0004000 ==> 80004000

when I do make uImage,
/bin/bash /home/nmenon/Src/opensource/linux-2.6/scripts/mkuboot.sh -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n 'Linux-2.6.37-rc1-00005-gd88c092'

Quoted 8 lines
Quoted 4 lines

0x80007FC0 is kernel load address (0x80008000) minus size of u-boot header (64 bytes). So load address is exactly the same as image address inside loaded blob, and we avoid memmoving kernel to it's load address.

thanks for the clarification -> it might be good for us to come up with something a bit more automated as you can, in theory run mkuboot.sh with a different address.

in theory yes, but practically it's just a default config for default uImage target. Can you suggest a way to coordinate load addresses across kernel & bootloader build?

#5 lore raw

PATCH 1/1 OMAP4: speed up booting on Pandaboard

Sergiy Kibrik wrote, on 11/05/2010 10:44 AM:

Quoted 7 lines · Nishanth Menon
Quoted 6 lines

Sergiy Kibrik wrote, on 11/05/2010 08:35 AM:

Quoted 5 lines · Nishanth Menon
Quoted 4 lines

Sergiy Kibrik wrote, on 11/04/2010 05:38 AM:

Quoted 3 lines

Improved default config for OMAP4 Pandaboard for faster boot:

      -reduced environment size to speed up memory initialization;
      -USB TTY driver turned off;
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
Quoted 1 line

Do we really want to do this?

well, Pandaboard has serial port. It can be used instead of usbtty

how about all those folks who dont have a serial cable handy instead would like to power the board + see the terminal over usb?

you're right, it can be the reason not to touch usbtty now.

lets drop this change for the timebeing then.

Quoted 13 lines
Quoted 13 lines
Quoted 13 lines
Quoted 7 lines
Quoted 4 lines

-tweaked blob load address to avoid image relocation (according to
default uImage load address);

What kind of savings did we get? I am guessing we have some time x savings..

reducing ENV_SIZE saves ~0.2 s.
turning off usbtty saves ~0.2 s.
changing loadaddr saves about a second. As shown my measurements, all introduced changes save
about 1.3 - 1.5 seconds.

Quoted 6 lines
Quoted 3 lines

for what? getting to u-boot shell prompt? if so, I wonder how it does it actually happen.

no, not getting shell, but jumping to kernel. But even in case of getting shell, why we have to wait 1 more second?

aaah, it would be good to fix up $subject to reflect this. "speed up booting" can mean anything.

Quoted 21 lines
Quoted 21 lines
Quoted 21 lines
Quoted 20 lines
Quoted 10 lines
---
    include/configs/omap4_panda.h |    8 ++++----
    1 files changed, 4 insertions(+), 4 deletions(-)
include/configs/omap4_panda.h +0 -0
index 74defab..5aba424 100644

include/configs/omap4_panda.h line 68

Quoted 9 lines
include/configs/omap4_panda.h +2 -2
@@ -62,10 +62,10 @@
 
    /*
     * Size of malloc() pool
- * Total Size Environment - 256k
+ * Total Size Environment - 2k
     * Malloc - add 256k
     */
-#define CONFIG_ENV_SIZE            (256<<    10)
+#define CONFIG_ENV_SIZE            (256<<    4)

/me likes the change, but not sure how it saves boot time.

Quoted 9 lines
Quoted 5 lines
Quoted 1 line

again, it's about 0.2 seconds

surprised how changing env saves 0.2 seconds - apologies, I dont have a panda on hand at the moment to do some actual tests with the board and patch :(

I guess it's because of memory initializaion issues in mem_malloc_init(), and because of 256k environment it takes longer to do memset.

interesting. thanks for the explanation.

Quoted 22 lines
Quoted 22 lines
Quoted 22 lines
Quoted 13 lines

include/configs/omap4_panda.h line 149

Quoted 10 lines
include/configs/omap4_panda.h +1 -1
    #define CONFIG_SYS_CONSOLE_IS_IN_ENV    1
 
    /* Flash */
@@ -146,7 +146,7 @@
    #define CONFIG_ENV_OVERWRITE
 
    #define CONFIG_EXTRA_ENV_SETTINGS \
-    "loadaddr=0x82000000\0" \
+    "loadaddr=0x80007FC0\0" \

btw, Dumb question: how did we decide on this address? building from
kernel.org, I see System.map @ c0004000 ==> 80004000

Quoted 5 lines

when I do make uImage,
/bin/bash /home/nmenon/Src/opensource/linux-2.6/scripts/mkuboot.sh -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n 'Linux-2.6.37-rc1-00005-gd88c092'

0x80007FC0 is kernel load address (0x80008000) minus size of u-boot header (64 bytes). So load address is exactly the same as image address inside loaded blob, and we avoid memmoving kernel to it's load address.

Quoted 6 lines
Quoted 4 lines

thanks for the clarification -> it might be good for us to come up with something a bit more automated as you can, in theory run mkuboot.sh with a different address.

in theory yes, but practically it's just a default config for default uImage target.

actually there are blokes who use it that way as well. for e.g., in the old days of using BuildRoot inside TI, it just did the mkimage outside instead of just doing make uImage.

Quoted 2 lines

Can you suggest a way to coordinate load addresses across kernel& bootloader build?

Hmm.. good point -> need to try an idea I am thinking at the moment - this info is present in the memory already -> just need to think how to drag it out

Signature · 2 lines
Regards,
Nishanth Menon
#6 lore raw

PATCH 1/1 OMAP4: speed up booting on Pandaboard

Quoted 2 lines · Nishanth Menon

lets drop this change for the timebeing then.

agree =)

Quoted 7 lines
Quoted 4 lines

Can you suggest a way to coordinate load addresses across kernel& bootloader build?

Hmm.. good point -> need to try an idea I am thinking at the moment - this info is present in the memory already -> just need to think how to drag it out

I'm also quite interested in it, so will be very glad to see your suggestions.

Thanks for your comments. I'll resubmit patch with different $subject.

Signature · 2 lines
Regards,
Sergey
#9 lore raw

PATCH 1/1 OMAP4: speed up booting on Pandaboard

In reply to Sergiy Kibrik

Dear Sergiy Kibrik,

Quoted 9 lines · In message <[email protected]> you wrote:

Improved default config for OMAP4 Pandaboard for faster boot:

	-reduced environment size to speed up memory initialization;
	-USB TTY driver turned off;
	-tweaked blob load address to avoid image relocation (according to default uImage load address);
---
 include/configs/omap4_panda.h |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

...

include/configs/omap4_panda.h line 68

Quoted 6 lines

- * Total Size Environment - 256k
+ * Total Size Environment - 2k
* Malloc - add 256k
*/

include/configs/omap4_panda.h +1 -1
-#define CONFIG_ENV_SIZE			(256 << 10)
+#define CONFIG_ENV_SIZE			(256 << 4)

I think we had this discussion before. "256 << 4" makes no sense when you mean 2 KiB - it requires the reader to actually perform the calculation, which means it makes it hard for him to understand the code. Without need. Please either write 2048, which everybody can parse easily, or write "2 << 10" which can be parsed easily well.

Best regards,

Wolfgang Denk

Signature · 5 lines
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [email protected]
"If a computer can't directly address all the RAM you can  use,  it's
just a toy."         - anonymous comp.sys.amiga posting, non-sequitir
#10 lore raw

PATCH 1/1 OMAP4: speed up booting on Pandaboard

Quoted 13 lines · Wolfgang Denk

Dear Sergiy Kibrik,

Quoted 9 lines · In message <[email protected]> you wrote:

Improved default config for OMAP4 Pandaboard for faster boot:

	-reduced environment size to speed up memory initialization;
	-USB TTY driver turned off;
	-tweaked blob load address to avoid image relocation (according to default uImage load address);
---
 include/configs/omap4_panda.h |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

...

Quoted 13 lines

include/configs/omap4_panda.h line 68

Quoted 6 lines

- * Total Size Environment - 256k
+ * Total Size Environment - 2k
* Malloc - add 256k
*/

include/configs/omap4_panda.h +1 -1
-#define CONFIG_ENV_SIZE			(256 << 10)
+#define CONFIG_ENV_SIZE			(256 << 4)

I think we had this discussion before. "256 << 4" makes no sense when you mean 2 KiB - it requires the reader to actually perform the calculation, which means it makes it hard for him to understand the code. Without need. Please either write 2048, which everybody can parse easily, or write "2 << 10" which can be parsed easily well.

I've considered advices you gave me in this thread:
http://marc.info/?t=128897628400001&r=1&w=2

and resubmitted the patch
http://marc.info/?l=u-boot&m=128922349828119&w=2

Haven't you received that?

-regards,
Sergey