ChanServ changed the topic of #linux-sunxi to: Allwinner/sunxi development - Did you try looking at our wiki? https://linux-sunxi.org - Don't ask to ask. Just ask and wait for an answer! - This channel is logged at https://oftc.irclog.whitequark.org/linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
grming has quit [Quit: Konversation terminated!]
chuangzhu has quit [Ping timeout: 480 seconds]
chuangzhu has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
chuangzhu has quit [Ping timeout: 480 seconds]
chuangzhu has joined #linux-sunxi
chuangzhu has quit [Ping timeout: 480 seconds]
chuangzhu has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
arti_ has quit [Remote host closed the connection]
arti has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
apritzel has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
arti has quit [Quit: arti]
arti has joined #linux-sunxi
arti has quit [Quit: arti]
arti has joined #linux-sunxi
apritzel has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
cnxsoft1 has joined #linux-sunxi
cnxsoft has quit [Read error: Connection reset by peer]
apritzel has joined #linux-sunxi
indy has quit []
indy has joined #linux-sunxi
JohnDoe_71Rus has quit []
<karlp> does anyone know where the "USB DFU Speed" numbers came from here? https://linux-sunxi.org/FEL/USBBoot (from the table with soc support status)
<karlp> even using a ram backend, I'm capping out at ~1.3MB/sec which seems to be goverend byt he 4k limit on control transfers.
<karlp> I've instrumented dfu-util and there' no bwPollTimeout sleeps, so it seems to be at the protocol limit?
<gamiee> karlp: afaik the u-boot doesn't use DMA, so it is slower. The benchmarks were probably. Made on BSP?
<karlp> I suspect more likely that they were made on mac, that doesn't have the windows/linux 4k control transfer limit...
<karlp> bleh, if I disable "CONFIG_ENV_IS_IN_FAT" because I want it in mmc only, uboot doesn't boot. with it, it complains about unable to use fat on mmc block..
cnxsoft1 has quit []
cnxsoft has joined #linux-sunxi
cnxsoft has quit []
aggi_ has joined #linux-sunxi
aggi has quit [Ping timeout: 480 seconds]
aggi_ is now known as aggi
JohnDoe_71Rus has joined #linux-sunxi
rajkosto has joined #linux-sunxi
<apritzel> karlp: are you doing this on latest mainline? We fixed some issues about environment priority lately ...
<apritzel> and I am pretty sure I tested a raw MMC environment at some point in the past
<karlp> this is 22.07, 22.10 hadn't come out yet,
<apritzel> and you did enable CONFIG_ENV_IS_IN_MMC, and disabled CONFIG_ENV_IS_IN_FAT?
<karlp> if I have _only_ _IS_IN_MMC, it doesn't boot, if I have both, it boots, and saves in mmc.
<apritzel> IIRC the algorithm is to save where it loaded from, so that sounds about right
<apritzel> (and if possible: please ignore release tags, and just use the latest master)
<karlp> well, I'm trying to do "initial" programming, so can't it just do the "no env found, using default" instead of just freezing?
<apritzel> it should, but this whole priority thing is surprisingly tricky
<karlp> I don't doubt it. I've been spinning wheels in circles on this sort of thing all week.
<apritzel> it took somewhat like three fixes to get it right ;-)
<karlp> trying to ignore some of the desires to understand things properly and just get on with what I need to be doing...
grming has joined #linux-sunxi
<apritzel> and the generic U-Boot environment code is somewhat nasty, and silently hangs if the wrong environment source is returned
<apritzel> if you can live with the FAT warning, I recommend you just leave that in, for now, and I have a look at it later
<karlp> yeah, I'm living with it right now, it goes away the first time I do a save env..
<apritzel> or you try latest master (maybe 2022.10)
<karlp> if you want to poke something fun, "ums 0 mmc 1.1" then ctrl-c then "ums 0 mmc 1" (or any thjing where you try and reexpose UMS) asserts.
<karlp> I'm not even sure why the assert is there, all the callers _appear_ to handle the bool, but, that's another thing I can just work with right now, it reboots, and I re-issue the UMS command and move on.
<apritzel> it says "for all defconfigs ..."
<apritzel> I guess it's time to fix this properly, in the generic code ...
<apritzel> karlp: although I am wondering why you get there in the first place. You should exit above, with "return ENVL_MMC;"
<karlp> I dunno man, I can look at that again on monday and tryu just those steps for you, but I'm trying to get a couple of steps forward to finish the week right now.
<apritzel> karlp: are you booting from FEL, by any chance?
<karlp> yes,
<karlp> oh huh, boot dev != mmc then :)
<apritzel> yeah, that would explain it
<karlp> so if I could flash it directly, without fel, then it woudl work, but I can't get it flashed without running it via fel first.
<apritzel> we hoped we had fixed that issue, by always returning a valid source, but that assumes that you have either FAT, UBI or NOWHERE compiled in
<apritzel> and you have neither
<karlp> I mean, I only tried turning off FAT to try and make the warnings go away, it looked sus, and I don't have a fat partition I want it in anyway,
<apritzel> karlp: thanks for the report, I will have a look later
<karlp> you're very welcome :)
grming has quit [Quit: Konversation terminated!]
apritzel has quit [Ping timeout: 480 seconds]
swiftgeek has quit [Ping timeout: 480 seconds]
apritzel has joined #linux-sunxi
JohnDoe_71Rus has quit []
apritzel has quit [Ping timeout: 480 seconds]
apritzel has joined #linux-sunxi
swiftgeek has joined #linux-sunxi
vagrantc has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
grming has joined #linux-sunxi
<apritzel> karlp: So I can reproduce your problem: when I remove ENV_IS_IN_FAT, and enable ENV_IS_IN_MMC, it hangs when doing FEL booting.
<apritzel> karlp: if you want a quick hack, just add "if (IS_ENABLED(CONFIG_ENV_IS_IN_MMC)) return ENVL_MMC;" to that "if (prio == 0) .... " statement at the end of env_get_location()
<apritzel> meanwhile it's env_init() that needs to be fixed, but that is used by other platforms as well, and even outside of init_sequence_f[], so it's a bit dangerous to change that ...