IABSD.fr/xenocara/lib/mesa/src/gallium/tests
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 | |
|
b5d82fed | 2023-01-28 08:56:19 | Merge Mesa 22.3.4 | |
|
5642995e | 2023-01-28 08:09:28 | Import Mesa 22.3.4 | |
|
75c71730 | 2022-02-24 02:29:36 | Merge Mesa 21.3.7 | |
|
50b4ee55 | 2022-02-24 01:51:18 | Import Mesa 21.3.7 | |
|
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 | |
|
6cd42bcb | 2020-08-26 06:02:31 | Merge Mesa 20.1.6 | |
|
241b1c13 | 2020-08-26 05:26:37 | Import Mesa 20.1.6 | |
|
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 | |
|
1c9ad579 | 2019-05-23 05:33:19 | Merge Mesa 19.0.5 | |
|
1dab445d | 2019-05-23 04:22:53 | Import Mesa 19.0.5 | |
|
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. | |
|
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 | |
|
e2d98075 | 2016-12-11 08:53:19 | Merge Mesa 13.0.2 | |
|
a53e30e0 | 2016-12-11 08:25:29 | Import Mesa 13.0.2 | |
 |
fd18c20e | 2016-10-11 22:14:30 | regen | |
|
363dd58b | 2016-05-29 10:40:19 | Merge Mesa 11.2.2 | |
|
f8d9379c | 2016-05-29 10:11:54 | Import Mesa 11.2.2 | |
|
a06be69d | 2015-12-23 13:43:05 | Merge Mesa 11.0.8 | |
|
987bf76a | 2015-11-22 07:14:29 | regen | |
|
1fe54f21 | 2015-11-22 02:36:47 | import Mesa 11.0.6 |