On 05/09/2018 02:45 PM, Chunming Zhou wrote:
move implemenation from ttm to amdgpu driver. (suggested by Christian)
per-vm-lru is because of per-vm-bo, which has no chance to refresh lru, the
nagtive effect is game performance isn't stable.
so all per-vm-bo should have a default order, every per
Expect to add an evitable bo who has reservation object
to the correct lru[bo->priority] list
Signed-off-by: Junwei Zhang
---
drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 11 ++-
drivers/gpu/drm/ast/ast_ttm.c | 2 +-
drivers/gpu/drm/bochs/bochs_mm.c| 2 +-
dr
https://bugzilla.kernel.org/show_bug.cgi?id=199025
--- Comment #35 from todd (todd...@gmail.com) ---
p.s.
As you can see, that version listed above is for fedora 27, not 28 so you will
need to re-install fedora 27 first.
--
You are receiving this mail because:
You are watching the assignee of th
https://bugzilla.kernel.org/show_bug.cgi?id=199025
--- Comment #34 from todd (todd...@gmail.com) ---
Did you delete all your symlinks?
Also, it sounds like you might just have done a "dnf system-upgrade reboot"
rather than a clean install.?.? Fedora's system-upgrade is a total and complete
P.o.S.
https://bugs.freedesktop.org/show_bug.cgi?id=91808
Dave Airlie changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
2018년 05월 09일 17:59에 Marek Szyprowski 이(가) 쓴 글:
> From: Andrzej Pietrasiewicz
>
> There are two Scaler devices in Exynos5433 SoCs. Add nodes for them and
> their SYSMMU controllers.
>
> Signed-off-by: Andrzej Pietrasiewicz
> Signed-off-by: Marek Szyprowski
Reviewed-by: Inki Dae
Thanks,
In
2018년 05월 09일 17:59에 Marek Szyprowski 이(가) 쓴 글:
> From: Andrzej Pietrasiewicz
>
> There are 3 scaler devices in Exynos5420 SoCs, all are a part of MSCL
> power domain. MSCL power domain and SYSMMU controllers (two per each
> scaler device) have been already added to exynos5420.dtsi earlier,
> s
According to Display Stream compression spec 1.2, the picture
parameter set metadata is sent from source to sink device
using the DP Secondary data packet. An infoframe is formed
for the PPS SDP header and PPS SDP payload bytes.
This patch adds helpers to fill the PPS SDP header
and PPS SDP payload
https://bugs.freedesktop.org/show_bug.cgi?id=106456
--- Comment #3 from John Lindgren ---
Yes, that looks like the same fix.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedeskto
Hi Ezequiel,
On Wed, 2018-05-09 at 17:14 -0300, Ezequiel Garcia wrote:
> Change how dma_fence_add_callback() behaves, when the fence
> has error-signaled by the time it is being add. After this commit,
> dma_fence_add_callback() returns the fence error, if it
> has error-signaled before dma_fence_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Stone (3):
drm/atomic: Refuse to add invalid objects to requests
headers: Sync with drm-next
headers: Update README
Dylan Baker (1):
meson: don't use compiler.has_header
Emil Velikov (1):
Revert "libd
https://bugs.freedesktop.org/show_bug.cgi?id=106456
--- Comment #2 from Ilia Mirkin ---
Fixed by this?
https://github.com/skeggsb/nouveau/commit/f84973838226b8a599bce64376665ec8f0087629
--
You are receiving this mail because:
You are the assignee for the bug.___
VESA Display Stream Compression is a specification for visually losless
video compression over display links. The DSC standard also defines
a picture parameter set (PPS) which encoder must communicate to decoders.
This is done by encapsulating PPS header and payload bytes in an infoframe
that can b
This patch defines a new header file for all the DSC 1.2 structures
and creates a structure for PPS infoframe which will be used to send
picture parameter set secondary data packet for display stream compression.
All the PPS infoframe syntax elements are taken from DSC 1.2 specification
from VESA.
According to Display Stream compression spec 1.2, the picture
parameter set metadata is sent from source to sink device
using the DP Secondary data packet. An infoframe is formed
for the PPS SDP header and PPS SDP payload bytes.
This patch adds helpers to fill the PPS SDP header
and PPS SDP payload
From: Gaurav K Singh
This defines all the DSC parameters as per the VESA DSC spec
that will be required for DSC encoder/decoder
v2: Define this struct in DRM (From Manasi)
* Changed the data types to u8/u16 instead of unsigned longs (Manasi)
* Remove driver specific fields (Manasi)
* Move this s
DP 1.4 spec defines DP secondary data packet for DSC
picture parameter set. This patch defines its payload size
according to the DP 1.4 specification.
Signed-off-by: Manasi Navare
Cc: Jani Nikula
Cc: Ville Syrjala
Cc: Anusha Srivatsa
Cc: dri-devel@lists.freedesktop.org
---
include/drm/drm_dp_
https://bugs.freedesktop.org/show_bug.cgi?id=106259
--- Comment #4 from James Harvey ---
Alex, thank you for the patch! This indeed fixes the hang.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dr
https://bugs.freedesktop.org/show_bug.cgi?id=106447
--- Comment #9 from Thomas Martitz ---
Here's the bisect log:
git bisect start
# bad: [75bc37fefc4471e718ba8e651aa74673d4e0a9eb] Linux 4.17-rc4
git bisect bad 75bc37fefc4471e718ba8e651aa74673d4e0a9eb
# good: [bebc6082da0a9f5d47a1ea2edc099bf6710
https://bugs.freedesktop.org/show_bug.cgi?id=106447
--- Comment #8 from Thomas Martitz ---
Created attachment 139453
--> https://bugs.freedesktop.org/attachment.cgi?id=139453&action=edit
dmesg of last good commit after suspend
--
You are receiving this mail because:
You are the assignee for t
https://bugs.freedesktop.org/show_bug.cgi?id=106447
--- Comment #7 from Thomas Martitz ---
I did a bisect and git reported this as the culprit:
kugel@thomas-nb:linux.git$ git bisect good
08810a4119aaebf6318f209ec5dd9828e969cba4 is the first bad commit
commit 08810a4119aaebf6318f209ec5dd9828e969c
https://bugs.freedesktop.org/show_bug.cgi?id=93199
--- Comment #26 from Christian Kellner ---
Just stumbled into the same issue, disabled secure boot, and the issue
disappeared. Now I am having a different issue, but I think it is just my
version being too old.
--
You are receiving this mail be
Hi Dave,
A little bigger than normal since this is two weeks of fixes.
- Atom firmware table updates for vega12
- Fix fallout from huge page support
- Fix up smu7 power profile interface to be consistent with vega
- Misc other fixes
The following changes since commit a02cbe2e34c576cdc5e7846a3cd55
Hi Dave,
This weeks fixes is a little busier than normal, due to the omap changes.
However since these aren't regressions, it shouldn't be something to be
concerned about.
drm-misc-fixes-2018-05-09:
atomic: Clear state pointers on clear (Ville)
vc4: Fix oops in dpi disable (Eric)
omap: Various
https://bugs.freedesktop.org/show_bug.cgi?id=106456
--- Comment #1 from John Lindgren ---
Created attachment 139452
--> https://bugs.freedesktop.org/attachment.cgi?id=139452&action=edit
Fix mutex deadlock in nouveau driver
--
You are receiving this mail because:
You are the assignee for the b
On Tue, May 08, 2018 at 04:39:45PM +0530, Nautiyal, Ankit K wrote:
> From: "Sharma, Shashank"
>
> HDMI 2.0/CEA-861-F introduces two new aspect ratios:
> - 64:27
> - 256:135
>
> This patch:
> - Adds new DRM flags for to represent these new aspect ratios.
> - Adds new cases to handle these aspec
https://bugs.freedesktop.org/show_bug.cgi?id=106456
Bug ID: 106456
Summary: [regression][bisected] Mutex deadlock in nouveau
(nv50_display.c)
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux
On Wed, May 2, 2018 at 11:04 AM, Harry Wentland wrote:
> On 2018-05-02 10:43 AM, Colin King wrote:
>> From: Colin Ian King
>>
>> The declaration of pointer amdgpu_crtc has a redundant assignment to
>> amdgpu_crtc. Clean this up by removing it.
>>
>> Detected by CoverityScan, CID#1460299 ("Evaluat
On Sat, Apr 28, 2018 at 6:21 PM, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistake in PP_ASSERT_WITH_CODE message text
>
> Signed-off-by: Colin Ian King
Applied. thanks!
Alex
> ---
> drivers/gpu/drm/amd/powerplay/hwmgr/smu7_hwmgr.c | 2 +-
> drivers/gpu/drm/amd/
Em Wed, 9 May 2018 15:11:07 -0400 (EDT)
Alan Stern escreveu:
> On Wed, 9 May 2018, Mauro Carvalho Chehab wrote:
>
> > Em Wed, 9 May 2018 19:15:01 +0200
> > Andrea Parri escreveu:
>
> > > > tools/memory-model/README | 10 +-
> > >
> > > As mentioned in the pre
https://bugs.freedesktop.org/show_bug.cgi?id=106259
--- Comment #3 from Alex Deucher ---
Should be fixed with this patch:
https://patchwork.freedesktop.org/patch/221510/
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-
On Wed, 9 May 2018, Mauro Carvalho Chehab wrote:
> Em Wed, 9 May 2018 19:15:01 +0200
> Andrea Parri escreveu:
> > > tools/memory-model/README | 10 +-
> >
> > As mentioned in the previous thread, I am for keeping the current
> > references: the REAMDE is listing th
https://bugs.freedesktop.org/show_bug.cgi?id=105684
--- Comment #19 from Alex Deucher ---
Does this patch help?
https://patchwork.freedesktop.org/patch/218586/
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mail
https://bugs.freedesktop.org/show_bug.cgi?id=105684
Alex Deucher changed:
What|Removed |Added
CC||sunpeng...@amd.com
--- Comment #18 from
https://bugs.freedesktop.org/show_bug.cgi?id=106374
--- Comment #2 from tempel.jul...@gmail.com ---
I suppose the Windows Wattman doesn't consider the values defined by the OEM
and instead always allows +75% (not 50% as I mentioned before) on top of the
card's value that is defined for 100%:
https
Em Wed, 9 May 2018 19:15:01 +0200
Andrea Parri escreveu:
> On Wed, May 09, 2018 at 10:18:52AM -0300, Mauro Carvalho Chehab wrote:
> > As we move stuff around, some doc references are broken. Fix some of
> > them via this script:
> > ./scripts/documentation-file-ref-check --fix-rst
> >
> > Ma
On 05/09/18 19:22, David Lechner wrote:
> On 03/19/2018 04:05 AM, Jyri Sarha wrote:
>> Thanks,
>> I'll pick this for v4.18.
>
> Ping. I don't see this in drm-misc-next yet.
>
Thanks for the ping. I thought I would have time to do something more
for tilcdc in v4.18, but it seems I have not. After
Hi Dave,
Please pull the tilcdc changes for Linux v4.18.
Best regards and thanks,
Jyri
The following changes since commit 6d08b06e67cd117f6992c46611dfb4ce267cd71e:
Linux 4.17-rc2 (2018-04-22 19:20:09 -0700)
are available in the git repository at:
https://github.com/jsarha/linux tags/tilcdc
On 03/19/2018 04:05 AM, Jyri Sarha wrote:
Thanks,
I'll pick this for v4.18.
Ping. I don't see this in drm-misc-next yet.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
On Wed, May 9, 2018 at 6:06 AM, zhoucm1 wrote:
>
>
> On 2018年05月09日 17:50, Daniel Vetter wrote:
>>
>> On Wed, May 09, 2018 at 10:34:51AM +0200, Lucas Stach wrote:
>>>
>>> All of those changes are including a Change-Id that has no bearing in
>>> upstream patches and are missing a proper commit desc
https://bugs.freedesktop.org/show_bug.cgi?id=106303
--- Comment #5 from Mike ---
>Can you bisect?
No, I'm using pre-compiled kernels.
However, it's clearly happens in-between 4.15.8 and 4.16.{0 .. 2}.
Reproduces stably.
>Are you using multiple monitors?
No, single monitor via DisplayPort (2560x1
Hi Lukasz,
On Wed, May 9, 2018 at 12:39 PM, Lukasz Majewski wrote:
> +Example device-tree definition when connected to iMX6Q based board
> +
> + lcd_panel: lcd-panel {
> + compatible = "auo,g070vvn01";
> + backlight = <&backlight_lcd>;
> + bus-form
https://bugs.freedesktop.org/show_bug.cgi?id=106194
--- Comment #11 from Leo Li ---
I'm having trouble reproducing the BUG_ON in Ubuntu 18.04.
For those who can, the below info will be helpful:
- Distribution & version
- Window manager used
- Xorg log
- journalctl log, if on Wayland
Xorg log is
https://bugs.freedesktop.org/show_bug.cgi?id=106447
--- Comment #6 from Thomas Martitz ---
last dmesg output is with amdgpu.dc=0
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freede
https://bugs.freedesktop.org/show_bug.cgi?id=106447
--- Comment #5 from Thomas Martitz ---
Created attachment 139445
--> https://bugs.freedesktop.org/attachment.cgi?id=139445&action=edit
dmesg of 4.17-rc4 before suspend
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=106447
--- Comment #4 from Thomas Martitz ---
Yes, on both 4.16.7 and 4.17-rc4
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop
>-Original Message-
>From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Tuesday, April 3, 2018 7:28 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;
https://bugs.freedesktop.org/show_bug.cgi?id=99403
--- Comment #8 from i...@yahoo.com ---
This patch seems to fix rendering on Evergreen:
https://bugs.freedesktop.org/page.cgi?id=splinter.html&bug=91808&attachment=139438
Now, it remains to find out why it is reproducible on Tahiti.
--
You are r
>-Original Message-
>From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Tuesday, April 3, 2018 7:28 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;
On 04.05.2018 15:51, Peter Rosin wrote:
> Bridge drivers can now (temporarily, in a transition phase) select if
> they want to provide a full owner device or keep just providing an
> of_node.
>
> By providing a full owner device, the bridge drivers no longer need
> to provide an of_node since that
https://bugs.freedesktop.org/show_bug.cgi?id=91808
--- Comment #15 from i...@yahoo.com ---
Looks perfect to me. The shadow flickering is also gone.
Tested with the real game on "lowest" and "very high" settings.
In addition, it also seems to fix the witcher1 trace too.
Can you give a long explan
>-Original Message-
>From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Tuesday, April 3, 2018 7:28 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;
On Mon, 7 May 2018 17:24:08 +0200
Daniel Vetter wrote:
> On Mon, May 07, 2018 at 04:44:34PM +0200, Boris Brezillon wrote:
> > Now that the plane code takes the underscan setup into account, we can
> > safely attach the underscan props to the HDMI connector.
> >
> > We also take care of filling A
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Tuesday, April 3, 2018 7:28 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Tuesday, April 3, 2018 7:28 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;
https://bugs.freedesktop.org/show_bug.cgi?id=105880
--- Comment #19 from Chí-Thanh Christopher Nguyễn ---
Per https://lists.freedesktop.org/archives/amd-gfx/2018-May/022021.html it
seems that AMD developers lack hardware to implement LVDS/VGA support at this
time.
KABINI devices with VGA, DVI-I
https://bugs.freedesktop.org/show_bug.cgi?id=106399
Michel Dänzer changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
>-Original Message-
>From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Tuesday, April 3, 2018 7:28 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Tuesday, April 3, 2018 7:28 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Tuesday, April 3, 2018 7:27 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;
https://bugs.freedesktop.org/show_bug.cgi?id=106447
--- Comment #3 from Michel Dänzer ---
Does it also happen with amdgpu.dc=0?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedes
The script:
./scripts/documentation-file-ref-check --fix-rst
Gives multiple hints for broken references on some files.
Manually use the one that applies for some files.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/ABI/obsolete/sysfs-gpio | 2 +-
.../devicet
As we move stuff around, some doc references are broken. Fix some of
them via this script:
./scripts/documentation-file-ref-check --fix-rst
Manually checked if the produced result is valid, removing a few
false-positives.
Signed-off-by: Mauro Carvalho Chehab
---
.../admin-guide/kernel-p
Hello,
This is a new attempt at fixing the "panel is missing" issue (described
in this thread [1]). I lost track of Eric's proposal, but I recently
proposed to address this problem through a new ->detect() hook in the
panel_funcs interface [2], which was rejected.
So here is a new version based o
Having a device with a status property != "okay" in the DT is a valid
use case, and we should not prevent the registration of the DRM device
when the DSI device connected to the DSI controller is disabled.
Consider the ENODEV return code as a valid result and do not expose the
DSI encoder/connecto
Right now, the DRM panel logic returns NULL when a panel pointing to
the passed OF node is not present in the list of registered panels.
Most drivers interpret this NULL value as -EPROBE_DEFER, but we are
about to modify the semantic of of_drm_find_panel() and let the
framework return -ENODEV when
There's no point searching for a drm_bridge or drm_panel if the OF node
we're pointing has a status property that is not "okay" or "ok". Just
return -ENODEV in this case.
Signed-off-by: Boris Brezillon
Reviewed-by: Thierry Reding
Acked-by: Thierry Reding
---
Changes in v3:
- Add Thierry's A-b/R
Hi,
Il 07/05/2018 09:30, Maxime Ripard ha scritto:
Otherwise as in-tree dts with make dtbs "-@" argument is not passed.
Right?
You should use DTC_FLAGS='-@'
Thank you, I'm going to use that.
--
Giulio Benetti
CTO
MICRONOVA SRL
Sede: Via A. Niedda 3 - 35010 Vigonza (PD)
Tel. 049/8931563 -
DT nodes might be present in the DT but with a status property set to
"disabled" or "fail". In this case, we should not return -EPROBE_DEFER
when the caller asks for a drm_panel instance. Return -ENODEV instead.
Signed-off-by: Boris Brezillon
Reviewed-by: Thierry Reding
Acked-by: Thierry Reding
On Wed, May 09, 2018 at 09:18:57AM +0100, Chris Wilson wrote:
> Quoting Dan Carpenter (2018-05-09 09:12:54)
> > There is a comment here which says that DIV_ROUND_UP() can overflow and
> > that's where the problem comes from. Say you pick:
> >
> > args->bpp = UINT_MAX - 7;
> > args
https://bugs.freedesktop.org/show_bug.cgi?id=106447
--- Comment #2 from Thomas Martitz ---
Created attachment 139444
--> https://bugs.freedesktop.org/attachment.cgi?id=139444&action=edit
dmesg (actually journalctl -k) output before suspend
--
You are receiving this mail because:
You are the a
Hi,
On Wed, 2018-05-09 at 09:12 +0200, Maxime Ripard wrote:
> On Tue, May 08, 2018 at 12:04:11AM +0200, Paul Kocialkowski wrote:
> > This adds timings for the RGB666 variant of the Innolux AT070TN90 panel,
> > as found on the Ainol AW1 tablet.
> >
> > The panel also supports RGB888 output. When R
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Tuesday, April 3, 2018 7:27 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;
>-Original Message-
>From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Tuesday, April 3, 2018 7:27 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;
On Tue, May 08, 2018 at 06:34:36PM +0800, Lowry Li wrote:
> Pixel blend modes represent the alpha blending equation
> selection, describing how the pixels from the current
> plane are composited with the background.
>
> Add a pixel_blend_mode to drm_plane_state and a
> blend_mode_property to drm_p
On Wed, 09 May 2018, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistakes in WARN warning message text and
> in comments:
>
> "seqeuncer", "seqeuencer" -> "sequencer"
>
> Signed-off-by: Colin Ian King
Reviewed-by: Jani Nikula
(Waiting for the CI runs before merging.)
>-Original Message-
>From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Tuesday, April 3, 2018 7:27 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Tuesday, April 3, 2018 7:27 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;
>-Original Message-
>From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Tuesday, April 3, 2018 7:27 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;
>-Original Message-
>From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Tuesday, April 3, 2018 7:27 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;
From: Colin Ian King
Trivial fix to spelling mistakes in WARN warning message text and
in comments:
"seqeuncer", "seqeuencer" -> "sequencer"
Signed-off-by: Colin Ian King
---
V2: Also fix seqeuencer in comments
---
drivers/gpu/drm/i915/intel_dp.c | 12 ++--
1 file changed, 6 inserti
>-Original Message-
>From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Tuesday, April 3, 2018 7:27 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Tuesday, April 3, 2018 7:27 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Tuesday, April 3, 2018 7:27 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;
On 2018年05月09日 17:50, Daniel Vetter wrote:
On Wed, May 09, 2018 at 10:34:51AM +0200, Lucas Stach wrote:
All of those changes are including a Change-Id that has no bearing in
upstream patches and are missing a proper commit description explaining
why a specific change is done.
Imo the Change-I
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Tuesday, April 3, 2018 7:27 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;
>-Original Message-
>From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Tuesday, April 3, 2018 7:27 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;
On Wed, May 09, 2018 at 10:34:51AM +0200, Lucas Stach wrote:
> All of those changes are including a Change-Id that has no bearing in
> upstream patches and are missing a proper commit description explaining
> why a specific change is done.
Imo the Change-Id: is ok if it makes people happy wrt inte
https://bugs.freedesktop.org/show_bug.cgi?id=105869
Jan Vesely changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Bug 99553 depends on bug 105869, which changed state.
Bug 105869 Summary: [amdgcn/llvm-5] clang crashes when compiling OpenCL kernel
https://bugs.freedesktop.org/show_bug.cgi?id=105869
What|Removed |Added
--
On Wed, 09 May 2018, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistake in WARN warning message text
While at it, would you mind fixing the plethora of "seqeuencer" typos in
the comments in the same file please?
BR,
Jani.
>
> Signed-off-by: Colin Ian King
> ---
> dr
https://bugs.freedesktop.org/show_bug.cgi?id=105869
--- Comment #12 from Lyberta ---
Alright, I've installed Mesa ICD that uses LLVM 6 and the program no longer
crashes.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-
On Wed, 09 May 2018, Feng Tang wrote:
> On Wed, May 09, 2018 at 10:53:53AM +0300, Jani Nikula wrote:
>> On Wed, 09 May 2018, Feng Tang wrote:
>> > On Tue, May 08, 2018 at 10:30:19PM +0300, Jani Nikula wrote:
>> >> On Wed, 09 May 2018, Feng Tang wrote:
>> >> >> Well if it's edp probing, then atm
From: Colin Ian King
Trivial fix to spelling mistake in WARN warning message text
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/i915/intel_dp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
index dde92e
https://bugs.freedesktop.org/show_bug.cgi?id=106404
Michel Dänzer changed:
What|Removed |Added
Attachment #139359|text/x-csrc |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=106404
Michel Dänzer changed:
What|Removed |Added
Attachment #139358|text/x-log |text/plain
mime type|
From: Andrzej Pietrasiewicz
There are two Scaler devices in Exynos5433 SoCs. Add nodes for them and
their SYSMMU controllers.
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Marek Szyprowski
---
arch/arm64/boot/dts/exynos/exynos5433.dtsi | 46 ++
1 file changed, 46 ins
From: Andrzej Pietrasiewicz
There are 3 scaler devices in Exynos5420 SoCs, all are a part of MSCL
power domain. MSCL power domain and SYSMMU controllers (two per each
scaler device) have been already added to exynos5420.dtsi earlier,
so bind them to newly added devices.
Signed-off-by: Andrzej Pi
From: Andrzej Pietrasiewicz
Exynos Scaler is a hardware module, which processes graphic data fetched
from memory and transfers the resultant dato another memory buffer.
Graphics data can be up/down-scaled, rotated, flipped and converted color
space. Scaler hardware modules are a part of Exynos542
This patch adapts Exynos DRM FIMC driver to new IPP v2 core API.
The side effect of this conversion is a switch to driver component API
to register properly in the Exynos DRM core.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/Kconfig |2 +-
drivers/gpu/drm/exynos/exyn
1 - 100 of 145 matches
Mail list logo
