acassis commented on PR #16977:
URL: https://github.com/apache/nuttx/pull/16977#issuecomment-3266063832

   > @acassis @linguini1 @xiaoxiang781216 On some complex platforms, syslog 
supports multiple channel backends, which complicates the entire printing cycle.
   > 
   > <img alt="image" width="2000" height="1131" 
src="https://private-user-images.githubusercontent.com/758493/486752101-3f2e3343-4e83-406e-9929-291a324f0207.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTczMzQwOTAsIm5iZiI6MTc1NzMzMzc5MCwicGF0aCI6Ii83NTg0OTMvNDg2NzUyMTAxLTNmMmUzMzQzLTRlODMtNDA2ZS05OTI5LTI5MWEzMjRmMDIwNy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwOTA4JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDkwOFQxMjE2MzBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iYWNiNGI5NDk2MWY2NzBmZGRmMDFiM2IzN2YyZTIxY2MwYmFmMTBmNzU5ZmY5MTlmMmEwZmI0ZTE3NGE3NjJlJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.sfX4II7LL6_Eo6kH4pvqMz8c6FR1m-Na6IvAc3zntaI";>
   > But, in some extreme cases (early startup/interrupt context/crash), we may 
need a debugging method to achieve synchronous printing. Its backend only 
supports up_putc/up_nputs, which is not affected by the system environment and 
resources. I think this PR is a good choice as a starting point.
   
   @anchao so, it is better to create some LOG_ directive that avoid all the 
channels and print directly to the stdout. Please don't introduce printk(), it 
will create more confusion. I think the only option to include printk() is if 
we remove syslog() and adopt printk(), but of course, we will lose all syslog() 
flexibility.
   
   @anchao @wangchdo  BTW, this diagram is very useful, could you please 
include it to our syslog Documentation?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to