On Tue, May 07, 2019 at 05:27:12PM +0200, Sébastien Szymanski wrote:
> This patch adds support for the Armadeus ST0700 Adapt. It comes with a
> Santek ST0700I5Y-RBSLW 7.0" WVGA (800x480) TFT and an adapter board so
> that it can be connected on the TFT header of Armadeus Dev boards.
>
> Cc:
https://bugs.freedesktop.org/show_bug.cgi?id=110721
--- Comment #17 from Doug Ty ---
19.0.5 also completely broke Blender 2.8 for me, which now crashes whenever I
select any geometry in edit more. 19.0.4 was fine.
Can confirm that building master & reverting "mesa: unreference current winsys
https://bugs.freedesktop.org/show_bug.cgi?id=110702
--- Comment #4 from Pierre Ossman ---
As a workaround, is it possible to configure VA-API to refuse to handle this
specific format? It would be nice to have to disable hardware acceleration
entirely.
--
You are receiving this mail because:
Hi Daniel.
One detail I noticed while brosing the changes.
>
> @@ -1064,9 +1062,13 @@ static void fbcon_init(struct vc_data *vc, int init)
> int logo = 1, new_rows, new_cols, rows, cols, charcnt = 256;
> int cap, ret;
>
> - if (info_idx == -1 || info == NULL)
> + if
Hi Daniel
> It's dead code, and removing it avoids me having to understand
> what it's doing with lock_fb_info.
I pushed the series through my build tests which include the sh
architecture.
One error and one warning was triggered from sh_mobile_lcdcfb.c.
The rest was fine.
The patch below
fix below warnings reported by coccicheck
/drivers/gpu/drm/tegra/drm.c:509:1-3: WARNING: PTR_ERR_OR_ZERO can be
used
./drivers/gpu/drm/tegra/gem.c:419:1-3: WARNING: PTR_ERR_OR_ZERO can be
used
Signed-off-by: Hariprasad Kelam
---
drivers/gpu/drm/tegra/drm.c | 6 ++
fix below warnings reported by coccicheck
./drivers/gpu/drm/omapdrm/dss/hdmi_phy.c:197:1-3: WARNING:
PTR_ERR_OR_ZERO can be used
./drivers/gpu/drm/omapdrm/dss/hdmi4_core.c:937:1-3: WARNING:
PTR_ERR_OR_ZERO can be used
./drivers/gpu/drm/omapdrm/dss/hdmi5_core.c:913:1-3: WARNING:
PTR_ERR_OR_ZERO
https://bugs.freedesktop.org/show_bug.cgi?id=110759
--- Comment #1 from Doug Ty ---
Update:
This also happens with the latest development build of mesa
(19.2.0_devel.111215.1dc593e9b93 as compiled via mesa-git package on AUR)
I believe this is related to Bug 110721:
On Sat, May 25, 2019 at 9:30 AM Hariprasad Kelam
wrote:
>
> fix below warnings reported by coccicheck
>
Hi,
a similar patch was nacked because it makes backports more difficult:
https://lore.kernel.org/lkml/3dec4093-824e-b13d-d712-2dedd445a...@ti.com/
Tomi, what's your thought?
--
Matteo
https://bugs.freedesktop.org/show_bug.cgi?id=110759
Bug ID: 110759
Summary: Blender 2.8 crash when selecting geometry with 19.0.5
Product: Mesa
Version: 19.0
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
On Mon, May 13, 2019 at 12:18:27AM +0530, Jagan Teki wrote:
> Vertical front and back porch values on existing driver are swapped.
> The existing timings are still working as expected, but to make sure
> it can compatible with techstar ts8550b bsp timings this patch swap
> the same values.
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=110760
Bug ID: 110760
Summary: Low FPS in Quake Champions with Vega20
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Hi Linus
On Wed, May 22, 2019 at 09:21:53AM +0200, Linus Walleij wrote:
> This adds a new DRM driver for the ST-Ericsson Multi Channel
> Display Engine, MCDE display controller.
This driver breaks build in drm-misc-next at the moment.
Following patch fixed both a build warning and a build
https://bugs.freedesktop.org/show_bug.cgi?id=110721
--- Comment #18 from Doug Ty ---
*** Bug 110759 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
On Sat, 2019-05-25 at 00:39 +0200, Thomas Hellström wrote:
> Hi, Emil
>
> On Fri, 2019-05-24 at 16:26 +0100, Emil Velikov wrote:
> > On 2019/05/24, Thomas Hellstrom wrote:
> > > On Fri, 2019-05-24 at 13:14 +0100, Emil Velikov wrote:
> > > > On 2019/05/23, Thomas Hellstrom wrote:
> > > > > Hi,
https://bugs.freedesktop.org/show_bug.cgi?id=110759
Doug Ty changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
On Wed, May 15, 2019 at 06:06:12PM +0200, Lukasz Majewski wrote:
> This commit adds support for KOE's 5.7" display.
>
> Signed-off-by: Lukasz Majewski
> Reviewed-by: Rob Herring
Thanks, applied.
Sam
On Wed, May 15, 2019 at 06:04:28PM +0200, Lukasz Majewski wrote:
> This commit adds documentation entry description for KOE's 5.7" display.
>
> Signed-off-by: Lukasz Majewski
Thanks, applied
Sam
___
dri-devel mailing list
fix below warnings reported by coccicheck
./drivers/gpu/drm/sun4i/sun8i_hdmi_phy_clk.c:174:1-3: WARNING:
PTR_ERR_OR_ZERO can be used
./drivers/gpu/drm/sun4i/sun4i_hdmi_tmds_clk.c:236:1-3: WARNING:
PTR_ERR_OR_ZERO can be used
./drivers/gpu/drm/sun4i/sun4i_hdmi_i2c.c:285:1-3: WARNING:
Add proper forward declarations to minimize dependencies on
other header files.
Just add enough that we can safely include all header files in
alphabetically order in relevant files.
Signed-off-by: Sam Ravnborg
Acked-by: Daniel Vetter
Acked-by: Patrik Jakobsson
Cc: David Airlie
---
The DRM_UDELAY wrapper from drm_os_linux.h is used in a few places,
all other places calls udelay() with no wrapper.
There is no reason to continue to use this wrapper - so drop it
and direct call udelay().
Signed-off-by: Sam Ravnborg
Acked-by: Daniel Vetter
Acked-by: Patrik Jakobsson
Cc:
The header file gma_drm.h is empty so remove it and
drop all uses of the file.
Signed-off-by: Sam Ravnborg
Acked-by: Daniel Vetter
Acked-by: Patrik Jakobsson
Cc: David Airlie
---
drivers/gpu/drm/gma500/cdv_device.c | 2 +-
drivers/gpu/drm/gma500/gem.c | 2 +-
Drop use of drmP.h from all header files in drm/gma500.
Fix fallout in all files.
In some cases moved include lines and sorted them too.
With drmP.h removed from all header files it can now be removed from
each .c file without any further dependencies
Signed-off-by: Sam Ravnborg
Acked-by: Daniel
Just a quick (final) probe. If there are no further feedback I will
commit this set sunday.
Added intel-...@lists.freedesktop.org just to get a bit more coverage.
The following patchset remove use of the deprecated drmP.h
header file in the gma500 driver.
As preparation an empty header file is
Drop remaining uses of the deprecated drmP.h header
file in drm/gma500.
Replaced drmp.h with forward declarations and/or include
files as relevant.
Moved all include files to blocks in following order:
\#include
\#include
\#include
\#include ""
And within each block sort the include files
https://bugs.freedesktop.org/show_bug.cgi?id=109239
--- Comment #13 from Raman Gupta ---
Still having this problem with newer software:
Linux edison 5.0.16-200.fc29.x86_64 #1 SMP Tue May 14 18:27:35 UTC 2019 x86_64
x86_64 x86_64 GNU/Linux
Mesa 18.3.6-3.fc29
It seems to happen more often when
Previously center scaling would get scaling applied to it (when it was
only supposed to center the image), and aspect-corrected scaling did not
always correctly pick whether to reduce width or height for a particular
combination of inputs/outputs.
Bugzilla:
On Fri, 24 May 2019 09:44:55 -0300 Jason Gunthorpe wrote:
> Now that -mm merged the basic hmm API skeleton I think running like
> this would get us quickly to the place we all want: comprehensive in tree
> users of hmm.
>
> Andrew, would this be acceptable to you?
Sure. Please take care not
Hi Daniel.
On Fri, May 24, 2019 at 10:53:46AM +0200, Daniel Vetter wrote:
> There's a callchain of:
>
> fbcon_fb_blaned -> do_(un)blank_screen -> consw->con_blank
^^
Spelling error - as this is a callchain it would be good to have it
fixed.
Patch itself looks fine.
Sam
Hi Daniel.
Good work, nice cleanup all over.
A few comments to a few patches - not something that warrant a
new series to be posted as long as it is fixed before the patches are
applied.
> btw for future plans: I think this is tricky enough (it's old code and all
> that) that we should let
https://bugs.freedesktop.org/show_bug.cgi?id=106302
--- Comment #2 from s...@vestigecounty.com ---
Pierre-Eric, in my interpretation of OpenGL(R) ES Version 3.0.5 (November 3,
2016) Specification, Appendix 4: Shared Objects and Multiple Contexts, D.3.
Propagating Changes to Objects, Rule 4:...
https://bugs.freedesktop.org/show_bug.cgi?id=107296
--- Comment #12 from John Pathy ---
Created attachment 144345
--> https://bugs.freedesktop.org/attachment.cgi?id=144345=edit
Complete kern.log
I have attached a complete copy of my kern.log as a reference to show the
trace.
--
You are
fix below warning reported by coccicheck
./drivers/gpu/drm/bridge/analogix/analogix_dp_core.c:1414:6-8: WARNING:
possible condition with no effect (if == else)
Signed-off-by: Hariprasad Kelam
---
drivers/gpu/drm/bridge/analogix/analogix_dp_core.c | 2 --
1 file changed, 2 deletions(-)
diff
Hi!
Dne četrtek, 16. maj 2019 ob 13:19:06 CEST je Robin Murphy napisal(a):
> On 16/05/2019 00:22, Rob Herring wrote:
> > On Wed, May 15, 2019 at 5:06 PM Clément Péron
wrote:
> >> Hi Robin,
> >>
> >> On Tue, 14 May 2019 at 23:57, Robin Murphy wrote:
> >>> On 2019-05-14 10:22 pm, Clément Péron
https://bugs.freedesktop.org/show_bug.cgi?id=107296
--- Comment #13 from John Pathy ---
I have the same problem with my 2400G.
My kernel is as follows
[0.00] Linux version 4.19.0-5-amd64 (debian-ker...@lists.debian.org)
(gcc version 8.3.0 (Debian 8.3.0-7)) #1 SMP Debian 4.19.37-3
Higher layers tend to add a lot of modes not actually in the EDID, such
as the standard DMT modes. Changing this would be extremely intrusive to
everyone, so just force the scaler more often. There are no practical
cases we're aware of where a LVDS/eDP panel has multiple resolutions
exposed, and
https://bugzilla.kernel.org/show_bug.cgi?id=203627
--- Comment #2 from Aleksandr Mezin (mezin.alexan...@gmail.com) ---
vega10_sos.bin
Copying that file from previous firmware release into /lib/firmware/amdgpu
makes the system boot again with 4.19.45
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=110637
--- Comment #9 from Alexander Mezin ---
Tried Mesa 19.1.0-rc3
Geekbench hangs, but there are no immediate errors in dmesg. It looks like gpu
is doing something based on 'sensors' output (~130 W power consumption, at idle
it is <20W). And power
38 matches
Mail list logo
