From: Jean-Sebastien s. <js....@gm...> - 2006-01-10 18:30:15
|
Hello, Regarding the following products: - gumstix connex 200 - gumstix connex 400 - gumstix connex 400-bt I would like to know the boot time for these boards, i.e. time between power-up and launching of the user application (this time includes initializing the hardware and bootinig linux). Thank you in advance. Jean-Sebastien |
From: Darren G. <ts...@ya...> - 2006-01-11 03:12:00
|
I haven't timed it with a stopwatch, but the 200 boots for me in about 12-15 seconds. The 400 boots a little faster, but not 2x. On Jan 10, 2006, at 8:30 AM, Jean-Sebastien stoezel wrote: > Hello, > > Regarding the following products: > - gumstix connex 200 > - gumstix connex 400 > - gumstix connex 400-bt > > I would like to know the boot time for these boards, i.e. time > between power-up and launching of the user application (this time > includes initializing the hardware and bootinig linux). > > Thank you in advance. > Jean-Sebastien > |
From: Dave H. <dhy...@gm...> - 2006-01-11 07:39:15
|
Hi Jean-Sebastien, > > Regarding the following products: > > - gumstix connex 200 > > - gumstix connex 400 > > - gumstix connex 400-bt > > > > I would like to know the boot time for these boards, i.e. time > > between power-up and launching of the user application (this time > > includes initializing the hardware and bootinig linux). On 1/10/06, Darren Gibbs <ts...@ya...> wrote: > I haven't timed it with a stopwatch, but the 200 boots for me in > about 12-15 seconds. The 400 boots a little faster, but not 2x. My 400 connex xm (no bluetooth) takes 25 seconds from plugging in the power until the login prompt is presented. I ran portmon (from www.sysinternals.com - running under XP) and got the following times: Time from poweron to first display: 3 seconds Time to scan 16 Mb JFFS2: 10 seconds (4Mb would be faster) About 2 seconds to decompress the kernel About 5 seconds until module loading starts About 3 seconds more until prompt for login Total boot time from poweron: 23 seconds -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Arthur M. <ar...@ar...> - 2006-01-11 23:10:33
|
This maybe a daft idea, but is it possible to use something like suspend2 (http://www.suspend2.net/) to store an image of a freshly booted system, and simply load that on startup rather than going through the whole boot process? Would it actually be any faster? I think an ARM patch exists, but I don't know how stable it is. 23 seconds isn't a long time, but it's certainly not instant on. Arthur Dave Hylands wrote: > Hi Jean-Sebastien, > > >>>Regarding the following products: >>>- gumstix connex 200 >>>- gumstix connex 400 >>>- gumstix connex 400-bt >>> >>>I would like to know the boot time for these boards, i.e. time >>>between power-up and launching of the user application (this time >>>includes initializing the hardware and bootinig linux). > > > On 1/10/06, Darren Gibbs <ts...@ya...> wrote: > >>I haven't timed it with a stopwatch, but the 200 boots for me in >>about 12-15 seconds. The 400 boots a little faster, but not 2x. > > > My 400 connex xm (no bluetooth) takes 25 seconds from plugging in the > power until the login prompt is presented. > > I ran portmon (from www.sysinternals.com - running under XP) and got > the following times: > > Time from poweron to first display: 3 seconds > Time to scan 16 Mb JFFS2: 10 seconds (4Mb would be faster) > About 2 seconds to decompress the kernel > About 5 seconds until module loading starts > About 3 seconds more until prompt for login > > Total boot time from poweron: 23 seconds > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_idv37&alloc_id865&op=click > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Doug S. <do...@pr...> - 2006-01-11 23:37:28
|
The freshmeat page says: Changes: ARM support was added. Changelog states: Add ARM support, thanks to Hiroki Kaminaga at Sony. The suspend2 patch certainly has arm support, looking at the source. The whole thing (suspend2) is a patch. -- Doug Arthur Magill wrote: > I think an ARM patch exists |
From: Craig H. <cr...@gu...> - 2006-01-12 18:19:44
|
On Jan 10, 2006, at 11:39 PM, Dave Hylands wrote: > My 400 connex xm (no bluetooth) takes 25 seconds from plugging in the > power until the login prompt is presented. > > I ran portmon (from www.sysinternals.com - running under XP) and got > the following times: > > Time from poweron to first display: 3 seconds By "first display" do you mean when it starts the u-boot countdown? That should be practically instantaneous -- I certainly haven't ever seen a 3 second delay on any board I've booted. Then of course there'll be a delay while the timer counts down 2..1..0.. > Time to scan 16 Mb JFFS2: 10 seconds (4Mb would be faster) I think that's both scanning and loading the kernel from flash to RAM. I don't believe it's actually scanning the entirety of the JFFS2, I believe it's just traversing the directory structures to find /boot/uImage so it can load it. I haven't compared head-to-head recently, but I believe this takes about the same amount of time on the 4MB vs 16MB versions, though 10 seconds sounds high (my memory is ~4-5 seconds) -- is that a factory flash image Dave, or have you copied a uImage to the running linux system then rebooted (in which case the uImage will likely be physically somewhere else in flash, and the directory structures might need more traversing) > About 2 seconds to decompress the kernel That will be about twice as fast on the 400MHz as on the 200MHz. > About 5 seconds until module loading starts By "module load" do you mean the part where it's running /etc/init.d/ rc.modules? That's basically the start of running stuff in /etc/ init.d -- but the "modules" which are compiled in to the kernel will have already done a bunch of initialization stuff by then. > About 3 seconds more until prompt for login This could be reduced a lot by removing stuff in /etc/init.d/S* which wasn't wanted. > Total boot time from poweron: 23 seconds I'll compile a kernel with "timing for printks" turned on and post a trace of that. C |
From: Dave H. <dhy...@gm...> - 2006-01-12 19:52:09
|
HI Craig, > > Time from poweron to first display: 3 seconds > > By "first display" do you mean when it starts the u-boot countdown? > That should be practically instantaneous -- I certainly haven't ever > seen a 3 second delay on any board I've booted. Then of course > there'll be a delay while the timer counts down 2..1..0.. I think that this is an artifact of the serial program I'm using. I observe the 3 second delay. Portmon actually showed zero time. In any event, the 3 seconds is waiting for a keypress to break into uboot. > > Time to scan 16 Mb JFFS2: 10 seconds (4Mb would be faster) > > I think that's both scanning and loading the kernel from flash to > RAM. I don't believe it's actually scanning the entirety of the > JFFS2, I believe it's just traversing the directory structures to > find /boot/uImage so it can load it. I haven't compared head-to-head > recently, but I believe this takes about the same amount of time on > the 4MB vs 16MB versions, though 10 seconds sounds high (my memory is > ~4-5 seconds) -- is that a factory flash image Dave, or have you > copied a uImage to the running linux system then rebooted (in which > case the uImage will likely be physically somewhere else in flash, > and the directory structures might need more traversing) It's not a factory flash image, but I've never copied uImage into it, although I have extensively copied lots of other things. > > About 5 seconds until module loading starts > > By "module load" do you mean the part where it's running /etc/init.d/ > rc.modules? That's basically the start of running stuff in /etc/ > init.d -- but the "modules" which are compiled in to the kernel will > have already done a bunch of initialization stuff by then. Yeah - I was referring to rc.modules running. If something is compiled as a module and it hasn't been loaded yet, then no intiializations should have taken place yet. Drivers which are compiled into the kernel will certainly have done lots of stuff by then. > I'll compile a kernel with "timing for printks" turned on and post a > trace of that. Excellent. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Craig H. <cr...@gu...> - 2006-01-12 22:53:37
|
On Jan 12, 2006, at 11:51 AM, Dave Hylands wrote: >> I'll compile a kernel with "timing for printks" turned on and post a >> trace of that. I also had a shell running in the background as: (while true;do date;sleep 1;done)& Summary ------- It takes about 10 seconds including the countdown timer just to get to the point where it begins booting linux -- ie loading linux from flash to RAM, checking CRC, etc, etc. This is in a version of u-boot which uses the bootcmd: setenv stderr nulldev; setenv stdout nulldev; if mmcinit && fatload mmc 0 a2000000 gumstix-factory.script; then setenv stdout serial; setenv stderr serial; echo Found gumstix-factory script...; autoscr; else setenv stdout serial;setenv stderr serial;fsload a2000000 boot/ uImage && bootm; fi which is now the factory default. This likely wouldn't be substantially sped up by just going straight to the fsload -- mmcinit fails fast if there's no MMC card present, and the timer shows it's not spending much time before getting the "JFFS2 loading 'boot/ uImage'" bit. Once linux is in RAM, it takes about 1 second to uncompress the kernel and begin executing it. I've timed storing an uncompressed kernel in flash, but it's actually slower -- reading the compressed kernel then uncompressing is about 4x faster than reading the uncompressed kernel, since flash is such a snail. Initialize CPU and RAM takes about 0.1 seconds. Loading the rest of the kernel and initializing all the basic hardware and OS structures is another 0.5 seconds or so. Mounting the rootfs from flash takes about 2 seconds. Loading init and running it takes about 0.5 seconds, then stuff starts getting run from the inittab (like the modprobe of unix). Populating udev and starting udevd takes about 1 second. Starting all the bluetooth stuff (no bluetooth module present) takes about 4 seconds. Then another 3 seconds or so for the rest of the stuff (httpd etc) Total time: 23s for a 400xm non-bt with just-burned 2.6.14 snapshot image (modulo the printk timing info). The biggest chunk of that is getting the linux kernel into RAM in the first place. It's possible that something like XIP might be able to reduce the time somewhat here; but I suspect a bit part of the issue is the time it just takes to get the ~700kB from flash into RAM. I'll take a look at the timing params we poke into the PXA at initialization time for the flash -- it's possible we blew a calculation there somewhere and told the CPU that the flash is way slower than it actually is... C Thu Jan 12 14:32:17 PST 2006 [power plug connected here] U-Boot 1.1.2 (Sep 27 2005 - 10:41:36) *** Welcome to Gumstix *** U-Boot code: A3F00000 -> A3F23894 BSS: -> A3F58938 RAM Configuration: Bank #0: a0000000 64 MB Flash: 16 MB SMC91C1111-0 Hit any key to stop autoboot: 2 Thu Jan 12 14:32:18 PST 2006 1 Thu Jan 12 14:32:20 PST 2006 0 Thu Jan 12 14:32:21 PST 2006 ### JFFS2 loading 'boot/uImage' to 0xa2000000 Scanning JFFS2 FS: ......\ Thu Jan 12 14:32:22 PST 2006 / Thu Jan 12 14:32:23 PST 2006 done. Thu Jan 12 14:32:24 PST 2006 Thu Jan 12 14:32:25 PST 2006 Thu Jan 12 14:32:26 PST 2006 ### JFFS2 load complete: 755148 bytes loaded to 0xa2000000 ## Booting image at a2000000 ... Image Name: uImage Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 755084 Bytes = 737.4 kB Load Address: a0008000 Entry Point: a0008000 Verifying Checksum ... Thu Jan 12 14:32:27 PST 2006 OK OK Starting kernel ... Uncompressing Linux................................................... done, booting the kernel. [42949372.960000] Linux version 2.6.14gum (craig@azazel) (gcc version 3.4.4) #2 Thu Jan 12 10:21:22 PST 2006 [42949372.960000] CPU: XScale-PXA255 [69052d06] revision 6 (ARMv5TE) [42949372.960000] Machine: The Gumstix Platform [42949372.960000] Memory policy: ECC disabled, Data cache writeback [42949372.960000] Memory clock: 99.53MHz (*27) [42949372.960000] Run Mode clock: 398.13MHz (*4) [42949372.960000] Turbo Mode clock: 398.13MHz (*1.0, inactive) [42949372.960000] CPU0: D VIVT undefined 5 cache [42949372.960000] CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets [42949372.960000] CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets [42949372.960000] Built 1 zonelists [42949372.960000] Kernel command line: console=ttyS0,115200n8 root=1f01 rootfstype=jffs2 reboot=cold,hard [42949372.960000] PID hash table entries: 512 (order: 9, 8192 bytes) [42949373.040000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [42949373.050000] Inode-cache hash table entrThu Jan 12 14:32:28 PST 2006 ies: 8192 (order: 3, 32768 bytes) [42949373.070000] Memory: 64MB = 64MB total [42949373.070000] Memory: 63232KB available (1265K code, 241K data, 60K init) [42949373.300000] Mount-cache hash table entries: 512 [42949373.300000] CPU: Testing write buffer coherency: ok [42949373.310000] softlockup thread 0 started up. [42949373.320000] NET: Registered protocol family 16 [42949373.340000] JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc. [42949373.350000] Initializing Cryptographic API [42949373.350000] ttyS0 at MMIO 0x40100000 (irq = 15) is a FFUART [42949373.360000] ttyS1 at MMIO 0x40200000 (irq = 14) is a BTUART [42949373.370000] ttyS2 at MMIO 0x40700000 (irq = 13) is a STUART [42949373.370000] ttyS3 at MMIO 0x41600000 (irq = 0) is a HWUART [42949373.380000] io scheduler noop registered [42949373.390000] Probing Gumstix Flash ROM at physical address 0x00000000 (16-bit bankwidth) [42949373.400000] Gumstix Flash ROM: Found 1 x16 devices at 0x0 in 16- bit bank [42949373.410000] Intel/Sharp Extended Query Table at 0x0031 [42949373.420000] Using buffer write method [42949373.420000] cfi_cmdset_0001: Erase suspend on write enabled [42949373.430000] Using static partitions on Gumstix Flash ROM [42949373.430000] Creating 2 MTD partitions on "Gumstix Flash ROM": [42949373.440000] 0x00000000-0x00040000 : "Bootloader" [42949373.440000] 0x00040000-0x01000000 : "RootFS" [42949373.450000] NET: Registered protocol family 2 [42949373.560000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes) [42949373.560000] TCP established hash table entries: 4096 (order: 2, 16384 bytes) [42949373.570000] TCP bind hash table entries: 4096 (order: 2, 16384 bytes) [42949373.580000] TCP: Hash tables configured (established 4096 bind 4096) [42949373.590000] TCP reno registered [42949373.590000] TCP bic registered Thu Jan 12 14:32:29 PST 2006 Thu Jan 12 14:32:30 PST 2006 [42949375.630000] VFS: Mounted root (jffs2 filesystem). [42949375.640000] Freeing init memory: 60K Thu Jan 12 14:32:31 PST 2006 [42949376.360000] NET: Registered protocol family 1 Loading modules: mmc_block pxamci vfat nls_iso8859-1 nls_cp437 : Loaded. Thu Jan 12 14:32:32 PST 2006 Populating /dev using udev... done Starting udevd... done Initializing random number generator... Thu Jan 12 14:32:33 PST 2006 done. [42949378.980000] Set (GPIO,out,clear) via /proc/gpio/GPIO7 [42949379.010000] Set (GPIO,out,set) via /proc/gpio/GPIO7 Thu Jan 12 14:32:35 PST 2006 Thu Jan 12 14:32:36 PST 2006 Starting Bluetooth subsystem:[42949381.260000] Bluetooth: Core ver 2.7 [42949381.270000] NET: Registered protocol family 31 [42949381.270000] Bluetooth: HCI device and connection manager initialized [42949381.280000] Bluetooth: HCI socket layer initialized [42949381.310000] Bluetooth: HCI UART driver ver 2.1 [42949381.320000] Bluetooth: HCI H4 protocol initialized /dev/ttyS3 hcid[42949381.610000] Bluetooth: L2CAP ver 2.7 [42949381.620000] Bluetooth: L2CAP socThu Jan 12 14:32:37 PST 2006 ket layer initialized sdpd[42949381.910000] Bluetooth: RFCOMM ver 1.5 [42949381.910000] Bluetooth: RFCOMM socket layer initialized [42949381.920000] Bluetooth: RFCOMM TTY layer initialized rfcomm[42949382.130000] Bluetooth: BNEP (Ethernet Emulation) ver 1.2 [42949382.140000] Bluetooth: BNEP filters: protocol multicast pand. Starting network... udhcpc (v0.9.9-pre) started Dec 31 16:00:19 udhcpc[220]: udhcpc (v0.9.9-pre) started [42949382.660000] pxa2xx_udc: version 4-May-2005 [42949382.730000] usb0: Ethernet Gadget, version: May Day 2005 [42949382.740000] usb0: using pxa2xx_udc, OUT ep2out-bulk IN ep1in- bulk STATUS ep6in-bulk [42949382.740000] usb0: MAC 06:00:ad:41:d5:21 [42949382.750000] usb0: HOST MAC 06:00:ad:41:d5:22 [42949382.7Thu Jan 12 14:32:38 PST 2006 50000] usb0: RNDIS ready [42949382.980000] NET: Registered protocol family 17 Starting dropbear sshd: OK Starting httpd... Thu Jan 12 14:32:39 PST 2006 Welcome to the Gumstix Linux Distribution! gumstix login: Thu Jan 12 14:32:40 PST 2006 |
From: Paul S. <psc...@gm...> - 2006-01-11 22:09:57
|
Hello Jean, (I can get you a definitive answer later if you wish, but I don't have the GumStix in front of me at the moment..) > Regarding the following products: > - gumstix connex 200 > - gumstix connex 400 > - gumstix connex 400-bt > > I would like to know the boot time for these boards, i.e. time between > power-up and launching of the user application (this time includes > initializing the hardware and bootinig linux). With the Waysmall, it takes approximately 30 seconds. (This has an equivalent processor board to the connex 200.. ) I'm very interested in anything that can be done to reduct this.. Cheers, Paul |
From: Darren G. <ts...@ya...> - 2006-01-12 04:09:32
|
I got out the stopwatch and it took 14 seconds from power on until my =20= app launched on a connex 400. On Jan 11, 2006, at 2:09 PM, Paul Schulz wrote: > Hello Jean, > > (I can get you a definitive answer later if you wish, but I don't have > the GumStix in front of me at the moment..) > >> Regarding the following products: >> - gumstix connex 200 >> - gumstix connex 400 >> - gumstix connex 400-bt >> >> I would like to know the boot time for these boards, i.e. time =20 >> between >> power-up and launching of the user application (this time includes >> initializing the hardware and bootinig linux). > > With the Waysmall, it takes approximately 30 seconds. (This has an > equivalent processor board to the connex 200.. ) I'm very interested > in anything that can be done to reduct this.. > > Cheers, > Paul > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through =20 > log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD =20 > SPLUNK! > http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=3Dclick > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Craig H. <cr...@gu...> - 2006-01-13 00:00:22
|
Ok, I cleaned up the flash timings based on the docs, and now get up about 2 seconds faster (took 2 seconds out of u-boot's 10). That change is committed to the buildroot now on both the trunk and the 2.6.14 branch. C Thu Jan 12 15:53:00 PST 2006 [power applied here] U-Boot 1.1.2 (Jan 6 2006 - 12:20:18) *** Welcome to Gumstix *** U-Boot code: A3F00000 -> A3F2361C BSS: -> A3F586C0 RAM Configuration: Bank #0: a0000000 64 MB Flash: 16 MB SMC91C1111-0 Hit any key to stop autoboot: 2 Thu Jan 12 15:53:01 PST 2006 1 Thu Jan 12 15:53:02 PST 2006 0 Thu Jan 12 15:53:03 PST 2006 ### JFFS2 loading 'boot/uImage' to 0xa2000000 Scanning JFFS2 FS: ...... Thu Jan 12 15:53:04 PST 2006 done. Thu Jan 12 15:53:06 PST 2006 Thu Jan 12 15:53:07 PST 2006 ### JFFS2 load complete: 755148 bytes loaded to 0xa2000000 ## Booting image at a2000000 ... Image Name: uImage Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 755084 Bytes = 737.4 kB Load Address: a0008000 Entry Point: a0008000 Verifying Checksum ... Thu Jan 12 15:53:08 PST 2006 OK OK Starting kernel ... Uncompressing Linux................Thu Jan 12 15:53:09 PST 2006 ........ ........................... done, booting the kernel. [42949372.960000] Linux version 2.6.14gum (craig@azazel) (gcc version 3.4.4) #2 Thu Jan 12 10:21:22 PST 2006 [42949372.960000] CPU: XScale-PXA255 [69052d06] revision 6 (ARMv5TE) [42949372.960000] Machine: The Gumstix Platform [42949372.960000] Memory policy: ECC disabled, Data cache writeback [42949372.960000] Memory clock: 99.53MHz (*27) [42949372.960000] Run Mode clock: 398.13MHz (*4) [42949372.960000] Turbo Mode clock: 398.13MHz (*1.0, inactive) [42949372.960000] CPU0: D VIVT undefined 5 cache [42949372.960000] CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets [42949372.960000] CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets [42949372.960000] Built 1 zonelists [42949372.960000] Kernel command line: console=ttyS0,115200n8 root=1f01 rootfstype=jffs2 reboot=cold,hard [42949372.960000] PID hash table entries: 512 (order: 9, 8192 bytes) [42949373.040000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [42949373.050000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [42949373.070000] Memory: 64MB = 64MB total [42949373.070000] Memory: 63232KB available (1265K code, 241K data, 60K init) [42949373.300000] Mount-cache hash table entries: 512 [42949373.300000] CPU: Testing write buffer coherency: ok [42949373.310000] softlockup thread 0 started up. [42949373.320000] NET: Registered protocol family 16 [42949373.340000] JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc. [42949373.350000] Initializing Cryptographic API [42949373.350000] ttyS0 at MMIO 0x40100000 (irq = 15) is a FFUART [42949373.360000] ttyS1 at MMIO 0x40200000 (irq = 14) is a BTUART [42949373.370000] ttyS2 at MMIO 0x40700000 (irq = 13) is a STUART [42949373.370000] ttyS3 at MMIO 0x41600000 (irq = 0) is a HWUART [42949373.380000] io scheduler noop registered [42949373.390000] Probing Gumstix Flash ROM at physical address 0x00000000 (16-bit bankwidth) [42949373.400000] Gumstix Flash ROM: Found 1 x16 devices at 0x0 in 16- bit bank [42949373.410000] Intel/Sharp Extended Query Table at 0x0031 [42949373.420000] Using buffer write method [42949373.420000] cfi_cmdset_0001: Erase suspend on write enabled [42949373.430000] Using static partitions on Gumstix Flash ROM [42949373.430000] Creating 2 MTD partitions on "Gumstix Flash ROM": [42949373.440000] 0x00000000-0x00040000 : "Bootloader" [42949373.440000] 0x00040000-0x00400000 : "RootFS" [42949373.450000] NET: Registered protocol family 2 [42949373.560000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes) [42949373.560000] TCP established hash table entries: 4096 (order: 2, 16384 bytes) [42949373.570000] TCP bind hash table entries: 4096 (order: 2, 16384 bytes) [42949373.580000] TCP: Hash tables configured (established 4096 bind 4096) [42949373.590000] TCP reno registered [42949373.590000] TCP bic registered Thu Jan 12 15:53:10 PST 2006 [42949373.750000] VFS: Mounted root (jffs2 filesystem). [42949373.760000] Freeing init memory: 60K [42949374.460000] NET: Registered protocol family 1 Thu Jan 12 15:53:11 PST 2006 Loading modules: mmc_block pxamci vfat nls_iso8859-1 nls_cp437 : Loaded. Populating /dev using udev... Thu Jan 12 15:53:12 PST 2006 done Starting udevd... done Initializing random number generator... done. Thu Jan 12 15:53:13 PST 2006 [42949377.070000] Set (GPIO,out,clear) via /proc/gpio/GPIO7 [42949377.100000] Set (GPIO,out,set) via /proc/gpio/GPIO7 Thu Jan 12 15:53:14 PST 2006 Thu Jan 12 15:53:15 PST 2006 Starting Bluetooth subsystem:[42949379.340000] Bluetooth: Core ver 2.7 [42949379.350000] NET: Registered protocol family 31 [42949379.350000] Bluetooth: HCI device and connection manager initialized [42949379.360000] Bluetooth: HCI socket layer initialized [42949379.390000] Bluetooth: HCI UART driver ver 2.1 [42949379.400000] Bluetooth: HCI H4 protocol initialized /dev/ttyS3 hcid[42949379.690000] Bluetooth: L2CAP ver 2.7 [42949379.700000] Bluetooth: L2CAP socket layer initialized sdpd rfcommThu Jan 12 15:53:16 PST 2006 [42949380.030000] Bluetooth: RFCOMM ver 1.5 [42949380.040000] Bluetooth: RFCOMM socket layer initialized [42949380.040000] Bluetooth: RFCOMM TTY layer initialized [42949380.200000] Bluetooth: BNEP (Ethernet Emulation) ver 1.2 [42949380.210000] Bluetooth: BNEP filters: protocol multicast pand. Starting network... udhcpc (v0.9.9-pre) started Dec 31 16:00:15 udhcpc[220]: udhcpc (v0.9.9-pre) started [42949380.730000] pxa2xx_udc: version 4-May-2005 [42949380.800000] usb0: Ethernet Gadget, version: May Day 2005 [42949380.810000] usb0: using pxa2xx_udc, OUT ep2out-bulk IN ep1in- bulk STATUS ep6in-bulk [42949380.820000] usb0: MAC 02:00:f5:41:ec:a1 [42949380.820000] usb0: HOST MAC 02:00:f5:41:ec:a2 [42949380.820000] usb0: RNDIS ready Thu Jan 12 15:53:17 PST 2006 [42949381.050000] NET: Registered protocol family 17 Starting dropbear sshd: OK Starting httpd... Thu Jan 12 15:53:18 PST 2006 Welcome to the Gumstix Linux Distribution! gumstix login: Thu Jan 12 15:53:19 PST 2006 |
From: Paul S. <psc...@gm...> - 2006-01-13 00:30:22
Attachments:
boot-timing.pl
|
Greetings, For those that might find it useful.. please find attached a short perl script that I use to time output from ttyS0.. It just listens to ttyS0, and reports the time difference between consecutive lines. Comments welcome. Cheers Paul On 1/13/06, Craig Hughes <cr...@gu...> wrote: > Ok, I cleaned up the flash timings based on the docs, and now get up > about 2 seconds faster (took 2 seconds out of u-boot's 10). That > change is committed to the buildroot now on both the trunk and the > 2.6.14 branch. > > C > |
From: Craig H. <cr...@gu...> - 2006-01-13 00:15:29
|
Doing some basic timing tests once in linux, it actually looks like I might have just sped up flash reads by about 2x in linux -- at least, doing date;dd if=/dev/mtdblock1 of=/dev/null;date gives 4 seconds with the old u-boot, 2 seconds with the new u-boot for 4MB flash. I think I killed the u-boot on my XM gumstix here so I won't be able to time that with the new u-boot under linux until I JTAG it. C On Jan 12, 2006, at 3:59 PM, Craig Hughes wrote: > Ok, I cleaned up the flash timings based on the docs, and now get > up about 2 seconds faster (took 2 seconds out of u-boot's 10). > That change is committed to the buildroot now on both the trunk and > the 2.6.14 branch. |
From: Dave H. <dhy...@gm...> - 2006-01-13 00:44:12
|
Hi Craig, On 1/12/06, Craig Hughes <cr...@gu...> wrote: > Doing some basic timing tests once in linux, it actually looks like I > might have just sped up flash reads by about 2x in linux -- at least, > doing > > date;dd if=3D/dev/mtdblock1 of=3D/dev/null;date > > gives 4 seconds with the old u-boot, 2 seconds with the new u-boot > for 4MB flash. I think I killed the u-boot on my XM gumstix here so > I won't be able to time that with the new u-boot under linux until I > JTAG it. I'll bet that u-boot isn't turning on the cache, which is why it isn't seeing as significant an improvement. I was able to "steal" the kernel code so I could run some standalone tests and measure the performance both with and without caching enabled (on my ARM9). -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |