dri-devel August 2012

dri-devel@lists.freedesktop.org

145 participants
811 discussions

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot
by bugzilla-daemon＠freedesktop.org 30 Aug '12

30 Aug '12

https://bugs.freedesktop.org/show_bug.cgi?id=26891 --- Comment #35 from Alex Deucher <agd5f(a)yahoo.com> 2012-08-30 14:25:55 UTC --- (In reply to comment #34) > Alex, > Please see the DSDT table from a Macbook Pro booted in EFI mode. Maybe it will > give you some ideas for extracting the VBIOS. Sorry, I'm not really much of an ACPI or Mac expert. I don't see anything relevant. IIRC, the vbios on macs is only available in boot services so it's likely gone by the time the OS is loaded. You'd probably need the boot loader to grab it and store a copy somewhere so the OS can access it when it loads. I'm not sure how Apple does it. Someone more familiar with Macs may have some ideas. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[Bug 42708] drm:radeon_cs_ioctl "Failed to schedule IB" error after s2ram and wakeup
by bugzilla-daemon＠bugzilla.kernel.org 30 Aug '12

30 Aug '12

https://bugzilla.kernel.org/show_bug.cgi?id=42708 Alan <alan(a)lxorguk.ukuu.org.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alan(a)lxorguk.ukuu.org.uk Component|Video(Other) |Video(DRI - non Intel) AssignedTo|drivers_video-other@kernel- |drivers_video-dri@kernel-bu |bugs.osdl.org |gs.osdl.org -- 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 0

[PATCH] drm/radeon: fix dig encoder selection on DCE61
by alexdeucher＠gmail.com 30 Aug '12

30 Aug '12

From: Alex Deucher <alexander.deucher(a)amd.com> Was using the DCE41 code which was wrong. Fixes blank displays on a number of Trinity systems. Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> Cc: stable(a)vger.kernel.org --- drivers/gpu/drm/radeon/atombios_encoders.c | 31 +++++++++++++++++++++++---- 1 files changed, 26 insertions(+), 5 deletions(-) diff --git a/drivers/gpu/drm/radeon/atombios_encoders.c b/drivers/gpu/drm/radeon/atombios_encoders.c index 4a7f95e..6e8803a 100644 --- a/drivers/gpu/drm/radeon/atombios_encoders.c +++ b/drivers/gpu/drm/radeon/atombios_encoders.c @@ -1769,13 +1769,34 @@ static int radeon_atom_pick_dig_encoder(struct drm_encoder *encoder) struct radeon_crtc *radeon_crtc = to_radeon_crtc(encoder->crtc); struct radeon_encoder *radeon_encoder = to_radeon_encoder(encoder); struct drm_encoder *test_encoder; - struct radeon_encoder_atom_dig *dig; + struct radeon_encoder_atom_dig *dig = radeon_encoder->enc_priv; uint32_t dig_enc_in_use = 0; - /* DCE4/5 */ - if (ASIC_IS_DCE4(rdev)) { - dig = radeon_encoder->enc_priv; - if (ASIC_IS_DCE41(rdev)) { + if (ASIC_IS_DCE6(rdev)) { + /* DCE6 */ + switch (radeon_encoder->encoder_id) { + case ENCODER_OBJECT_ID_INTERNAL_UNIPHY: + if (dig->linkb) + return 1; + else + return 0; + break; + case ENCODER_OBJECT_ID_INTERNAL_UNIPHY1: + if (dig->linkb) + return 3; + else + return 2; + break; + case ENCODER_OBJECT_ID_INTERNAL_UNIPHY2: + if (dig->linkb) + return 5; + else + return 4; + break; + } + } else if (ASIC_IS_DCE4(rdev)) { + /* DCE4/5 */ + if (ASIC_IS_DCE41(rdev) && !ASIC_IS_DCE61(rdev)) { /* ontario follows DCE4 */ if (rdev->family == CHIP_PALM) { if (dig->linkb) -- 1.7.7.5

4 3

udl vs udlfb and EDID trouble
by Tvrtko Ursulin 30 Aug '12

30 Aug '12

Hi all, I've been playing with some DisplayLink adapters, six of them to be precise connected to six identical HDMI monitors. Under kernel 3.5 things did not really work for me apparently because of the udl driver's inability to fetch EDID. Interestingly, logged EDID blocks were different for each of the six monitors which suggests a serious bug somewhere. I've then went to see if I can load my own EDID, because I remember doing it via /sys/class/graphics/fb?/edid before, but that file was not there. (Is it possible to override EDID with the udl driver?) To cut the long story short, I figured out there are two drivers for this hardware. Fedora based 3.5 kernel builds and uses udl, while the older 3.3.2 I played with before builds and uses udlfb. (Why two drivers?) Now going back to 3.3.2 and udlfb, EDID got correctly fetched from all six monitors. Udlfb seems the EDID like this: # hexdump /sys/class/graphics/fb1/edid -C 00000000 00 ff ff ff ff ff ff 00 4c 2d 02 09 00 00 00 00 |........L-......| 00000010 29 15 01 03 80 29 17 78 0a ee 91 a3 54 4c 99 26 |)....).x....TL.&| 00000020 0f 50 54 bd ef 80 71 4f 81 c0 81 00 81 80 95 00 |.PT...qO........| 00000030 a9 c0 b3 00 01 01 02 3a 80 18 71 38 2d 40 58 2c |.......:..q8-@X,| 00000040 45 00 a0 5a 00 00 00 1e 66 21 56 aa 51 00 1e 30 |E..Z....f!V.Q..0| 00000050 46 8f 33 00 a0 5a 00 00 00 1e 00 00 00 fd 00 18 |F.3..Z..........| 00000060 4b 0f 51 17 00 0a 20 20 20 20 20 20 00 00 00 fc |K.Q... ....| 00000070 00 53 41 4d 53 55 4e 47 0a 20 20 20 20 20 01 f1 |.SAMSUNG. ..| 00000080 Below are the corrupt EDID blocks udl under 3.5 was getting. It's a lot of text but someone perhaps will be able to infer something from them. 2012-08-29T16:53:00.048995+01:00 kernel[] info:[ 18.343314] [drm] vendor descriptor length:2e data:2e 5f 01 002c 00 04 04 01 00 03 2012-08-29T16:53:00.048999+01:00 kernel[] err:[ 18.362643] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 199 2012-08-29T16:53:00.049008+01:00 kernel[] err:[ 18.362655] Raw EDID: 2012-08-29T16:53:00.049014+01:00 kernel[] err:[ 18.362662] 00 40 39 a0 ff ff ff ff 00 70 41 a0 ff ff ff ff 2012-08-29T16:53:00.049017+01:00 kernel[] err:[ 18.362667] 04 00 00 00 00 00 00 00 99 a9 77 61 00 88 ff ff 2012-08-29T16:53:00.049020+01:00 kernel[] err:[ 18.362672] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049024+01:00 kernel[] err:[ 18.362677] b0 a9 77 61 00 88 ff ff 30 95 6c 60 00 88 ff ff 2012-08-29T16:53:00.049101+01:00 kernel[] err:[ 18.362681] 7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049105+01:00 kernel[] err:[ 18.362686] 40 a6 c3 62 00 88 ff ff e0 16 00 00 00 00 00 00 2012-08-29T16:53:00.049108+01:00 kernel[] err:[ 18.362690] 40 00 00 00 00 00 00 00 58 82 02 00 00 00 00 00 2012-08-29T16:53:00.049119+01:00 kernel[] err:[ 18.362695] 00 00 00 00 40 00 38 00 07 00 40 00 1c 00 1b 00 2012-08-29T16:53:00.049124+01:00 kernel[] warning:[ 18.362707] usb 2-1.2: DVI-I-1: EDID invalid. 2012-08-29T16:53:00.049126+01:00 kernel[] info:[ 18.364581] fb1: udldrmfb frame buffer device 2012-08-29T16:53:00.049130+01:00 kernel[] info:[ 18.364594] [drm] Initialized udl 0.0.1 20120220 on minor 1 2012-08-29T16:53:00.049133+01:00 kernel[] info:[ 18.365388] [drm] vendor descriptor length:2e data:2e 5f 01 002c 00 04 04 01 00 03 2012-08-29T16:53:00.049136+01:00 kernel[] err:[ 18.421823] Raw EDID: 2012-08-29T16:53:00.049139+01:00 kernel[] err:[ 18.421842] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049142+01:00 kernel[] err:[ 18.421848] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049152+01:00 kernel[] err:[ 18.421853] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049157+01:00 kernel[] err:[ 18.421857] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049160+01:00 kernel[] err:[ 18.421862] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049163+01:00 kernel[] err:[ 18.421866] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049167+01:00 kernel[] err:[ 18.421871] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049170+01:00 kernel[] err:[ 18.421875] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049173+01:00 kernel[] warning:[ 18.421889] usb 2-1.3: DVI-I-2: EDID invalid. 2012-08-29T16:53:00.049182+01:00 kernel[] info:[ 18.424921] fb2: udldrmfb frame buffer device 2012-08-29T16:53:00.049187+01:00 kernel[] info:[ 18.424987] [drm] Initialized udl 0.0.1 20120220 on minor 2 2012-08-29T16:53:00.049190+01:00 kernel[] info:[ 18.428455] [drm] vendor descriptor length:2e data:2e 5f 01 002c 00 04 04 01 00 03 2012-08-29T16:53:00.049193+01:00 kernel[] err:[ 18.491450] Raw EDID: 2012-08-29T16:53:00.049196+01:00 kernel[] err:[ 18.491469] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049199+01:00 kernel[] err:[ 18.491475] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049202+01:00 kernel[] err:[ 18.491479] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049206+01:00 kernel[] err:[ 18.491484] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049215+01:00 kernel[] err:[ 18.491489] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049220+01:00 kernel[] err:[ 18.491493] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049224+01:00 kernel[] err:[ 18.491497] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049227+01:00 kernel[] err:[ 18.491502] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049230+01:00 kernel[] warning:[ 18.491515] usb 2-1.4: DVI-I-3: EDID invalid. 2012-08-29T16:53:00.049233+01:00 kernel[] info:[ 18.494223] fb3: udldrmfb frame buffer device 2012-08-29T16:53:00.049236+01:00 kernel[] info:[ 18.494241] [drm] Initialized udl 0.0.1 20120220 on minor 3 2012-08-29T16:53:00.049246+01:00 kernel[] info:[ 18.495604] [drm] vendor descriptor length:2e data:2e 5f 01 002c 00 04 04 01 00 03 2012-08-29T16:53:00.049252+01:00 kernel[] err:[ 18.525219] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 87 2012-08-29T16:53:00.049254+01:00 kernel[] err:[ 18.525231] Raw EDID: 2012-08-29T16:53:00.049257+01:00 kernel[] err:[ 18.525238] 00 40 32 a0 ff ff ff ff 00 c0 32 a0 ff ff ff ff 2012-08-29T16:53:00.049260+01:00 kernel[] err:[ 18.525243] 04 00 00 00 00 00 00 00 99 80 7e 61 00 88 ff ff 2012-08-29T16:53:00.049264+01:00 kernel[] err:[ 18.525248] 18 b0 92 60 00 88 ff ff 98 78 1c 50 00 88 ff ff 2012-08-29T16:53:00.049267+01:00 kernel[] err:[ 18.525253] 30 b0 92 60 00 88 ff ff b0 78 1c 50 00 88 ff ff 2012-08-29T16:53:00.049270+01:00 kernel[] err:[ 18.525257] 40 73 1c 50 00 88 ff ff 40 73 1c 50 00 88 ff ff 2012-08-29T16:53:00.049280+01:00 kernel[] err:[ 18.525262] 00 01 5d 62 00 88 ff ff e0 ba 7e 61 00 88 ff ff 2012-08-29T16:53:00.049285+01:00 kernel[] err:[ 18.525266] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049288+01:00 kernel[] err:[ 18.525271] 00 00 00 00 40 00 38 00 07 00 40 00 1c 00 1b 00 2012-08-29T16:53:00.049291+01:00 kernel[] warning:[ 18.525283] usb 2-1.1.1: DVI-I-4: EDID invalid. 2012-08-29T16:53:00.049294+01:00 kernel[] info:[ 18.527493] fb4: udldrmfb frame buffer device 2012-08-29T16:53:00.049297+01:00 kernel[] info:[ 18.527512] [drm] Initialized udl 0.0.1 20120220 on minor 4 2012-08-29T16:53:00.049301+01:00 kernel[] info:[ 18.529482] [drm] vendor descriptor length:2e data:2e 5f 01 002c 00 04 04 01 00 03 2012-08-29T16:53:00.049311+01:00 kernel[] err:[ 18.554576] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 171 2012-08-29T16:53:00.049315+01:00 kernel[] err:[ 18.554584] Raw EDID: 2012-08-29T16:53:00.049318+01:00 kernel[] err:[ 18.554588] 00 10 bf 12 00 c9 ff ff 00 20 d7 12 00 c9 ff ff 2012-08-29T16:53:00.049321+01:00 kernel[] err:[ 18.554591] 04 00 00 00 00 00 00 00 98 7c 1c 50 00 88 ff ff 2012-08-29T16:53:00.049324+01:00 kernel[] err:[ 18.554594] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049328+01:00 kernel[] err:[ 18.554596] b0 7c 1c 50 00 88 ff ff b0 73 1c 50 00 88 ff ff 2012-08-29T16:53:00.049331+01:00 kernel[] err:[ 18.554598] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049334+01:00 kernel[] err:[ 18.554600] 80 4d 43 60 00 88 ff ff 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049343+01:00 kernel[] err:[ 18.554603] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049348+01:00 kernel[] err:[ 18.554605] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.049351+01:00 kernel[] warning:[ 18.554613] usb 2-1.1.2: DVI-I-5: EDID invalid. 2012-08-29T16:53:00.049354+01:00 kernel[] info:[ 18.558351] fb5: udldrmfb frame buffer device 2012-08-29T16:53:00.049357+01:00 kernel[] info:[ 18.558366] [drm] Initialized udl 0.0.1 20120220 on minor 5 2012-08-29T16:53:00.049361+01:00 kernel[] info:[ 18.561871] [drm] vendor descriptor length:2e data:2e 5f 01 002c 00 04 04 01 00 03 2012-08-29T16:53:00.063248+01:00 dbus[994] notice: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper) 2012-08-29T16:53:00.063258+01:00 dbus-daemon[994] info: dbus[994]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper) 2012-08-29T16:53:00.074611+01:00 kernel[] err:[ 18.584027] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 212 2012-08-29T16:53:00.074618+01:00 kernel[] err:[ 18.584039] Raw EDID: 2012-08-29T16:53:00.074622+01:00 kernel[] err:[ 18.584046] 01 00 00 00 00 00 00 00 08 03 47 62 00 88 ff ff 2012-08-29T16:53:00.074626+01:00 kernel[] err:[ 18.584051] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.074629+01:00 kernel[] err:[ 18.584056] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.074633+01:00 kernel[] err:[ 18.584061] 51 02 00 00 00 00 00 00 e0 be c2 81 ff ff ff ff 2012-08-29T16:53:00.074636+01:00 kernel[] err:[ 18.584065] 00 00 00 00 00 00 00 00 58 30 9d 66 00 88 ff ff 2012-08-29T16:53:00.074640+01:00 kernel[] err:[ 18.584070] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.074643+01:00 kernel[] err:[ 18.584074] 58 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.074647+01:00 kernel[] err:[ 18.584078] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2012-08-29T16:53:00.074650+01:00 kernel[] warning:[ 18.584091] usb 2-1.1.3: DVI-I-6: EDID invalid. 2012-08-29T16:53:00.074653+01:00 kernel[] info:[ 18.586045] fb6: udldrmfb frame buffer device 2012-08-29T16:53:00.074656+01:00 kernel[] info:[ 18.586063] [drm] Initialized udl 0.0.1 20120220 on minor 6 Tvrtko

2 1

[RFC] New dma_buf -> EGLImage EGL extension
by Tom Cooksey 30 Aug '12

30 Aug '12

Hi All, Over the last few months I've been working on & off with a few people from Linaro on a new EGL extension. The extension allows constructing an EGLImage from a (set of) dma_buf file descriptors, including support for multi-plane YUV. I envisage the primary use-case of this extension to be importing video frames from v4l2 into the EGL/GLES graphics driver to texture from. Originally the intent was to develop this as a Khronos-ratified extension. However, this is a little too platform-specific to be an officially sanctioned Khronos extension. It also goes against the general "EGLStream" direction the EGL working group is going in. As such, the general feeling was to make this an EXT "multi-vendor" extension with no official stamp of approval from Khronos. As this is no-longer intended to be a Khronos extension, I've re-written it to be a lot more Linux & dma_buf specific. It also allows me to circulate the extension more widely (I.e. To those outside Khronos membership). ARM are implementing this extension for at least our Mali-T6xx driver and likely earlier drivers too. I am sending this e-mail to solicit feedback, both from other vendors who might implement this extension (Mesa3D?) and from potential users of the extension. However, any feedback is welcome. Please find the extension text as it currently stands below. There several open issues which I've proposed solutions for, but I'm not really happy with those proposals and hoped others could chip-in with better ideas. There are likely other issues I've not thought about which also need to be added and addressed. Once there's a general consensus or if no-one's interested, I'll update the spec, move it out of Draft status and get it added to the Khronos registry, which includes assigning values for the new symbols. Cheers, Tom ---------8<--------- Name EXT_image_dma_buf_import Name Strings EGL_EXT_image_dma_buf_import Contributors Jesse Barker Rob Clark Tom Cooksey Contacts Jesse Barker (jesse 'dot' barker 'at' linaro 'dot' org) Tom Cooksey (tom 'dot' cooksey 'at' arm 'dot' com) Status DRAFT Version Version 3, August 16, 2012 Number EGL Extension ??? Dependencies EGL 1.2 is required. EGL_KHR_image_base is required. The EGL implementation must be running on a Linux kernel supporting the dma_buf buffer sharing mechanism. This extension is written against the wording of the EGL 1.2 Specification. Overview This extension allows creating an EGLImage from a Linux dma_buf file descriptor or multiple file descriptors in the case of multi-plane YUV images. New Types None New Procedures and Functions None New Tokens Accepted by the <target> parameter of eglCreateImageKHR: EGL_LINUX_DMA_BUF_EXT Accepted as an attribute in the <attrib_list> parameter of eglCreateImageKHR: EGL_LINUX_DRM_FOURCC_EXT EGL_DMA_BUF_PLANE0_FD_EXT EGL_DMA_BUF_PLANE0_OFFSET_EXT EGL_DMA_BUF_PLANE0_PITCH_EXT EGL_DMA_BUF_PLANE1_FD_EXT EGL_DMA_BUF_PLANE1_OFFSET_EXT EGL_DMA_BUF_PLANE1_PITCH_EXT EGL_DMA_BUF_PLANE2_FD_EXT EGL_DMA_BUF_PLANE2_OFFSET_EXT EGL_DMA_BUF_PLANE2_PITCH_EXT Additions to Chapter 2 of the EGL 1.2 Specification (EGL Operation) Add to section 2.5.1 "EGLImage Specification" (as defined by the EGL_KHR_image_base specification), in the description of eglCreateImageKHR: "Values accepted for <target> are listed in Table aaa, below. +-------------------------+--------------------------------------------+ | <target> | Notes | +-------------------------+--------------------------------------------+ | EGL_LINUX_DMA_BUF_EXT | Used for EGLImages imported from Linux | | | dma_buf file descriptors | +-------------------------+--------------------------------------------+ Table aaa. Legal values for eglCreateImageKHR <target> parameter ... If <target> is EGL_LINUX_DMA_BUF_EXT, <dpy> must be a valid display, <ctx> must be EGL_NO_CONTEXT, and <buffer> must be NULL, cast into the type EGLClientBuffer. The details of the image is specified by the attributes passed into eglCreateImageKHR. Required attributes and their values are as follows: * EGL_WIDTH & EGL_HEIGHT: The logical dimensions of the buffer in pixels * EGL_LINUX_DRM_FOURCC_EXT: The pixel format of the buffer, as specified by drm_fourcc.h and used as the pixel_format parameter of the drm_mode_fb_cmd2 ioctl. * EGL_DMA_BUF_PLANE0_FD_EXT: The dma_buf file descriptor of plane 0 of the image. * EGL_DMA_BUF_PLANE0_OFFSET_EXT: The offset from the start of the dma_buf of the first sample in plane 0, in bytes. * EGL_DMA_BUF_PLANE0_PITCH_EXT: The number of bytes between the start of subsequent rows of samples in plane 0. May have special meaning for non-linear formats. For images in an RGB color-space or those using a single-plane YUV format, only the first plane's file descriptor, offset & pitch should be specified. For semi-planar YUV formats, the chroma samples are stored in plane 1 and for fully planar formats, U-samples are stored in plane 1 and V-samples are stored in plane 2. Planes 1 & 2 are specified by the following attributes, which have the same meanings as defined above for plane 0: * EGL_DMA_BUF_PLANE1_FD_EXT * EGL_DMA_BUF_PLANE1_OFFSET_EXT * EGL_DMA_BUF_PLANE1_PITCH_EXT * EGL_DMA_BUF_PLANE2_FD_EXT * EGL_DMA_BUF_PLANE2_OFFSET_EXT * EGL_DMA_BUF_PLANE2_PITCH_EXT If eglCreateImageKHR is successful for a EGL_LINUX_DMA_BUF_EXT target, the EGL takes ownership of the file descriptor and is responsible for closing it, which it may do at any time while the EGLDisplay is initialized." Add to the list of error conditions for eglCreateImageKHR: "* If <target> is EGL_LINUX_DMA_BUF_EXT and <buffer> is not NULL, the error EGL_BAD_PARAMETER is generated. * If <target> is EGL_LINUX_DMA_BUF_EXT, and the list of attributes is incomplete, EGL_BAD_PARAMETER is generated. * If <target> is EGL_LINUX_DMA_BUF_EXT, and the EGL_LINUX_DRM_FOURCC_EXT attribute is set to a format not supported by the EGL, EGL_BAD_MATCH is generated. * If <target> is EGL_LINUX_DMA_BUF_EXT, and the EGL_LINUX_DRM_FOURCC_EXT attribute indicates a single-plane format, EGL_BAD_ATTRIBUTE is generated if any of the EGL_DMA_BUF_PLANE1_* or EGL_DMA_BUF_PLANE2_* attributes are specified. Issues 1. Should this be a KHR or EXT extension? ANSWER: EXT. Khronos EGL working group not keen on this extension as it is seen as contradicting the EGLStream direction the specification is going in. The working group recommends creating additional specs to allow an EGLStream producer/consumer connected to v4l2/DRM or any other Linux interface. 2. Should this be a generic any platform extension, or a Linux-only extension which explicitly states the handles are dma_buf fds? ANSWER: There's currently no intention to port this extension to any OS not based on the Linux kernel. Consequently, this spec can be explicitly written against Linux and the dma_buf API. 3. Does ownership of the file descriptor pass to the EGL library? PROPOSAL: If eglCreateImageKHR is successful, EGL assumes ownership of the file descriptors and is responsible for closing them. 4. How are the different YUV color spaces handled (BT.709/BT.601)? Open issue, still TBD. Doesn't seem to be specified by either the v4l2 or DRM APIs. PROPOSAL: Undefined and implementation/format dependent. 5. What chroma-siting is used for sub-sampled YUV formats? Open issue, still TBD. Doesn't seem to be specified by either the v4l2 or DRM APIs. PROPOSAL: Undefined and implementation/format dependent. 5. How can an application query which formats the EGL implementation supports? PROPOSAL: Don't provide a query mechanism but instead add an error condition that EGL_BAD_MATCH is raised if the EGL implementation doesn't support that particular format. 5. Which image formats should be supported and how is format specified? Open issue, still TBD. Seem to be two options 1) specify a new enum in this specification and enumerate all possible formats. 2) Use an existing enum already in Linux, either v4l2_mbus_pixelcode and/or those formats listed in drm_fourcc.h? PROPOSAL: Go for option 2) and just use values defined in drm_fourcc.h. Revision History #3 (Tom Cooksey, August 16, 2012) - Changed name from EGL_EXT_image_external and re-written language to explicitly state this for use with Linux & dma_buf. - Added a list of issues, including some still open ones. #2 (Jesse Barker, May 30, 2012) - Revision to split eglCreateImageKHR functionality from export Functionality. - Update definition of EGLNativeBufferType to be a struct containing a list of handles to support multi-buffer/multi-planar formats. #1 (Jesse Barker, March 20, 2012) - Initial draft.

1 0

[Bug 42182] Screen brightness is still set to MINIMUM and am unable to change it
by bugzilla-daemon＠bugzilla.kernel.org 30 Aug '12

30 Aug '12

https://bugzilla.kernel.org/show_bug.cgi?id=42182 Alex Deucher <alexdeucher(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alexdeucher(a)gmail.com --- Comment #1 from Alex Deucher <alexdeucher(a)gmail.com> 2012-08-30 13:46:33 --- Is this still an issue with a newer kernel? Make sure your kernel has the acpi backlight controls included. My drm-next queue for 3.7 has support for native backlight control (assuming the OEM uses the on chip backlight controller) if you can't get the acpi backlight controls working. http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.7-wip -- 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 0

[Bug 42182] Screen brightness is still set to MINIMUM and am unable to change it
by bugzilla-daemon＠bugzilla.kernel.org 30 Aug '12

30 Aug '12

https://bugzilla.kernel.org/show_bug.cgi?id=42182 Alan <alan(a)lxorguk.ukuu.org.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alan(a)lxorguk.ukuu.org.uk Component|x86-64 |Video(DRI - non Intel) AssignedTo|platform_x86_64@kernel-bugs |drivers_video-dri@kernel-bu |.osdl.org |gs.osdl.org Product|Platform Specific/Hardware |Drivers -- 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 0

[PATCH] DRM DRIVERS: Remove unnecessary test for ARM.
by Robert P. J. Day 30 Aug '12

30 Aug '12

Since arch/arm/include/asm/pgtable.h contains: #define io_remap_pfn_range(vma,from,pfn,size,prot) \ remap_pfn_range(vma, from, pfn, size, prot) there is no point treating ARM as a special case in distinguishing between remap_pfn_range() and io_remap_pfn_range(). Signed-off-by: Robert P. J. Day <rpjday(a)crashcourse.ca> --- diff --git a/drivers/gpu/drm/drm_vm.c b/drivers/gpu/drm/drm_vm.c index 961ee08..34e6503 100644 --- a/drivers/gpu/drm/drm_vm.c +++ b/drivers/gpu/drm/drm_vm.c @@ -619,20 +619,11 @@ int drm_mmap_locked(struct file *filp, struct vm_area_struct *vma) offset = drm_core_get_reg_ofs(dev); vma->vm_flags |= VM_IO; /* not in core dump */ vma->vm_page_prot = drm_io_prot(map->type, vma); -#if !defined(__arm__) if (io_remap_pfn_range(vma, vma->vm_start, (map->offset + offset) >> PAGE_SHIFT, vma->vm_end - vma->vm_start, vma->vm_page_prot)) return -EAGAIN; -#else - if (remap_pfn_range(vma, vma->vm_start, - (map->offset + offset) >> PAGE_SHIFT, - vma->vm_end - vma->vm_start, - vma->vm_page_prot)) - return -EAGAIN; -#endif - DRM_DEBUG(" Type = %d; start = 0x%lx, end = 0x%lx," " offset = 0x%llx\n", map->type, -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================

1 0

drm_vm.c: many arches equate remap_pfn_range() and io_remap_pfn_range()
by Robert P. J. Day 30 Aug '12

30 Aug '12

a pedantic observation, you can do with it what you wish (i'm not a list subscriber). in drivers/gpu/drm/drm_vm.c, we read (line 629): #if !defined(__arm__) if (io_remap_pfn_range(vma, vma->vm_start, (map->offset + offset) >> PAGE_SHIFT, vma->vm_end - vma->vm_start, vma->vm_page_prot)) return -EAGAIN; #else if (remap_pfn_range(vma, vma->vm_start, (map->offset + offset) >> PAGE_SHIFT, vma->vm_end - vma->vm_start, vma->vm_page_prot)) return -EAGAIN; #endif suggesting that only with ARM need we distinguish between those two routines. but for various architectures, in pgtable.h, you can see: #define io_remap_pfn_range remap_pfn_range even the arm file contains: #define io_remap_pfn_range(vma,from,pfn,size,prot) \ remap_pfn_range(vma, from, pfn, size, prot) so it's not clear what the preprocessor test is for. admittedly, it should work, it just seems unnecessary. and it makes the code more confusing than it needs to be, but perhaps i've just misread something. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================

2 3

[Bug 40622] New: [radeon] - kms wrong resolution mode used after backlight on/off switch
by bugzilla-daemon＠bugzilla.kernel.org 30 Aug '12

30 Aug '12

https://bugzilla.kernel.org/show_bug.cgi?id=40622 Summary: [radeon] - kms wrong resolution mode used after backlight on/off switch Product: Drivers Version: 2.5 Kernel Version: 3.0 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: tkrah(a)fachschaft.imn.htwk-leipzig.de Regression: Yes Hi, updated to recent 3.0 kernel (oneiric ubuntu build package) and got some behaviour i would not expect. Got a Samsung P35 Notebook - pressing my "backlight" Key does give this in dmesg: keyboard: can't emulate rawmode for keycode 240 On and Off, both a mesage. The native resolution is 1400x1050 of my LVDS Panel. [ 23.577259] [drm] Panel ID String: Samsung LTN150P1-L02 [ 23.577264] [drm] Panel Size 1400x1050 But after pressing backlight twice (off+on) my screen resolution does change to 1600x1024 - afaik not supported, at least it is not mentioned in Xorg.0.log for detected valid panel Modelines. But it does use this mode after backlight switch: (II) RADEON(0): Allocate new frame buffer 1600x1024 stride 1600 I wonder why? However i am forced to switch my resolution back everytime - don't know if its good for the panel to use this resolution (because i don't know if it will blast my panel away i'll set prio to high - if this won't going to happen please set it back to normal ;-) ). Bug or Feature? Both (message and resolution change) did not happen with 2.6.32.x before, so i guess its a regression, is it? Tell me if you need more input or kernel testing. -- 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 7

← Newer
1
...
45
46
47
48
49
50
51
...
82
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel August 2012