anchao commented on issue #17282: URL: https://github.com/apache/nuttx/issues/17282#issuecomment-3495225227
> > > > There is `syslogd` for syslog over the network. Not sure how it's different from netdev though. > > > > > > > > > it's different path: > > > > > > * syslog->ramlog->syslogd->netdev > > > * syslog->netdev > > > > > > The major difference is that the second path could output panic log, and run much fast with smaller overhead than first which is important for note trace. > > > > > > how can we ensure that the netdev/wifi driver should work as expected during exception interruptions in second path? > > wifi driver need adjust to work in the interrupt context before enabling this functionality. This work item will ensure the framework and several select netdev drivers work under the interrupt context. This places high demands on the quality of the driver. I'm wondering if it's possible to return to the thread from the exception context and treat the exception context as a thread suicide. -- 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]
