# HG changeset patch # User Mychaela Falconia # Date 1584262805 0 # Node ID c6a79ac125acbdb3d41e93403df4661d16fa3ee5 # Parent f888ae294b1bbfd4d3c838691efe9e387c01d314 fluid-mnf: rm Performance, incorporated into README diff -r f888ae294b1b -r c6a79ac125ac fluid-mnf/Performance --- a/fluid-mnf/Performance Sun Mar 15 08:59:12 2020 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,19 +0,0 @@ -Even though it cannot be a replacement for fc-loadtool in most use cases, FLUID -is very aggressively optimized for speed in ways that would be hard to match in -our fc-loadtool architecture. Therefore, on those targets which are supported -by both FLUID and fc-loadtool, flash programming with FLUID is faster. Here -are the performance numbers, flashing an Openmoko GTA02 modem with firmware -version moko-new-fw-20190128, going through the external headset jack, -UberWaves CP2102 Professional cable: - -fluid-mnf at 115200 baud: 2m28s -fc-loadtool at 115200 baud: 4m02s -fluid-mnf at 812500 baud: 0m40s -fc-loadtool at 812500 baud: 1m12s - -With both tools the m0 version of the firmware image (fwimage.m0) was being -flashed; in the case of fc-loadtool the new flash e-program-m0 command was used. -The version of fc-loadtool used for this test is the one that is about to be -released with fc-host-tools-r13; previous versions would be even slower. In -the case of fluid-mnf the -C option was used to disable delta downloads, making -the test operation independent of previous flash state.