Quote:
Originally Posted by hawhill
Really nice demos. On my K3, 50% of the CPU time is spent in the Kernel (according to unreliable "top"). Probably, the eink driver could be a bit more optimized...
Code:
[root@kindle us]# time ./cosmegg
real 3m 56.15s
user 2m 9.67s
sys 1m 46.24s
The Moiré effects in the Cosmegg demo are nice :-) |
Now that ixtab has a K3 kernel with kexec, we can fix that kernel eink optimization issue.
EDIT: What goes on the display is just the same old boring stuff I have been doing since the "big iron" mainframe days of printing these on fan-fold line-printer paper and hanging them around my office. I do similar algorithms with SOUND too, by connecting an output bit to a speaker. People say the sounds are "hypnotic". I had a large collection of totally different but very interesting sound algorithms back in the day, and I could re-create most of them pretty easily. This stuff works the same for sound and light. On the K4(mini), I could PWM the power LED, and a photocell connected to amplified speakers would do the trick.
What I want to know is your opinion of the "re-usability factor" of my code. Is it simple enough for beginning programmers? Is it small enough to not scare people away (i.e. "above the fold")? There are no modules to link, no header files to worry about. Just "arm-linux-gcc -o demo demo.c" and you are good to go. I try to follow the "Make it work, then make it small, then make it fast" philosophy. What is your opinion about my SOURCE CODE? Do you like these C proggies better than my /bin/sh scripts? 
