From: Jani Nikula <jani.nikula@linux.intel.com>
To: Wolfgang Haupt <haupt.wolfgang@gmail.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: force yuv 4:2:0 output
Date: Thu, 21 Sep 2017 11:14:01 +0300 [thread overview]
Message-ID: <87efr079km.fsf@nikula.org> (raw)
In-Reply-To: <CANdnG_=ANsW5-YSwvXR9tpCY4hGJic94K7_Biy2OCfqZ227XOg@mail.gmail.com>
On Wed, 20 Sep 2017, Wolfgang Haupt <haupt.wolfgang@gmail.com> wrote:
> I've tried v4.14-rc1.
> Now I do not have 4k@60 anymore.
Okay, please file a bug at
https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
> dmesg with drm.debug:
> http://sprunge.us/TKbO
Attach dmesg all the way from boot to the bug please.
BR,
Jani.
>
>
> Best Regards,
> Wolfgang
>
> Jani Nikula <jani.nikula@linux.intel.com> schrieb am Di., 19. Sep. 2017 um
> 12:08 Uhr:
>
>> On Mon, 18 Sep 2017, Wolfgang Haupt <haupt.wolfgang@gmail.com> wrote:
>> > Hello everyone,
>> >
>> > recently I played around with my kabylake i5 nuc box and found that on
>> some
>> > TV's
>> > the screen stays black as soon as I go to 4k@60.
>> > The TV only accepts 4k@60 at yuv 4:2:0 (I also saw hdmi range extenders
>> and
>> > stuff that don't support yuv 4:4:4 on 4k@60).
>> > I tried to force limited mode through xrandr or by overriding the edid
>> > information, but nothing worked so far.
>> > Now I wonder if there is a way to force yuv 4:2:0 ouptut on the kernel
>> > level.
>> > Thanks.
>>
>> Please try v4.14-rc1.
>>
>> BR,
>> Jani.
>>
>>
>> --
>> Jani Nikula, Intel Open Source Technology Center
>>
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-09-21 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 21:29 force yuv 4:2:0 output Wolfgang Haupt
2017-09-19 10:07 ` Jani Nikula
2017-09-20 19:09 ` Wolfgang Haupt
2017-09-21 8:14 ` Jani Nikula [this message]
2017-09-21 14:29 ` Wolfgang Haupt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efr079km.fsf@nikula.org \
--to=jani.nikula@linux.intel.com \
--cc=haupt.wolfgang@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox