On Sunday 08 November 2009, Freddie Chopin wrote:
> David Brownell pisze:
> > How about a utility to display KByte/second rates,
> > down to say one decimal point?
>
> IMHO 3 decimal poinst would do best (3 decimals ~ bytes per second)
Rates vary more in those low digits, which is why I
suggested
On Sun, 2009-11-08 at 19:38 -0700, David Brownell wrote:
> On Sunday 08 November 2009, Zachary T Welch wrote:
> > This patch changes the duration_* API in several ways. First, it
> > updates the API to use better names. Second, string formatting has
> > been removed from the API (with its associa
David Brownell pisze:
> How about a utility to display KByte/second rates,
> down to say one decimal point?
IMHO 3 decimal poinst would do best (3 decimals ~ bytes per second)
4\/3!!
___
Openocd-development mailing list
Openocd-development@lists.berlios
On Sunday 08 November 2009, Zachary T Welch wrote:
> This patch changes the duration_* API in several ways. First, it
> updates the API to use better names. Second, string formatting has
> been removed from the API (with its associated malloc). Finally, a
> new function added to convert the time
This patch changes the duration_* API in several ways. First, it
updates the API to use better names. Second, string formatting has
been removed from the API (with its associated malloc). Finally, a
new function added to convert the time into seconds, which can be
used (or formatted) by the cal
