Re: RFC: Stopping Zephyr networking from being painful by enabling error logging by default
On Thu, 14 Sep 2017 13:22:43 +0200
Tomasz Bursztyka <tomasz.bursztyka@...> wrote:
you discover CONFIG_NET_LOG_GLOBAL
I have been using it when porting new devices, it's an easy option toRight, I had the same idea, mentioned in the other mails.
I posted https://github.com/zephyrproject-rtos/zephyr/pull/1507 showingAs the name implies, the CONFIG_NET_LOG_GLOBAL is only forMost probably yes
how this can be tackled in a scalable way (without introducing unneeded
Kconfig interdependencies, etc.).
Besides all that, debugging net stack is complex mostly because it'sYes, and we can make it simpler.
We could probably add a documentation about how to relevantly use theExtending on what was said in the previous mails, people first want to
see stuff working (or telling them what's wrong), and then maybe
they'll dig into documentation. Seeing hangs and crashes in this age
will likely prompt "let's move on to something else" approach rather
than give encouragement to read long docs.
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog