before anyone gets too excited, this doesn’t seem like it applies to DG2 gaming cards, ATSM and PVC are compute cards
<span style="color:#323232;">+SR-IOV Capability
</span><span style="color:#323232;">+=================
</span><span style="color:#323232;">+
</span><span style="color:#323232;">+Due to SR-IOV complexity and required co-operation between hardware, firmware
</span><span style="color:#323232;">+and kernel drivers, not all Xe architecture platforms might have SR-IOV enabled
</span><span style="color:#323232;">+or fully functional.
</span><span style="color:#323232;">+
</span><span style="color:#323232;">+To control at the driver level which platform will provide support for SR-IOV,
</span><span style="color:#323232;">+as we can't just rely on the PCI configuration data exposed by the hardware,
</span><span style="color:#323232;">+we will introduce "has_sriov" flag to the struct xe_device_desc that describes
</span><span style="color:#323232;">+a device capabilities that driver checks during the probe.
</span><span style="color:#323232;">+
</span><span style="color:#323232;">+Initially this flag will be set to disabled even on platforms that we plan to
</span><span style="color:#323232;">+support. We will enable this flag only once we finish merging all required
</span><span style="color:#323232;">+changes to the driver and related validated firmwares are also made available.
</span><span style="color:#323232;">+
</span><span style="color:#323232;">+
</span><span style="color:#323232;">+SR-IOV Platforms
</span><span style="color:#323232;">+================
</span><span style="color:#323232;">+
</span><span style="color:#323232;">+Initially we plan to add SR-IOV functionality to the following SDV platforms
</span><span style="color:#323232;">+already supported by the Xe driver:
</span><span style="color:#323232;">+
</span><span style="color:#323232;">+ - TGL (up to 7 VFs)
</span><span style="color:#323232;">+ - ADL (up to 7 VFs)
</span><span style="color:#323232;">+ - MTL (up to 7 VFs)
</span><span style="color:#323232;">+ - ATSM (up to 31 VFs)
</span><span style="color:#323232;">+ - PVC (up to 63 VFs)
</span><span style="color:#323232;">+
</span><span style="color:#323232;">+Newer platforms will be supported later, but we hope that enabling will be
</span><span style="color:#323232;">+much faster, as majority of the driver changes are either platform agnostic
</span><span style="color:#323232;">+or are similar between earlier platforms (hence we start with SDVs).
</span>
I myself am currently using a Chuwi Hi10X. I don’t have too many major complaints about it other than its quite underpowered. It does perform decently well until you need something graphics related then just kinda sucks. However I can use Firefox with it without any major gripes aisde from video playback, then I need to use chromium.
The desktop environment you use can actually play a massive part in its usability. I have found that GNOME is pretty much useless. KDE isn’t bad but it’s still heavy. I have been testing Cosmic DE and it has been pretty good. Definitely the best performing of the bunch so when that releases I’ll probably be using that full time.
Intel A350, can’t say I have many complaints now. a lot of the issues have been ironed out. I’m not sure if the sparse work has landed for i915 yet, but once it does I don’t think I will have too many super major issues left. Im getting some artifacts when using gamescope, but that’s not a major issue for me since I don’t really need gamescope