Hello Morimoto-san,
On Monday, 18 December 2017 02:35:56 EET Kuninori Morimoto wrote:
> From: Kuninori Morimoto
>
> In general, PLL has VCO (= Voltage controlled oscillator),
> one of the very important electronic feature called as "jitter"
> is related to this
https://bugs.freedesktop.org/show_bug.cgi?id=104281
--- Comment #2 from Daniel Drake ---
Suspend/resume is working OK on these machines with DC disabled, so it seems to
be a DC regression.
--
You are receiving this mail because:
You are the assignee for the
Hello Morimoto-san,
Thankk you for the patch.
On Monday, 18 December 2017 02:35:18 EET Kuninori Morimoto wrote:
> From: Kuninori Morimoto
>
> It is difficult to understand its scale if number has many 0s.
> This patch uses "* 1000" to avoid it in
Hi Laurent, David
These are v4 of DPLLCR patch for rcar-du.
Mainly fixuped 2000 -> 2kHz to unambiguous
Kuninori Morimoto (2):
drm: rcar-du: use 1000 to avoid misunderstanding in rcar_du_dpll_divider()
drm: rcar-du: calculate DPLLCR to be more small jitter
iommu_map_sg() doesn't return a error value, but a size of the requested
IOMMU mapping or zero in case of error.
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/drm/tegra/gem.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git
Commit 7772fdaef939 ("drm/tegra: Support ARGB and ABGR formats") broke
DRM's MODE_ADDFB IOCTL on Tegra20/30, because it uses XRGBA format if
requested FB depth is 24bpp. As a result, Xorg doesn't work anymore with
both modesetting and opentegra drivers. On all Tegra's each plane has a
blending
From: Kuninori Morimoto
In general, PLL has VCO (= Voltage controlled oscillator),
one of the very important electronic feature called as "jitter"
is related to this VCO.
In academic generalism, VCO should be maximum to be more small jitter.
In high frequency
Hi Geert
> >> > From: Kuninori Morimoto
> >> > In general, PLL has VCO (= Voltage controlled oscillator),
> >> > one of the very important electronic feature called as "jitter"
> >> > is related to this VCO.
> >> > In academic generalism, VCO should be maximum
Older Tegra's do not support RGBA format for the cursor, but instead
overlay plane could be used for it. Since there is no much use for the
overlays on a regular desktop and HW-accelerated cursor is much nicer
than the jerky SW cursor, let's trade one overlay plane for the cursor.
Signed-off-by:
HW reset isn't actually broken on Tegra20, but there is a dependency on
first display controller to be taken out of reset for the second to be
enabled successfully.
Signed-off-by: Dmitry Osipenko
---
Change log:
v2: Got rid of global variable and now use
Hi Philipp
I have an i.MX6Q running 4.9 LTS with etnaviv.
We would like to have both the HDMI and LVDS outputs enabled a once.
If I enable hdmi and lvds in the devicetree, we have only output on the
hdmi port.
[ 0.00] Linux version 4.9.34 (oe-user@oe-host) (gcc version 6.3.0
(GCC) ) #1
host1x_syncpt_wait() takes timeout value in jiffies, but DRM passes it in
milliseconds.
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/drm/tegra/drm.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/tegra/drm.c
Hi Morimoto-san,
On Monday, 18 December 2017 10:38:19 EET Kuninori Morimoto wrote:
> Hi Laurent
>
> Thank you for your feedback
>
> >> + * To be small jitter,
> >
> > Nitpicking, I would write this "to minimize the jitter".
>
> (snip)
>
> >> + * This code is assuming
Hi Linus,
Thank you for the patch.
On Friday, 15 December 2017 14:10:47 EET Linus Walleij wrote:
> If the bridge has a too strict setup time for the incoming
> signals, we may not be fast enough and then we need to
> compensate by outputting the signal on the inverse clock
> edge so it is for
https://bugs.freedesktop.org/show_bug.cgi?id=104299
--- Comment #1 from Christian König ---
Please add the full dmesg output as attachment.
--
You are receiving this mail because:
You are the assignee for the bug.___
Hi Linus,
Thank you for the patch.
On Friday, 15 December 2017 14:10:46 EET Linus Walleij wrote:
> This extends the dumb VGA DAC bridge to handle the THS8134A
> and THS8134B VGA DACs in addition to those already handled.
>
> We assign the proper timing data to the pointer inside the
> bridge
Hello Linus,
Thank you for the patch.
On Friday, 15 December 2017 14:10:45 EET Linus Walleij wrote:
> After some discussion and failed patch sets trying to convey
> the right timing information between the display engine and
> a bridge using the connector, I try instead to use an optional
>
AMD is the major user of TTM, so it also makes sense that we maintain
it.
v2: mention Alex git tree as well
Signed-off-by: Christian König
Acked-by: Alex Deucher
Acked-by: Thomas Hellstrom
---
MAINTAINERS | 9
Hi Sean,
On Mon, 2017-12-18 at 09:10 +0100, Sean Nyekjær wrote:
> Hi Philipp
>
> I have an i.MX6Q running 4.9 LTS with etnaviv.
> We would like to have both the HDMI and LVDS outputs enabled a once.
>
> If I enable hdmi and lvds in the devicetree, we have only output on the
> hdmi port.
Hello Linus,
Thank you for the patch.
On Friday, 15 December 2017 14:10:44 EET Linus Walleij wrote:
> This adds device tree bindings for the Texas Instruments
> THS8134, THS8134A and THS8134B VGA DACs by extending and
> renaming the existing bindings for THS8135.
>
> These DACs are used for the
On 15.12.2017 16:54, Daniel Vetter wrote:
> On Fri, Dec 15, 2017 at 01:30:24PM +0100, Linus Walleij wrote:
>> On Fri, Dec 15, 2017 at 1:10 PM, Linus Walleij
>> wrote:
>>
>>> - The connector is apparently not the right abstraction to carry
>>> the detailed timings
https://bugzilla.kernel.org/show_bug.cgi?id=197925
Charles (ylang-yl...@libertysurf.fr) changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=104289
--- Comment #2 from Michel Dänzer ---
Can you bisect?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
Hey Ard,
It seems that Ben already committed a similar patch to his tree (see [0]). I do
not know whether he is planning to have it part of a pull request of fixes for
4.15.
Best regards,
Pierre
[0]:
https://github.com/skeggsb/nouveau/commit/9068f1df2394f0e4ab2b2a28cac06b462fe0a0aa
On
On Mon, Dec 18, 2017 at 2:28 AM, Joe Perches wrote:
> Some functions definitions have either the initial open brace and/or
> the closing brace outside of column 1.
>
> Move those braces to column 1.
>
> This allows various function analyzers like gnu complexity to work
>
https://bugs.freedesktop.org/show_bug.cgi?id=104295
--- Comment #3 from kaspar.t...@gmail.com ---
(In reply to Michel Dänzer from comment #2)
> Can you bisect?
Not familiar enough with the project probably to do it in a reasonable time.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=104319
--- Comment #2 from Carlo Caione ---
Created attachment 136248
--> https://bugs.freedesktop.org/attachment.cgi?id=136248=edit
dc-extended-journal
I just reproduced the same issue this time with the external HDMI monitor in
https://bugs.freedesktop.org/show_bug.cgi?id=104319
Carlo Caione changed:
What|Removed |Added
Summary|AMDGPU/DC: Internal display |AMDGPU/DC: Internal
If we try to read the backend registers while it fetches the new values, we
end up with the value of some random register instead of the one we asked
for.
In order to prevent that, let's make sure that the very first thing we do
during our atomic modesetting is to let the commit bit come to a
We will need to store some additional data in the future to the state.
Create a custom plane state that will embed those data, in order to store
the pipe or whether or not that plane should use the frontend.
Reviewed-by: Neil Armstrong
Signed-off-by: Maxime Ripard
Our operations were missing some documentation to explain what was expected
from them.
Let's make that clearer.
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/sun4i/sun4i_backend.c | 2 +-
drivers/gpu/drm/sun4i/sunxi_engine.h | 51
We have some restrictions on what the planes and CRTC can provide that are
tied to only one generation of display engines.
For example, on the first generation, we can only have one YUV plane or one
plane that uses the frontend output.
Let's allow our engines to provide an atomic_check callback
Setup the line stride in the buffer setup function, since it's tied to the
buffer itself, and is not needed when we do not set the buffer in the
backend.
This is for example the case when using the frontend and then routing its
output to the backend.
Reviewed-by: Neil Armstrong
Hi,
This is a first serie to enable the display engine frontend.
This hardware block is found in the first generation Display Engine from
Allwinner. Its role is to implement more advanced features that the
associated backend, even though the backend alone can be used (and was used
so far) for
During a hardware commit, the commit bit in the backend will only be
cleared if the TCON is enabled. Use the runtime_pm variant of the
atomic_commit_tail hook that makes sure that the CRTC, our TCON, is enabled
when we perform an atomic_commit.
Signed-off-by: Maxime Ripard
We have to implement some display engine specific behaviours in
atomic_begin. Let's add a function for that.
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/sun4i/sun4i_crtc.c | 6 +-
drivers/gpu/drm/sun4i/sunxi_engine.h | 13 +
2 files
The new debugfs registration fails to build when CONFIG_DEBUGFS is
disabled, because the drm_crtc structure is lacking a member in that
configuration:
drivers/gpu/drm/tegra/dc.c: In function 'tegra_dc_late_register':
drivers/gpu/drm/tegra/dc.c:1204:28: error: 'struct drm_crtc' has no member
Now that we have everything in place, we can start enabling the frontend.
This is more difficult than one would assume since there can only be one
plane using the frontend per-backend.
We therefore need to make sure that the userspace will not try to setup
multiple planes using it, since that
The display frontend is an hardware block that can be used to implement
some more advanced features like hardware scaling or colorspace
conversions. It can also be used to implement the output format of the VPU.
Let's create a minimal driver for it that will only enable the hardware
scaling
Now that we have a driver, we can make use of it. This is done by
adding a flag to our custom plane state that will trigger whether we should
use the frontend on that particular plane or not.
The rest is just plumbing to set up the backend to not perform the DMA but
receive its data from the
The display frontend can be used to do hardware scaling, colorspaces
conversion or to implement the buffer format output by the Cedar VPU.
Since we're starting to have some support for it in the DRM driver, let's
enable its DT node.
Signed-off-by: Maxime Ripard
Hi Alex,
On Friday, 15 December 2017 03:57:48 EET Alex Deucher wrote:
> On Thu, Dec 14, 2017 at 3:30 PM, Daniel Vetter wrote:
> > DK put some nice docs into the commit introducing driver private
> > state, but in the git history alone it'll be lost.
> >
> > Also, since Ville remove the void*
On 18.12.2017 14:02, Fabio Estevam wrote:
> From: Fabio Estevam
>
> devm_ioremap_resource() already checks if the resource is NULL, so
> remove the unnecessary platform_get_resource() error check.
>
> Cc: Inki Dae
> Signed-off-by: Fabio Estevam
https://bugs.freedesktop.org/show_bug.cgi?id=104299
--- Comment #2 from Andrey Grodzovsky ---
Hi, have you noticed any specific scenario under which those crashes happened
to you ?
Thanks,
Andrey
--
You are receiving this mail because:
You are the assignee for the
Hi Daniel,
Thank you for the patch.
On Thursday, 14 December 2017 22:30:53 EET Daniel Vetter wrote:
> DK put some nice docs into the commit introducing driver private
> state, but in the git history alone it'll be lost.
You might want to spell DK's name fully.
> Also, since Ville remove the
Am Sonntag, den 17.12.2017, 03:34 +0100 schrieb Jonathan Neuschäfer:
> The compatible string for this panel was specified as
> toshiba,lt089ac29000.txt. I believe this is a mistake.
>
> Fixes: 06e733e41f87 ("drm/panel: simple: add Toshiba LT089AC19000")
> > Cc: Lucas Stach
Hi Daniel,
On Friday, 15 December 2017 17:54:15 EET Daniel Vetter wrote:
> On Fri, Dec 15, 2017 at 01:30:24PM +0100, Linus Walleij wrote:
> > On Fri, Dec 15, 2017 at 1:10 PM, Linus Walleij
wrote:
> >> - The connector is apparently not the right abstraction to carry
>
Hi Andrzej,
On Monday, 18 December 2017 10:43:51 EET Andrzej Hajda wrote:
> On 15.12.2017 16:54, Daniel Vetter wrote:
> > On Fri, Dec 15, 2017 at 01:30:24PM +0100, Linus Walleij wrote:
> >> On Fri, Dec 15, 2017 at 1:10 PM, Linus Walleij
wrote:
> >>> - The connector is
https://bugs.freedesktop.org/show_bug.cgi?id=104295
--- Comment #2 from Michel Dänzer ---
Can you bisect?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
Following up by e-mail, since I can't find Peter Rosin in the kernel
bugzilla.
On 2017-12-16 02:41 AM, bugzilla-dae...@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=198123
>
> --- Comment #8 from Deposite Pirate (dpir...@metalpunks.info) ---
> Ok, I went through all
https://bugs.freedesktop.org/show_bug.cgi?id=102800
--- Comment #16 from Alex Deucher ---
Created attachment 136269
--> https://bugs.freedesktop.org/attachment.cgi?id=136269=edit
workaround to test
To narrow things down further, does this patch also work?
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=104299
--- Comment #5 from higu...@gmx.net ---
Created attachment 136267
--> https://bugs.freedesktop.org/attachment.cgi?id=136267=edit
syslog capture for the oops
I didn't saved the dmesg directly but i could salvage this from the syslog
--
You
From: Fabio Estevam
devm_ioremap_resource() already checks if the resource is NULL, so
remove the unnecessary platform_get_resource() error check.
Cc: Heiko Stübner
Signed-off-by: Fabio Estevam
---
From: Fabio Estevam
devm_ioremap_resource() already checks if the resource is NULL, so
remove the unnecessary platform_get_resource() error check.
Cc: Archit Taneja
Signed-off-by: Fabio Estevam
---
From: Fabio Estevam
devm_ioremap_resource() already checks if the resource is NULL, so
remove the unnecessary platform_get_resource() error check.
Cc: Heiko Stübner
Signed-off-by: Fabio Estevam
---
From: Fabio Estevam
devm_ioremap_resource() already checks if the resource is NULL, so
remove the unnecessary platform_get_resource() error check.
Cc: Inki Dae
Signed-off-by: Fabio Estevam
---
From: Fabio Estevam
devm_ioremap_resource() already checks if the resource is NULL, so
remove the unnecessary platform_get_resource() error check.
Cc: Philippe Cornu
Signed-off-by: Fabio Estevam
---
From: Fabio Estevam
devm_ioremap_resource() already checks if the resource is NULL, so
remove the unnecessary platform_get_resource() error check.
Cc: Thierry Reding
Signed-off-by: Fabio Estevam
---
From: Fabio Estevam
devm_ioremap_resource() already checks if the resource is NULL, so
remove the unnecessary platform_get_resource() error check.
Cc: Philippe Cornu
Signed-off-by: Fabio Estevam
---
https://bugs.freedesktop.org/show_bug.cgi?id=104319
Bug ID: 104319
Summary: AMDGPU/DC: Internal display corrupted when mirroring
on external monitor on HDMI
Product: DRI
Version: XOrg git
Hardware: Other
https://bugs.freedesktop.org/show_bug.cgi?id=104319
--- Comment #1 from Carlo Caione ---
Created attachment 136246
--> https://bugs.freedesktop.org/attachment.cgi?id=136246=edit
dc-warning-hdmi-detached
We have also verified that when disconnecting the HDMI cable, the system
On Mon, 18 Dec 2017 01:28:44 +0100,
Joe Perches wrote:
>
> Some functions definitions have either the initial open brace and/or
> the closing brace outside of column 1.
>
> Move those braces to column 1.
>
> This allows various function analyzers like gnu complexity to work
> properly for these
On 12/15/2017 12:59 PM, Sushmita Susheelendra wrote:
Use the direction argument passed into begin_cpu_access
and end_cpu_access when calling the dma_sync_sg_for_cpu/device.
The actual cache primitive called depends on the direction
passed in.
Acked-by: Laura Abbott
Hi Dave,
I expect to have one more pile next week for rc6. But for now consider
already applying this one.
On this one here we had one backmerge for a reconciliation drm_print.h
between us and drm-misc-next. But that should be transparent to you.
On the GVT side it is worth to highlight that
https://bugs.freedesktop.org/show_bug.cgi?id=103791
--- Comment #18 from Anthony Parsons ---
Hi, I'm seeing the same problem on an RX550 (polaris12). Running xrandr doesn't
seem to work as a workaround but flipping VTs does. Would having the debug
output for this one
On Thu, Dec 7, 2017 at 5:38 AM, Jose Abreu wrote:
> Hi Sean,
>
> On 07-12-2017 00:00, Sean Paul wrote:
>> Welcome to version 4 of the patchset. I think we're nearing the finish line
>> (hopefully) now. This set addresses the review feedback from v3. I applied
>> some
>>
Hi Dave,
Please pull the tilcdc changes for Linux v4.16.
Best regards and thanks,
Jyri
The following changes since commit 9428088c90b6f7d5edd2a1b0d742c75339b36f6e:
drm/qxl: reapply cursor after resetting primary (2017-12-08 13:37:02
+1000)
are available in the git repository at:
On Sun, Dec 17, 2017 at 7:28 PM, Joe Perches wrote:
> Some functions definitions have either the initial open brace and/or
> the closing brace outside of column 1.
>
> Move those braces to column 1.
>
> This allows various function analyzers like gnu complexity to work
>
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next
head: ba5f48e76ee6fb35b2be46a017d05b2c5cda703b
commit: c1888183e1764d55d51ae051bd8651e634febe4d [374/799] ASoC: AMD: enable
ACP3x drivers build
config: sh-allmodconfig (attached as .config)
compiler: sh4-linux-gnu-gcc
On Sun, Dec 17, 2017 at 11:11 PM, Daniel Vetter wrote:
>
> This didn't seem to have made it into -rc4. Anything needed to get it
> going?
Do you actually see the problem in -rc4?
Because we ended up removing the cross-release checking due to other
developers complaining. It
On Monday, December 18, 2017 1:28:44 AM CET Joe Perches wrote:
> Some functions definitions have either the initial open brace and/or
> the closing brace outside of column 1.
>
> Move those braces to column 1.
>
> This allows various function analyzers like gnu complexity to work
> properly for
2017년 12월 18일 22:02에 Fabio Estevam 이(가) 쓴 글:
> From: Fabio Estevam
>
> devm_ioremap_resource() already checks if the resource is NULL, so
> remove the unnecessary platform_get_resource() error check.
>
> Cc: Inki Dae
> Signed-off-by: Fabio Estevam
https://bugs.freedesktop.org/show_bug.cgi?id=104299
--- Comment #3 from higu...@gmx.net ---
Well, both times it happen while playing rimworld but i didn't notice any
special action how to trigger this.
my hardware is a A10-7850k and a RX480, slackware64-current, dual head
1920x1080,
https://bugs.freedesktop.org/show_bug.cgi?id=104331
Bug ID: 104331
Summary: [r600g] Ogre demo "TutorialUAV01" crash at
r600_decompress_color_images
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS:
https://bugs.freedesktop.org/show_bug.cgi?id=104299
--- Comment #4 from higu...@gmx.net ---
Created attachment 136266
--> https://bugs.freedesktop.org/attachment.cgi?id=136266=edit
dmesg without the crash
This is my current dmesg
--
You are receiving this mail because:
You are the assignee
On 18.12.2017 12:28, Marc Zyngier wrote:
> Stopping the X display manager on a kevin platform results in the
> following crash:
>
> [ 674.833536] Synchronous External Abort: synchronous external abort
> (0x9610) at 0x0c970640
> [ 674.843886] Internal error: : 9610 [#1] PREEMPT
https://bugs.freedesktop.org/show_bug.cgi?id=104306
--- Comment #1 from eric vz ---
Similar experience here on Arch Linux with a Radeon HD 8870M / R9 M270X/M370X.
Firefox hangs on launch before drawing a window, and Chromium won't start
either unless I
On Mon, Dec 18, 2017 at 10:57 PM, Maxime Ripard
wrote:
> Setup the line stride in the buffer setup function, since it's tied to the
> buffer itself, and is not needed when we do not set the buffer in the
> backend.
>
> This is for example the case when using the
On Mon, Dec 18, 2017 at 10:57 PM, Maxime Ripard
wrote:
> Our operations were missing some documentation to explain what was expected
> from them.
>
> Let's make that clearer.
>
> Signed-off-by: Maxime Ripard
> ---
>
On Mon, Dec 18, 2017 at 10:57 PM, Maxime Ripard
wrote:
> We have some restrictions on what the planes and CRTC can provide that are
> tied to only one generation of display engines.
>
> For example, on the first generation, we can only have one YUV plane or one
>
On Mon, Dec 18, 2017 at 10:57 PM, Maxime Ripard
wrote:
> We will need to store some additional data in the future to the state.
> Create a custom plane state that will embed those data, in order to store
> the pipe or whether or not that plane should use the
On Mon, Dec 18, 2017 at 10:57 PM, Maxime Ripard
wrote:
> In some cases, the display engine needs to apply some quirks during the
> VBLANK event. In the Display Engine 1.0 case for example, we can only
> disable the frontend once the backend has been, which is at
https://bugs.freedesktop.org/show_bug.cgi?id=95306
--- Comment #80 from Kelly Anderson ---
4.15rc4 also seems to work fine with respect to this problem.
--
You are receiving this mail because:
You are the assignee for the bug.___
On Mon, Dec 18, 2017 at 10:57 PM, Maxime Ripard
wrote:
> We have to implement some display engine specific behaviours in
> atomic_begin. Let's add a function for that.
>
> Signed-off-by: Maxime Ripard
> ---
>
This flag has become redundant since
commit 4d90f2d507ab ("drm/i915: Start tracking PSR state in crtc state")
It is set at the same place as psr.enabled, which is also exposed via
debugfs.
Cc: Rodrigo Vivi
Cc: Ville Syrjälä
Signed-off-by:
The first 3 patches are minor PSR improvements. The last 5 introduce a new
power domain to disable DC states when vblanks are required. The tricky
part is to enable and disable the DC_OFF power well in atomic context. I
have addressed the locking issues that CI caught in the last revision.
The HW frame counter can get reset when devices enters low power
states and this messes up any following vblank count updates. So, compute
the missed vblank interrupts for that low power state duration using time
stamps. This is similar to _crtc_vblank_on() except that it doesn't enable
vblank
The global variable dev_priv->psr.sink_support is set if an eDP sink
supports PSR. Use this instead of redoing the check with is_edp_psr().
Combine source and sink support checks into a macro that can be used to
return early from psr_{invalidate, single_frame_update, flush}.
Cc: Rodrigo Vivi
Disable DC states before enabling vblank interrupts and conversely
enable DC states after disabling. Since the frame counter may have got
reset between disabling and enabling, use drm_crtc_vblank_restore() to
compute the missed vblanks.
Cc: Daniel Vetter
Cc: Ville Syrjälä
When DC states are enabled and PSR is active, the hardware enters DC5/DC6
states resulting in frame counter resets. The frame counter resets mess
up the vblank counting logic. In order to disable DC states when
vblank interrupts are required and to disallow DC states when vblanks
interrupts are
Convert the power_domains->domain_use_count array that tracks per-domain
use count to atomic_t type. This is needed to be able to read/write the use
counts outside of the power domain mutex.
Cc: Daniel Vetter
Cc: Ville Syrjälä
Cc: Rodrigo
DPCD read for the eDP is complete by the time intel_psr_init() is
called, which means we can avoid initializing PSR structures and state
if there is no sink support.
Cc: Rodrigo Vivi
Cc: Ville Syrjälä
Signed-off-by: Dhinakaran Pandiyan
https://bugs.freedesktop.org/show_bug.cgi?id=104331
Dave Airlie changed:
What|Removed |Added
Resolution|--- |FIXED
93 matches
Mail list logo