yes, to a software guy orthagonality in the API means a lot, and thus
forward and reverse transformations of data to/from formats is thought of as
but, to a hardware guy, every feature costs gates, takes up area, uses
power, and generates heat.
so if a spec doesnt ask for a feature, the hw guy wont think to add it,
I suspect if you look at the DDI spec in the DDK, you will find support for
this feature is either called out as optional or not called out at all.
which means the hw and hw driver guys never see the feature as important or
never see it at all.
That and YUV is typically seen as a video format and not a 3D format. Since
the chips are 3D, and in my experience the 2D and 3D teams dont get along,
ipso post facto, video support is sometimes questionable. For instance,
D3D10 and D3D11 do not natively support DShow and playing DShow formats as a
texture. You should be aware of this fact and have your company ( or you )
send design feedback in. There is usually an address for both the DX SDK
(D3D ) and the Windows SDK ( DShow ) so get your asks in, dont assume
others are doing that. And you can ask the driver teams for a feature.
Perhaps the hw does it, its just not exposed yet. The more feedback a
feature gets, the more likely it gets implemented..