You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 17, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on Jan 17, 2019. It is now read-only.
The old rmbox printed handy timestamps with seconds as measure unit. It was easy to see e.g. how long the copy() operation for a component took in microseconds and convert that to a (coarse) MCPS value. The new logger shows timestamp only as a counter value. Could this be changed back to time?
It also would help a lot to compare side by side kernel dmesg and firmware logs.
@singalsu@mengdonglin
Feature was implemented during unification of rmbox and logger tools: #88 merged 3 days ago.
-c parameter allows to specify clock rate, with default 19.2, similarly as rmbox did.
That sounds excellent, I'll test it and close this. I'm anyways using a script due to more command line parameters required for typical usage so it's easy to add the -c for clock rate there.
@akloniex Could you help to submit a PR for a README, as a user guide for the new logger?
Or could you guide us to the document if it's ready there? Thanks
@singalsu, does it work on your side? If yes, please close this issue. @akloniex I created a new issue #102 for the document, could you help on that? Thanks!
@akloniex OK, now when I use executable /usr/local/bin/logger it works and shows with -c 19.2 the time as expected.
However why was the name changed back to logger? I have also on my computer /usr/bin/logger from Ubuntu package bsdutils for totally different purpose. I'll close this anyway since the executable name is another discussion.
Activity
akloniex commentedon Oct 11, 2018
@singalsu @mengdonglin
Feature was implemented during unification of rmbox and logger tools: #88 merged 3 days ago.
-c parameter allows to specify clock rate, with default 19.2, similarly as rmbox did.
Please check current version.
singalsu commentedon Oct 11, 2018
That sounds excellent, I'll test it and close this. I'm anyways using a script due to more command line parameters required for typical usage so it's easy to add the -c for clock rate there.
mengdonglin commentedon Oct 11, 2018
@akloniex Could you help to submit a PR for a README, as a user guide for the new logger?
Or could you guide us to the document if it's ready there? Thanks
cujomalainey commentedon Oct 11, 2018
Please make sure this documentation is available publically.
mengdonglin commentedon Oct 12, 2018
@singalsu, does it work on your side? If yes, please close this issue.
@akloniex I created a new issue #102 for the document, could you help on that? Thanks!
singalsu commentedon Oct 12, 2018
@akloniex OK, now when I use executable /usr/local/bin/logger it works and shows with -c 19.2 the time as expected.
However why was the name changed back to logger? I have also on my computer /usr/bin/logger from Ubuntu package bsdutils for totally different purpose. I'll close this anyway since the executable name is another discussion.
singalsu commentedon Oct 12, 2018
Closing
mengdonglin commentedon Oct 14, 2018
@singalsu I saw PR #105 is renaming the new logger name from logger to sof_logger.