https://bugs.freedesktop.org/show_bug.cgi?id=102358
--- Comment #1 from Michel Dänzer ---
Can you bisect which Mesa Git commit introduced the issue?
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=102300
--- Comment #4 from Michel Dänzer ---
Please attach the Xorg configuration snippets you created in
/etc/X11/xorg.conf.d and/or /usr/share/X11/xorg.conf.d , in particular anything
related to a mode named "1920x1080_60.00".
https://bugzilla.kernel.org/show_bug.cgi?id=196635
--- Comment #12 from Michel Dänzer (mic...@daenzer.net) ---
(In reply to Janpieter Sollie from comment #11)
> disabling CIK support in my kernel and upgrading it to rc6 solved the
> problem.
> Probably CIK and SI are not really cooperating
https://bugs.freedesktop.org/show_bug.cgi?id=98324
--- Comment #6 from Darren Salt ---
That patch makes no difference to this problem.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #33 from Shmerl ---
Created attachment 133707
--> https://bugs.freedesktop.org/attachment.cgi?id=133707=edit
Save file near freeze area (Devil's Pit, Velen)
Just turn around a bit, especially looking at
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #32 from Shmerl ---
The problem still happen with kernel 4.13:
penGL renderer string: AMD Radeon (TM) RX 480 Graphics (POLARIS10 / DRM 3.18.0
/ 4.13.0-rc5-amd64, LLVM 5.0.0)
OpenGL core profile version string:
Hi Daniel,
On Tuesday 22 August 2017 12:01 PM, Daniel Vetter wrote:
On Sat, Aug 19, 2017 at 11:58:17PM +0530, Arvind Yadav wrote:
i2c_device_id are not supposed to change at runtime. All functions
working with i2c_device_id provided by work with
const i2c_device_id. So mark the non-const
On Mon, Aug 21, 2017 at 11:53:01AM +0100, Lorenzo Pieralisi wrote:
> On Thu, Aug 17, 2017 at 09:30:28PM +1000, Daniel Axtens wrote:
> > A system without PCI legacy resources (e.g. ARM64) may find that no
> > default/boot VGA device has been marked, because the VGA arbiter
> > checks for legacy
On Monday 07 August 2017 11:09 PM, David Lechner wrote:
> ARM: dts: da850-lego-ev3: Add node for LCD display
> ARM: davinci_all_defconfig: enable tinydrm and ST7586
Queuing these two patches (4/5 and 5/5) through davinci tree.
Thanks,
Sekhar
___
On Sat, Aug 19, 2017 at 01:52:26PM +0530, Bhumika Goyal wrote:
> Make this const as it is only stored in the type field of a device
> structure, which is const.
> Done using Coccinelle.
>
> Signed-off-by: Bhumika Goyal
Acked-by: Heikki Krogerus
https://bugzilla.kernel.org/show_bug.cgi?id=196733
Ilia Mirkin (imir...@alum.mit.edu) changed:
What|Removed |Added
CC||imir...@alum.mit.edu
https://bugzilla.kernel.org/show_bug.cgi?id=196733
Bug ID: 196733
Summary: GM107 video card displays blank screen after 4.12
update with error EDID checksum
Product: Drivers
Version: 2.5
Kernel Version: 4.12.8
https://bugs.freedesktop.org/show_bug.cgi?id=98324
--- Comment #5 from dwagner ---
JFYI: A patch attached to report
https://bugs.freedesktop.org/show_bug.cgi?id=102323 provided some improved
behaviour regarding switched-off HDMI displays.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=102323
--- Comment #3 from dwagner ---
The good news: Your draft fix works for me - the system no longer crashes when
woken up from S3 with HDMI display off. Thanks a lot for this really important
fix.
The mediocre news: Lots
This is partly to silence a static checker warning:
drivers/gpu/drm/amd/amdgpu/ci_dpm.c:4553 ci_set_mc_special_registers()
error: buffer overflow 'table->mc_reg_address' 16 <= 16
The story is that it's valid to exit the loop with "j" less than or equal
to
This is partly to silence a static checker warning:
drivers/gpu/drm/amd/amdgpu/ci_dpm.c:4553 ci_set_mc_special_registers()
error: buffer overflow 'table->mc_reg_address' 16 <= 16
The story is that it's valid to exit the loop with "j" less than or equal
to
https://bugs.freedesktop.org/show_bug.cgi?id=101026
--- Comment #3 from dwagner ---
One more cosmetic note: Despite HDMI 2 modes with up to 600MHz working fine for
me, now, log messages emitted still talk about "max TMDS clock 300MHz", but
other messages and the display
https://bugs.freedesktop.org/show_bug.cgi?id=101026
--- Comment #2 from dwagner ---
I just wanted to mention here that I currently use an RX 460 GPU to drive an
HDMI display at 3840x2160 60Hz, this became possible some time ago when DC code
was merged into the open source
https://bugs.freedesktop.org/show_bug.cgi?id=102300
f...@mt2015.com changed:
What|Removed |Added
Summary|Second monitor shows black |Missing 1920x1080_59.94Hz
Actually adding mailing lists ...
On Tue, Aug 22, 2017 at 9:39 PM, Daniel Vetter wrote:
> Hi Bram,
>
> Adding mailing lists, private mails to maintainers doesn't scale.
>
> On Tue, Aug 22, 2017 at 9:12 PM, Bram Vlerick wrote:
>> Hi Daniel,
>>
>> I was
Currently the hikey dsi logic cannot generate accurate byte
clocks values for all pixel clock values. Thus if a mode clock
is selected that cannot match the calculated byte clock, the
device will boot with a blank screen.
This patch uses the new mode_valid callback (many thanks to
Jose Abreu for
https://bugs.freedesktop.org/show_bug.cgi?id=102358
har...@gmx.de changed:
What|Removed |Added
Summary|WarThunder freezes always |WarThunder freezes at
https://bugs.freedesktop.org/show_bug.cgi?id=102358
har...@gmx.de changed:
What|Removed |Added
Summary|WarThunder freezes always |WarThunder freezes always
https://bugs.freedesktop.org/show_bug.cgi?id=100991
Matt Turner changed:
What|Removed |Added
Component|Drivers/DRI/i915|Drivers/DRI/i965
Hi All,
When I last send this patch not everyone was enthusiastic about this
patch. As already mentioned in the v2 discussion, solving this in userspace
is not really feasible since there is no single place to fix it there, it
will need fixing in at least 6 different places from the top of my
On some (Bay Trail) devices the LCD panel is mounted upside-down.
This commit uses the code to read back the initial rotation of the
primary plane in get_initial_plane_config from Ville Syrjala's
"drm/fb-helper: Inherit rotation wip" patch and when re-using the
initial fb it stores that in
On Tue, Aug 22, 2017 at 9:47 AM, Fabio Estevam wrote:
> Hi,
>
> I am running kernel 4.12.8 and mesa 17.1.6 on a imx6q, but glmark2
> never runs successfully until the end. It always crashes like this:
>
> ** Failed to set swap interval. Results may be bounded above by refresh
https://bugs.freedesktop.org/show_bug.cgi?id=98324
Darren Salt changed:
What|Removed |Added
Attachment #127405|0 |1
is
https://bugs.freedesktop.org/show_bug.cgi?id=102323
--- Comment #2 from Harry Wentland ---
Thanks for reporting this. I've seen this myself and been debugging it a bit. I
have a patch but am not completely happy with it as it seems like it leaves a
pipe running in some
https://bugs.freedesktop.org/show_bug.cgi?id=102323
--- Comment #1 from Harry Wentland ---
Created attachment 133672
--> https://bugs.freedesktop.org/attachment.cgi?id=133672=edit
Draft fix
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=98324
--- Comment #3 from Darren Salt ---
Created attachment 133671
--> https://bugs.freedesktop.org/attachment.cgi?id=133671=edit
Kernel log showing normal blank & unblank.
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=98324
--- Comment #2 from Darren Salt ---
Currently running amd-staging-drm-next 0313e8bfbbdd. The behaviour is now
improved, though is still regressed vs. mainline.
Unblanking works. If I allow the problem monitor to
DRM core already checks the validity of the pixelformat.
Signed-off-by: Tobias Jakobi
---
drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 4 +---
drivers/gpu/drm/exynos/exynos7_drm_decon.c| 7 +--
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 8 +---
A recent commit (272725c7db4da1fd3229d944fc76d2e98e3a144e) has removed
the use of 'bits_per_pixel' in DRM. However the corresponding Exynos
driver code still uses the ambiguous 'bpp', even though it is now
initialized from fb->cpp[0].
Consistenly use 'cpp' in FIMD, DECON7 and DECON5433 drivers.
Both FIMD and DECON5433 support a pitch in bytes.
Signed-off-by: Tobias Jakobi
---
drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 1 +
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 1 +
2 files changed, 2 insertions(+)
diff --git
In some of subdrivers we compute something like 'pitch / cpp' at some
point, silently assuming that the pitch (which is in bytes) is
divisible by the buffer's cpp. This must not be true, in particular
it depends on the underlying hardware.
If userspace should request such a setup, we should
We always translate the dma address such that the offsets of
the source image are zero. Hence we can remove manipulation of
the MXR_GRAPHIC_SXY(win) register and just zero them once
in mixer_win_reset().
Signed-off-by: Tobias Jakobi
---
DRM core already checks in drm_atomic_plane_check() if the
pixelformat is valid. Hence we can collapse the default case
of the switch statement with the XRGB case.
No functional change.
Signed-off-by: Tobias Jakobi
---
drivers/gpu/drm/exynos/exynos_mixer.c |
DRM core already checks in drm_atomic_plane_check() if the
pixelformat is valid. Hence we can drop the default case of
the switch statement and collapse most of the code.
Also rename the two booleans to reflect what true/false
actually means, and to avoid mixing CrCb/NV21 descriptions.
No
The video processor supports a tiled version of the NV12 format,
known as NV12MT in V4L2 terms. The support was removed in commit
083500baefd5f4c215a5a93aef2492c1aa775828 due to not being a real
pixel format, but rather NV12 with a special memory layout.
With the introduction of FB modifiers, we
Hello,
this is the second iteration of [1], with the following changes:
- split patch 3/8 (suggested by Inki)
- zero init registers in patch 4/8 (suggested by Inki)
- rephrased commit description of patch 5/8 to make it more
clear that this behaviour depends on the hw
- replace zero with linear
The current comment sounds like the division op is done to
compensate for some hardware erratum. But the chroma plane
having half the height of the luma plane is just the way
NV12/NV21 is defined, so clarify this behaviour.
Signed-off-by: Tobias Jakobi
---
ping? Haven't seen any comments on amd-gfx or dri-devel.
Cheers,
Tom
On 18/08/17 10:07 AM, Tom St Denis wrote:
These functions replace a section of common code found
in radeon/amdgpu drivers (and possibly others) as part
of the ttm_tt_*populate() callbacks.
Signed-off-by: Tom St Denis
+ Sean
On Mon, 2017-08-21 at 18:16 +0200, Daniel Vetter wrote:
> On Sat, Aug 19, 2017 at 01:05:58PM +0100, Chris Wilson wrote:
> > This is the same bug as we fixed in commit f6cd7daecff5 ("drm: Release
> > driver references to handle before making it available again"), but now
> > the exposure is
Reviewed-by: Christian König for this one as
well as the two patches for radeon and amdgpu.
Feel free to also add my Acked-by to the nouveau patch.
Regards,
Christian.
Am 22.08.2017 um 13:13 schrieb Tom St Denis:
ping? Haven't seen any comments on amd-gfx or
Hi,
I am running kernel 4.12.8 and mesa 17.1.6 on a imx6q, but glmark2
never runs successfully until the end. It always crashes like this:
** Failed to set swap interval. Results may be bounded above by refresh rate.
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 63 FrameTime: 15.873 ms
[
https://bugs.freedesktop.org/show_bug.cgi?id=102358
Bug ID: 102358
Summary: WarThunder freezes always with vblanc=1
Product: Mesa
Version: git
Hardware: Other
OS: Linux (All)
Status: NEW
Severity: normal
https://bugzilla.kernel.org/show_bug.cgi?id=196635
Janpieter Sollie (janpieter.sol...@dommel.be) changed:
What|Removed |Added
Status|NEW |RESOLVED
Am Dienstag, den 22.08.2017, 11:58 +0200 schrieb Christian Gmeiner:
[...]
> >> @@ -1444,6 +1463,11 @@ static irqreturn_t irq_handler(int irq, void *data)
> >>
> >> dev_dbg(gpu->dev, "event %u\n", event);
> >>
> >> + if (gpu->event[event].sync_point) {
> >>
Hi,
On 22-08-17 11:00, Imre Deak wrote:
On Sun, Aug 20, 2017 at 02:59:20PM +0200, Hans de Goede wrote:
diff --git a/arch/x86/platform/intel/iosf_mbi.c
b/arch/x86/platform/intel/iosf_mbi.c
index a952ac199741..a5361fd11e6e 100644
--- a/arch/x86/platform/intel/iosf_mbi.c
+++
Hi Lucas
2017-08-08 12:34 GMT+02:00 Lucas Stach :
> Am Samstag, den 22.07.2017, 11:53 +0200 schrieb Christian Gmeiner:
>> In order to support performance counters in a sane way we need to provide
>> a method to sync the GPU with the CPU. The GPU can process multpile
Hi Hans,
>>
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
On 11/08/17 13:57, Tomi Valkeinen wrote:
>>
>>> I'm doing some testing with this series on my panda. One issue I see is
>>> that when I unload the display
On Sun, Aug 20, 2017 at 02:59:20PM +0200, Hans de Goede wrote:
> intel_uncore_forcewake_reset() does forcewake puts and gets as such
> we need to make sure that no-one tries to access the PUNIT->PMIC bus
> (on systems where this bus is shared) while it runs, otherwise bad
> things happen.
>
>
Hi Lucas,
2017-08-22 10:39 GMT+02:00 Lucas Stach :
> Hi Christian,
>
> Am Dienstag, den 22.08.2017, 10:27 +0200 schrieb Christian Gmeiner:
>> Hi Lucas.
>>
>> Thanks for your review - hopefully there will be only one last v3
>> series of that patches.
>
> Yep, I would
Hi Christian,
Am Dienstag, den 22.08.2017, 10:27 +0200 schrieb Christian Gmeiner:
> Hi Lucas.
>
> Thanks for your review - hopefully there will be only one last v3
> series of that patches.
Yep, I would really like to merge this series. It's been in the making
for long enough. :)
> 2017-08-08
2017-08-08 12:49 GMT+02:00 Lucas Stach :
> Am Samstag, den 22.07.2017, 11:53 +0200 schrieb Christian Gmeiner:
>> With 'sync points' we can sample the reqeustes perform signals
>> before and/or after the submited command buffer.
>>
>> Signed-off-by: Christian Gmeiner
2017-08-08 12:13 GMT+02:00 Lucas Stach :
> Am Samstag, den 22.07.2017, 11:53 +0200 schrieb Christian Gmeiner:
>> Changes from v1 -> v2:
>> - renamed submit_perfmon_request() to submit_perfmon_validate()
>> - extended flags validation
>> - added comment about offset 0
>> -
Am 21.08.2017 um 23:42 schrieb Jason Ekstrand:
On Wed, Aug 16, 2017 at 1:10 PM, Jason Ekstrand > wrote:
On Wed, Aug 16, 2017 at 9:53 AM, Christian König
> wrote:
Hi Lucas.
Thanks for your review - hopefully there will be only one last v3
series of that patches.
2017-08-08 12:00 GMT+02:00 Lucas Stach :
> Am Samstag, den 22.07.2017, 11:53 +0200 schrieb Christian Gmeiner:
>> This makes it possible to allocate multiple events under
Hi,
> These are both from Gerd. Gerd, do you have any objection to using a
> union to provide either the dmabuf fd or region index?
No.
> > It's like we want to propose a general interface used to share
> > guest's buffer with host. And the
> > general interface, so far, has two choice:
https://bugs.freedesktop.org/show_bug.cgi?id=100991
tompl...@gmail.com changed:
What|Removed |Added
Priority|medium |high
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=100991
tompl...@gmail.com changed:
What|Removed |Added
Assignee|intel-3d-bugs@lists.freedes |dri-devel@lists.freedesktop
https://bugs.freedesktop.org/show_bug.cgi?id=98324
Michel Dänzer changed:
What|Removed |Added
Summary|amd-staging-4.7: problems |[DC]
https://bugs.freedesktop.org/show_bug.cgi?id=102323
Michel Dänzer changed:
What|Removed |Added
CC|
On Mon, Aug 21, 2017 at 04:37:32PM +0530, Arvind Yadav wrote:
> drm_fb_helper_funcs are not supposed to change at runtime.
> All functions working with drm_fb_helper_funcs provided
> by work with const drm_fb_helper_funcs.
> So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav
On Sat, Aug 19, 2017 at 11:58:17PM +0530, Arvind Yadav wrote:
> i2c_device_id are not supposed to change at runtime. All functions
> working with i2c_device_id provided by work with
> const i2c_device_id. So mark the non-const structs as const.
All applied.
btw I think this isn't your first
On Mon, Aug 21, 2017 at 08:53:08PM +0200, Noralf Trønnes wrote:
> Hi,
>
> I'm looking into what happens if fbdev has open file handles when
> drm_dev_unplug() is called. udl is the only user of drm_dev_unplug(),
> but AFAICT it will keel over if unplugged with a /dev/fb handle open
> since fbdev
67 matches
Mail list logo