24 May
2024
24 May
'24
2:15 a.m.
Hi Pierre-Louis
Thank you for your feedback
There are two options a) we don't even try to test the codec-cpu match in terms of capabilities. That means the same behavior as today. b) we add a chicken bit for platforms to disable the codec-cpu match if it breaks specific platforms.
The problem with b) is that we don't know what platforms will break. I reported one example that was caught by our CI, but there could be additional Chromebooks impacted, who knows.
My vote is a).
Yeah, it is a little big problem for us. Let's keep current style for now.
I will mark it on source code when we remove dpcm_xxx flag to be possible to resolve someday.
Thank you for your help !!
Best regards --- Renesas Electronics Ph.D. Kuninori Morimoto