dri-devel June 2013

dri-devel@lists.freedesktop.org

132 participants
727 discussions

[Bug 53971] New: radeon:Soft reset GPU in StarCraft2 under Wine
by bugzilla-daemon＠bugzilla.kernel.org 09 Oct '14

09 Oct '14

https://bugzilla.kernel.org/show_bug.cgi?id=53971 Summary: radeon:Soft reset GPU in StarCraft2 under Wine Product: Drivers Version: 2.5 Kernel Version: 3.8.0-rc7 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: stalkerg(a)gmail.com Regression: No Random GPU resets and freeze on Radeon 6770 with SC2 game under wine 1.5.23 (GLSL disable, pbuffer enable). Linux sagita 3.8.0-rc7 #1 SMP PREEMPT Sat Feb 16 18:13:51 MSK 2013 x86_64 AMD FX(tm)-8120 Eight-Core Processor AuthenticAMD GNU/Linux Mesa 9.2-devel (git-f1ab67c) radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000002236b last fence id 0x000000000002235e) radeon 0000:01:00.0: Saved 407 dwords of commands on ring 0. radeon 0000:01:00.0: GPU softreset: 0x00000003 radeon 0000:01:00.0: GRBM_STATUS = 0xE4002CA4 radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0xC0000005 radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x04000000 radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00040000 radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00048402 radeon 0000:01:00.0: R_008680_CP_STAT = 0x80860243 radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 radeon 0000:01:00.0: GPU reset succeeded, trying to resume [drm] probing gen 2 caps for device 1002:5a16 = 2/0 [drm] PCIE gen 2 link speeds already enabled [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). radeon 0000:01:00.0: WB enabled radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8802321edc00 radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8802321edc0c [drm] ring test on 0 succeeded in 3 usecs [drm] ring test on 3 succeeded in 1 usecs [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 1 usecs -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 1

[Bug 34462] New: 180 second hang on boot, DRM doesn't seem to initialize (firmware issue?)
by bugzilla-daemon＠freedesktop.org 14 Sep '14

14 Sep '14

https://bugs.freedesktop.org/show_bug.cgi?id=34462 Summary: 180 second hang on boot, DRM doesn't seem to initialize (firmware issue?) Product: DRI Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: owen.riddy(a)gmail.com Created an attachment (id=43540) --> (https://bugs.freedesktop.org/attachment.cgi?id=43540) dmesg from Debian Unstable, fails to load I have a Radeon 3450 graphics card and have been using Debian Squeeze (linux 2.6.32). The card was/is very well supported by the radeon graphics driver, and firmware was being properly loaded (Debian splits the firmware into a separate package from the kernel). Whenever I compiled a newer vanilla kernel KMS didn't work (starting with 2.6.33, I believe. It was a while ago) and X wouldn't load. Every so often I tried a different kernel, and the problem remained. On X, the system would completely hang with a blank screen (I couldn't access any virtual terminals). I assumed I'd mis-configured my kernel and gave up. Debian has now upgraded to linux 2.6.37-1 and this image seems to have the same problem. After upgrading, I get a suspicious 180 second pause when the kernel "populates /dev", which I now attribute to a bug. I'm getting an error message about modprobe blocking (in dmesg). I suspect firmware loading problems: Wheezy (fails, 2.6.37): dmesg | grep -C 4 icroc [ 4.325551] [drm] radeon: 256M of VRAM memory ready [ 4.325554] [drm] radeon: 512M of GTT memory ready. [ 4.325619] [drm] radeon: irq initialized. [ 4.325622] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 4.326544] [drm] Loading RS780 Microcode [ 4.329997] input: HDA ATI SB Headphone as /devices/pci0000:00/0000:00:14.2/sound/card0/input7 [ 4.414321] radeon 0000:01:05.0: WB enabled [ 4.446469] [drm] ring test succeeded in 1 usecs [ 4.446595] [drm] radeon: ib pool ready. Squeeze (works, 2.6.32): dmesg | grep -C 4 icroc [ 4.616162] [drm] radeon: 256M of VRAM memory ready [ 4.616163] [drm] radeon: 512M of GTT memory ready. [ 4.616204] [drm] radeon: irq initialized. [ 4.616206] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 4.616624] [drm] Loading RS780 Microcode [ 4.616627] platform radeon_cp.0: firmware: requesting radeon/RS780_pfp.bin [ 4.714728] hda_codec: ALC1200: BIOS auto-probing. [ 4.716081] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:14.2/input/input6 [ 4.809447] platform radeon_cp.0: firmware: requesting radeon/RS780_me.bin -- [ 4.941941] radeon 0000:02:00.0: irq 30 for MSI/MSI-X [ 4.941946] radeon 0000:02:00.0: radeon: using MSI. [ 4.941978] [drm] radeon: irq initialized. [ 4.941980] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 4.942370] [drm] Loading RV620 Microcode [ 4.942372] platform radeon_cp.0: firmware: requesting radeon/RV620_pfp.bin [ 4.982496] platform radeon_cp.0: firmware: requesting radeon/RV620_me.bin [ 4.988086] platform radeon_cp.0: firmware: requesting radeon/R600_rlc.bin [ 5.025570] [drm] ring test succeeded in 0 usecs To be sure I haven't tainted the configuration, the method to get a test platform was: * Installed the Squeeze release base system * Upgrade to Wheezy, rebooted to test KMS (virtual terminal screen resolution was large, suggesting it worked) * Upgraded to unstable and reboot, at which point I get the 180 second hang and modprobe errors, as well as a rather low resolution VT. lspci and other info can be found on this bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613922 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 8

[Bug 44126] New: [r300g] 0ad: carpet textures "flash" and get hidden by ground texture.
by bugzilla-daemon＠freedesktop.org 05 Sep '14

05 Sep '14

https://bugs.freedesktop.org/show_bug.cgi?id=44126 Bug #: 44126 Summary: [r300g] 0ad: carpet textures "flash" and get hidden by ground texture. Classification: Unclassified Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: fabio.ped(a)libero.it Created attachment 54794 --> https://bugs.freedesktop.org/attachment.cgi?id=54794 example of carpets partially hidden by ground texture Since 0ad alpha 8 there is a new faction: Persians. Their civic center has a couple of carpets on it (just start a map with Persians and see the main building). When you zoom (using mouse wheel) or rotate (using Q and E keys) the screen, the carpets on the civic center "flash" and get partially hidden by the ground texture. An example screenshot is attached. Llvmpipe doesn't have this problem, as well other videos and screenshots found on the net. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 6

[Bug 30102] New: Radeon : ring test failed
by bugzilla-daemon＠bugzilla.kernel.org 03 Sep '14

03 Sep '14

https://bugzilla.kernel.org/show_bug.cgi?id=30102 Summary: Radeon : ring test failed Product: Drivers Version: 2.5 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: b747xx(a)gmail.com Regression: No Created an attachment (id=49622) --> (https://bugzilla.kernel.org/attachment.cgi?id=49622) dmesg On the radoen module load, I got this error: [ 9.874444] [drm:r600_ring_test] *ERROR* radeon: ring test failed (scratch(0x8504)=0xCAFEDEAD) [ 9.874447] radeon 0000:01:05.0: disabling GPU acceleration [ 9.875771] radeon 0000:01:05.0: ffff88043c78dc00 unpin not necessary This is intermittent. I got theses error two weeks ago and it vanish after a reboot about 1 week ago. The video acceleration was working perfectly until yesterday reboot (adding an option in the kernel) and now the problem is back. After the problem came back, I tried booting on the 3 others kernels I used this week (when it was working correctly) and the problem is still there with them. I have attached the dmesg and my .config if this can help find the problem. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 15

[Bug 58660] New: Radeon HD 6950 completely broken.
by bugzilla-daemon＠freedesktop.org 01 Sep '14

01 Sep '14

https://bugs.freedesktop.org/show_bug.cgi?id=58660 Priority: medium Bug ID: 58660 Assignee: dri-devel(a)lists.freedesktop.org Summary: Radeon HD 6950 completely broken. Severity: normal Classification: Unclassified OS: All Reporter: v10lator(a)myway.de Hardware: Other Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI I own a Sapphire Radeon HD 6950. This card has a dual-bios where one of them has unlocked shaders (Radeon HD 6970). This is not a modded BIOS, it's made by Sapphire and fully supported by them. Now my problem is that with the Radeon HD 6950 BIOS (locked shaders) the GPU seems to hang as soon as compiz starts. With the unlocked BIOS it starts just fine. -- You are receiving this mail because: You are the assignee for the bug.

1 12

PCI Radeon RV100 detection hang on sparc64
by Meelis Roos 31 Aug '14

31 Aug '14

This is with initialyy unmodified 3.6.0-rc4-00101-g0809095 kernel in Ultra 10 (clean, without my "Video RAM" hack that I talked in other sparclinux posts). When I saw that Sun XVR-100 was detected fine by the kernel, I compiled radeon drm driver with modesetting enabled and tried it: [drm] radeon defaulting to kernel modesetting. [drm] radeon kernel modesetting enabled. PCI: Enabling device: (0000:02:02.0), cmd 82 [drm] initializing kernel modesetting (RV100 0x1002:0x5159 0x1002:0x0908). [drm] register mmio base: 0x10000000 [drm] register mmio size: 32768 [drm:radeon_device_init] *ERROR* Unable to find PCI I/O BAR And here the machine hangs. Debugging printk-s reveal that it does not find any active I/O port resources and then continues into initializing the card. Down in igp_read_bios_from_vram() it successfully ioremaps memory region 0 (vram_base=1ff08000000 and size=40000) and tries to read 2 bytes from there and hangs on reading bios[0]. With radeon.modeset=0, it boots and I collected the following info: 02:02.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV100 QY [Radeon 7000/VE] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices [AMD] nee ATI XVR-100 (supplied by Sun) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 (2000ns min) Interrupt: pin A routed to IRQ 16 Region 0: Memory at 08000000 (32-bit, prefetchable) [size=64M] Region 1: I/O ports at 0400 [disabled] [size=256] Region 2: Memory at 10000000 (32-bit, non-prefetchable) [size=32K] Region 3: [virtual] Memory at fffffe0100000000 (32-bit, non-prefetchable) [size=1] Region 4: [virtual] Memory at fffffe0100000000 (32-bit, non-prefetchable) [size=1] Region 5: [virtual] Memory at fffffe0100000000 (32-bit, non-prefetchable) [size=1] Expansion ROM at 10020000 [disabled] [size=128K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- # cat /proc/iomem 1fc00400000-1fc0040000f : ffb dac 1fc00600000-1fc00600983 : ffb fbc 1ff00000000-1ffffffffff : /pci@1f,0 1ff00002000-1ff00002fff : aic7xxx 1ff000a0000-1ff000bffff : Video RAM area 1ff000f0000-1ff000fffff : System ROM 1ff11000000-1ff11ffffff : atyfb 1ff12040000-1ff1204ffff : tg3 1ffc0000000-1ffdfffffff : IOMMU 1ffe0000000-1ffe000701f : sunhme 1ffe1000000-1ffe1ffffff : atyfb 1fff1000000-1fff1001fff : eeprom 1fff1200000-1fff120000f : cs4231 1fff13062f8-1fff13062ff : su 1fff13083f8-1fff13083ff : su 1fff1400000-1fff140003f : sab 1fff1400040-1fff140007f : sab 1fff1702000-1fff170200f : cs4231_pdma 1fff1704000-1fff170400f : cs4231_cdma 1fff1724000-1fff1724003 : power 1fff1726000-1fff1726003 : auxio -- Meelis Roos (mroos(a)linux.ee)

8 30

[Bug 40699] New: KMS on Thinkpad W500: no picture on external monitors with DisplayPort, but DVI works.
by bugzilla-daemon＠freedesktop.org 25 Aug '14

25 Aug '14

https://bugs.freedesktop.org/show_bug.cgi?id=40699 Summary: KMS on Thinkpad W500: no picture on external monitors with DisplayPort, but DVI works. Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: andreas.wallberg(a)gmail.com Hi all! I have troubles connecting my Thinkpad W500 running Arch Linux 64-bit to external monitors via DisplayPort (DP) while using Kernel Mode Setting (KMS) and a recent kernel (3.0.4). KMS + DP appears to be broken. The laptop has a ATI Radeon HD 3650 chip. I have tried two monitors: the HP ZR22w and the Eizo EV2333W. HP ZR22w ======== When KMS+DP is used on boot, I get this error message on the HP ZR22w: Input signal Out of Range Change Settings to 1920 x 1080 - 60Hz Inside X11, I am unable to get the screen going when KMS+DP is used. xrandr reports the screen being connected and that 1920x1080 is being sent to it. I still have the same error message. If I turn off KMS, the monitor works just fine with DP and X11 and xrandr do their jobs but I obviously lose all the niceties with KMS. If I use a DP->DVI adaptor and instead use the DVI connector on the monitor, KMS works just fine. However, using the 2.6.35 kernel in Fedora 14, KMS + DP works just fine. Eizo EV2333W ============ The same behavior as reported for the HP is true on the Eizo EV2333W monitor, but the latter provides more informative dialogs. Using the old Fedora 2.6.35 kernel and KMS+DP, the monitor shows this info about the video signal on the Information dialog: DisplayPort 1920x1080 fH: 76.5kHz fV: 59.9Hz Using a 3.0.4 kernel in Arch and KMS+DP, the monitor shows: Signal Error DisplayPort fD: 111.1MHz fH: 50.5kHz fV: 44.8Hz The "44.8" on the last line is read so there is obviously something wrong with the signal here. My guess is that the EDID handling is broken somehow on DP. I have tried adding various video= switches in grub to force the resolution but I am not really sure how apply them to the DisplayPort (unable to find any documentation on this) or whether it matters since the problem seems to be that the kernel is unaware it sends an incorrect video signal to the monitor. The only reference I have found to this monitor and KMS is this one, but I am not sure what to make of it: http://www.spinics.net/lists/dri-devel/msg13061.html I would much appreciate any pointers! What logs and config files would you like to follow up on this? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 9

[Bug 38917] New: [patch] Radeon clocks should not be limited to defaults
by bugzilla-daemon＠freedesktop.org 24 Aug '14

24 Aug '14

https://bugs.freedesktop.org/show_bug.cgi?id=38917 Summary: [patch] Radeon clocks should not be limited to defaults Product: DRI Version: unspecified Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: ahlaht(a)gmail.com Created an attachment (id=48691) --> (https://bugs.freedesktop.org/attachment.cgi?id=48691) Do not limit clocks.patch As of Linux 3.0-rc5 radeon_set_power_state() does not accept clock speeds higher than the defaults set by firmware. However on my HP laptop the default clock speeds are much lower than the maximum speeds accepted by the card. These are the default values on my HP laptop: engine 100000 kHz, memory 157000 kHz, vddc 900 mV And the other values: echo low > power_profile power_state 4, clock_mode 0, engine 100000, memory 150000, vddc 900 echo mid > power_profile power_state 4, clock_mode 1, engine 100000, memory 150000, vddc 900 echo high > power_profile power_state 1, clock_mode 2, engine 100000, memory 157000, vddc 1000 The problem occurs with the "high" profile and also when using "dynpm". See the provided patch, it fixes the problem. With the patch applied, correct frequencies are set: echo high > power_profile power_state 1, clock_mode 2, engine 550000, memory 800000, vddc 1000 Now the question remains: why where those checks added in the first place? They don't make sense to me unless default clock speeds are specified to be the highest possible. Also there is no such check for voltage. I do not know if this patch can break some other already broken systems, but it's important to fix the problem somehow because it severely limits 3d performance. The hardware is AMD Mobility Radeon HD 5650 (1002:68C1). I'm attaching a complete list of power states on this system. Also for reference here are the values used by Windows 7 when on AC power (I forgot to test battery power): Win 7 Catalyst PowerPlay disabled: engine 100000, memory 157000, vddc 900 Win 7 Catalyst PowerPlay enabled: engine 100000, memory 150000, vddc 900 GPU idle engine 450000, memory 800000, vddc 950 Light load engine 550000, memory 800000, vddc 1000 Heavy load The last 2 modes here are identical to what dynpm uses on Linux after the patch. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 7

[Bug 65822] New: [radeonsi] OpenCL is broken
by bugzilla-daemon＠freedesktop.org 21 Aug '14

21 Aug '14

https://bugs.freedesktop.org/show_bug.cgi?id=65822 Priority: medium Bug ID: 65822 Assignee: dri-devel(a)lists.freedesktop.org Summary: [radeonsi] OpenCL is broken Severity: normal Classification: Unclassified OS: Linux (All) Reporter: mustrumr97(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 80907 --> https://bugs.freedesktop.org/attachment.cgi?id=80907&action=edit Test results I've attached test results. a[i]=i+1 b[i]=2*a[i] Test 1: add uints and divide by 3 Test 2: test 1 done 10 times in a for loop Test 3: divide uints Test 4: if statement dependent on load with an addition in the false branch. Test 1 works, tests 2 and 3 halt and test 4 crashes. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 52054] New: gallium/opencl doesnt support includes for opencl kernels
by bugzilla-daemon＠freedesktop.org 21 Aug '14

21 Aug '14

https://bugs.freedesktop.org/show_bug.cgi?id=52054 Bug #: 52054 Summary: gallium/opencl doesnt support includes for opencl kernels Classification: Unclassified Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: alexxy(a)gentoo.org when running tests for opencl enabled jtr (http://www.openwall.com/john/) i get following error OpenCL platform 0: Default, 1 device(s). Using device 0: AMD JUNIPER 1 error generated. Compilation log: cl_input:17:10: fatal error: 'opencl_rar.h' file not found #include "opencl_rar.h" ^ OpenCL error (CL_INVALID_PROGRAM_EXECUTABLE) in file (rar_fmt.c) at line (588) - (Error creating kernel. Double-check kernel name?) xeon ~ # ./clInfo Found 1 platform(s). platform[(nil)]: profile: FULL_PROFILE platform[(nil)]: version: OpenCL 1.1 MESA platform[(nil)]: name: Default platform[(nil)]: vendor: Mesa platform[(nil)]: extensions: platform[(nil)]: Found 1 device(s). device[0xc82360]: NAME: AMD JUNIPER device[0xc82360]: VENDOR: X.Org device[0xc82360]: PROFILE: FULL_PROFILE device[0xc82360]: VERSION: OpenCL 1.1 MESA device[0xc82360]: EXTENSIONS: device[0xc82360]: DRIVER_VERSION: device[0xc82360]: Type: GPU device[0xc82360]: EXECUTION_CAPABILITIES: Kernel device[0xc82360]: GLOBAL_MEM_CACHE_TYPE: None (0) device[0xc82360]: CL_DEVICE_LOCAL_MEM_TYPE: Local (1) device[0xc82360]: SINGLE_FP_CONFIG: 0x7 device[0xc82360]: QUEUE_PROPERTIES: 0x2 device[0xc82360]: VENDOR_ID: 4098 device[0xc82360]: MAX_COMPUTE_UNITS: 1 device[0xc82360]: MAX_WORK_ITEM_DIMENSIONS: 3 device[0xc82360]: MAX_WORK_GROUP_SIZE: 256 device[0xc82360]: PREFERRED_VECTOR_WIDTH_CHAR: 16 device[0xc82360]: PREFERRED_VECTOR_WIDTH_SHORT: 8 device[0xc82360]: PREFERRED_VECTOR_WIDTH_INT: 4 device[0xc82360]: PREFERRED_VECTOR_WIDTH_LONG: 2 device[0xc82360]: PREFERRED_VECTOR_WIDTH_FLOAT: 4 device[0xc82360]: PREFERRED_VECTOR_WIDTH_DOUBLE: 2 device[0xc82360]: MAX_CLOCK_FREQUENCY: 0 device[0xc82360]: ADDRESS_BITS: 32 device[0xc82360]: MAX_MEM_ALLOC_SIZE: 0 device[0xc82360]: IMAGE_SUPPORT: 1 device[0xc82360]: MAX_READ_IMAGE_ARGS: 32 device[0xc82360]: MAX_WRITE_IMAGE_ARGS: 32 device[0xc82360]: IMAGE2D_MAX_WIDTH: 32768 device[0xc82360]: IMAGE2D_MAX_HEIGHT: 32768 device[0xc82360]: IMAGE3D_MAX_WIDTH: 32768 device[0xc82360]: IMAGE3D_MAX_HEIGHT: 32768 device[0xc82360]: IMAGE3D_MAX_DEPTH: 32768 device[0xc82360]: MAX_SAMPLERS: 16 device[0xc82360]: MAX_PARAMETER_SIZE: 1024 device[0xc82360]: MEM_BASE_ADDR_ALIGN: 128 device[0xc82360]: MIN_DATA_TYPE_ALIGN_SIZE: 128 device[0xc82360]: GLOBAL_MEM_CACHELINE_SIZE: 0 device[0xc82360]: GLOBAL_MEM_CACHE_SIZE: 0 device[0xc82360]: GLOBAL_MEM_SIZE: 201326592 device[0xc82360]: MAX_CONSTANT_BUFFER_SIZE: 65536 device[0xc82360]: MAX_CONSTANT_ARGS: 1 device[0xc82360]: LOCAL_MEM_SIZE: 32768 device[0xc82360]: ERROR_CORRECTION_SUPPORT: 0 device[0xc82360]: PROFILING_TIMER_RESOLUTION: 0 device[0xc82360]: ENDIAN_LITTLE: 1 device[0xc82360]: AVAILABLE: 1 device[0xc82360]: COMPILER_AVAILABLE: 1 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 2

← Newer
1
...
29
30
31
32
33
34
35
...
73
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2013