Udpserver init thread allocation should not happen within the booter but within the RK instead.
Currently, the RK requests that the booter provides the thdcap associated with that init thread when the RK wants to add that thread to its scheduling context. This is hacky as the the init thread is already within the scheduling context of the booter. To solve this, the RK just needs to allocate the init thread itself while leaving the booter to create the comp itself.
Udpserver init thread allocation should not happen within the booter but within the RK instead.
Currently, the RK requests that the booter provides the thdcap associated with that init thread when the RK wants to add that thread to its scheduling context. This is hacky as the the init thread is already within the scheduling context of the booter. To solve this, the RK just needs to allocate the init thread itself while leaving the booter to create the comp itself.