> On Nov 9, 2016, at 7:34 PM, Kevin Townsend <[email protected]> wrote:
> 
> This results in the following output on the shell:
> 
>   5594:Scanning I2C bus 0
>         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
>   00:          -- -- -- -- -- -- -- -- -- -- -- -- --
>   10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 1f
>   20: -- 21 -- -- -- -- -- -- -- 29 -- -- -- -- -- --
>   30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>   40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>   50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>   60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>   70: -- -- -- -- -- -- 76 --
>   Found 4 devices on I2C bus 0
> 
> My question is ... is there a way to optionally suppress the tick counter on 
> 'console_printf' calls for individual instances???
> 
> It might get in the way of formatting output with multiple printf lines. I 
> had to limit the number of times I used console_printf to avoid the tick 
> counter messing the output up.


In the first implementation of the console prompt, it did not print the tick 
counter. Subsequent versions did, and the version that ultimately was 
incorporated does. I woke up at 2am thinking about this, and thinking that an 
on/off toggle for the tick counter would be a nice thing to have, since some 
people won't care about the ticks in general.

Implementing this is pretty straight forward and could be done via a sys config 
and a shell command, like the prompt. 

dg
--
David G. Simmons
(919) 534-5099
Web <https://davidgs.com/> • Blog <https://davidgs.com/davidgs_blog> • Linkedin 
<http://linkedin.com/in/davidgsimmons> • Twitter 
<http://twitter.com/TechEvangelist1> • GitHub <http://github.com/davidgs>
/** Message digitally signed for security and authenticity.  
* If you cannot read the PGP.sig attachment, please go to 
 * http://www.gnupg.com/ <http://www.gnupg.com/> Secure your email!!!
 * Public key available at keyserver.pgp.com <http://keyserver.pgp.com/>
**/
♺ This email uses 100% recycled electrons. Don't blow it by printing!

There are only 2 hard things in computer science: Cache invalidation, naming 
things, and off-by-one errors.


Reply via email to