On Tue, 26 Nov 2019, Lyude Paul wrote:
> I'm about to post some more review comments for the v2 version of this, but
> some comments down below...
>
> On Tue, 2019-10-08 at 12:19 +0300, Jani Nikula wrote:
>> On Mon, 07 Oct 2019, Adam Jackson wrote:
>> > On Mon, 2019-10-07 at 12:08 +0300, Jani Nik
I'm about to post some more review comments for the v2 version of this, but
some comments down below...
On Tue, 2019-10-08 at 12:19 +0300, Jani Nikula wrote:
> On Mon, 07 Oct 2019, Adam Jackson wrote:
> > On Mon, 2019-10-07 at 12:08 +0300, Jani Nikula wrote:
> >
> > > The problem with the EDID q
On Tue, 08 Oct 2019, Jani Nikula wrote:
>On Mon, 07 Oct 2019, Adam Jackson wrote:
>> On Mon, 2019-10-07 at 12:08 +0300, Jani Nikula wrote:
>>
>>> The problem with the EDID quirks is that exposing the quirks sticks out
>>> like a sore thumb. Thus far all of it has been contained in drm_edid.c
>>>
On Mon, 07 Oct 2019, Adam Jackson wrote:
> On Mon, 2019-10-07 at 12:08 +0300, Jani Nikula wrote:
>
>> The problem with the EDID quirks is that exposing the quirks sticks out
>> like a sore thumb. Thus far all of it has been contained in drm_edid.c
>> and they affect how the EDID gets parsed, for a
On Mon, 2019-10-07 at 12:08 +0300, Jani Nikula wrote:
> The problem with the EDID quirks is that exposing the quirks sticks out
> like a sore thumb. Thus far all of it has been contained in drm_edid.c
> and they affect how the EDID gets parsed, for all drivers. Obviously
> this could be changed, b
On Mon, 07 Oct 2019, "Jani Nikula"
mailto:jani.nik...@intel.com>> wrote:
>On Mon, 07 Oct 2019, "Lee, Shawn C"
>mailto:shawn.c@intel.com>> wrote:
>> On Fri, 04 Oct 2019, Jani Nikula
>> mailto:jani.nik...@intel.com>> wrote:
>>>On Fri, 04 Oct 2019, Adam Jackson mailto:a...@redhat.com>>
>>>wro
On Mon, 07 Oct 2019, "Jani Nikula" wrote:
>On Mon, 07 Oct 2019, "Lee, Shawn C" wrote:
>> On Fri, 04 Oct 2019, Jani Nikula wrote:
>>>On Fri, 04 Oct 2019, Adam Jackson wrote:
On Sat, 2019-10-05 at 05:58 +0800, Lee Shawn C wrote:
> This panel (manufacturer is SDC, product ID is 0x4141) u
On Mon, 07 Oct 2019, "Lee, Shawn C" wrote:
> On Fri, 04 Oct 2019, Jani Nikula wrote:
>>On Fri, 04 Oct 2019, Adam Jackson wrote:
>>> On Sat, 2019-10-05 at 05:58 +0800, Lee Shawn C wrote:
This panel (manufacturer is SDC, product ID is 0x4141) used
manufacturer defined DPCD register to c
On Fri, 04 Oct 2019, Jani Nikula wrote:
>On Fri, 04 Oct 2019, Adam Jackson wrote:
>> On Sat, 2019-10-05 at 05:58 +0800, Lee Shawn C wrote:
>>> This panel (manufacturer is SDC, product ID is 0x4141) used
>>> manufacturer defined DPCD register to control brightness that not
>>> defined in eDP spe
On Fri, 04 Oct 2019, Adam Jackson wrote:
> On Sat, 2019-10-05 at 05:58 +0800, Lee Shawn C wrote:
>> This panel (manufacturer is SDC, product ID is 0x4141)
>> used manufacturer defined DPCD register to control brightness
>> that not defined in eDP spec so far. This change follow panel
>> vendor's i
On Sat, 2019-10-05 at 05:58 +0800, Lee Shawn C wrote:
> This panel (manufacturer is SDC, product ID is 0x4141)
> used manufacturer defined DPCD register to control brightness
> that not defined in eDP spec so far. This change follow panel
> vendor's instruction to support brightness adjustment.
I'
This panel (manufacturer is SDC, product ID is 0x4141)
used manufacturer defined DPCD register to control brightness
that not defined in eDP spec so far. This change follow panel
vendor's instruction to support brightness adjustment.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=97883
Cc
12 matches
Mail list logo
