On 2018-03-07 22:15, Harry Wentland wrote:
amd-stg has some other patches relating to DCN pipe-split that I don't fully
understand. We might need one or more of those.
As a workaround you can probably set 'force_single_disp_pipe_split' to 'false'
in 'debug_defaults_drv' in dc/dcn10/dcn10_resou
On 2018-03-07 02:54 PM, KARBOWSKI Piotr wrote:
> On 2018-03-07 20:31, KARBOWSKI Piotr wrote:
>> On 2018-03-07 20:12, Harry Wentland wrote:
>>> Thanks for testing.
>>>
>>> What do you mean with broken video? I tried going back in the email thread
>>> but I'm not 100% clear what you mean by this.
>>
On 2018-03-07 20:12, Harry Wentland wrote:
Thanks for testing.
What do you mean with broken video? I tried going back in the email thread but
I'm not 100% clear what you mean by this.
BTW, drm-fixes-4.16 are fixes we intend to get into the 4.16 upstream kernel.
amd-staging-drm-next is our dev
On 2018-03-07 20:31, KARBOWSKI Piotr wrote:
On 2018-03-07 20:12, Harry Wentland wrote:
Thanks for testing.
What do you mean with broken video? I tried going back in the email
thread but I'm not 100% clear what you mean by this.
BTW, drm-fixes-4.16 are fixes we intend to get into the 4.16 ups
Yup, that's there as
commit e92b44fdee3ec0b679bacdb9c7e95e55699167f0
Author: Tony Cheng
Date: Thu Oct 5 14:38:46 2017 -0400
drm/amd/display: default force_single_disp_pipe_split = 1 on RV
...
Harry
On 2018-03-07 02:16 PM, Tom St Denis wrote:
> It's an old patch but does drm-fixes-4.16
It's an old patch but does drm-fixes-4.16 have this patch
commit e92b44fdee3ec0b679bacdb9c7e95e55699167f0
Refs: v4.14-rc3-1871-ge92b44fdee3e
Author: Tony Cheng
AuthorDate: Thu Oct 5 14:38:46 2017 -0400
Commit: Alex Deucher
CommitDate: Sat Oct 21 16:52:21 2017 -0400
drm
On 2018-03-07 12:38 PM, KARBOWSKI Piotr wrote:
> On 2018-03-07 17:48, KARBOWSKI Piotr wrote:
>> On 2018-03-07 17:14, Harry Wentland wrote:
>>> Pushed a drm-fixes-4.16 branch (based on Alex's) to my FDO repo
>>> athttps://cgit.freedesktop.org/~hwentland/linux/ but I don't have a Raven
>>> system
On 2018-03-07 17:48, KARBOWSKI Piotr wrote:
On 2018-03-07 17:14, Harry Wentland wrote:
Pushed a drm-fixes-4.16 branch (based on Alex's) to my FDO repo
athttps://cgit.freedesktop.org/~hwentland/linux/ but I don't have a
Raven system setup to test this at the moment.
Tom, or Piotr, would you b
On 2018-03-07 17:14, Harry Wentland wrote:
Pushed a drm-fixes-4.16 branch (based on Alex's) to my FDO repo
athttps://cgit.freedesktop.org/~hwentland/linux/ but I don't have a Raven
system setup to test this at the moment.
Tom, or Piotr, would you be able to check that the fix works as intende
Cloning/building will take a bit. I'll let you know later this afternoon.
Cheers,
Tom
On 03/07/2018 11:14 AM, Harry Wentland wrote:
On 2018-03-07 09:55 AM, Harry Wentland wrote:
I'm prepping some cherry-picks for drm-fixes-4.16, including this. Should've
done that a while ago, but shouldn't
On 2018-03-07 09:55 AM, Harry Wentland wrote:
> I'm prepping some cherry-picks for drm-fixes-4.16, including this. Should've
> done that a while ago, but shouldn't be too late yet.
>
Pushed a drm-fixes-4.16 branch (based on Alex's) to my FDO repo at
https://cgit.freedesktop.org/~hwentland/linux
I'm prepping some cherry-picks for drm-fixes-4.16, including this. Should've
done that a while ago, but shouldn't be too late yet.
Harry
On 2018-03-07 07:55 AM, Tom St Denis wrote:
> It's in the next set of display patches for drm-next but I don't think it'll
> be in 4.16 at this point unless i
It's in the next set of display patches for drm-next but I don't think
it'll be in 4.16 at this point unless it gets cherry picked out.
Alex would know for sure since he co-ordinates that with Dave.
Tom
On 03/06/2018 12:38 PM, KARBOWSKI Piotr wrote:
On 2018-03-06 18:28, Tom St Denis wrote:
I
On 2018-03-06 18:28, Tom St Denis wrote:
I routinely rebase this patch on top of our amd-staging-drm-next tree at
fdo.
https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next
Awesome.
So I used this tree, branch amd-staging-drm-next, and applied the patch
- and my screen works
Hi,
On 2018-03-06 12:18, Tom St Denis wrote:
I believe this is the same issue I had which is a VGA handoff problem.
Can you try this patch the display team sent me?
Harry: Will this patch be promoted in the next cycle?
What is the base for this patch? I cannot apply it on the top of any
4.
I routinely rebase this patch on top of our amd-staging-drm-next tree at
fdo.
https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next
Tom
On 03/06/2018 12:27 PM, KARBOWSKI Piotr wrote:
Hi,
On 2018-03-06 12:18, Tom St Denis wrote:
I believe this is the same issue I had which
On 2018-03-06 11:13 AM, Alex Deucher wrote:
> On Tue, Mar 6, 2018 at 6:18 AM, Tom St Denis wrote:
>> I believe this is the same issue I had which is a VGA handoff problem.
>>
>> Can you try this patch the display team sent me?
>>
>> Harry: Will this patch be promoted in the next cycle?
>
> I thi
On Tue, Mar 6, 2018 at 6:18 AM, Tom St Denis wrote:
> I believe this is the same issue I had which is a VGA handoff problem.
>
> Can you try this patch the display team sent me?
>
> Harry: Will this patch be promoted in the next cycle?
I think it will eventually. IIRC, there were some regressio
I believe this is the same issue I had which is a VGA handoff problem.
Can you try this patch the display team sent me?
Harry: Will this patch be promoted in the next cycle?
Tom
On 03/05/2018 11:40 AM, KARBOWSKI Piotr wrote:
Hi list,
I'd like to report a very odd screen artifacts while runn
19 matches
Mail list logo