Zitat von y33H@
THX @ Loeschzwerg =)
Zhaoxin KX-U6780A review:
https://www.golem.de/news/zhaoxin-kx...05-148364.html
Great work! Unfortunately, I found some inaccuracies.
Zitat von y33H@
Die vier Kerne sind nativ, wie bei Via auch - zuvor gab es zwei Chips auf einem Träger.
Zitat von y33H@
The four cores are native, as with Via - previously there were two chips on a carrier.
This was true for VIA CNQ (2011), because it was basically two Nano X2 in a multi-chip module. However, CNR (2015, samples available in 2014) provides 4 cores on a single die area.
See also:
https://www.forum-3dcenter.org/vbull...4#post12148644
Zitat von y33H@
Mit den KX-5000 (ZX-C+) koppelte Zhaoxin dann zwei Quadcore-Dies, um so acht CPU-Kerne zu erhalten.
Zitat von y33H@
Zhaoxin then coupled two quad-core dies with the KX-5000 (ZX-C+) in order to obtain eight CPU cores.
First of all, KX-5000 is ZX-D, not ZX-C+. There are 4-cores ZX-C+ CPUs (e.g. C4701 - 4 cores on a single die), as well as 8-cores (e.g. FC-1081 - basically two quad-core CPUs in a multi-chip module).
See also:
http://en.zhaoxin.com/ZXC.aspx?seriesid=5
http://en.zhaoxin.com/ZXC.aspx?seriesid=13
Zitat von y33H@
Außerdem wurde die Zhanjiang-Technik um SM3 und SM4 erweitert: Diese Verschlüsselungsverfahren sind erforderlich, damit die Prozessoren in staatlichen Institutionen in China eingesetzt werden dürfen.
Zitat von y33H@
In addition, the Zhanjiang technology was expanded to include SM3 and SM4: These encryption methods are required so that the processors can be used in state institutions in China.
This is not false, but it could be better explained: ZX-C is basically CNR, while ZX-C is CNR with additional instruction sets: SM3 and SM4. Both ZX-C and ZX-C+ belongs to the Zhangjiang microarchitecture, which is based on Isaiah II (the same CPUID). In other words, CNR (Isaiah II), ZX-C (Zhangjiang) and ZX-C+ (Zhangjiang) have the same CPUID, although the last one provides support for additional instruction sets: SM3 and SM4.
Zitat von y33H@
Waren bisher alle CPUs auf einen I/O-Chip namens ZX-100S
Zitat von y33H@
Until now, all CPUs had to rely on an I/O chip called ZX-100S
ZX-A, ZX-B, ZX-C, and ZX-C+ can also work with the VIA VX11(PH) chipset. It is even more popular option than ZX-100(S), which was created mainly for ZX-C+. The main difference between VX11 and ZX-100 is the GPU: Chrome 640/645 [1106:3a01] vs Chrome 320 [1d17:3a02] (or rather C-320, since they can't use the Chrome brand, because VIA sold S3G to HTC). Both are based on the Excalibur microarchitecture.
- Chrome 640 (C-640) iGPU & Chrome 645 (C-645) iGPU from the VX11/VX11H/VX11PH chipset - Vendor Id: 1106 ("VIA Technologies, Inc."), Device Id: 3a01 ("VX11 Graphics [Chrome 645/640]")
- Chrome 320 (C-320) iGPU from the ZX-100S chipset - Vendor Id: 1d17 ("Zhaoxin"), Device Id: 3a02 ("ZX-100 C-320 GPU")
- Chrome 860 (C-860) iGPU from the ZX-D/KX-5000 (codename "WuDaoKou") SoC - Vendor Id: 1d17 ("Zhaoxin"), Device Id: 3a03 ("ZX-D C-860 GPU")
- Chrome 960 (C-960) iGPU from the ZX-E/KX-6000 (codename "LuJiaZui") SoC - Vendor Id: 1d17 ("Zhaoxin"), Device Id: 3a04 ("ZX-E C-960 GPU")
I have confirmation that these motherboards has the VIA VX11 chipset and the ZX-C+ CPU:
http://archive.is/tiaPR/c17dc7beb984...40be1dfc24.jpg
http://archive.is/tiaPR/97120ab0f645...b21d43629c.jpg
http://archive.is/tiaPR/1fe2d100322d...2ce25755dc.jpg
http://archive.is/tiaPR/b14dc77bc8ac...ac150089b3.jpg
https://i.ibb.co/6BgMwFn/C4710-photo1.png
https://i.ibb.co/xmJC2FG/C4710-photo2.png
https://i.ibb.co/m0NvRkn/C4710-photo3.png
https://i.ibb.co/3fH4Ns8/C4710-photo4.png
As you can see, there is visible model string: 90EWZ1G4CN
See also:
https://www.forum-3dcenter.org/vbull...1#post12203741
Zitat von y33H@
The cores support instruction set extensions such as SSE 4.2 and AVX
Zitat von y33H@
Die Kerne unterstützen Befehlssatzerweiterungen wie SSE 4.2 und AVX
As far as I know, even CNR has support for AVX2, at least when it comes to these instructions:
https://pastebin.com/raw/4TRjNZkT
However, it should be noted that CNR doesn't support FMA3.
https://www.forum-3dcenter.org/vbull...0#post11018020
Zitat:
I've seen that one about the VIA C4650. It can't run the AVX2 binary because it needs more than that. You need AVX, AVX2, FMA3, BMI2, and ABM. Haswell and Excavator have all of them. I believe the VIA is missing the last 3.
So the naming may be a bit deceptive. Generally speaking these instructions sets are linear in that a new one implies all the old ones and the ones that come out simultaneously on the same generation. AVX2, and BMI2 all came out at the same time on Haswell. FMA3 came slightly earlier with Piledriver. And all processors with AVX2 have FMA3. So without knowledge of the VIA processor, everyone who targets Haswell will use all of them.
The good thing is that y-cruncher actually checks for everything before using the binary. And it correctly detected the lack of FMA3 and BMI2 and decided not to use the AVX2 binary. Otherwise, it would just crash.
See also:
https://raw.githubusercontent.com/In...aiah_CPUID.png
https://raw.githubusercontent.com/In...iah_CPUID3.txt
https://raw.githubusercontent.com/In...InstLatX64.txt
Zitat von y33H@
Bei der iGPU handelt es sich um eine C-960, die zumindest laut Zhaoxin auf einer eigenen Lösung statt auf einer Chrome von HTCs S3 Graphics basiert.
Zitat von y33H@
The iGPU is a C-960, which, at least according to Zhaoxin, is based on its own solution instead of a Chrome from HTC's S3 Graphics.
It's not true. It still based on S3G's IP. What's more, it uses the same microarchitecture as Chrome 640/645, C-320 or C-860: Excalibur.
Here you can find my documentation of C-860 AKA CHX001:
https://www.forum-3dcenter.org/vbull...4#post12205314
C-960 is only a slightly improvement over C-860.
Zitat von y33H@
Sie unterstützt OpenCL 1.1, OpenGL 3.2 und Direct3D 11.
Zitat von y33H@
It supports OpenCL 1.1, OpenGL 3.2 and Direct3D 11.
It has support for OpenGL ES 2.0 as well. According to Zhaoxin, it also supports OpenVG 1.1 (please note that back in time VIA/S3G claimed to provide an OpenVG 1.1 driver for Destination GPUs, including Chrome 5400E and eH1). What's more, it should be possible to use 3D acceleration via Direct3D 12 API (feature level: Direct3D 11 - "DX11 with DX12 API support").
See also:
https://www.forum-3dcenter.org/vbull...7&d=1566792950
Zitat von y33H@
Hier zeigt sich jedoch ein weiteres Problem mit dem Chip, denn für die integrierte GPU auf Basis einer S3-Grafikeinheit gibt es keinen Treiber.
Zitat von y33H@
However, this shows another problem with the chip, because there is no driver for the integrated GPU based on an S3 graphics unit.
Of course Linux drivers exist. I have access to the following drivers:
-
zhaoxin-chx001-linux-graphics-driver-19.00.33_x86_64.deb (SHA2: 53d591eb907791e8ac035aea8c7a6982a72c17b37e763c8200517112394b49f5) - DRIVER_DATE: 2017-10-30, upload date: 2018-01-10
-
zhaoxin-chx001-linux-graphics-driver-19.00.34_x86_64.deb (SHA2: 763c045ee8ab68e95d545278cb3aca75308553cc444afe7d600f839cee2d2604) - DRIVER_DATE: 2017-11-07, upload date: 2018-01-10
-
CHX001 中科方德3.0x64_19.00.38.zip (SHA2: 6dac1e3127f0dfc16683ca767322f55dd1c1d07242a5373e2cdcadb18f0c2f34) - DRIVER_DATE: 2017-12-28, upload date: 2018-01-10
-
zhaoxin-graphics-19.00.38-i386.tar.bz2 (SHA2: 6d7edd8acec49d1ef22a8bc64250274f08e46b2388d21d8848cc3ed55ecab16d) - DRIVER_DATE: 2017-12-28, upload date: 2018-01-10
-
zhaoxin-chx001-linux-graphics-driver-19.00.38_i386.deb (SHA2: 9d939ef84c4e59c18e9de70e91d31bccbf487a837073477be1a55d7577334c2d) - DRIVER_DATE: 2017-12-28, upload date: 2018-01-10
-
zhaoxin-graphics-19.00.38-x86_64.tar.bz2 (SHA2: ab83a6eeed977e08eedda403d808ed7cf4d2aa32e5546114f9cdfcd8d7ddba4e) - DRIVER_DATE: 2017-12-28, upload date: 2018-01-10
-
zhaoxin-chx001-linux-graphics-driver-19.00.38_x86_64.deb (SHA2: 34458e6b71df181a9006aa871806475fafa3eb2f8ddc9973207aa1105771cd38) - DRIVER_DATE: 2017-12-28, upload date: 2018-01-10
-
CHX001 中科方德3.0x64-GFX-19.00.40.zip (SHA2: db1d61228814c9922e1865ef1c02c79b71976d399723be6db3d94b86efae6155) - DRIVER_DATE: 2018-01-26, upload date: 2018-03-05
-
zhaoxin-graphics-19.00.40-i386.tar.bz2 (SHA2: 32b1f50e9713c684be8947097733ace0395e2f587b98a52916e9cb9d0d0a1b03) - DRIVER_DATE: 2018-01-26, upload date: 2018-03-05
-
zhaoxin-chx001-linux-graphics-driver-19.00.40_i386.deb (SHA2: 7a887d7cfe0c07dd48243a5ad08705d1bbb93e41be0fa329d7c0556ce50163f7) - DRIVER_DATE: 2018-01-26, upload date: 2018-03-05
-
zhaoxin-graphics-19.00.40-x86_64.tar.bz2 (SHA2: d3eee7cdbe81c39269819a3450c5f668f4b710581c8741ee5f1ff7fa5ae268c8) - DRIVER_DATE: 2018-01-26, upload date: 2018-03-05
-
zhaoxin-chx001-linux-graphics-driver-19.00.40_x86_64.deb (SHA2: 909d70c6314a34cb4fda3c830e607721b25afff715236806955ec0916fe39830) - DRIVER_DATE: 2018-01-26, upload date: 2018-03-05
-
ZX-D 中科方德3.0_x64_GFX_19.00.45.zip (SHA2: b6df0329c3f451f8d9bcf41dcf85effc477682c3e7d136355211dd22cfd4040b) - DRIVER_DATE: 2018-05-02, upload date: 2018-05-11
-
zhaoxin-ZX-D-graphics-19.00.45-i386.tar.bz2 (SHA2: 71e73d9ecae21cc1fb45d702884e1cc59f89b4b7cdb1ffa5d0c31d0f9cce9f67) - DRIVER_DATE: 2018-05-02, upload date: 2018-05-11
-
zhaoxin-ZX-D-linux-graphics-driver-19.00.45_i386.deb (SHA2: 5d464cfdaa5fde0151954cdbbed12b2fe2194e98ce5813ededd1e52111781fd4) - DRIVER_DATE: 2018-05-02, upload date: 2018-05-11
-
zhaoxin-ZX-D-graphics-19.00.45-x86_64.tar.bz2 (SHA2: b1651f78ae5eb09b731afa0abf85866a4f941506fd98f31f5cb12f3d85dc1b09) - DRIVER_DATE: 2018-05-02, upload date: 2018-05-11
-
zhaoxin-ZX-D-linux-graphics-driver-19.00.45_x86_64.deb (SHA2: b1d9a6d8b622caba0b1aa3cc3e2a82c68491659fa96a47e0066e6046f1e4dba0) - DRIVER_DATE: 2018-05-02, upload date: 2018-05-11
-
zhaoxin-chx001-linux-graphics-driver_19.00.45_amd64.deb (SHA2: 63291f86cfd58e40048d92480e89619673882da2222939cb163f57730fb5e3f2) - DRIVER_DATE: 2018-05-02, upload date: 2018-05-11
-
zhaoxin-chx001-linux-graphics-driver_19.00.45+1nfs1_amd64.deb (SHA2: 982284fdebe368906223ed282cf41377a917e030ae3eb163024df6c9a3c2e5a2) - DRIVER_DATE: 2018-05-02, upload date: 2018-05-30
-
ZX-D+中科方德3.0_x64_19.00.46.zip (SHA2: a070819ecd5cb58d14f4a5b2fbf6d39293efd454ceefabe459caa9e5ad5b8ec8) - DRIVER_DATE: 2018-05-16, upload date: 2018-06-22
-
zhaoxin-ZX-D-graphics-19.00.46-i386.tar.bz2 (SHA2: c57ec559919836319131daab01ca87771dcecab5bed76b16aeb10662d59fae9d) - DRIVER_DATE: 2018-05-16, upload date: 2018-06-22
-
zhaoxin-ZX-D-linux-graphics-driver-19.00.46_i386.deb (SHA2: 54c6f681397ac3286baa9ea62a06357d98848b8b15b1f842c1e54cf3d4dc22a6) - DRIVER_DATE: 2018-05-16, upload date: 2018-06-22
-
zhaoxin-ZX-D-graphics-19.00.46-x86_64.tar.bz2 (SHA2: 6676d7fc3a879c1201762829afb8a088ec671987fe3a854b6adfe8e923a548d4) - DRIVER_DATE: 2018-05-16, upload date: 2018-06-22
-
zhaoxin-ZX-D-linux-graphics-driver-19.00.46_x86_64.deb (SHA2: 4be505a20a3fb7e230ddab6c6c60780574e8fb317bc11361c8057a90f7954bbd) - DRIVER_DATE: 2018-05-16, upload date: 2018-06-22
-
19.00.47b.zip (SHA2: 045fa9c8ec4cd3279eb35737b4dc1881da1f784214c0e6cc8c110688ac626d01) - DRIVER_DATE: 2018-07-31, upload date: 2018-08-10
-
zhaoxin-ZX-D-linux-graphics-driver-19.00.47b_x86_64.deb (SHA2: f4ada6ca5679419456a3fe1c7e4b82af0414d3058e06651be2258256a52d1435) - DRIVER_DATE: 2018-07-31, upload date: 2018-08-10
-
zhaoxin-chx001-linux-graphics-driver_19.00.47b_amd64.deb (SHA2: 2d960d349ca5ee57e62fb8ea303064b2df49f6f3e58b235812dee1c98ac2b7c7) - DRIVER_DATE: 2018-07-31, upload date: 2018-08-10
-
zhaoxin-ZX-D-linux-graphics-driver-19.00.47c_x86_64.deb (SHA2: b4f63131053106cc5ad0df082da4f34e0acaefffe200b3eb7e1ac1660bc3681d) - DRIVER_DATE: 2018-10-10, upload date: 2018-10-12
-
zhaoxin-chx001-linux-graphics-driver_19.00.47c_amd64.deb (SHA2: 172495e7e953d1a3f2367967959873daea87e0564a8a5b9e1e00dd749ca8cbd9) - DRIVER_DATE: 2018-10-10, upload date: 2018-10-12
-
zhaoxin-linux-graphics-driver-dri_21.00.13_amd64.deb (SHA2: dc339abac231df1362c2765f9f97f330311c4232c1d0173ac2dc32d9ed031096) - DRIVER_DATE: 2019-12-12, upload date: 2019-12-14
-
zhaoxin-linux-graphics-driver-dri_21.00.16_amd64.deb (SHA2: e2cbd6262af696aac657c18bb810034de22d2dd6cc5c518bd4260744240ecff0) - DRIVER_DATE: 2020-02-25, upload date: 2020-03-21
The latest 21.00.16 driver ("zhaoxin-linux-graphics-driver-dri_21.00.16_amd64.deb" from 2020-03-21 according to upload date, or 2020-02-25 according to DRIVER_DATE) provides support for:
- Chrome 860 (C-860) iGPU from the ZX-D/KX-5000 (codename "WuDaoKou") SoC - Vendor Id: 1d17 ("Zhaoxin"), Device Id: 3a03 ("ZX-D C-860 GPU")
- Chrome 960 (C-960) iGPU from the ZX-E/KX-6000 (codename "LuJiaZui") SoC - Vendor Id: 1d17 ("Zhaoxin"), Device Id: 3a04 ("ZX-E C-960 GPU")
Code:
static struct pci_device_id pciidlist[] =
{
{0x1d17, 0x3A03, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, //chx001
{0x1d17, 0x3A04, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, //chx002 qt
{0, 0, 0}
};
The old 19.00.47c driver ("zhaoxin-ZX-D-linux-graphics-driver-19.00.47c_x86_64.deb"/"zhaoxin-chx001-linux-graphics-driver_19.00.47c_amd64.deb" from 2018-10-12 according to upload date, or 2018-10-10 according to DRIVER_DATE) provided support for:
- Chrome 640 (C-640) iGPU & Chrome 645 (C-645) iGPU from the VX11/VX11H/VX11PH chipset - Vendor Id: 1106 ("VIA Technologies, Inc."), Device Id: 3a01 ("VX11 Graphics [Chrome 645/640]")
- Chrome 860 (C-860) iGPU from the ZX-D/KX-5000 (codename "WuDaoKou") SoC - Vendor Id: 1d17 ("Zhaoxin"), Device Id: 3a03 ("ZX-D C-860 GPU")
Code:
static struct pci_device_id pciidlist[] =
{
{0x1106, 0x3A01, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
{0x1106, 0x3A03, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, //chx001 qt
{0x1d17, 0x3A03, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, //chx001
{0, 0, 0}
};
We can assume that pre-19 series driver had support for older Zhaoxin's GPUs:
- Chrome 320 (C-320) iGPU from the ZX-100S chipset - Vendor Id: 1d17 ("Zhaoxin"), Device Id: 3a02 ("ZX-100 C-320 GPU")
Please keep in mind that the standard driver package doesn't include stuff related to OpenCL. It requires an additional driver.
Major issues with the current drivers:
- Although these drivers are included in Chinese distributions (e.g. UOS or NFS China), there are no repos, nor packages for "Western" Linux distros, such as Fedora or openSUSE.
- Support for hybrid GPU configurations requires a patched version of Mesa.
- Support for older GPUs is relatively quickly dropped: 19-series driver doesn't support Chrome 320 from the ZX-100(S) chipset, 21-series driver doesn't support Chrome 640/645 from the VX11(PH) chipset - in other words, the latest driver supports only ZX-D (2017) and ZX-E (2018) hardware.
- OpenGL support is outdated: no support for OGL 4.x at all.
- OpenGL ES support is outdated: no support for OGL ES 3.x at all.
- OpenCL support is outdated: no support for OCL 2.x at all.
- No support for Vulkan at all.
- Although VDPAU and VA-API are supported, it still requires a modified version of MPlayer/SMPlayer to make use of video decoding acceleration.
- Video encoding for H.264/H.265 is limited to 1920x1080p50.
- 3D performance is comparable to the Chrome 640/645 GPU from 2012.
See also:
https://www.forum-3dcenter.org/vbull...4#post12205314
Zitat von y33H@
Zwar gibt es und gab es in der Vergangenheit immer wieder Versuche der Linux-Community dahingehend, aber wirklich weit fortgeschritten sind diese nicht.
Zitat von y33H@
There have been and have always been attempts by the Linux community to do this, but they are not really very advanced.
It's not true. There are open source drivers for:
- Unichrome series [2002] (from CLE266's iGPU to CX700M(2)'s iGPU), which are based on updated ProSavage - hybrid Savage 4/Savage 2000 [2000]: Savage 4 3D core [1998] and Savage 2000 2D functionality [1999]) → pre-DirectX 9 era (DirectX 7 without T&L)
- Chrome9 series [2005] (from K8M890's iGPU to VX900's iGPU), which derived from DeltaChrome - Columbia microarchitecture [2004] → DirectX 9 era
However, literally no one has worked on open source drivers for:
- Chrome 400 series [2008] (from Chrome 430 GT to Chrome 4300E) and 500 series [2009] (from Chrome 540 GTX to VN1000's iGPU) - Destination microarchitecture [2008] → DirectX 10 era
- Chrome 600 series [2012] and derivatives [2016] - Excalibur microarchitecture [2012] → DirectX 11 era
Not a single line of code has been created for this!
In the past, VIA provided proprietary driver for the Chrome9 series ("via_chrome9_dri.so"/"via_drv.so"), and S3G provided proprietary driver for the Chrome 400/500 series ("s3g_dri.so"/"s3g_drv.so").
Currently, Zhaoxin supports the Chrome 600 series and its derivatives ("zx_dri.so"/"zx_drv.so"). This includes Chrome 640/645 from the VX11(PH) chipset, as well as C-860 from the ZX-D/KX-5000 SoC and C-960 from the ZX-E/KX-6000 SoC. Anyway, it is a proprietary driver, similar to the NVIDIA driver (open source "glue" over a binary blob).
See also:
https://www.phoronix.com/forums/foru...79#post1027179
https://www.freedesktop.org/wiki/Ope...ortedHardware/
Zitat von y33H@
Zhaoxin arbeitet längst an den KX-7000 alias ZX-F für 2021. Die nutzen weiterhin acht Kerne, sollen aber Big- statt Little-Cores sein. Die Chinesen wollen die Leistung pro Takt um mehrere Faktoren steigern und auch einen DDR5-Speichercontroller integrieren, was durch TSMCs 7-nm-Verfahren unterstützt wird.
Zitat von y33H@
Zhaoxin has long been working on the KX-7000 alias ZX-F for 2021. They continue to use eight cores, but are said to be big cores instead of little cores. The Chinese want to increase the performance per clock by several factors and also integrate a DDR5 memory controller, which is supported by TSMC's 7 nm process.
Such were their plans, but they have changed them some time ago. What's more, we already have an early samples of ZX-F, produced in 2019:
https://browser.geekbench.com/v5/cpu/526995
Anyway, ZX-F should be produced in the TSMC's 16 nm process and supports DDR4.
ZX-G will continue to support DDR4, but it should be produced in the TSMC's 7 nm process. Moreover, it may provide even 16 cores.
The first generation with support for DDR5 will be probably ZX-H.
Of course, these are just plans and they may change in the future. Zhaoxin confirmed that they will try to use modern technologies available on the market. However, they can't use something that is not there yet, and the release date of DDR5 has been delayed. According to Gamers Nexus, a leaked internal AMD roadmap is reported to show DDR5 support for 2022 Zen 4 CPUs and Zen 3+ APU. As you can see, it not really the near future.
See also:
https://www.forum-3dcenter.org/vbull...7#post12205567
https://www.forum-3dcenter.org/vbull...1#post12231741
https://www.forum-3dcenter.org/vbull...chmentid=69318
http://www.zhaoxin.com/InCenterContent.aspx?id=282
http://www.gdinsa.org/uploadfile/202...6055237805.pdf