gregory-nutt commented on issue #11321:
URL: https://github.com/apache/nuttx/issues/11321#issuecomment-2599716717
> Is there anything more to do ?
I think a proper solution would be the complete remove of the archi-init
logic, not just disabling it. I think that would cause a lot of
raiden00pl commented on issue #11321:
URL: https://github.com/apache/nuttx/issues/11321#issuecomment-2599599965
Yes, it seems like a lot of work. But it will only get worse over time as
new boards come in.
We can automate most of the work. What we need to do is:
1. remove all `
gregory-nutt commented on issue #11321:
URL: https://github.com/apache/nuttx/issues/11321#issuecomment-2573610507
> NSH_ARCHINIT can be achieved in board initializiton code, so it could be
removed to avoid the confusion.
Agreed. But removing CONFIG_NSH_ARCHINIT will be a very big job
xiaoxiang781216 commented on issue #11321:
URL: https://github.com/apache/nuttx/issues/11321#issuecomment-2572806394
NSH_ARCHINIT can be achieved in board initializiton code, so it could be
removed to avoid the confusion.
--
This is an automated message from the Apache Git Service.
To res
raiden00pl commented on issue #11321:
URL: https://github.com/apache/nuttx/issues/11321#issuecomment-2572573053
hi, are we trying to solve this problem? Does anyone have any objections to
removing `CONFIG_NSH_ARCHINIT` ?
This option is slowly starting to cause problems in the case of PCI
raiden00pl commented on issue #11321:
URL: https://github.com/apache/nuttx/issues/11321#issuecomment-1845240121
+1 from me
--
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.
T
xiaoxiang781216 commented on issue #11321:
URL: https://github.com/apache/nuttx/issues/11321#issuecomment-1839862069
Yes, I think the suggestion is reasonable.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL ab
