Hello,
> And, FWIW, when I said "they ignorantly use usleep" I was referring to
> the lack of any comments indicating awareness that usleep() could take
> as long as 10,000 microseconds to return. As a long time maintenance
> programmer, that's the kind of code that makes one wonder how the
> hardware really works, and if the author understood the functions being
> used.
Seeing as though the 10ms delay is not hardware specific, but rather
kernel specific I didn't add any comments. In my opinion comments
explaining how the Linux scheduler works don't belong in the ts7800ctl
utility source code. If I would have added a comment stating each sleep
may sleep for as long as 10ms, the comment would have been misleading.
As the comment would have made the assumption the kernel tick rate was
set to 100Hz.
> And generally is a very deliberate choice of words, because,
> at least on our board, ts7800ctl doesn't work 100% of the time.
> Sometimes it gets (and doesn't handle, but that's expected in a demo, I
> guess) errors selecting, reading or writing. And a couple times it just
> kinda hung until we killedi it.
Interesting, this is the first report I've heard of such a failure. Can
you provide more information on how to reproduce this problem?
--
Best Regards,
________________________________________________________________
Eddie Dawydiuk, Technologic Systems | voice: (480) 837-5200
16610 East Laser Drive Suite 10 | fax: (480) 837-5300
Fountain Hills, AZ 85268 | web: www.embeddedARM.com
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|