Hi Pacca
Well, looking through tc-config and the RPi Zero specs nothing jumps out at me. So now you have to ask yourself the following:
"How badly do i want to try to eliminate that 1 second delay?"
Before answering, consider the following:
1. There might be something inherent in the Zero and the delay can't be eliminated.
2. It might be something in the kernel, in which case it likely would be difficult to track down.
3. It is something in tc-config, and would require adding some debug code to track down.
4. It could be something entirely different that I haven't thought of.
Only item 3 looks like you might be able to do something about. It would require extracting the tc-config file from the piCore image
file. You then need to find the line that says:
modprobe -q squashfs 2>/dev/null
You can now add code that writes markers to the log files so you can see execution time of sections of tc-config, something like:
echo "***** TC 1 *****" >> /dev/kmsg
So you would add the code like this:
modprobe -q squashfs 2>/dev/null
echo "***** TC 1 *****" >> /dev/kmsg
# Original tc-config code
echo "***** TC 2 *****" >> /dev/kmsg
# Original tc-config code
echo "***** TC 3 *****" >> /dev/kmsg
# Original tc-config code
You would then need to repack the image file. I don't know how to unpack/repack ARM images, so someone else will need to
answer that.
The logs will then have markers with whatever text you echoed into /dev/kmsg.
Welcome
FAQ
Downloads
Wiki
