cederom commented on PR #15304: URL: https://github.com/apache/nuttx/pull/15304#issuecomment-2571486061
> > @cederom: I would suggest renaming `debug_info` target to `sysinfo` or `dump_sysinfo` or `sysinfo_dump` (or similar) because we operate on **sysinfo** (i.e. `sysinfo.h` / `tools/parse_sysinfo.py` / `tools/host_sysinfo.py`) not really anything **debug** related (in terms of On-Chip-Debug) right? > > @patacongo: sysinfo() would collide with a Linux API of that name: https://man7.org/linux/man-pages/man2/sysinfo.2.html If it is not compatible that this might lead to naming issues in the future. Thank you Greg! Good catch :-) Maybe something like this? * `tools/nxdiag/host_info_dump.py`. * `tools/nxdiag/host_info_parse.py`. * `tools/nxdiag/target_info_dump.py`. * `tools/nxdiag/target_info_parse.py`. My main concern was not to use **debug** term for **system information** as we may use it for the real debug stuff (in terms of On-Chip-Debug) one day. Its common nowadays to misuse "debug" for "logging" etc. I know the system information will be used to debug a problem, but debug has precise specific meaning (i.e. control CPU registers and program execution, control memory, access bus peripherals, etc). Also "system information" is a bit misleading because it does not clearly state if it is about host or target information :-P -- 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: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
