On 2018-10-25 7:57 p.m., Wentland, Harry wrote:
> On 2018-10-12 4:31 a.m., Koenig, Christian wrote:
>> Am 12.10.2018 um 10:26 schrieb Michel Dänzer:
>>> On 2018-10-11 9:44 p.m., Harry Wentland wrote:
On 2018-10-03 04:25 AM, Mike Lothian wrote:
> I'm curious to know whether this will/could
On 2018-10-12 4:31 a.m., Koenig, Christian wrote:
> Am 12.10.2018 um 10:26 schrieb Michel Dänzer:
>> On 2018-10-11 9:44 p.m., Harry Wentland wrote:
>>> On 2018-10-03 04:25 AM, Mike Lothian wrote:
I'm curious to know whether this will/could work over PRIME
>>> I don't see why this shouldn't
Am 12.10.2018 um 10:26 schrieb Michel Dänzer:
> On 2018-10-11 9:44 p.m., Harry Wentland wrote:
>> On 2018-10-03 04:25 AM, Mike Lothian wrote:
>>> I'm curious to know whether this will/could work over PRIME
>> I don't see why this shouldn't work over PRIME as long as the
>> presenting GPU supports
On 2018-10-11 9:44 p.m., Harry Wentland wrote:
> On 2018-10-03 04:25 AM, Mike Lothian wrote:
>>
>> I'm curious to know whether this will/could work over PRIME
>
> I don't see why this shouldn't work over PRIME as long as the
> presenting GPU supports the new variable refresh rate API, but I know
On 2018-10-03 04:25 AM, Mike Lothian wrote:
> Hi
>
> I'm curious to know whether this will/could work over PRIME
>
I don't see why this shouldn't work over PRIME as long as the presenting GPU
supports the new variable refresh rate API, but I know very little about prime,
so maybe someone else
On 2018-10-03 04:41 AM, Daniel Vetter wrote:
> On Tue, Oct 02, 2018 at 10:49:17AM -0400, Harry Wentland wrote:
>>
>>
>> On 2018-10-01 03:15 AM, Daniel Vetter wrote:
>>> On Mon, Sep 24, 2018 at 02:15:34PM -0400, Nicholas Kazlauskas wrote:
These patches are part of a proposed new interface for
On 2018-10-03 02:35 PM, Manasi Navare wrote:
> On Wed, Oct 03, 2018 at 10:41:20AM +0200, Daniel Vetter wrote:
>> On Tue, Oct 02, 2018 at 10:49:17AM -0400, Harry Wentland wrote:
>>>
>>>
>>> On 2018-10-01 03:15 AM, Daniel Vetter wrote:
On Mon, Sep 24, 2018 at 02:15:34PM -0400, Nicholas
On Wed, Oct 03, 2018 at 10:41:20AM +0200, Daniel Vetter wrote:
> On Tue, Oct 02, 2018 at 10:49:17AM -0400, Harry Wentland wrote:
> >
> >
> > On 2018-10-01 03:15 AM, Daniel Vetter wrote:
> > > On Mon, Sep 24, 2018 at 02:15:34PM -0400, Nicholas Kazlauskas wrote:
> > >> These patches are part of a
On Tue, Oct 02, 2018 at 10:49:17AM -0400, Harry Wentland wrote:
>
>
> On 2018-10-01 03:15 AM, Daniel Vetter wrote:
> > On Mon, Sep 24, 2018 at 02:15:34PM -0400, Nicholas Kazlauskas wrote:
> >> These patches are part of a proposed new interface for supporting variable
> >> refresh rate via DRM
Hi
I'm curious to know whether this will/could work over PRIME
If the discrete card is rendering slower than the display's frequency could
the frequency be dropped on integrated display? I think there are laptops
that have freesync now
Cheers
Mike
On Mon, 1 Oct 2018 at 08:15 Daniel Vetter
On 2018-10-01 03:15 AM, Daniel Vetter wrote:
> On Mon, Sep 24, 2018 at 02:15:34PM -0400, Nicholas Kazlauskas wrote:
>> These patches are part of a proposed new interface for supporting variable
>> refresh rate via DRM properties.
>>
>> === Changes from v1 ===
>>
>> For drm:
>>
>> * The
On Mon, Sep 24, 2018 at 02:15:34PM -0400, Nicholas Kazlauskas wrote:
> These patches are part of a proposed new interface for supporting variable
> refresh rate via DRM properties.
>
> === Changes from v1 ===
>
> For drm:
>
> * The variable_refresh_capable property is now flagged as
>
These patches are part of a proposed new interface for supporting variable
refresh rate via DRM properties.
=== Changes from v1 ===
For drm:
* The variable_refresh_capable property is now flagged as
DRM_MODE_PROP_IMMUTABLE
For drm/gpu/amd/display:
* Patches no longer pull in IOCTL/FreeSync
13 matches
Mail list logo
