driver1998

Results 114 comments of driver1998

The VCHIQ initialization issue with blinking ACT should be resolved with 051a7c89b500fc401f5d7f98dde3ff76959ff0ee, more validation needed.

If OBS supports va-api on Linux, we might be able to get it working on Windows with the new vaOn12 driver (which wraps va-api to DirectX 12). Not sure about...

> The question I'm talking about is which compiler or toolset we should use, ARM64 or ARM64EC. I would say ARM64. We are mostly dealing with open source plugins right...

Looks like vaOn12 is decode only on 8cx Gen 2: ``` $ vainfo Trying display: win32 libva info: VA-API version 1.18.0 libva info: User environment variable requested driver 'vaon12' libva...

Gen 3 is decode only as well, got this output from a friend with Dev Kit 2023: ![-18f553376f3c3432.jpg](https://github.com/obsproject/obs-deps/assets/22699485/99afeeb6-dd57-47d0-9d00-86c29c73497a)

I guess you may already know, but ARM64 Windows support of LuaJIT [seems to be ready](https://github.com/LuaJIT/LuaJIT/issues/593), cross-compiling from Windows x64 MSVC is possible too https://github.com/LuaJIT/LuaJIT/pull/1081.

I have some early tests about IoT Core 17763 ARM64 on RPi4 Features | Status ---------| ------- WiFi | ❌ Bluetooth | ❓ UART | ❓ LAN | ❌ (1)...

Check out https://github.com/raspberrypi/windows-drivers/pull/43.

Now I added package manifests for IoT Core ARM64 (https://github.com/raspberrypi/windows-drivers/pull/43), hopefully they'll also be useful for WCOS.

I would like to tackle the Windows ARM port but currently both Qualcomm and Parallels on M1 do not support Vulkan, and only do OpenGL 3.3. (Qualcomm: D3D12 Native, OpenGL...