So the existing printf library is broken in the sense that if it is in the process of flushing packets out the serial line it will fail all printf commands that are called on it. I have an alternate implementation that doesn't do this, but hasn't made its way into the repository yet because the interfaces it provides are somewhat different than the existing ones and would break existing code. The only 'real' reason it hasn't made it in yet is because I don't want to just throw it in there without any documentation as to how its different than the existing library -- I don't want people's existing code to break without at least some documentation on how to fix it.
The new implementation is much better though, and will make its way in once I have time to write up the documentation. For now you can grab it from here though if you want. http://sing.stanford.edu/klueska/printf_test.tar.gz Kevin On Fri, Apr 11, 2008 at 8:19 AM, Nitin Sharma <[EMAIL PROTECTED]> wrote: > I was just wondering how you guys manage flow control for testbeds connected > to a logging PC using a USB hub or something. > > I am currently using Xubuntos for the PC. The Hub seems to wear more i use > it, and the behavior of the logged packets using Serial Logging like Printf > library seems to be giving not-so-good responses. > > Any advices/suggestions to improve USB performances? > > Thanks. > > -- > Nitin Sharma > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > -- ~Kevin _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
