Fix-Point commented on PR #17556: URL: https://github.com/apache/nuttx/pull/17556#issuecomment-3670206013
> Guys, instead of compete to see who implemented first or which implementation has best performance, it is better to work together to get best part of each implementation and contribute a better solution to NuttX. > > This features is very important to everyone using NuttX (not only LiAuto or Xiaomi). > > @Fix-Point and @anchao please align between you both how to integrate it in a way that the best interest is the project quality, not individual ego. I agree. The main problem is that NuttX should consider all application scenarios, including IoT devices, automotive devices, and multi-core embedded devices. But, @wangchdo only considered his `tc397` board in his design, adding so many ugly workarounds to NuttX kernel just to fix the Tricore timer driver issues. I believe such code and implementation should be removed later. For the HRtimer, I believe my implementation is better in performance, composability and general. So I insist this hrtimer is a better implementation, not just "a optimization for their hrtimer". I suggest they added optimization on this implementation, that's my opinion. -- 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]
