2021-06-17, 13:28
After reading a bit more, seems both use Intel XE GPUs so they should be somewhat similar, but maybe the difference is significant enough that the media-driver needs specific changes.
Who knows...
Who knows...
(2021-05-31, 10:05)a1rwulf Wrote: I have following in my log: driver in use: Intel iHD driver for Intel® Gen Graphics - 21.2.0 (3312e66b).Which configure options did you use for mediadriver?
I'm only guessing around, but maybe you can compile the same commit and verify.
(2021-04-20, 08:08)deadite66 Wrote: but it does work via mpv --hwdec=vaapiSame here, mpv works
Quote:Using hardware decoding (vaapi-copy).and mpv also uses VA_EXPORT_SURFACE_SEPARATE_LAYERS
AO: [alsa] 48000Hz stereo 2ch s16
VO: [gpu] 1920x1080 nv12
(2021-06-17, 10:44)a1rwulf Wrote: Yeah in that case I think it makes sense that you open an issue on the media-driver github and ask aboutDone: https://github.com/intel/media-driver/issues/1210
the state of rocketlake support.
Quote:DEBUG <general>: CDRMUtils::DrmFbGetFromBo - using modifier: 0x100000000000002This drm modifier translates to I915_FORMAT_MOD_Y_TILED:
(2021-06-27, 19:41)fritsch Wrote: I don't see the reason intel should do a "special case" for this machine - rendering it incompatible to all standard softwareMost likely because their implementation is wrong: https://github.com/intel/media-driver/is...-866529700
(2021-06-30, 07:17)a1rwulf Wrote: they should fix their sidemaybe they did, using this tree