I believe the intention of the commit 2c9fc9bf45f8
("drm: omapdrm: Move FEAT_HDMI_* features to hdmi4 driver")
was to identify omap4430 ES1.x, omap4430 ES2.x and other OMAP4 revisions,
like omap4460.
By using family=OMAP4 in the match the code will treat omap4460 ES1.x in a
same way as it would tr
If the device tree for a board did not specify a cec clock, then
adv7511_cec_init would return an error, which would cause adv7511_probe()
to fail and thus there is no HDMI output.
There is no need to have adv7511_probe() fail if the CEC initialization
fails, so just change adv7511_cec_init() to a
On Thu, 2017-11-16 at 09:17 -0800, Joe Perches wrote:
> On Thu, 2017-11-16 at 12:11 -0500, Mimi Zohar wrote:
> > On Thu, 2017-11-16 at 07:27 -0800, Joe Perches wrote:
> > > Avoid using line continations in formats as that causes unexpected
> > > output.
> >
> > Is having lines greater than 80 char
Hi Andrew,
> Am 16.11.2017 um 16:53 schrieb Andrew F. Davis :
>
> On 11/16/2017 07:43 AM, H. Nikolaus Schaller wrote:
>>
>>> Am 16.11.2017 um 13:32 schrieb Tomi Valkeinen :
>>>
>>> On 16/11/17 10:50, H. Nikolaus Schaller wrote:
The vendor name was "toppoly" but other panels and the vendor
On 11/16/2017 07:43 AM, H. Nikolaus Schaller wrote:
>
>> Am 16.11.2017 um 13:32 schrieb Tomi Valkeinen :
>>
>> On 16/11/17 10:50, H. Nikolaus Schaller wrote:
>>> The vendor name was "toppoly" but other panels and the vendor list
>>> have defined it as "tpo". So let's fix it in driver and bindings.
On 11/16/17, Jani Nikula wrote:
> On Wed, 15 Nov 2017, Tuncer Ayaz wrote:
> > I don't follow why you think it's a different platform and how I
> > might have "more" definitely shown v4.1 to be good, but I'll trust
> > your judgement as a drm dev and not argue :).
>
> You apparently have Sandy Bri
On 05.11.2017 14:01, Mikko Perttunen wrote:
> To allow client drivers to free resources when jobs have completed,
> deliver job completion callbacks to them. This requires adding
> reference counting to context objects, as job completion can happen
> after the userspace application has closed the c
On 05.11.2017 14:01, Mikko Perttunen wrote:
> To allow client drivers to free resources when jobs have completed,
> deliver job completion callbacks to them. This requires adding
> reference counting to context objects, as job completion can happen
> after the userspace application has closed the c
Hi Andrew,
> Am 16.11.2017 um 19:32 schrieb Andrew F. Davis :
>
> On 11/16/2017 12:18 PM, H. Nikolaus Schaller wrote:
>>
>>> Am 16.11.2017 um 18:08 schrieb Andrew F. Davis :
>>>
>>> On 11/16/2017 10:10 AM, H. Nikolaus Schaller wrote:
Hi Andrew,
> Am 16.11.2017 um 16:53 schrieb An
> Am 16.11.2017 um 18:08 schrieb Andrew F. Davis :
>
> On 11/16/2017 10:10 AM, H. Nikolaus Schaller wrote:
>> Hi Andrew,
>>
>>> Am 16.11.2017 um 16:53 schrieb Andrew F. Davis :
>>>
>>> On 11/16/2017 07:43 AM, H. Nikolaus Schaller wrote:
> Am 16.11.2017 um 13:32 schrieb Tomi Valkeinen
On 11/16/2017 12:18 PM, H. Nikolaus Schaller wrote:
>
>> Am 16.11.2017 um 18:08 schrieb Andrew F. Davis :
>>
>> On 11/16/2017 10:10 AM, H. Nikolaus Schaller wrote:
>>> Hi Andrew,
>>>
Am 16.11.2017 um 16:53 schrieb Andrew F. Davis :
On 11/16/2017 07:43 AM, H. Nikolaus Schaller wrote:
On 11/16/2017 10:10 AM, H. Nikolaus Schaller wrote:
> Hi Andrew,
>
>> Am 16.11.2017 um 16:53 schrieb Andrew F. Davis :
>>
>> On 11/16/2017 07:43 AM, H. Nikolaus Schaller wrote:
>>>
Am 16.11.2017 um 13:32 schrieb Tomi Valkeinen :
On 16/11/17 10:50, H. Nikolaus Schaller wrote:
> T
On Thu, 2017-11-16 at 07:27 -0800, Joe Perches wrote:
> Avoid using line continations in formats as that causes unexpected
> output.
Is having lines greater than 80 characters the preferred method?
Could you add quotes before the backlash and before the first word on
the next line instead?
Mimi
On 15 November 2017 at 18:28, Hans Verkuil wrote:
> On 15/11/17 13:37, Arnd Bergmann wrote:
>> An otherwise correct cleanup patch from Dan Carpenter turned a broken
>> failure handling from a feature patch by Hans Verkuil into a kernel
>> Oops, so bisection points to commit 7af35b0addbc ("drm/kiri
https://bugs.freedesktop.org/show_bug.cgi?id=103788
--- Comment #1 from Michel Dänzer ---
Please attach the corresponding dmesg output and Xorg log file.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing li
From: aknautiy
A new drm client cap is required to enable user-space to advertise
if it supports modes with aspect-ratio. Based on this cap value, the
kernel will take a call on exposing the aspect ratio information in
modes or not.
This patch adds the client cap for aspect-ratio.
Cc: Ville Syr
From: Ankit Nautiyal
If the user mode does not support aspect-ratio, and requests for
a modeset with aspect ratio flags, then the flag bits reprsenting
aspect ratio must be ignored.
Similarly, if user space doesn't set the aspect ratio client cap,
while preparing a usermode, the aspect-ratio inf
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 versa.
This patch was once reviewed and merged, and la
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 (https://pw-emeril.freedesktop.org/series/10850/) had
4 patches, out of which 2 patches were
From: aknautiy
We parse the EDID and add all the modes in the connector's
modelist. This adds CEA modes with aspect ratio information
too, regadless of if user space requested this information or
not.
This patch prunes the modes with aspect-ratio information, from
a connector's modelist, if the
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 to wrong VIC.
This patch adds aspect ratio information
https://bugs.freedesktop.org/show_bug.cgi?id=103370
Timo Aaltonen changed:
What|Removed |Added
CC||tjaal...@ubuntu.com
--- Comment #26 fro
https://bugs.freedesktop.org/show_bug.cgi?id=103370
--- Comment #27 from Michel Dänzer ---
Thanks for bisecting, but I don't think that commit can be directly responsible
for a GPU hang. Before that commit, the DRI3 code in Mesa would only use one
back buffer for glxgears, which means that the GP
Hi everyone,
Michel already reviewed this back in April, but I didn't found time to actually
fully test it before now.
So sending this one out once more because it's an interface change which
affects all driver using TTM.
Please review and/or comment.
Regards,
Christian.
Instead of specifying interruptible and no_wait_gpu manually.
v2: rebase
Signed-off-by: Christian König
Reviewed-by: Michel Dänzer
---
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 5 +++--
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c| 11 ++-
drivers/gpu/drm/nouveau/nouveau_bo.c
Give moving a BO into place an operation context to work with.
v2: rebased
Signed-off-by: Christian König
Reviewed-by: Michel Dänzer
---
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 14 --
drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c | 3 ++-
drivers/gpu/drm/amd/amdgpu/amdgpu_obje
Instead of passing down the parameters manually to every function.
Signed-off-by: Christian König
Reviewed-by: Michel Dänzer
---
drivers/gpu/drm/ttm/ttm_bo.c | 67 +++-
1 file changed, 29 insertions(+), 38 deletions(-)
diff --git a/drivers/gpu/drm/ttm/tt
Instead of specifying if sleeping should be interruptible.
Signed-off-by: Christian König
Reviewed-by: Michel Dänzer
---
drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 3 ++-
drivers/gpu/drm/ttm/ttm_bo.c | 12 +---
include/drm/ttm/ttm_bo_api.h | 5 ++---
3 fi
Instead of passing the parameters manually.
Signed-off-by: Christian König
Reviewed-by: Michel Dänzer
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 21 +++--
drivers/gpu/drm/nouveau/nouveau_bo.c| 27 ---
drivers/gpu/drm/qxl/qxl_ttm.c | 9 ++
This way we can finally use some more stats.
Signed-off-by: Christian König
Reviewed-by: Michel Dänzer
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 30 --
1 file changed, 12 insertions(+), 18 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
b/driv
Add some statistics how many bytes we have moved.
Signed-off-by: Christian König
Reviewed-by: Michel Dänzer
---
drivers/gpu/drm/ttm/ttm_bo.c | 1 +
include/drm/ttm/ttm_bo_api.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
inde
Instead of the global statistics use the per context bytes moved counter.
v2: rebased
Signed-off-by: Christian König
Reviewed-by: Michel Dänzer
---
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 9 +++--
drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 10 +++---
2 files changed, 6 insertio
https://bugs.freedesktop.org/show_bug.cgi?id=103370
--- Comment #28 from Shih-Yuan Lee ---
`vblank_mode=0 DRI_PRIME=1 glxgears` will also introduce the GPU lock up.
However when using radeon.dpm=0, it won't happen but it is tearing all the
time.
--
You are receiving this mail because:
You are t
https://bugs.freedesktop.org/show_bug.cgi?id=103370
Shih-Yuan Lee changed:
What|Removed |Added
Summary|`DRI_PRIME=1 glxgears |`DRI_PRIME=1 glxgears
Den 17.11.2017 10.10, skrev Alexey Brodkin:
Hi Noralf,
On Thu, 2017-11-16 at 21:11 +0100, Noralf Trønnes wrote:
Den 16.11.2017 09.14, skrev Shawn Guo:
On Wed, Nov 15, 2017 at 03:19:39PM +0100, Noralf Trønnes wrote:
This patchset adds drm_fb_cma_fbdev_init/fini() functions that replaces
drm_f
https://bugs.freedesktop.org/show_bug.cgi?id=103370
Shih-Yuan Lee changed:
What|Removed |Added
Summary|`DRI_PRIME=1 glxgears |`vblank_mode=0 DRI_PRIME=1
https://bugs.freedesktop.org/show_bug.cgi?id=103370
--- Comment #29 from Michel Dänzer ---
Tearing is expected with vblank_mode=0.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.free
Cc: Greg
On Wed, 15 Nov 2017, Ville Syrjälä wrote:
> On Wed, Nov 15, 2017 at 04:44:54PM +, alexander.le...@verizon.com wrote:
>> On Wed, Nov 15, 2017 at 01:08:05PM +0200, Ville Syrjälä wrote:
>> >On Wed, Nov 15, 2017 at 02:45:43AM +, alexander.le...@verizon.com wrote:
>> >> From: Ville S
On Fri, Nov 17, 2017 at 08:49:49AM +0530, Sharma, Shashank wrote:
> Regards
>
> Shashank
>
>
> On 11/16/2017 9:53 PM, Ville Syrjälä wrote:
> > On Thu, Nov 16, 2017 at 08:21:44PM +0530, Sharma, Shashank wrote:
> >> Regards
> >>
> >> Shashank
> >>
> >>
> >> On 11/13/2017 10:34 PM, Ville Syrjala wr
On Tue, Nov 07, 2017 at 04:30:58PM +0100, Lukasz Majewski wrote:
> Signed-off-by: Lukasz Majewski
>
> ---
> Changes for v2:
> - Provide more detailed ./Documentation/devicetree/bindings/display/panel
> entry to describe this panel device.
> ---
> .../bindings/display/panel/tianma,tm070rvhg71.t
On Fri, Nov 17, 2017 at 08:53:54AM +0530, Sharma, Shashank wrote:
> Regards
>
> Shashank
>
>
> On 11/16/2017 9:56 PM, Ville Syrjälä wrote:
> > On Thu, Nov 16, 2017 at 08:31:36PM +0530, Sharma, Shashank wrote:
> >> Regards
> >>
> >> Shashank
> >>
> >>
> >> On 11/13/2017 10:34 PM, Ville Syrjala wr
On Fri, Nov 17, 2017 at 11:02:47AM +0100, Lukasz Majewski wrote:
> Dear All,
>
> > On Tue, Nov 07, 2017 at 04:30:58PM +0100, Lukasz Majewski wrote:
> > > Signed-off-by: Lukasz Majewski
> > >
> > > ---
> > > Changes for v2:
> > > - Provide more
> > > detailed ./Documentation/devicetree/bindings/d
On Sat, Oct 21, 2017 at 12:06:09AM +0200, Lukasz Majewski wrote:
> This commit adds support for Mitsubishi aa070mc01 TFT panel working
> with 8 bit ISP mode (pin 19 "mode" HIGH for 20 pin TFT connector).
>
> Signed-off-by: Lukasz Majewski
> ---
> Changes for v2:
> - Place the code sorted alphabet
https://bugs.freedesktop.org/show_bug.cgi?id=103791
Bug ID: 103791
Summary: Tearing after screen wakeup/on
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Prio
https://bugs.freedesktop.org/show_bug.cgi?id=103791
--- Comment #1 from denisgolo...@yandex.ru ---
Created attachment 135552
--> https://bugs.freedesktop.org/attachment.cgi?id=135552&action=edit
xorg.conf
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=103791
--- Comment #2 from denisgolo...@yandex.ru ---
Created attachment 135553
--> https://bugs.freedesktop.org/attachment.cgi?id=135553&action=edit
dmesg
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=103791
--- Comment #3 from denisgolo...@yandex.ru ---
Created attachment 135554
--> https://bugs.freedesktop.org/attachment.cgi?id=135554&action=edit
Xorg.0.log
--
You are receiving this mail because:
You are the assignee for the bug.___
Regards
Shashank
On 11/17/2017 5:05 PM, Ville Syrjälä wrote:
On Fri, Nov 17, 2017 at 08:49:49AM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 11/16/2017 9:53 PM, Ville Syrjälä wrote:
On Thu, Nov 16, 2017 at 08:21:44PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 11/13/2017
On Fri, Nov 17, 2017 at 01:17:12PM +0100, Lukasz Majewski wrote:
> Hi Thierry,
>
> > On Fri, Nov 17, 2017 at 11:02:47AM +0100, Lukasz Majewski wrote:
> > > Dear All,
> > >
> > > > On Tue, Nov 07, 2017 at 04:30:58PM +0100, Lukasz Majewski wrote:
> > > > > Signed-off-by: Lukasz Majewski
> > >
On Fri, Nov 17, 2017 at 01:28:05PM +0200, Jani Nikula wrote:
>
> Cc: Greg
>
> On Wed, 15 Nov 2017, Ville Syrjälä wrote:
> > On Wed, Nov 15, 2017 at 04:44:54PM +, alexander.le...@verizon.com wrote:
> >> On Wed, Nov 15, 2017 at 01:08:05PM +0200, Ville Syrjälä wrote:
> >> >On Wed, Nov 15, 2017
On Fri, Nov 17, 2017 at 05:50:11PM +0530, Sharma, Shashank wrote:
> Regards
>
> Shashank
>
>
> On 11/17/2017 5:05 PM, Ville Syrjälä wrote:
> > On Fri, Nov 17, 2017 at 08:49:49AM +0530, Sharma, Shashank wrote:
> >> Regards
> >>
> >> Shashank
> >>
> >>
> >> On 11/16/2017 9:53 PM, Ville Syrjälä wro
On 16.11.2017 21:57, Dave Airlie wrote:
On 16 November 2017 at 14:59, Linus Torvalds
wrote:
On Wed, Nov 15, 2017 at 6:34 PM, Dave Airlie wrote:
There is some code touched on sound/soc, but I think the sound tree
should have the same commits from the same base,so this may luck different
if yo
On Fri, Nov 17, 2017 at 01:41:23PM +0100, Greg KH wrote:
> On Fri, Nov 17, 2017 at 01:28:05PM +0200, Jani Nikula wrote:
> >
> > Cc: Greg
> >
> > On Wed, 15 Nov 2017, Ville Syrjälä wrote:
> > > On Wed, Nov 15, 2017 at 04:44:54PM +, alexander.le...@verizon.com
> > > wrote:
> > >> On Wed, Nov
On 17/11/17 10:00, Peter Ujfalusi wrote:
> I believe the intention of the commit 2c9fc9bf45f8
> ("drm: omapdrm: Move FEAT_HDMI_* features to hdmi4 driver")
> was to identify omap4430 ES1.x, omap4430 ES2.x and other OMAP4 revisions,
> like omap4460.
>
> By using family=OMAP4 in the match the code w
On Fri, 17 Nov 2017, Greg KH wrote:
> On Fri, Nov 17, 2017 at 01:28:05PM +0200, Jani Nikula wrote:
>>
>> Cc: Greg
>>
>> On Wed, 15 Nov 2017, Ville Syrjälä wrote:
>> > On Wed, Nov 15, 2017 at 04:44:54PM +, alexander.le...@verizon.com
>> > wrote:
>> >> On Wed, Nov 15, 2017 at 01:08:05PM +020
On Fri, Nov 17, 2017 at 02:53:43PM +0200, Ville Syrjälä wrote:
> On Fri, Nov 17, 2017 at 01:41:23PM +0100, Greg KH wrote:
> > On Fri, Nov 17, 2017 at 01:28:05PM +0200, Jani Nikula wrote:
> > >
> > > Cc: Greg
> > >
> > > On Wed, 15 Nov 2017, Ville Syrjälä wrote:
> > > > On Wed, Nov 15, 2017 at 04
Hi Greg, all,
Pardon for the silly question, but I'm struggling to find
documentation about this new 'autoselection' process?
Where can one read up on it - be that about the tooling or the heuristics used?
I think the above may be the core reason behind the discussion here.
Thanks
Emil
_
On 2017-11-17 14:55, Tomi Valkeinen wrote:
> On 17/11/17 10:00, Peter Ujfalusi wrote:
>> I believe the intention of the commit 2c9fc9bf45f8
>> ("drm: omapdrm: Move FEAT_HDMI_* features to hdmi4 driver")
>> was to identify omap4430 ES1.x, omap4430 ES2.x and other OMAP4 revisions,
>> like omap4460.
On Wed, Nov 15, 2017 at 03:19:57PM +0100, Noralf Trønnes wrote:
> Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on
> the fact that drm_device holds a pointer to the drm_fb_helper structure.
> This means that the driver doesn't have to keep track of that.
> Also use the drm_fb
On Fri, Nov 17, 2017 at 03:01:08PM +0200, Jani Nikula wrote:
> On Fri, 17 Nov 2017, Greg KH wrote:
> > On Fri, Nov 17, 2017 at 01:28:05PM +0200, Jani Nikula wrote:
> >>
> >> Cc: Greg
> >>
> >> On Wed, 15 Nov 2017, Ville Syrjälä wrote:
> >> > On Wed, Nov 15, 2017 at 04:44:54PM +, alexander.l
On Fri, Nov 17, 2017 at 01:13:27PM +, Emil Velikov wrote:
> Hi Greg, all,
>
> Pardon for the silly question, but I'm struggling to find
> documentation about this new 'autoselection' process?
> Where can one read up on it - be that about the tooling or the heuristics
> used?
>
> I think the
There is no need to #define the license of the driver, just put it in
the MODULE_LICENSE() line directly as a text string.
This allows tools that check that the module license matches the source
code license to work properly, as there is no need to unwind the
unneeded dereference, especially when
https://bugs.freedesktop.org/show_bug.cgi?id=103791
Michel Dänzer changed:
What|Removed |Added
Attachment #135554|text/x-log |text/plain
mime type|
On 17/11/17 11:49 AM, Christian König wrote:
> Hi everyone,
>
> Michel already reviewed this back in April, but I didn't found time to
> actually fully test it before now.
>
> So sending this one out once more because it's an interface change which
> affects all driver using TTM.
>
> Please re
Hey Martin,
On Fri, 2017-11-17 at 15:27 +0100, Martin Fuzzey wrote:
> Hi,
>
> I'm trying to get Android graphics working on i.MX6 using upstream
> versions:
>
> Kernel 4.14
>
> Mesa: mesa-17.3.0-rc2
>
> Libdrm: libdrm-2.4.88
>
> drm_hwcomposer (git head)
>
> gbm_gralloc (git head from git:
https://bugs.freedesktop.org/show_bug.cgi?id=103370
--- Comment #30 from Shih-Yuan Lee ---
Tearing won't happen on battery power, but it will only happen when plugged in
AC power.
Is this behavior also expected?
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=103370
--- Comment #31 from Michel Dänzer ---
With vblank_mode=0, the only thing that can prevent tearing is luck.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mail
On 2017-11-10 05:38 PM, Gustavo A. R. Silva wrote:
> Make use of the swap macro instead of _manually_ swapping values
> and remove unnecessary variable temp.
>
> This makes the code easier to read and maintain.
>
> This code was detected with the help of Coccinelle.
>
> Signed-off-by: Gustavo A.
On 2017-11-10 05:31 PM, Gustavo A. R. Silva wrote:
> Make use of the swap macro instead of _manually_ swapping values
> and remove unnecessary variable swap.
>
> This makes the code easier to read and maintain.
>
> This code was detected with the help of Coccinelle.
>
> Signed-off-by: Gustavo A.
On Friday, November 10, 2017 05:32:31 PM Colin King wrote:
> From: Colin Ian King
>
> The pointer fbi is dereferenced with par = fbi->par before there is a
> null check on fbi, hence there is a potential null pointer dereference
> on a null par. Fix this by moving the dereference after the null
On Tuesday, November 14, 2017 09:12:28 AM Dan Carpenter wrote:
> We cap the upper bound of "fbnum" but we also need to check for
> negatives or make the type unsigned.
>
> Signed-off-by: Dan Carpenter
Patch queued for 4.15, thanks.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institut
On Fri, Nov 17, 2017 at 4:51 AM, Nicolai Hähnle wrote:
>
> This raises the question of how people feel about putting the source
> database into the kernel (most likely as XML in our case) and
> auto-generating the headers from there instead.
I suspect that at least in some cases, the "source" da
On Fri, Nov 17, 2017 at 9:19 AM, Lukas Wunner wrote:
>> and tell me that there isn't any room for making these things smarter.
>
> ... or deduplicate them. :-)
You could even - wait for it - have _automation_ that does it.
Yeah, it's easier to write a stupid sed-script or whatever to generate
th
On Fri, Nov 17, 2017 at 08:57:53AM -0800, Linus Torvalds wrote:
> On Fri, Nov 17, 2017 at 4:51 AM, Nicolai Hähnle wrote:
> To see the effects of this, I picked something at random from one of
> those huge AMD header files.
>
> I swear. It was entirely at random, and the first thing I picked. Do t
First of all I can certainly agree with everything said so far, so just
skipping to the technical problem.
Am 17.11.2017 um 17:57 schrieb Linus Torvalds:
People say "it's a ton of work to do it by hand". They'd be right. I'm
not saying you should do it by hand. But "automation" does not always
From: Colin Ian King
The two comparisons of the unsigned int ret for -ve error returns is
always false because ret is unsigned. Fix this by making ret a signed
int.
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/omapdrm/dss/hdmi4_cec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Fri, Nov 17, 2017 at 10:14 AM, Christian König
wrote:
>
> Taking an example from the AMD headers why this automation is more tricky
> than it sounds in the first place: Look at the
> mmVM_CONTEXT*_PAGE_TABLE_BASE_ADDR registers for example.
>
> Register 0-7 are consecutive and so could be perfe
Am 17.11.2017 um 19:55 schrieb Linus Torvalds:
On Fri, Nov 17, 2017 at 10:14 AM, Christian König
wrote:
Taking an example from the AMD headers why this automation is more tricky
than it sounds in the first place: Look at the
mmVM_CONTEXT*_PAGE_TABLE_BASE_ADDR registers for example.
Register 0-
On Thu, Nov 16, 2017 at 10:50 AM, Joe Perches wrote:
> On Thu, 2017-11-16 at 10:38 -0500, Harry Wentland wrote:
>> On 2017-11-16 10:27 AM, Joe Perches wrote:
>> > Line continuations with excess spacing causes unexpected output.
> []
>> > @@ -872,9 +870,8 @@ static bool perform_clock_recovery_seque
https://bugs.freedesktop.org/show_bug.cgi?id=103769
--- Comment #3 from bartos.p...@gmail.com ---
For additional info, I've compiled latest mesa git with llvm 4.0 (stock version
of Fedora 26) and Unity games are working.
But I've no idea whether the problem is in llvm 6.0 itself, or how mesa is
us
https://bugs.freedesktop.org/show_bug.cgi?id=103107
--- Comment #5 from Hector Velazquez
---
This tests has the same failure on GLK QA
igt@gem_ctx_param@invalid-param-get
igt@gem_ctx_param@invalid-param-set
IGT-Version: 1.20-g88d6550 (x86_64) (Linux: 4.14.0-drm-tip-ww46-commit-1fc4fe8+
x86_64)
https://bugs.freedesktop.org/show_bug.cgi?id=92248
--- Comment #45 from Hector Velazquez
---
This test continue failing on GLK QA
igt@kms_plane_scaling
IGT-Version: 1.20-g88d6550 (x86_64) (Linux: 4.14.0-drm-tip-ww46-commit-1fc4fe8+
x86_64)
fastfeedback-nov-ww46-thursday-07-03-33-code-179785857
https://bugs.freedesktop.org/show_bug.cgi?id=103804
Bug ID: 103804
Summary: igt/benchmark/gem_exec_nop does not permit to select
execution ring
Product: DRI
Version: unspecified
Hardware: Other
OS: All
https://bugs.freedesktop.org/show_bug.cgi?id=103804
Dmitry Rogozhkin changed:
What|Removed |Added
Assignee|dri-devel@lists.freedesktop |ch...@chris-wilson.co.uk
Hi Daniel,
Some cleanup/fixes, some noticed during testing of Noralf Trønnes
rework of the suspend/resume helper. He will rebase the patchset
ontop of this.
I did bsae this still on drm-misc-next-fixes, hope that is still
fine.
--
Stefan
The following changes since commit a9386bb051931778436db3
Andrzej Hajda writes:
> On 16.11.2017 21:27, Eric Anholt wrote:
>> Andrzej Hajda writes:
>>
>>> On 15.11.2017 21:26, Eric Anholt wrote:
I'm happy to have the DSI panel finally working on VC4 (just waiting on
https://lists.freedesktop.org/archives/dri-devel/2017-October/156407.html),
>>
Tested on nouveau with the CRTC only.
Signed-off-by: Ilia Mirkin
---
Please note that I have no clue what the proper way to operate the gamma
interface is. This seemed OK, but the 256 seems awefully hardcoded. Perhaps
that won't work on other HW?
tests/modetest/buffers.c | 2 ++
tests/modete
https://bugs.freedesktop.org/show_bug.cgi?id=103788
--- Comment #2 from coolo...@gmail.com ---
Created attachment 135571
--> https://bugs.freedesktop.org/attachment.cgi?id=135571&action=edit
xorg log after issue
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=103788
--- Comment #3 from coolo...@gmail.com ---
Created attachment 135572
--> https://bugs.freedesktop.org/attachment.cgi?id=135572&action=edit
dmesg after issue
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=103788
coolo...@gmail.com changed:
What|Removed |Added
Summary|Screen goes blank after |Screen goes blank after
On Fri, Nov 17, 2017 at 11:56 PM, Ilia Mirkin wrote:
> Tested on nouveau with the CRTC only.
>
> Signed-off-by: Ilia Mirkin
> ---
>
> Please note that I have no clue what the proper way to operate the gamma
> interface is. This seemed OK, but the 256 seems awefully hardcoded. Perhaps
> that won't
91 matches
Mail list logo
