Hi, Peng!
On 04/12/2018 05:21 AM, Peng Fan wrote:
Hi Oleksandr,
Just have a question, is this drm/xen-front stuff orthogonal to xen shared
coprocessor framework for gpu, or are they exclusive?
They are orthogonal
Thanks,
Peng.
___
dri-devel
Code is expecing to observe the same number of buffers returned from
dma_map_sg() function compared to sg_alloc_table_from_pages(). This
doesn't hold true universally especially for systems with IOMMU.
The hardware actually needs the dma_address on a page by page basis.
Joining multiple
Hi Oleksandr,
Just have a question, is this drm/xen-front stuff orthogonal to xen shared
coprocessor framework for gpu, or are they exclusive?
Thanks,
Peng.
> Subject: [Xen-devel] [PATCH v6 0/1] drm/xen-front: Add support for Xen PV
> display frontend
>
> From: Oleksandr Andrushchenko
2018-04-12 0:20 GMT+02:00 Gabriel C :
> 2018-04-11 20:35 GMT+02:00 Jean-Marc Valin :
>> On 04/11/2018 05:37 AM, Christian König wrote:
With your patches my EPYC box is unusable with 4.15++ kernels.
The whole Desktop is acting weird. This one
On 4/11/2018 8:03 AM, Robin Murphy wrote:
> On 10/04/18 21:59, Sinan Kaya wrote:
>> Code is expecing to observe the same number of buffers returned from
>> dma_map_sg() function compared to sg_alloc_table_from_pages(). This
>> doesn't hold true universally especially for systems with IOMMU.
>
>
2018-04-11 11:37 GMT+02:00 Christian König :
> 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,
On 04/11/2018 05:37 AM, Christian König wrote:
>> With your patches my EPYC box is unusable with 4.15++ kernels.
>> The whole Desktop is acting weird. This one is using
>> an Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] GPU.
>>
>> Box is 2 * EPYC 7281 with 128 GB ECC RAM
>>
>> Also a 14C Xeon
2018-04-11 20:35 GMT+02:00 Jean-Marc Valin :
> On 04/11/2018 05:37 AM, Christian König wrote:
>>> With your patches my EPYC box is unusable with 4.15++ kernels.
>>> The whole Desktop is acting weird. This one is using
>>> an Cape Verde PRO [Radeon HD 7750/8740 / R7 250E]
On 11 April 2018 at 22:27, Jani Nikula wrote:
> On Wed, 11 Apr 2018, Ian W MORRISON wrote:
>>
>>
>>>
>>> NAK on indiscriminate Cc: stable. There are zero guarantees that older
>>> kernels will work with whatever firmware you throw at them.
2018-04-11 16:26 GMT+02:00 Gabriel C :
> 2018-04-11 11:37 GMT+02:00 Christian König :
>> Am 11.04.2018 um 06:00 schrieb Gabriel C:
...
>>
>> Please test Alex's amd-staging-drm-next branch from
>> git://people.freedesktop.org/~agd5f/linux.
>
> I'm on
https://bugzilla.kernel.org/show_bug.cgi?id=199357
--- Comment #6 from Michel Dänzer (mic...@daenzer.net) ---
(In reply to Harry Wentland from comment #5)
> I'm reluctant to just revert the offending commit as it's not incorrect
> but seems to expose some other flaws in our atomic check/commit
>
On 2018-04-12 01:30 AM, Cyr, Aric wrote:
>> From: Michel Dänzer [mailto:mic...@daenzer.net]
>> Sent: Wednesday, April 11, 2018 05:50
>> On 2018-04-11 08:57 AM, Nicolai Hähnle wrote:
>>> On 10.04.2018 23:45, Cyr, Aric wrote:
How does it work fine today given that all kernel seems to know is
On Mon, 9 Apr 2018 13:58:13 -0700
Eric Anholt wrote:
> Signed-off-by: Eric Anholt
> Fixes: 65101d8c9108 ("drm/vc4: Expose performance counters to userspace")
Reviewed-by: Boris Brezillon
> ---
> drivers/gpu/drm/vc4/vc4_drv.c |
https://bugzilla.kernel.org/show_bug.cgi?id=199085
Stuart Foster (smf.li...@ntlworld.com) changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Am 12.04.2018 um 11:11 schrieb Lucas Stach:
Am Mittwoch, den 11.04.2018, 20:26 +0200 schrieb Christian König:
Am 11.04.2018 um 19:11 schrieb Robin Murphy:
For dma_map_sg(), DMA API implementations are free to merge consecutive
segments into a single DMA mapping if conditions are suitable, thus
https://bugs.freedesktop.org/show_bug.cgi?id=105996
Bug ID: 105996
Summary: [DC][CIK] Bonaire mobile - No displays being turned
on
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
https://bugs.freedesktop.org/show_bug.cgi?id=105996
--- Comment #1 from Shawn Starr ---
Created attachment 138778
--> https://bugs.freedesktop.org/attachment.cgi?id=138778=edit
Xorg log
--
You are receiving this mail because:
You are the assignee for the
Am Donnerstag, den 12.04.2018, 11:35 +0200 schrieb Christian König:
> Am 12.04.2018 um 11:11 schrieb Lucas Stach:
> > Am Mittwoch, den 11.04.2018, 20:26 +0200 schrieb Christian König:
> > > Am 11.04.2018 um 19:11 schrieb Robin Murphy:
> > > > For dma_map_sg(), DMA API implementations are free to
https://bugs.freedesktop.org/show_bug.cgi?id=105680
Marta Löfstedt changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.freedesktop.org/show_bug.cgi?id=105680
Marta Löfstedt changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
https://bugs.freedesktop.org/show_bug.cgi?id=105880
--- Comment #10 from Michel Dänzer ---
(In reply to David Henningsson from comment #8)
> The regression is between 4.15rc2 and 4.15rc3
Any chance you can bisect between these two?
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=105680
Marta Löfstedt changed:
What|Removed |Added
Status|CLOSED |REOPENED
Hi Lucas,
On Wed, 2018-04-11 at 17:31 +0200, Lucas Stach wrote:
> The LVDS signal integrity is only guaranteed when the correct enable
> sequence (first IPU DI, then LDB) is used. If the LDB display output was
> active before the imx-drm driver is loaded (like when a bootsplash was
> active) the
https://bugs.freedesktop.org/show_bug.cgi?id=97909
--- Comment #13 from Joonas Sarajärvi ---
I can test this week.
In my opinion, leaving this a WONTFIX would be quite unfortunate, because as
far as I know, the free AMD GPU drivers are pretty much the only way to run
X-Plane
Am Mittwoch, den 11.04.2018, 20:26 +0200 schrieb Christian König:
> Am 11.04.2018 um 19:11 schrieb Robin Murphy:
> > For dma_map_sg(), DMA API implementations are free to merge consecutive
> > segments into a single DMA mapping if conditions are suitable, thus the
> > resulting DMA addresses may
Am 12.04.2018 um 08:26 schrieb Christoph Hellwig:
On Wed, Apr 11, 2018 at 01:03:59PM +0100, Robin Murphy wrote:
On 10/04/18 21:59, Sinan Kaya wrote:
Code is expecing to observe the same number of buffers returned from
dma_map_sg() function compared to sg_alloc_table_from_pages(). This
doesn't
On 05.04.2018 11:49, Enric Balletbo i Serra wrote:
> From: Tomasz Figa
>
> Driver callbacks, such as system suspend or resume can be called any
> time, specifically they can be called before the component bind
> callback. Let's use dp->adp pointer as a safeguard and skip
Change-Id: I4abf5cf0aaf946162dabd08fc1fd0406c2abf418
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/ttm/ttm_bo.c| 1 +
include/drm/ttm/ttm_bo_driver.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
Change-Id: Ib68bff91fd127162cf8c72516101546e1fe014df
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 1 -
drivers/gpu/drm/ttm/ttm_bo.c | 39 --
2 files changed, 26 insertions(+), 14 deletions(-)
diff
Change-Id: I5b6afbdd715e28e5266b5099ca9a34399d1fc3a1
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/ttm/ttm_bo.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
index
Change-Id: I877b2d5c54b3e47b66f2d58454dcf1e5f5a68972
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
On Tue, Apr 10, 2018 at 07:25:03PM +0100, Ayan Kumar Halder wrote:
> On some Mali-DP processors, the LAYER_FORMAT register contains fields
> other than the format. These bits were unconditionally cleared when
> setting the pixel format, whereas they should be preserved at their
> reset values.
>
Am 12.04.2018 um 11:49 schrieb Lucas Stach:
Am Donnerstag, den 12.04.2018, 11:35 +0200 schrieb Christian König:
Am 12.04.2018 um 11:11 schrieb Lucas Stach:
Am Mittwoch, den 11.04.2018, 20:26 +0200 schrieb Christian König:
Am 11.04.2018 um 19:11 schrieb Robin Murphy:
For dma_map_sg(), DMA API
On 12.04.2018 01:30, Cyr, Aric wrote:
At least with VDPAU, video players are already explicitly specifying the
target presentation time, so no changes should be required at that
level. Don't know about other video APIs.
The X11 Present extension protocol is also prepared for specifying the
https://bugs.freedesktop.org/show_bug.cgi?id=98271
Timothy Arceri changed:
What|Removed |Added
QA Contact|mesa-dev@lists.freedesktop.
https://bugs.freedesktop.org/show_bug.cgi?id=104190
--- Comment #7 from Gregor Münch ---
Is it a good idea to close this bug? There seem to be a number of bugs affected
by a problem with llvm 5.0. Unfortunatly, LLVM 5.0 series releases no stable
builds, so a fix cant be
Change-Id: I4de8146567b858ae07a8a27cadf71d13d490e8ac
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c| 7 +--
drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 4 +++-
2 files changed, 8 insertions(+), 3 deletions(-)
diff --git
Change-Id: Id2333f69119222a7e9bdb0357bbed97cf08636da
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/ttm/ttm_bo.c| 59 ++---
include/drm/ttm/ttm_bo_driver.h | 3 ++-
2 files changed, 52 insertions(+), 10 deletions(-)
diff --git
Change-Id: Ie43f3c73cc65526a449208f3ce927b1dfad5cf6b
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 2 ++
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 1 +
2 files changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu.h
https://bugzilla.kernel.org/show_bug.cgi?id=199357
Mathias Tillman (master.ho...@gmail.com) changed:
What|Removed |Added
Attachment #275291|0 |1
is
Change-Id: Ifb0dc95db6a358cf7f76e2a99f94c58637ad6ee6
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/amd/amdgpu/amdgpu.h| 3 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c | 2 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c| 17 ++-
Change-Id: I0f533c6512f3b72fcf2fbf11d738f38d9e087f26
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/ttm/ttm_bo.c| 39 +++
include/drm/ttm/ttm_bo_api.h| 3 ++-
include/drm/ttm/ttm_bo_driver.h | 2 +-
3 files changed, 34
https://bugs.freedesktop.org/show_bug.cgi?id=104216
--- Comment #25 from Germano Massullo ---
Some very good news
https://bugzilla.mozilla.org/show_bug.cgi?id=1421353#c22
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=104216
--- Comment #26 from Michel Dänzer ---
The question remains where all the file descriptors are coming from. Maybe
there's a leak somewhere.
FWIW, I've never noticed such issues with the default limit of 1024. My main
https://bugs.freedesktop.org/show_bug.cgi?id=105819
--- Comment #2 from Andy Burns ---
Experienced same/similar error on Fedora 28 beta, with an RX 460 card
$ lspci | grep AMD
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Baffin
Since per-process-bo feature is introduced, old lru isn't working for it.
old lru order is depending on BO list order, which will be updated by bo
list after every command submission.
But for per-process-bo, which aren't in bo list, so it have no chance to
refresh its order in lru. Which also will
Change-Id: I34924a40392653e72f143c30ab312cbbf9fa
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/ttm/ttm_bo.c| 23 +++
include/drm/ttm/ttm_bo_api.h| 1 +
include/drm/ttm/ttm_bo_driver.h | 10 ++
3 files changed, 34 insertions(+)
Change-Id: I2cf802e641d8b2cdb2bf8bdf1957f3f4f27afaba
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 2 ++
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h | 2 ++
2 files changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
https://bugs.freedesktop.org/show_bug.cgi?id=97909
--- Comment #14 from Amarildo ---
It's a shame they don't officially support OSS drivers despite them running
X-Plane better.
All this contributes to driver separation, confusion, and Linux still being
regarded as
https://bugzilla.kernel.org/show_bug.cgi?id=199357
--- Comment #7 from Mathias Tillman (master.ho...@gmail.com) ---
Wanted to add some more info. The soft lock up will release after approximately
30 seconds, but after a few seconds it will lock up again and repeat.
Looking at the kernel log, it
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #24 from MirceaKitsune ---
Created attachment 138798
--> https://bugs.freedesktop.org/attachment.cgi?id=138798=edit
GALLIUM_HUD pre crash screenshot
--
You are receiving this mail because:
(changed subject and decoupling from udmabuf thread)
On Wed, Apr 11, 2018 at 08:59:32AM +0300, Oleksandr Andrushchenko wrote:
> On 04/10/2018 08:26 PM, Dongwon Kim wrote:
> >On Tue, Apr 10, 2018 at 09:37:53AM +0300, Oleksandr Andrushchenko wrote:
> >>On 04/06/2018 09:57 PM, Dongwon Kim wrote:
>
On Thu, Apr 12, 2018 at 01:08:51AM +0200, Paul Kocialkowski wrote:
> > > + backlight: backlight {
> > > + compatible = "pwm-backlight";
> > > + pinctrl-names = "default";
> > > + pinctrl-0 = <_enable_pin>;
> >
> > You don't need any of the pinctrl nodes for the GPIOs
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #23 from MirceaKitsune ---
I just finished running the GALLIUM_HUD test, and will be taking a look at the
other options next. It was more difficult to test now since the freeze occurs
almost
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #25 from MirceaKitsune ---
Created attachment 138799
--> https://bugs.freedesktop.org/attachment.cgi?id=138799=edit
GALLIUM_HUD post crash photo
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=104216
Michel Dänzer changed:
What|Removed |Added
Resolution|--- |NOTOURBUG
In a situation when the reference count of the drm connector is greater than 1,
the unbind function should not invoke drm_connector_cleanup as this will lead
to an inconsistent state where the drm_crtc_state->connector_mask still has
a bitmask referring to the stale connector. Later, when drm
On 2018-04-12 01:39 PM, Nicolai Hähnle wrote:
> On 12.04.2018 01:30, Cyr, Aric wrote:
>>> At least with VDPAU, video players are already explicitly specifying the
>>> target presentation time, so no changes should be required at that
>>> level. Don't know about other video APIs.
>>>
>>> The X11
https://bugs.freedesktop.org/show_bug.cgi?id=105996
Alex Deucher changed:
What|Removed |Added
Attachment #138777|text/x-log |text/plain
https://bugs.freedesktop.org/show_bug.cgi?id=105996
Alex Deucher changed:
What|Removed |Added
Attachment #138778|text/x-log |text/plain
Atomic drivers can't use them so finish what was started in
commit 9c79e0b1d096 ("drm/fb-helper: Give up on kgdb for atomic drivers").
This prepares the ground for creating modesets on demand.
TODO:
- Actually remove the functions, not just the contents.
- Nuke
On 12/04/18 11:33, Christian König wrote:
Am 12.04.2018 um 11:49 schrieb Lucas Stach:
Am Donnerstag, den 12.04.2018, 11:35 +0200 schrieb Christian König:
Am 12.04.2018 um 11:11 schrieb Lucas Stach:
Am Mittwoch, den 11.04.2018, 20:26 +0200 schrieb Christian König:
Am 11.04.2018 um 19:11
Add functions to deal with the registred connectors as an array:
- drm_connector_get_all()
- drm_connector_put_all()
And to get the enabled status of those connectors:
drm_connector_get_enabled_status()
This is prep work to remove struct drm_fb_helper_connector.
Signed-off-by: Noralf Trønnes
On 12/04/18 10:42, Christian König wrote:
Am 12.04.2018 um 08:26 schrieb Christoph Hellwig:
On Wed, Apr 11, 2018 at 01:03:59PM +0100, Robin Murphy wrote:
On 10/04/18 21:59, Sinan Kaya wrote:
Code is expecing to observe the same number of buffers returned from
dma_map_sg() function compared to
https://bugs.freedesktop.org/show_bug.cgi?id=48424
Timothy Arceri changed:
What|Removed |Added
Status|NEW |RESOLVED
This moves the committing part of the modesetting code to drm_client.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_client.c| 242
drivers/gpu/drm/drm_fb_helper.c | 216 +--
Move them over from drm_fb_helper since they are connector functions.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_connector.c| 94 ++
drivers/gpu/drm/drm_fb_helper.c| 75 ++
Prepare to move the modeset committing code to drm_client.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_fb_helper.c | 161
include/drm/drm_fb_helper.h | 8 ++
2 files changed, 89 insertions(+), 80 deletions(-)
diff
For each enabled crtc the functions sets dpms on all registered connectors.
Limit this to only doing it once and on the connectors actually in use.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_fb_helper.c | 11 +--
1 file changed, 5 insertions(+), 6
https://bugs.freedesktop.org/show_bug.cgi?id=104216
--- Comment #27 from Germano Massullo ---
Created attachment 138784
--> https://bugs.freedesktop.org/attachment.cgi?id=138784=edit
lsof on Firefox
(In reply to Michel Dänzer from comment #26)
> FWIW, I've never
Getting rotation info is cheap so we can do it on demand.
This is done in preparation for the removal of struct drm_fb_helper_crtc.
Cc: Hans de Goede
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_fb_helper.c | 131
Prepare for moving drm_fb_helper modesetting code to drm_client.
drm_client will be linked to drm.ko, so move
__drm_atomic_helper_disable_plane() and __drm_atomic_helper_set_config()
out of drm_kms_helper.ko.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_atomic.c
From: David Herrmann
Rather than doing drm_file allocation/destruction right in the fops, lets
provide separate helpers. This decouples drm_file management from the
still-mandatory drm-fops. It prepares for use of drm_file without the
fops, both by possible separate fops
This the beginning of an API for in-kernel clients.
First out is a display representation that will be used by drm_fb_helper
in order to move out its mode setting code.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/Makefile | 2 +-
drivers/gpu/drm/drm_client.c |
This patchset explores the possibility of having generic fbdev emulation
in DRM for drivers that supports dumb buffers which they can export. An
API is added to support in-kernel clients in general.
In this version I was able to reuse the modesetting code from
drm_fb_helper in the client API.
It only makes sense for userspace clients.
Signed-off-by: Noralf Trønnes
Reviewed-by: Daniel Vetter
---
drivers/gpu/drm/drm_file.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/gpu/drm/drm_file.c
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #26 from MirceaKitsune ---
I preformed the next test suggested to me, by changing
/etc/X11/xorg.conf.d/50-device.conf to the following content:
Section "Device"
Identifier "Default Device"
https://bugs.freedesktop.org/show_bug.cgi?id=106006
--- Comment #1 from Joel Sass ---
Created attachment 138804
--> https://bugs.freedesktop.org/attachment.cgi?id=138804=edit
dmesg output with amdgpu.dc=0
--
You are receiving this mail because:
You are the assignee for
Add a notifier that fires when a new DRM device is registered.
This can be used by the bootsplash client to connect to all devices.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_drv.c | 32
include/drm/drm_drv.h | 4
2 files
https://bugs.freedesktop.org/show_bug.cgi?id=106013
Chris Wilson changed:
What|Removed |Added
Assignee|intel-gfx-bugs@lists.freede
https://bugs.freedesktop.org/show_bug.cgi?id=106006
Bug ID: 106006
Summary: Kernel 4.16.0+ switch amdgpu.dc=1 causes screen
brightness set to 1 to be dimmed by default
Product: DRI
Version: unspecified
Hardware: x86-64
https://bugs.freedesktop.org/show_bug.cgi?id=106006
--- Comment #2 from Joel Sass ---
Created attachment 138805
--> https://bugs.freedesktop.org/attachment.cgi?id=138805=edit
Xorg.0.log with amdgpu.dc=0
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=106006
--- Comment #4 from Joel Sass ---
A fix I've found for the issue seems to be issueing an xrandr brightness
command to each monitor output.
EG: ~$ xrandr --output DP-5 --brightness .99
If brightness is set to 1, the
https://bugs.freedesktop.org/show_bug.cgi?id=105996
Shawn Starr changed:
What|Removed |Added
Attachment #138777|0 |1
is
https://bugs.freedesktop.org/show_bug.cgi?id=106013
--- Comment #2 from Martin Peres ---
(In reply to Chris Wilson from comment #1)
> Boring, but true, there ain't no such device on brw!
Isn't that Broadwater?
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=106013
Martin Peres changed:
What|Removed |Added
Whiteboard||ReadyForDev
--
Call the function drm_client_find_display().
No functional change apart from making width/height arguments optional.
Some function name/signature changes and whitespace adjustments.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_client.c| 399
The modesetting code is already present, this adds the rest of the API.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_client.c | 573 +
drivers/gpu/drm/drm_debugfs.c | 7 +
drivers/gpu/drm/drm_drv.c | 11 +
Make ioctl wrappers for functions that will be used by the in-kernel API.
The following functions are touched:
- drm_mode_create_dumb_ioctl()
- drm_mode_destroy_dumb_ioctl()
- drm_mode_addfb2()
- drm_mode_rmfb()
- drm_prime_handle_to_fd_ioctl()
drm_mode_addfb2() also gets the ability to override
Give clients easy access to the display modes.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_client.c | 159 +--
include/drm/drm_client.h | 25 +++
2 files changed, 148 insertions(+), 36 deletions(-)
diff --git
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #27 from i...@yahoo.com ---
Loosing recently written files is unfortunately way too common, despite all
filesystem using journaling.
It might help if you call `sync` after writing the file.
If you have kernel with enabled
https://bugs.freedesktop.org/show_bug.cgi?id=105619
--- Comment #7 from Michael Lange ---
Created attachment 138811
--> https://bugs.freedesktop.org/attachment.cgi?id=138811=edit
kernel-4.16.2 dmesg
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=106006
--- Comment #6 from Joel Sass ---
Created attachment 138808
--> https://bugs.freedesktop.org/attachment.cgi?id=138808=edit
Xorg.0.log with amdgpu.dc=1
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=106006
--- Comment #5 from Joel Sass ---
Created attachment 138807
--> https://bugs.freedesktop.org/attachment.cgi?id=138807=edit
xrandr --verbose with amdgpu.dc=1
--
You are receiving this mail because:
You are the assignee
No need to maintain a list of registered connectors. Just use the
connector iterator.
TODO: Remove:
- drm_fb_helper_add_one_connector()
- drm_fb_helper_single_add_all_connectors()
- drm_fb_helper_remove_one_connector()
Signed-off-by: Noralf Trønnes
---
https://bugs.freedesktop.org/show_bug.cgi?id=106006
--- Comment #7 from Joel Sass ---
Created attachment 138809
--> https://bugs.freedesktop.org/attachment.cgi?id=138809=edit
dmesg output with amdgpu.dc=1
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=105619
--- Comment #6 from Michael Lange ---
Running in the same problem, same error in dmesg.
I have two monitors (AOG AG272FCX), one connected via hdmi to the discrete gpu
(HD 8800) and the second one connected via hdmi to the
These helpers keep track of fbdev users and drm_driver.last_close will
only restore fbdev when actually in use. Additionally the display is
turned off when the last user is closing. fbcon is a user in this context.
If struct fb_ops is defined in a library, fb_open() takes a ref on the
library
This adds generic fbdev emulation for drivers that supports
dumb buffers which they can export.
All the driver has to do is call drm_fbdev_generic_setup().
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_fb_helper.c | 255
A hack to test the client API.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/Kconfig | 2 +
drivers/gpu/drm/Makefile| 1 +
drivers/gpu/drm/client/Kconfig | 9 ++
drivers/gpu/drm/client/drm_bootsplash.c | 248
1 - 100 of 136 matches
Mail list logo