<wpwrak>
wolfspraul: quick check: all the M1rc3 shipped have the standby and rescue partitions locked, correct ?
<wolfspraul>
yes
<wolfspraul>
absolutely 100%
<wolfspraul>
yours is probably the only one that went out without locking
<wpwrak>
heh, as it should ;-)
<wpwrak>
and a question regarding shutdown: is "Shutdown > Power off" in the GUI the same as pressing and holding the middle button ? or are those two different mechanisms ?
<sb0>
the same
<wpwrak>
kewl, thanks
<kristianpaul>
mwalle: your uclibc for lm32 also support standalone programs, like let said milkymist bios? :)
<wpwrak>
phew. writing this kind of reports eats time like there's no tomorrow
<sb0>
wpwrak, nice report, thanks!
<sb0>
maybe it's a scheduler software bug that caused the corruption...?
<sb0>
did your reductions in cycle time include the scheduler replacement?
<wpwrak>
no, all that was before the scheduler change
<wpwrak>
the scheduler change was the reason why i didn't let the 4000+ cycles test to its bitter end. just didn't have the patience ;-)
<wpwrak>
with the scheduler change, the camera detection, and if we can get rid of the DHCP wait, the cycles could be much shorter. so this will help with getting more and better data
<sb0>
the camera detection?
<wpwrak>
the skipping of patches that use the camera if there is no signal
<sb0>
how is that related to boot time?
<wpwrak>
it affects the time to the first patch that actually does something i can see ;-)
<sb0>
you can reconfigure FN to skip DHCP and start with only one patch
<sb0>
just create a performance file with just the first patch, then go in system settings and select it for autostart
<sb0>
and disable dhcp in the network config also there
<wpwrak>
hmm, and where is this stored ? i'm a bit worried about things not surviving NOR corruption or restoration
<sb0>
in yaffs
<wpwrak>
okay, that's at the far end. might be safe :)
<wpwrak>
btw, as i understand things, flickernoise.git master is current unusable because of the FN/RTEMS hang. is this correct ?
<sb0>
as long as you stay in render mode it seems to work
<sb0>
but exiting it triggers the debilitating lag bug
<wpwrak>
aah. okay. i might *just* dodge it :)
<wpwrak>
any plans about fixing it ? or is xiangfu taking care of it ?
<sb0>
no, no plans yet
<sb0>
but should be
<sb0>
maybe when I have stopped traveling every second week or so, let's say around october 16
<wpwrak>
hehe. yes, the great M1 world tour ;-)
<wpwrak>
with grenoble as the big finale, no ?
<sb0>
nah, I'm going to Berne after that
<sb0>
I'll also have a round of measurements/characterization/testing to do on the TDC core when I'm back, so the lag bug will have to wait a bit