# Mc\_binary in RELEASE LSDK-21.08?

**URL:** <https://community.solid-run.com/t/mc-binary-in-release-lsdk-21-08/583>\
**Category:** NXP LX2160\
**Created:** [February 26, 2023, 3:56pm UTC](https://community.solid-run.com/t/mc-binary-in-release-lsdk-21-08/583 "2023-02-26T15:56:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![joema](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@joema](https://community.solid-run.com/u/joema)\
**Post date:** [February 26, 2023, 3:56pm UTC](https://community.solid-run.com/t/mc-binary-in-release-lsdk-21-08/583/1 "2023-02-26T15:56:56Z")

</div>

Hi,  
I’m confused which mc\_binary I should use in release 21.08.  
It seems lx2160a\_build’s runme.sh is configuring MC\_FORCE to mc\_lx2160a\_10.32.0.itb (I’m using the default SERDES:=8\_5\_2).  
But, in the LSDK-21.08 tag of [GitHub - NXP/qoriq-mc-binary](https://github.com/NXP/qoriq-mc-binary.git), we have mc\_lx2160a\_10.28.1.itb, not mc\_lx2160a\_10.32.0.itb.  
Should we use the file patches/mc\_lx2160a\_10.32.0.itb supplied inside the lx2160a\_build patches folder, and ignore nxp’s qoriq-mc-binary.git?  
Thanks!

---

<div class="post-metadata">

**Author:** ![wick](https://avatars.discourse-cdn.com/v4/letter/w/df788c/32.png) [@wick](https://community.solid-run.com/u/wick)\
**Post date:** [March 11, 2023, 10:59am UTC](https://community.solid-run.com/t/mc-binary-in-release-lsdk-21-08/583/2 "2023-03-11T10:59:55Z")

</div>

You can use either. They are both from NXP’s repo. NXP releases them via tags in their git repo - [here’s the changelog](https://github.com/nxp-qoriq/qoriq-mc-binary/blob/mc_release_10.36.0/CHANGELOG.md) that shows that you need 10.34.0 if you want to have lossless 10G links on the LX2160A.