Why is ThreadX still referred to as "Microsoft Azure RTOS ThreadX"?

Hoping to get some clarification on the status of the ThreadX code that's integrated into the e2 Configurator.

I'm curious why the latest FSP information on github (github.com/.../releases) still refers to ThreadX as "Microsoft Azure RTOS ThreadX v6.4.0". It's been months since Microsoft announced the donation of the ThreadX code to the Eclipse Foundation.

Shouldn't the ThreadX bundled with the FSP/e2 releases be "Eclipse ThreadX" at this point?

Thanks

Tom

Parents Reply Children
No Data