On 12.03.2018 08:12, Andrzej Hajda wrote:
> On 20.02.2018 07:45, Andrzej Hajda wrote:
>> Hi Inki,
>>
>> On 02.02.2018 16:11, Andrzej Hajda wrote:
>>> Hi Inki, Tobias,
>>>
>>> This is reviewed/updated/tested Tobias's patch addressing page-faults
>>> in Video Processor in interlaced mode. Plus
From: Ankit Nautiyal
This patch adds helper functions for determining if aspect-ratio is
expected in user-mode and for allowing/disallowing the aspect-ratio,
if its not expected.
Signed-off-by: Ankit Nautiyal
---
https://bugs.freedesktop.org/show_bug.cgi?id=106073
Gabriel Rauter changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.freedesktop.org/show_bug.cgi?id=106159
--- Comment #2 from Joel Sass ---
Created attachment 138958
--> https://bugs.freedesktop.org/attachment.cgi?id=138958=edit
dmesg output
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=106159
--- Comment #1 from Joel Sass ---
Created attachment 138957
--> https://bugs.freedesktop.org/attachment.cgi?id=138957=edit
Xorg.0.log
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=106159
Bug ID: 106159
Summary: When connecting or disconnecting a displayport to a DP
hub with 4.16.2+ kernel, hard freeze with frozen video
output
Product: DRI
On Fri, Apr 20, 2018 at 12:44:01PM +0200, Christian König wrote:
> > > What we need is an sg_alloc_table_from_resources(dev, resources,
> > > num_resources) which does the handling common to all drivers.
> > A structure that contains
> >
> > {page,offset,len} + {dma_addr+dma_len}
> >
> > is not
To allow bridge drivers to access state data such as the active mode in
their enable and disable handlers, pass a pointer to the connector state
to those handlers. From there the CRTC state can be accessed through
conn_state->crtc->state.
Signed-off-by: Laurent Pinchart
https://bugs.freedesktop.org/show_bug.cgi?id=104439
--- Comment #11 from magiblot ---
It has been working fine for me for quite a time with the 4.15 kernel as well.
--
You are receiving this mail because:
You are the assignee for the
On Tue, Apr 17, 2018 at 12:02:52PM +0300, Jani Nikula wrote:
> On Mon, 16 Apr 2018, "Srivatsa, Anusha" wrote:
> >>-Original Message-
> >>From: Jani Nikula [mailto:jani.nik...@linux.intel.com]
> >>Sent: Wednesday, April 11, 2018 5:27 AM
> >>To: Ian W MORRISON
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #40 from Jean Delvare ---
I believe there are 2 incarnations of this bug, with the same symptoms but
different root causes.
The first bug is affecting kernels v4.14 and v4.15, it is caused by 2 MB
allocations
On Fri, Apr 20, 2018 at 01:50:01PM +0200, Emil Lundmark wrote:
> This fixes a NULL pointer dereference that can happen if the UDL
> driver is unloaded before the framebuffer is initialized. This can
> happen e.g. if the USB device is unplugged right after it was plugged
> in.
>
JFYI, in future,
From: Ankit Nautiyal
To enable aspect-ratio support in DRM, blindly exposing the aspect
ratio information along with mode, can break things in existing
user-spaces which have no intention or support to use this aspect
ratio information.
To avoid this, a new drm
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 aspect ratios while converting
from user->kernel mode or vise
https://bugzilla.kernel.org/show_bug.cgi?id=199101
--- Comment #20 from Alex Deucher (alexdeuc...@gmail.com) ---
The revert is cc'ed to stable so it will show up in the 4.16 stable tree as
well.
--
You are receiving this mail because:
You are watching the assignee of the bug.
On 2018-04-11 11:37 AM, Christian König wrote:
> Am 11.04.2018 um 06:00 schrieb Gabriel C:
>> 2018-04-09 11:42 GMT+02:00 Christian König
>> :
>>> Am 07.04.2018 um 00:00 schrieb Jean-Marc Valin:
Hi Christian,
Thanks for the info. FYI, I've also
On Fri, Apr 20, 2018 at 07:01:46PM +0530, Nautiyal, Ankit K wrote:
> From: Ankit Nautiyal
>
> To enable aspect-ratio support in DRM, blindly exposing the aspect
> ratio information along with mode, can break things in existing
> user-spaces which have no intention or
Hi Enric,
On 05.04.2018 11:49, Enric Balletbo i Serra wrote:
> From: "Kristian H. Kristensen"
>
> To improve PSR exit latency, we speculatively start exiting when we
> receive input events. Occasionally, this may lead to false positives,
> but most of the time we get a
On Fri, Apr 20, 2018 at 07:01:47PM +0530, Nautiyal, Ankit K wrote:
> From: Ankit Nautiyal
>
> This patch adds helper functions for determining if aspect-ratio is
> expected in user-mode and for allowing/disallowing the aspect-ratio,
> if its not expected.
>
>
>-Original Message-
>From: Vivi, Rodrigo
>Sent: Friday, April 20, 2018 11:04 AM
>To: Jani Nikula
>Cc: Srivatsa, Anusha ; Ian W MORRISON
>; airl...@linux.ie; Greg KH
>;
edid should be freed once it's finished being used.
Fixes: 56fe8b6f4991 ("drm/bridge: Add RGB to VGA bridge support")
Cc: Rob Herring
Cc: Sean Paul
Cc: Maxime Ripard
Cc: Archit Taneja
Cc: Andrzej
From: "Sharma, Shashank"
Current DRM layer functions don't parse aspect ratio information
while converting a user mode->kernel mode or vice versa. This
causes modeset to pick mode with wrong aspect ratio, eventually
causing failures in HDMI compliance test cases, due
From: Ankit Nautiyal
If the user-space does not support aspect-ratio, and requests for a
modeset with mode having aspect ratio bits set, then the given
user-mode must be rejected. Secondly, while preparing a user-mode from
kernel mode, the aspect-ratio info must not
From: Ville Syrjälä
Make mode matching less confusing by allowing the caller to specify
which parts of the modes should match via some flags.
Signed-off-by: Ville Syrjälä
Reviewed-by: Shashank Sharma
---
From: Ankit Nautiyal
This patch series is a re-attempt to enable aspect ratio support in
DRM layer. Currently the aspect ratio information gets lost in translation
during a user->kernel mode or vice versa.
The old patch series
From: Ville Syrjälä
commit 6dffd431e229 ("drm: Add aspect ratio parsing in DRM layer")
cause us to not send out any VICs in the AVI infoframes. That commit
was since reverted, but if and when we add aspect ratio handing back
we need to be more careful.
Let's
https://bugzilla.kernel.org/show_bug.cgi?id=199101
--- Comment #19 from Kevin McCormack (wittyma...@yahoo.com) ---
Thanks for testing, Martin. This doesn't appear to be included in 4.16.3
looking at https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.16.3 and
Arch just bumped the kernel from
https://bugs.freedesktop.org/show_bug.cgi?id=106153
--- Comment #1 from bernhardu ---
A little addition:
Looks like I can reliably reproduce by just pressing alt+tab and holding it for
some seconds, while on the left the window previews are iterating through.
And it looks
Hi Tony!
On 20 April 2018 at 15:25, Tony Lindgren wrote:
> * Daniel Stone [180420 10:21]:
>> On 20 April 2018 at 08:09, Tomi Valkeinen wrote:
>> > It's actually not quite clear to me how manual update displays work with
>> > DRM...
https://bugs.freedesktop.org/show_bug.cgi?id=106153
Bug ID: 106153
Summary: KWin crashed when Alt+Tab-ing through open windows
Product: Mesa
Version: 17.3
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
On Thursday, April 05, 2018 04:29:42 PM Mauro Carvalho Chehab wrote:
> This driver builds cleanly with COMPILE_TEST, and it is
> needed in order to allow building drivers/media omap2
> driver.
>
> So, change the logic there to allow building it.
>
> Signed-off-by: Mauro Carvalho Chehab
On Fri, Apr 20, 2018 at 08:31:56AM +, Lisovskiy, Stanislav wrote:
>
>
> From: Daniel Vetter [daniel.vet...@ffwll.ch] on behalf of Daniel Vetter
> [dan...@ffwll.ch]
>
> > The property documentation to tie all the bits together (property, helper,
> >
On Fri, Apr 20, 2018 at 05:46:25AM -0700, Christoph Hellwig wrote:
> On Fri, Apr 20, 2018 at 12:44:01PM +0200, Christian König wrote:
> > > > What we need is an sg_alloc_table_from_resources(dev, resources,
> > > > num_resources) which does the handling common to all drivers.
> > > A structure
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #37 from MirceaKitsune ---
I have just finished preforming the first new test.
First of all I must say I'm utterly amazed at the variability of this issue:
Last week when I played Xonotic with
On 04/20/2018 08:51 AM, Daniel Vetter wrote:
Control nodes are no more!
Signed-off-by: Daniel Vetter
Cc: VMware Graphics
Cc: Sinclair Yeh
Cc: Thomas Hellstrom
---
On Fri, Apr 20, 2018 at 07:01:49PM +0530, Nautiyal, Ankit K wrote:
> From: Ankit Nautiyal
>
> We parse the EDID and add all the modes in the connector's modelist.
> This adds CEA modes with aspect ratio information too, regardless of
> whether user space requested
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #38 from MirceaKitsune ---
Created attachment 138950
--> https://bugs.freedesktop.org/attachment.cgi?id=138950=edit
cat /var/log/messages
--
You are receiving this mail because:
You are the
From: Ville Syrjälä
AVI infoframe can only carry none, 4:3, or 16:9 picture aspect
ratios. Return an error if the user asked for something different.
Cc: Shashank Sharma
Cc: "Lin, Jia"
Cc: Akashdeep Sharma
From: Ankit Nautiyal
We parse the EDID and add all the modes in the connector's modelist.
This adds CEA modes with aspect ratio information too, regardless of
whether user space requested this information or not.
This patch prunes the modes with aspect-ratio
From: Ville Syrjälä
If the user mode would specify an aspect ratio other than 4:3 or 16:9
we now silently ignore it. Maybe a better apporoach is to return an
error? Let's try that.
Also we must be careful that we don't try to send illegal picture
aspect in the
From: Ville Syrjälä
Use drm_mode_equal_no_clocks_no_stereo() in
drm_match_hdmi_mode_clock_tolerance() for consistency as we
also use it in drm_match_hdmi_mode() and the cea mode matching
functions.
This doesn't actually change anything since the input mode
comes
https://bugs.freedesktop.org/show_bug.cgi?id=106153
--- Comment #2 from bernhardu ---
Being able to reproduce it I built a set of mesa packages
with the patch from #103234.
By adding a fprintf before the return I can confirm that
this patch avoids the crash.
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #39 from MirceaKitsune ---
Created attachment 138951
--> https://bugs.freedesktop.org/attachment.cgi?id=138951=edit
journalctl --since yesterday
--
You are receiving this mail because:
You
On 04/20/2018 05:31 PM, Russell King - ARM Linux wrote:
> Hi Hans,
>
> Any comments?
I have been traveling and haven't had time to look at this. Next week will
be busy as well, but I expect to be able to look at it the week after that.
I remember from the previous series that I couldn't test it
We are likely to write multiple page entries at once and already ensure
proper write buffer flushing before GPU submit, so this improves CPU
time usage in the submit path without any downsides.
Signed-off-by: Lucas Stach
---
drivers/gpu/drm/etnaviv/etnaviv_iommu.c|
I'm not aware of any case where tracing GPU register manipulation at the
kernel level would have been useful. It only adds more indirections and
adds to the code size.
Signed-off-by: Lucas Stach
---
drivers/gpu/drm/etnaviv/Kconfig | 8 --
With etnaviv not being tied into the IOMMU framework anymore, the MMU
functions will only be called under sleeping locks. Thus we are able
to allocate the memory for the 2nd level page tables on demand without
having to deal with memory allocation in atomic context.
This speeds up driver
https://bugs.freedesktop.org/show_bug.cgi?id=103234
bernhardu changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=106153
bernhardu changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://bugs.freedesktop.org/show_bug.cgi?id=103234
--- Comment #20 from bernhardu ---
Got already commited in master branch:
https://cgit.freedesktop.org/mesa/mesa/commit/src/mesa/state_tracker/st_draw.c?id=f7542175178e724510c7918edfe09ba33c7a
But not yet in 17.3 or
https://bugs.freedesktop.org/show_bug.cgi?id=106159
--- Comment #3 from Joel Sass ---
Created attachment 138959
--> https://bugs.freedesktop.org/attachment.cgi?id=138959=edit
lshw output
--
You are receiving this mail because:
You are the assignee for the
On Thu, Apr 19, 2018 at 11:26:07PM +0530, Sandeep Panda wrote:
> Add support for Innolux TV123WAM 12.3" panel which
> is an eDP panel.
It seems like you could just use the panel-simple driver, no? Given that this
driver doesn't have any power timing, that will probably work better since the
https://bugs.freedesktop.org/show_bug.cgi?id=105680
Jose Roberto de Souza changed:
What|Removed |Added
Assignee|dri-devel@lists.freedesktop
Daniel Vetter writes:
> Signed-off-by: Daniel Vetter
> Cc: Marek Vasut
4,5 are:
Reviewed-by: Eric Anholt
It would be great to land this series up to here soon, as I was
surprised to see another new
Daniel Vetter writes:
> On Thu, Apr 19, 2018 at 12:20:35PM -0700, Eric Anholt wrote:
>> This driver will be used to support Mesa on the Broadcom 7268 and 7278
>> platforms.
>>
>> V3D 3.3 introduces an MMU, which means we no longer need CMA or vc4's
>> complicated CL/shader
On Thu, Apr 19, 2018 at 11:26:05PM +0530, Sandeep Panda wrote:
> Add support for TI's sn65dsi86 dsi2edp bridge chip.
> The chip converts DSI transmitted signal to eDP signal,
> which is fed to the connected eDP panel.
>
> This chip can be controlled via either i2c interface or
> dsi interface.
Daniel Vetter writes:
> Note that a pile of drivers don't seem to take implicit fencing into
> account, or at least don't call drm_atoimc_set_fence_for_plane().
^atomic
> Cc'ing relevant people, or at least some. Some drivers also
The HVS supports mixing fixed alpha with per-pixel alpha or
setting a fixed plane alpha in case there is no per-pixel information.
This allows us to support the generic DRM plane alpha property.
Signed-off-by: Stefan Schake
---
drivers/gpu/drm/vc4/vc4_plane.c | 14
On Fri, Apr 20, 2018 at 03:10:26PM +0200, Ondřej Jirman wrote:
> Hello,
>
> On Thu, Apr 19, 2018 at 04:02:08PM +0200, Giulio Benetti wrote:
> > Hi everybody,
> >
> > Il 19/04/2018 15:36, Chen-Yu Tsai ha scritto:
> > > On Thu, Apr 19, 2018 at 9:34 PM, Ondřej Jirman
> > >
Ping.
On 2018-04-17 06:12 PM, Andres Rodriguez wrote:
Add a new function amdgpu_ucode_request_firmware() that encapsulates a
lot of the common behaviour we have around firmware requests.
This is the first step in my quest to get rid of the following annoying
messages when my polaris10 boots
On Wed, Apr 18, 2018 at 09:39:02AM +0200, Daniel Vetter wrote:
> On Wed, Apr 18, 2018 at 5:58 AM, Keith Packard wrote:
> > Michel Dänzer writes:
> >> Time-based presentation seems to be the right approach for preventing
> >> micro-stutter in games as well,
[+Philip]
On 2018-04-20 10:47 AM, Michel Dänzer wrote:
> On 2018-04-11 11:37 AM, Christian König wrote:
>> Am 11.04.2018 um 06:00 schrieb Gabriel C:
>>> 2018-04-09 11:42 GMT+02:00 Christian König
>>> :
Am 07.04.2018 um 00:00 schrieb Jean-Marc Valin:
> Hi
Daniel Vetter writes:
> I've done a lot of history digging. The first signs of this
> optimization was introduced in i915:
I can't come up with any reason this would matter. I almost came up
with "You're doing tearing X11 front buffer rendering, and you do a
modeset
Daniel Vetter writes:
> Same justification as for drm_gem_fb_prepare_fb.
Reviewed-by: Eric Anholt
signature.asc
Description: PGP signature
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
On Wed, Apr 18, 2018 at 08:46:44AM +0300, Jani Nikula wrote:
> On Tue, 17 Apr 2018, Souptick Joarder wrote:
> > On 17-Apr-2018 9:45 PM, "Matthew Wilcox" wrote:
> >>
> >> On Tue, Apr 17, 2018 at 09:14:32PM +0530, Souptick Joarder wrote:
> >> > Not
On Sat, Apr 21, 2018 at 1:45 AM, Eric Anholt wrote:
> Stefan Schake writes:
>
>> The HVS supports mixing fixed alpha with per-pixel alpha or
>> setting a fixed plane alpha in case there is no per-pixel information.
>> This allows us to support the generic DRM
Stefan Schake writes:
> The HVS supports mixing fixed alpha with per-pixel alpha or
> setting a fixed plane alpha in case there is no per-pixel information.
> This allows us to support the generic DRM plane alpha property.
Don't we need to set needs_bg_fill based on alpha !=
Hi all:
We tested GLK DMC 1.04 FW in last week of September 2017, using the latest
drm-tip version for that time (4.14.0-rc2) and according to our results we
could declare this FW as acceptable and healthy to be used with kernel version
4.14 .
However, we cannot guarantee quality and healthy
https://bugs.freedesktop.org/show_bug.cgi?id=106164
Bug ID: 106164
Summary: dal_gpio_open_ex+0x34/0x180 [amdgpu]
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
The HVS supports mixing fixed alpha with per-pixel alpha or
setting a fixed plane alpha in case there is no per-pixel information.
This allows us to support the generic DRM plane alpha property.
Signed-off-by: Stefan Schake
---
v2: Non-opaque plane alpha can trigger the
https://bugs.freedesktop.org/show_bug.cgi?id=104001
--- Comment #30 from Marek Olšák ---
This might fix it:
https://cgit.freedesktop.org/mesa/mesa/commit/?id=d15fb766aa3c98ffbe16d050b2af4804e4b12c57
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=101739
--- Comment #15 from Marek Olšák ---
We can add "glsl_correct_derivatives_after_discard=true" to Mesa's drirc and
call it a day.
--
You are receiving this mail because:
You are the assignee for the
Control nodes are no more!
Signed-off-by: Daniel Vetter
Cc: VMware Graphics
Cc: Sinclair Yeh
Cc: Thomas Hellstrom
---
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 8
1 file changed, 4
On Thu, Apr 19, 2018 at 10:11:05AM +0300, Tomi Valkeinen wrote:
> On 19/04/18 09:34, Daniel Vetter wrote:
>
> >> But the kernel cannot know what the user wants to do, so it cannot
> >> configure the planes. If we have an HDMI output which supports 2k+ and a
> >> -2k LCD, and 4 hw planes, we can
Hi Dave,
Just cleanup by removing Exynos specific framebuffer structure
and relevant two callback functions.
Please kindly let me know if there is any problem.
Thanks,
Inki Dae
The following changes since commit 97130968839a2928869a2d25500b5855017aac7d:
Merge tag
With the ioctl and driver prep done, we can remove everything else.
Signed-off-by: Daniel Vetter
Cc: Gustavo Padovan
Cc: Maarten Lankhorst
Cc: Sean Paul
Cc: David Airlie
We've disabled control nodes in
commit 8a357d10043c75e980e7fcdb60d2b913491564af
Author: Daniel Vetter
Date: Fri Oct 28 10:10:50 2016 +0200
drm: Nerf DRM_CONTROL nodes
and there was only a minor uapi break that we've paper over with
commit
Control nodes are no more!
Signed-off-by: Daniel Vetter
Cc: Jani Nikula
Cc: Joonas Lahtinen
Cc: Rodrigo Vivi
Cc: intel-...@lists.freedesktop.org
---
drivers/gpu/drm/i915/i915_drv.c |
Hi Jacopo,
On 04/18/2018 05:40 PM, Jacopo Mondi wrote:
> Document Thine THC63LVD1024 LVDS decoder device tree bindings.
>
> Signed-off-by: Jacopo Mondi
> Reviewed-by: Andrzej Hajda
> Reviewed-by: Niklas Söderlund
Hi Jacopo,
On 04/18/2018 05:40 PM, Jacopo Mondi wrote:
> Add DRM bridge driver for Thine THC63LVD1024 LVDS to digital parallel
> output converter.
>
> Signed-off-by: Jacopo Mondi
> Reviewed-by: Andrzej Hajda
> Reviewed-by: Niklas Söderlund
From: Stanislav Lisovskiy
Added content_type property to drm_connector_state
in order to properly handle external HDMI TV content-type setting.
v2:
* Moved helper function which attaches content type property
to the drm core, as was suggested.
Removed
From: Stanislav Lisovskiy
Added encoding of drm content_type property from drm_connector_state
within AVI infoframe in order to properly handle external HDMI TV
content-type setting.
This requires also manipulationg ITC bit, as stated in
HDMI spec.
v2:
* Moved
From: Stanislav Lisovskiy
Added content type setting property to drm_connector(part 1)
and enabled transmitting it with HDMI AVI infoframes
for i915(part 2).
Stanislav Lisovskiy (2):
drm: content-type property for HDMI connector
i915: content-type property for
Gerd Hoffmann (4):
qxl: remove qxl_io_log()
qxl: move qxl_send_monitors_config()
qxl: hook monitors_config updates into crtc, not encoder.
qxl: drop dummy functions
drivers/gpu/drm/qxl/qxl_drv.h | 3 -
drivers/gpu/drm/qxl/qxl_cmd.c | 36 +
qxl_io_log() sends messages over to the host (qemu) for logging.
Remove the function and all callers, we can just use standard
DRM_DEBUG calls (and if needed a serial console).
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/qxl/qxl_drv.h | 3 ---
Needed to avoid a forward declaration in a followup patch.
Pure code move, no functional change.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/qxl/qxl_display.c | 47 +++
1 file changed, 23 insertions(+), 24 deletions(-)
diff --git
The encoder callbacks are only called in case the video mode changes.
So any layout changes without mode changes will go unnoticed.
Add qxl_crtc_update_monitors_config(), based on the old
qxl_write_monitors_config_for_encoder() function. Hook it into the
enable, disable and flush atomic crtc
These days drm core checks function pointers everywhere before calling
them. So we can drop a bunch of dummy functions now.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/qxl/qxl_display.c | 50 ---
1 file changed, 50 deletions(-)
diff
We should get drvdata from struct device directly. Going via
platform_device is an unneeded step back and forth.
Signed-off-by: Wolfram Sang
---
Build tested only. buildbot is happy. Please apply individually.
drivers/gpu/drm/vc4/vc4_drv.c | 3 +--
1 file
On Tue, Apr 17, 2018 at 08:31:11PM +0300, Dmitry Osipenko wrote:
> On 17.04.2018 12:01, Daniel Vetter wrote:
> > On Mon, Apr 16, 2018 at 03:16:28PM +0300, Dmitry Osipenko wrote:
> >> This new property allows userspace to apply custom color conversion
> >> coefficients per plane, making possible to
On Fri, 20 Apr 2018, Ian W MORRISON wrote:
> I've performed backport testing and some additional analysis as follows:
What testing did you do beyond booting? Did you run igt?
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
On Wed, Apr 18, 2018 at 07:42:56AM +0200, Gerd Hoffmann wrote:
> s/PAGE_SIZE/PAGE_MASK/
>
> Luckily release_offset is never larger than PAGE_SIZE, so the bug has no
> bad side effects and managed to stay unnoticed for years that way ...
>
> Signed-off-by: Gerd Hoffmann
On Thu, Apr 19, 2018 at 12:20:35PM -0700, Eric Anholt wrote:
> This driver will be used to support Mesa on the Broadcom 7268 and 7278
> platforms.
>
> V3D 3.3 introduces an MMU, which means we no longer need CMA or vc4's
> complicated CL/shader validation scheme. This massively changes the
> GEM
Am 20.04.2018 um 09:13 schrieb Daniel Vetter:
On Thu, Apr 19, 2018 at 01:16:57AM -0700, Christoph Hellwig wrote:
On Mon, Apr 16, 2018 at 03:38:56PM +0200, Daniel Vetter wrote:
We've broken that assumption in i915 years ago. Not struct page backed
gpu memory is very real.
Of course we'll never
On Thu, Apr 19, 2018 at 01:16:57AM -0700, Christoph Hellwig wrote:
> On Mon, Apr 16, 2018 at 03:38:56PM +0200, Daniel Vetter wrote:
> > We've broken that assumption in i915 years ago. Not struct page backed
> > gpu memory is very real.
> >
> > Of course we'll never feed such a strange sg table to
On 20/04/18 10:00, Daniel Vetter wrote:
(Adding Benoit back, he was dropped at some point in the thread)
> Stuff randomly not working is officially how atomic works. That's what the
> TEST_ONLY mode is for. There's a lot more than virtualized planes that
> might or might not push any given plane
On Thu, Apr 19, 2018 at 03:43:19PM +0200, Hans de Goede wrote:
> Hi,
>
> On 05-04-18 15:26, Daniel Vetter wrote:
> > On Thu, Apr 5, 2018 at 1:47 PM, Hans de Goede wrote:
> > > Hi,
> > >
> > >
> > > On 05-04-18 09:14, Daniel Vetter wrote:
> > > >
> > > > On Fri, Mar 30,
Hi!
I naively thought that since there was support for both nxp,tda19988 (in
the tda998x driver) and the atmel-hlcdc, things would be a smooth ride.
But it wasn't, so I started looking around and realized I had to fix
things.
In v1 and v2 I fixed things by making the atmel-hlcdc driver a master
DRM_BUS_FLAG_DATA_* flags, defined in drm_connector.h header file are
used to swap ordering of LVDS RGB format to accommodate DRM objects
that need to handle LVDS components ordering.
Now that the only 2 users of DRM_BUS_FLAG_DATA_* flags have been ported
to use the newly introduced
We should get drvdata from struct device directly. Going via
platform_device is an unneeded step back and forth.
Signed-off-by: Wolfram Sang
---
Build tested only. buildbot is happy. Please apply individually.
drivers/gpu/drm/msm/msm_drv.c | 3 +--
1 file
1 - 100 of 169 matches
Mail list logo