IABSD.fr/xenocara/lib/mesa/src/intel

Branch :


Log

Author Commit Date CI Message
452696b8 2025-06-05 14:17:56 Merge Mesa 25.0.7
67d6f117 2025-06-05 11:23:11 Import Mesa 25.0.7
f3c1e4e9 2024-04-02 10:41:59 Merge Mesa 23.3.6
874d2ba3 2024-04-02 09:25:31 Import Mesa 23.3.6
4f0d8474 2023-11-02 04:53:12 Merge Mesa 23.1.9
60059fee 2023-11-02 04:31:01 Import Mesa 23.1.9
5f7ec4d4 2023-04-06 10:23:42 Merge Mesa 22.3.7
175bb703 2023-04-06 10:08:20 Import Mesa 22.3.7
b91c5a5e 2023-02-06 23:28:50 intel/dev: remove invalid EHL pci id a23e04b67367ae90e6fee06e4506bee3f00e6ae6 in mainline Mesa
b5d82fed 2023-01-28 08:56:19 Merge Mesa 22.3.4
5642995e 2023-01-28 08:09:28 Import Mesa 22.3.4
2e058c3c 2022-09-02 05:46:23 Merge Mesa 22.1.7
4968d392 2022-09-02 05:12:48 Import Mesa 22.1.7
f2c66683 2022-05-04 06:07:22 intel/dev: Add device info for RPL-P From Jordan Justen d257494ec4d826aec8841845479215820e612917 in mainline Mesa
c569ea33 2022-05-04 06:02:04 intel/dev: Add device info for RPL From Jordan Justen 4e0eca7dc34942759638ab00eb006ba40284a7c in mainline Mesa
72f7f716 2022-05-04 05:57:30 intel/dev: Add device ids for ADL-N From Jordan Justen 03cc5a8295e239b45623c89faac88030b33a4a14 in mainline Mesa
f4f27ace 2022-04-21 04:37:17 Merge Mesa 21.3.8
75c71730 2022-02-24 02:29:36 Merge Mesa 21.3.7
50b4ee55 2022-02-24 01:51:18 Import Mesa 21.3.7
3715a2f9 2021-09-09 09:59:12 Merge Mesa 21.1.8
bf4ec162 2021-09-09 09:42:50 Import Mesa 21.1.8
aa17e02d 2021-07-22 10:50:23 Merge Mesa 21.1.5
f849497a 2021-07-22 09:57:37 Import Mesa 21.1.5
41a55d03 2020-09-22 02:08:55 Merge Mesa 20.0.8 With Mesa 20.1 even after the kernel change to do wbinvd on all cpus sthen@ reported that hard hangs still occurred on his Haswell system with inteldrm. Mark Kane also reported seeing hangs on Ivy Bridge on bugs@. Some systems/workloads seem to be more prone to triggering this than others as I have not seen any hangs on Ivy Bridge and the only hangs I saw on Haswell when running piglit went away with the wbinvd change. It seems something is wrong with drm memory attributes or coherency in the kernel and newer Mesa versions expect behaviour we don't have.
5bc2fd43 2020-09-22 01:28:34 Import Mesa 20.0.8
1c44290c 2020-09-14 07:16:06 go back to brw_eu.h rev 1.9 matching upstream 20.1 branch haswell hangs still occurred just less frequently with the 1.10 revert of 'intel/eu: Use non-coherent mode (BTI=253) for stateless A64 messages' The recent kernel change to do wbinvd across all cpus instead of just one is a better approach and avoids hangs seen with piglit on haswell.
ccfe4498 2020-09-11 15:04:43 partially revert a Mesa commit to avoid hard hangs on Haswell intel/eu: Use non-coherent mode (BTI=253) for stateless A64 messages d23bbc8c28b6a5cd7f4d3d03c74d8319da5d47d5 on 20.1 branch 4985e380dd776ac65c4ae5627138211f9d9f03ce on mainline thanks to gnezdo@ sthen@ and espie@ for reports and testing
1c86a178 2020-09-03 07:17:20 Merge Mesa 20.1.7
7fa385c8 2020-09-03 06:40:00 Import Mesa 20.1.7
eb922cd9 2020-09-01 06:42:24 get available memory when assert() is disabled via NDEBUG problem spotted by Jason Ekstrand reviewing proposed patches upstream
6cd42bcb 2020-08-26 06:02:31 Merge Mesa 20.1.6
241b1c13 2020-08-26 05:26:37 Import Mesa 20.1.6
c0a649c0 2020-01-22 03:07:41 add files generated by python scripts which stopped being shipped with distfiles when upstream removed autotools
75490c6c 2020-01-22 03:02:59 add back autotools files removed upstream
2796e1e6 2020-01-22 02:49:17 Merge Mesa 19.2.8
18af3bca 2020-01-22 02:07:15 Import Mesa 19.2.8
cddeeb9f 2019-08-24 02:12:17 intel: Add support for Comet Lake From Anuj Phogat 82f6a746e8b47fb6e3f96d7f5f69973f50eec9ca in mesa master
ff40cb71 2019-07-01 08:36:47 Merge Mesa 19.0.8
b1b22c2a 2019-07-01 07:44:02 Import Mesa 19.0.8
bf1979f8 2019-05-27 07:20:30 Build Mesa intel and radeon vulkan drivers and amd64 and i386 The intel driver can be used with inteldrm on ivy bridge or newer. The radeon driver only works with amdgpu not radeondrm. As we can't use python in xenocara add phony targets to create the same output as python scripts which create json files for the loader. This is just the ICDs, to use vulkan the loader and additional ports are required. ok mpi@ on an earlier version. Changed to call shm_unlink() directly after shm_mkstemp() as suggested by kettenis@
6cb8ade4 2019-05-27 04:19:00 Call shm_unlink() directly after shm_mkstemp() rather than just before close(). Closer to memfd_create() behaviour.
1c9ad579 2019-05-23 05:33:19 Merge Mesa 19.0.5
1dab445d 2019-05-23 04:22:53 Import Mesa 19.0.5
702ae9a5 2019-03-19 10:59:02 Merge Mesa 18.3.5
34c49fbb 2019-03-19 09:37:42 Import Mesa 18.3.5
b9f320ec 2019-02-19 04:24:00 Merge Mesa 18.3.4
ae7ee137 2019-02-19 03:25:14 Import Mesa 18.3.4
338bc0a2 2019-01-29 11:52:04 Merge Mesa 18.3.2
fecc0d40 2019-01-29 10:45:31 Import Mesa 18.3.2
19f2c52c 2018-10-23 06:35:32 Merge Mesa 17.3.9 Mesa 18.x needs an ld with build-id for at least the intel code Mesa 18.2 assumes linux only memfd syscalls in intel code Tested by matthieu@, kettenis@ and myself on a variety of hardware and architectures. ok kettenis@
587354b6 2018-10-23 05:40:45 Import Mesa 17.3.9
646d14d2 2018-01-08 05:41:20 Revert to Mesa 13.0.6 again. Corruption has again been reported on Intel hardware running Xorg with the modesetting driver (which uses OpenGL based acceleration instead of SNA acceleration the intel driver defaults to). Reported in various forms on Sandy Bridge (X220), Ivy Bridge (X230) and Haswell (X240). Confirmed to not occur with the intel driver but the xserver was changed to default to the modesetting driver on >= gen4 hardware (except Ironlake). One means of triggering this is to open a large pdf with xpdf on an idle machine and highlight a section of the document. There have been reports of gpu hangs on gen4 intel hardware (T500 with GM45, X61 with 965GM) when starting Xorg as well.
702572c9 2017-12-31 07:12:12 Merge Mesa 17.2.8
cc122a5e 2017-12-31 06:17:38 Import Mesa 17.2.8
ad2ad70a 2017-08-26 16:59:17 Revert to Mesa 13.0.6 to hopefully address rendering issues a handful of people have reported with xpdf/fvwm on ivy bridge with modesetting driver.
c97e30df 2017-08-14 11:21:30 regen
46c4fa73 2017-08-14 11:17:43 cope with cvs import changing timestamps which caused make rules that invoke python to attempt to run and fail
36c1bd02 2017-08-14 09:57:57 Merge Mesa 17.1.6
6526d331 2017-08-14 09:30:06 Import Mesa 17.1.6
fa6c2100 2017-03-25 00:29:27 Merge Mesa 13.0.6
480cde33 2017-03-25 00:05:01 Import Mesa 13.0.6
ba80afc3 2017-02-26 12:06:04 Import Mesa 13.0.5
6d4ad6fa 2017-01-19 05:38:52 Import Mesa 13.0.3
54858cb1 2016-12-11 16:03:25 disable additional rules to regen sources when xxd is not found Found the hard way by Mark Patruck and naddy. Didn't encounter it here with a post import build for reasons unknown.
2047dff5 2016-12-11 10:03:01 disable additional rules to regen sources when python is not found After a cvs import timestamps change which triggers rules that attempt to call python to regenerate files. When python is not found this generates empty files that override those from the distfile, breaking the build. When building inside xenocara python is never found as the pkg paths are not searched.
e2d98075 2016-12-11 08:53:19 Merge Mesa 13.0.2
a53e30e0 2016-12-11 08:25:29 Import Mesa 13.0.2