Should rtems_error() use fprintf()?

2016-03-20 Thread Joel Sherrill
Hi I know this is a very old piece of code and predates printk() but should this routine be changed to use printk()? Is it still safe? Especially in light of SMP demands. --joel ___ devel mailing list devel@rtems.org

Re: Should rtems_error() use fprintf()?

2016-03-19 Thread Chris Johns
On 17/03/2016 06:41, Peter Dufault wrote: I’m answering only by looking at this email and not hunting through the source. But if “rtems_error()” can easily be replaced by either "fprintf(stderr, …)" or "printk()" then deprecate it with that recommendation. I’ve often had spirited discussions

Re: Should rtems_error() use fprintf()?

2016-03-19 Thread Peter Dufault
I’m answering only by looking at this email and not hunting through the source. But if “rtems_error()” can easily be replaced by either "fprintf(stderr, …)" or "printk()" then deprecate it with that recommendation. I’ve often had spirited discussions with clients because I think