Determine if generic_task_ctx_t in generic_resp_hdr_t is needed, or if it can just be peeled back to the opcode

TheNuclearDart / bringup

STM32F7 discovery board bringup

GNU Affero General Public License v3.0

0 stars 0 forks source link

Determine if generic_task_ctx_t in generic_resp_hdr_t is needed, or if it can just be peeled back to the opcode #24

Open TheNuclearDart opened 5 months ago

TheNuclearDart commented 5 months ago

Right now, when a response is sent back, a pointer to a ctx is created by the original requester, with their internal opcode attached. However, this is all that the ctx contains. Do we need this? Can we just peel it back sot hat the generic_resp_hdr_t member of the generic_resp_msg_t is just a uint32_t opcode?