On Thu, Aug 25, 2016 at 9:48 PM, Xinliang Liu
wrote:
> On 17 August 2016 at 19:11, Daniel Vetter wrote:
>> On Wed, Aug 17, 2016 at 07:02:01PM +0800, Xinliang Liu wrote:
>>> Hi,
>>>
>>> On 17 August 2016 at 18:17, Daniel Vetter wrote:
>>> > I just broke the build :(
>>> >
>>> > Note that the
On Thu, Aug 25, 2016 at 05:55:18PM +0530, Archit Taneja wrote:
> On 08/18/2016 02:26 AM, Daniel Vetter wrote:
> > +void drm_mode_object_unregister(struct drm_device *dev,
> > + struct drm_mode_object *object);
>
> Alignment issue in the declaration here.
Again I don't
On Thu, Aug 25, 2016 at 05:53:51PM +0530, Archit Taneja wrote:
>
> Hi,
>
> On 08/18/2016 02:25 AM, Daniel Vetter wrote:
> > Same treatment as before. Only hiccup is drm_crtc_mask, which
> > unfortunately can't be resolved until drm_crtc.h is less of a monster.
> > Untangle the header loop with a
Various cleanups to the DRM core initialization and exit handlers:
- Register chrdev last: Once register_chrdev() returns, open() will
succeed on the given chrdevs. This is usually not an issue, as no
chardevs are registered, yet. However, nodes can be created by
user-space via
vel/attachments/20160825/1fb80d4a/attachment.html>
tps://lists.freedesktop.org/archives/dri-devel/attachments/20160825/dcd93298/attachment.html>
On Thu, Aug 25, 2016 at 07:13:07PM +0200, Noralf Trønnes wrote:
>
> Den 25.08.2016 08:30, skrev Daniel Vetter:
> > On Wed, Aug 24, 2016 at 08:38:37PM +0200, Noralf Trønnes wrote:
> > > Den 23.08.2016 08:25, skrev Daniel Vetter:
> > > > Our update function is hooked to the single plane, which
2016ë
08ì 25ì¼ 17:42ì Daniel Vetter ì´(ê°) ì´ ê¸:
> On Thu, Aug 25, 2016 at 05:06:55PM +0900, Inki Dae wrote:
>>
>>
>> 2016ë
08ì 24ì¼ 20:57ì Daniel Vetter ì´(ê°) ì´ ê¸:
>>> On Wed, Aug 24, 2016 at 08:44:24PM +0900, Inki Dae wrote:
Hi,
2016ë
08ì 23ì¼
Den 25.08.2016 15:09, skrev Rob Herring:
> On Mon, Aug 22, 2016 at 3:25 PM, Noralf Trønnes
> wrote:
>> The SimpleDRM driver binds to simple-framebuffer devices and provides a
>> DRM/KMS API. It provides only a single CRTC+encoder+connector combination
>> plus one initial mode.
>>
>> Userspace
tps://lists.freedesktop.org/archives/dri-devel/attachments/20160825/49c1d3ab/attachment.html>
n HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/a493d8d8/attachment.html>
Den 25.08.2016 08:30, skrev Daniel Vetter:
> On Wed, Aug 24, 2016 at 08:38:37PM +0200, Noralf Trønnes wrote:
>> Den 23.08.2016 08:25, skrev Daniel Vetter:
>>> Our update function is hooked to the single plane, which might not get
>>> called for crtc-only updates. Which is surprising, so fix this
amdgpu loads amdkfd via symbol_request(). Add a softdep hint so that
userspace knows that amdgpu needs amdkfd in the initrd.
Reported-and-tested-by: Martin Jambor
Signed-off-by: Michal Marek
---
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 1 +
1 file changed, 1 insertion(+)
diff --git
--
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/b93527b5/attachment-0001.html>
--
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/d3b06208/attachment.html>
.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/d7681b49/attachment.html>
are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/351bfa18/attachment.html>
next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/6e9ceb51/attachment-0001.html>
bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/ff525be7/attachment.html>
tps://lists.freedesktop.org/archives/dri-devel/attachments/20160825/54d691a2/attachment.html>
On 08/18/2016 02:26 AM, Daniel Vetter wrote:
> They work exactly the same now, after the refcounting unification a bit
> ago. The only reason they're distinct is backwards compat with existing
> userspace.
>
> Cc: Daniel Stone
> Signed-off-by: Daniel Vetter
Reviewed-by: Archit Taneja
Archit
On 08/18/2016 02:26 AM, Daniel Vetter wrote:
> I figured an overview section here is overkill, and better
> to just document the 2 structures themselves well enough.
>
> Signed-off-by: Daniel Vetter
> ---
> drivers/gpu/drm/drm_mode_object.c | 9 +++
> include/drm/drm_mode_object.h |
On 08/18/2016 02:26 AM, Daniel Vetter wrote:
> This just contains the base property classes and all the code to
> handle blobs. I think for any kind of standardized/shared properties
> it's better to have separate files - this is fairly big already as-is.
>
> v2: resurrect misplaced hunk (Daniel
On 08/18/2016 02:26 AM, Daniel Vetter wrote:
> It's part of the drm fourcc handling code, mapping the old depth/bpp
> values to new fourcc codes.
Reviewed-by: Archit Taneja
>
> Cc: Laurent Pinchart
> Signed-off-by: Daniel Vetter
> ---
> drivers/gpu/drm/drm_crtc.c | 43
>
On 08/18/2016 02:26 AM, Daniel Vetter wrote:
> Just for the struct drm_mode_object base class. The header file was
> already partially extracted to help untangle the include loops.
>
> v2:
> - Also move the generic get/set property ioctls. At first this seemed
>like a bad idea since it
On 08/18/2016 02:26 AM, Daniel Vetter wrote:
> It's only used in drm_mode_object_get_properties, and we can compute
> it there directly with a bit of code shuffling.
>
Reviewed-by: Archit Taneja
> Signed-off-by: Daniel Vetter
> ---
> drivers/gpu/drm/drm_mode_object.c | 31
On 08/18/2016 02:25 AM, Daniel Vetter wrote:
> - Move missing bits into struct drm_encoder docs.
> - Explain that encoders are 95% internal and only 5% uapi, and that in
>general the uapi part is broken.
> - Remove verbose comments for functions not exposed to drivers.
>
> Signed-off-by:
Hi,
On 08/18/2016 02:25 AM, Daniel Vetter wrote:
> Same treatment as before. Only hiccup is drm_crtc_mask, which
> unfortunately can't be resolved until drm_crtc.h is less of a monster.
> Untangle the header loop with a forward delcaration for that static
s/delcaration/declaration
> inline.
>
On 08/24/2016 11:35 PM, Xiang, Haihao wrote:
>
>
>> -Original Message-
>> From: Randy Li [mailto:randy.li at rock-chips.com]
>> Sent: Wednesday, August 24, 2016 6:30 PM
>> To: Xiang, Haihao ; libva at lists.freedesktop.org
>> Cc: nicolas.dufresne at collabora.co.uk; Balachandran, Sreerenj
2016ë
08ì 24ì¼ 20:57ì Daniel Vetter ì´(ê°) ì´ ê¸:
> On Wed, Aug 24, 2016 at 08:44:24PM +0900, Inki Dae wrote:
>> Hi,
>>
>> 2016ë
08ì 23ì¼ 18:41ì Daniel Stone ì´(ê°) ì´ ê¸:
>>> Hi,
>>>
>>> On 22 August 2016 at 16:23, Rob Clark wrote:
I guess a lot comes down to 'how
On Thu, Aug 25, 2016 at 04:35:05PM +0200, David Herrmann wrote:
> The *only* known user of GETCLIENT is libva, which uses it to check
> whether its own context is authenticated. It used to iterate all clients,
> look for one that matches its own pid and then check its state.
>
> The entire
The drm_core.h header contains a set of constants meant to be used
throughout DRM. However, as it turns out, they're each used just once and
don't bring any benefit. They're also grossly mis-named and lack
name-spacing. This patch inlines them, or moves them into drm_internal.h
as appropriate:
-
The *only* known user of GETCLIENT is libva, which uses it to check
whether its own context is authenticated. It used to iterate all clients,
look for one that matches its own pid and then check its state.
The entire purpose for us to still have a GETCLIENT implementation is to
serve libva. So
|FIXED
Status|NEW |RESOLVED
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/1ec23ad2/attachment.html>
On 25 August 2016 at 12:14, Daniel Vetter wrote:
> On Thu, Aug 04, 2016 at 09:15:07AM +0100, Chris Wilson wrote:
>> On Thu, Aug 04, 2016 at 10:06:57AM +0200, David Herrmann wrote:
>> > The legacy DRI1 drivers expose highly broken interfaces to user-space. No
>> > modern system should enable them,
nalogix_dp_reg.c | 451
> ++---
> 3 files changed, 210 insertions(+), 555 deletions(-)
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/a6944994/attachment.html>
Add support for cdn DP controller which is embedded in the rk3399
SoCs. The DP is compliant with DisplayPort Specification,
Version 1.3, This IP is compatible with the rockchip type-c PHY IP.
There is a uCPU in DP controller, it need a firmware to work,
please put the firmware file to
Add blue-and-red-crossed -property to lcdc node. The am335x-evmsk has blue
and red wires crossed to get 24-bit RGB (and 16-bit BGR) support. See
details in Documentation/devicetree/bindings/display/tilcdc/tilcdc.txt.
Signed-off-by: Jyri Sarha
---
arch/arm/boot/dts/am335x-evmsk.dts | 2 ++
1
Whitespace cleanup of lcdc related nodes. Do all indentation and
alignment with tabs instead of spaces.
Signed-off-by: Jyri Sarha
---
arch/arm/boot/dts/am335x-evmsk.dts | 40 +++---
1 file changed, 20 insertions(+), 20 deletions(-)
diff --git
Add blue-and-red-crossed -property to lcdc node. The am335x-evm has blue
and red wires crossed to get 24-bit RGB (and 16-bit BGR) support. See
details in Documentation/devicetree/bindings/display/tilcdc/tilcdc.txt.
Signed-off-by: Jyri Sarha
---
arch/arm/boot/dts/am335x-evm.dts | 2 ++
1 file
Add comments on how to support 24 bit RGB mode. In other words how to
convert BGR from LCDC to RGB in tda19988 with video-ports property and
how to tell LCDC that blue and red wires are crossed, with
blue-and-red-crossed LCDC boolean property. This changes supported
color formats from 16 bit RGB
Choose console BPP that supports RGB and remove the old fbdev bpp
selection code. LCDC on AM335x has red and blue wires switched between
24 bit and 16 bit colors. If 24 format is wired for RGB colors, the 16
bit format is wired for BGR. drm_fbdev_cma_init() does not currently
like anything else
Add "blue-and-red-crossed"-device tree property and update devicetree
binding document. The red and blue components are reversed between 24
and 16 bit modes on am335x LCDC output pins. To get 24 RGB format the
red and blue wires has to be crossed and this in turn causes 16 colors
output to be in
drm_helper_disable_unused_functions() should not be called by atomic
drivers.
Signed-off-by: Jyri Sarha
---
drivers/gpu/drm/tilcdc/tilcdc_drv.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpu/drm/tilcdc/tilcdc_drv.c
b/drivers/gpu/drm/tilcdc/tilcdc_drv.c
index 3404d24..e45c268
Changes since v1:
- Change the blue-and-red-wiring property to boolean blue-and-red-crossed
- This breaks to little backward compatibility the earlier series had, but
makes the binding more straight forward
- This changes requires changes to am335x-evm and am335x-evmsk dts-files
- The
On Mon, Aug 8, 2016 at 1:33 AM, Jani Nikula
wrote:
> On Sat, 06 Aug 2016, Rodrigo Vivi wrote:
>> This patch is blocking PSR on panels that we know that our hardware support.
>
> And it also fixes a regression on Linus' laptop, and it's been merged
> upstream...
yeap, this patch is like setting
On Mon, 22 Aug 2016, Tony Vroon wrote:
> Recent i915 development appears to have stopped my eDP panel from being
> driven correctly. The last working release was 4.6.7; any 4.7 kernel
> will not drive the screen and 4.8-RC3 does not drive the screen either.
> I have both 4.6.7 and 4.8.0-rc3
On Thu, Aug 25, 2016 at 11:04:32AM +0200, Andrea Merello wrote:
> Up to now, once a bridge has been attached to a DRM device, it cannot
> be undone.
>
> In particular you couldn't rmmod/insmod a DRM driver that uses a bridge,
> because the bridge would remain bound to the first (dead) driver
On Thu, Aug 25, 2016 at 08:45:25PM +0900, Inki Dae wrote:
>
>
> 2016ë
08ì 25ì¼ 17:42ì Daniel Vetter ì´(ê°) ì´ ê¸:
> > On Thu, Aug 25, 2016 at 05:06:55PM +0900, Inki Dae wrote:
> >>
> >>
> >> 2016ë
08ì 24ì¼ 20:57ì Daniel Vetter ì´(ê°) ì´ ê¸:
> >>> On Wed, Aug 24, 2016 at
this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/cd6df765/attachment.html>
in Borderlands 2...
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/7035bc82/attachment.html>
ubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/9118842b/attachment.html>
--
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/30a3900e/attachment.html>
On Thu, Aug 25, 2016 at 1:15 PM, Sean Paul wrote:
>
>
> On Wed, Aug 24, 2016 at 10:25 PM, Mark yao wrote:
>>
>> On 2016å¹´08æ23æ¥ 21:13, Sean Paul wrote:
>>>
>>> On Mon, Aug 22, 2016 at 8:40 PM, Mark yao
>>> wrote:
On 2016å¹´08æ23æ¥ 04:30, Sean Paul wrote:
>
> On Thu,
>>>>> merged Sean's patches and then apply new version patches.
>>>>>
>>>>> Ok, so can I get a review/ack for these revised patches then?
>>>> Something is better than nothing, and there's a bunch of stuff that
>>>> depends on these changes.
>>>>
>>>> Sean
>>>>
>>> Yes, But I miss your [PATCH v3 0/5] and [PATCH v3 4/5]. do you mean the
>>> lost
>>> patches use v2 version?
>>>
>>> Yes, v2 4/5 was reviewed as-is, so I just applied it.
>>
>> Sean
>>
> Applied this series to my drm-next.
>
>
You should probably just rebase your downstream kernel on top of my branch
here: https://cgit.freedesktop.org/~seanpaul/dogwood/log/?h=for-next
Sean
Thanks.
>
>
>
>>>> Thanks.
>>>>>
>>>>> --
>>>>> ï¼ark Yao
>>>>>
>>>>>
>>>>>
>>>>
>>> --
>>> ï¼ark Yao
>>>
>>>
>>>
>>
>>
>
> --
> ï¼ark Yao
>
>
>
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/270d588c/attachment.html>
On Thu, Aug 04, 2016 at 09:15:07AM +0100, Chris Wilson wrote:
> On Thu, Aug 04, 2016 at 10:06:57AM +0200, David Herrmann wrote:
> > The legacy DRI1 drivers expose highly broken interfaces to user-space. No
> > modern system should enable them, or you will effectively allow user-space
> > to
was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/6ad21564/attachment.html>
From: Gustavo Padovan
If userspace is running an synchronously atomic commit and interrupts the
atomic operation during fence_wait() it will hang until the timer expires,
so here we change the wait to be interruptible so it stop immediately when
userspace wants
. And
it's easy for security conscious people to not modprobe them. My -1
would probably mean more if I were still following my initial plans of
adding r128 support to the radeon kernel module but at some point while
reading documentation I lost motivation. Hopefully this is temporary.
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/a8635885/attachment.sig>
On Thu, Aug 25, 2016 at 11:04 AM, Emil Velikov
wrote:
> On 25 August 2016 at 12:14, Daniel Vetter wrote:
>> On Thu, Aug 04, 2016 at 09:15:07AM +0100, Chris Wilson wrote:
>>> On Thu, Aug 04, 2016 at 10:06:57AM +0200, David Herrmann wrote:
>>> > The legacy DRI1 drivers expose highly broken
Hi Dave, i915 fixes for v4.8.
BR,
Jani.
The following changes since commit fa8410b355251fd30341662a40ac6b22d3e38468:
Linux 4.8-rc3 (2016-08-21 16:14:10 -0700)
are available in the git repository at:
git://anongit.freedesktop.org/drm-intel tags/drm-intel-fixes-2016-08-25
for you to fetch
Introduce drm_simple_display_pipe_attach_bridge() and
drm_simple_display_pipe_detach_bridge() in order to make it possible to use
drm encoders with the simple display pipes managed by simple_kms_helpers
Suggested-by: Daniel Vetter
Signed-off-by: Andrea Merello
Reviewed-by: Daniel Vetter
Cc:
drm_simple_display_pipe_init() pretends to attach a connector
to the display pipe.
In case a drm bridge has to be used, then it's the bridge that
takes care of connectors.
This patch makes the connector parameter optional for
drm_simple_display_pipe_init(), so that a drm bridge could
handle
Up to now, once a bridge has been attached to a DRM device, it cannot
be undone.
In particular you couldn't rmmod/insmod a DRM driver that uses a bridge,
because the bridge would remain bound to the first (dead) driver instance.
This patch fixes this by introducing drm_encoder_detach() and a
On Thu, Aug 25, 2016 at 05:06:55PM +0900, Inki Dae wrote:
>
>
> 2016ë
08ì 24ì¼ 20:57ì Daniel Vetter ì´(ê°) ì´ ê¸:
> > On Wed, Aug 24, 2016 at 08:44:24PM +0900, Inki Dae wrote:
> >> Hi,
> >>
> >> 2016ë
08ì 23ì¼ 18:41ì Daniel Stone ì´(ê°) ì´ ê¸:
> >>> Hi,
> >>>
> >>> On 22
On 2016å¹´08æ23æ¥ 21:13, Sean Paul wrote:
> On Mon, Aug 22, 2016 at 8:40 PM, Mark yao wrote:
>> On 2016å¹´08æ23æ¥ 04:30, Sean Paul wrote:
>>> On Thu, Aug 18, 2016 at 6:02 AM, Mark yao
>>> wrote:
On 2016å¹´08æ18æ¥ 17:11, Daniel Vetter wrote:
> On Thu, Aug 18, 2016 at 05:08:14PM
On 08/24/2016 03:07 PM, Milo Kim wrote:
> The helper, devm_regulator_bulk_get() initializes the consumer as NULL,
> so this code can be ignored.
>
> Cc: Kukjin Kim
> Cc: Krzysztof Kozlowski
> Cc: David Airlie
> Cc: Inki Dae
> Cc: Joonyoung Shim
> Cc: Seung-Woo Kim
> Cc: Kyungmin Park
> Cc:
On 08/24/2016 03:07 PM, Milo Kim wrote:
> Paring DT properties and getting the I2C adapter in one function.
>
> Cc: Kukjin Kim
> Cc: Krzysztof Kozlowski
> Cc: David Airlie
> Cc: Inki Dae
> Cc: Joonyoung Shim
> Cc: Seung-Woo Kim
> Cc: Kyungmin Park
> Cc: Rob Herring
>
On Wed, Aug 24, 2016 at 02:06:01PM +0200, Andrea Merello wrote:
> Introduce drm_simple_display_pipe_attach_bridge() and
> drm_simple_display_pipe_detach_bridge() in order to make it possible to use
> drm encoders with the simple display pipes managed by simple_kms_helpers
>
> Suggested-by: Daniel
On Wed, Aug 24, 2016 at 02:06:00PM +0200, Andrea Merello wrote:
> drm_simple_display_pipe_init() pretends to attach a connector
> to the display pipe.
>
> In case a drm bridge has to be used, then it's the bridge that
> takes care of connectors.
>
> This patch makes the connector parameter
On Wed, Aug 24, 2016 at 02:05:59PM +0200, Andrea Merello wrote:
> Up to now, once a bridge has been attached to a DRM device, it cannot
> be undone.
>
> In particular you couldn't rmmod/insmod a DRM driver that uses a bridge,
> because the bridge would remain bound to the first (dead) driver
On Wed, Aug 24, 2016 at 08:38:37PM +0200, Noralf Trønnes wrote:
>
> Den 23.08.2016 08:25, skrev Daniel Vetter:
> > Our update function is hooked to the single plane, which might not get
> > called for crtc-only updates. Which is surprising, so fix this by
> > always adding the plane.
> >
> >
On Mon, Aug 22, 2016 at 3:25 PM, Noralf Trønnes wrote:
> The SimpleDRM driver binds to simple-framebuffer devices and provides a
> DRM/KMS API. It provides only a single CRTC+encoder+connector combination
> plus one initial mode.
>
> Userspace can create dumb-buffers which can be blit into the
On Wed, Aug 17, 2016 at 5:50 PM, Steve Longerbeam
wrote:
> In this version:
>
> - rebased against latest drm-next.
> - cleaned up header includes in ipu-vdi.c.
> - do away with struct ipu_ic_tile_off in ipu-ic.c, and move tile offsets
> into struct ipu_ic_tile. This paves the way for possibly
||
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/8b7934b4/attachment.html>
119 for that, but you'll need to provide more information about
the flickering.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20
https://bugzilla.kernel.org/show_bug.cgi?id=153911
Bug ID: 153911
Summary: Nouveau driver overly verbose
Product: Drivers
Version: 2.5
Kernel Version: 4.7.2
Hardware: All
OS: Linux
Tree: Mainline
ML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/2c39b4bd/attachment-0001.html>
are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/445fa9c2/attachment.html>
vel/attachments/20160825/33618465/attachment.html>
for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/cafc4b7d/attachment-0001.html>
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/e1a05fef/attachment.html>
:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/761c9e47/attachment.html>
nee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160825/959d5a9c/attachment.html>
84 matches
Mail list logo