HedongGao opened a new pull request, #14713:
URL: https://github.com/apache/nuttx/pull/14713
The feature of preventing the same ID frame rotation should be done in the
lowerhalf or hardware, otherwise it may cause some problems.
## Summary
The CAN protocol stack only ensures that message is written into the
hardware in the order of application layer packets, and does not care hardware
sending order. This patch just remove this feature from CAN stack.
## Impact
*Update this section, where applicable, on how change affects users,
build process, hardware, documentation, security, compatibility, etc.*
## Testing
The application layer sends CAN messages with same can_id, constructs a
scenario where the sending queue is full, and manually adds log information to
record the frame in sending queue. Print the frame.can_id information for each
frame as follows:
sending_list has full
pending_list lentgth is :3 , and tx mailbox count is : 3
frame in tx mailbox is : 0x193, 0x193, 0x193
--
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]