Hi Alex!
Thanks for the reply. I've been wondering that, since the was no new soc_id
or special code to handle the R8 in sunxi-fel. I've added the R8 to the wiki
page accordingly.
Regards, B. Nortmann
Am 16.11.2015 um 23:26 schrieb Alexander Kaplan:
Hi Bernhard,
I observe roughly ~500 KB/s
Hello Alex!
Good catch, the AW_FEL_VERSION request caused by progress_chunk_size()
might in fact arrive in an untimely manner there.
Basically we'd have to make sure we retrieve the aw_fel_get_sram_info()
beforehand. I'm not sure there would be a more useful place for that
even earlier,
I have prepared an alternative version (v4) of this patch, and will
attach it below. (github is also updated, so you may retrieve the
patches from https://github.com/linux-sunxi/sunxi-tools/pull/35
alternatively)
progress_chunk_size() was renamed to get_chunk_size(), als I think that
makes
Hi Bernhard,
I observe roughly ~500 KB/s on the R8.
As the R8 is really similar to the A13 (and is also handled as an A13) by
the fel tool, I'm not sure weather it makes sense to update
https://linux-sunxi.org/FEL/USBBoot#SoC_support_status.
However, I'm happy to do so if you consider it useful.
Hi Bernhard,
great work! I like especially the --xgauge in combination with multiwrite.
However, I have been testing with an Allwinner R8, and there is a
problem with the lazy initialization of the progress chunk size:
In aw_write_buffer() a AW_FEL_1_WRITE request is sent before the
