intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: sdrb <sdrb@onet.eu>, intel-gfx@lists.freedesktop.org
Subject: Re: Artifacts on virtual console basing on inteldrmfb framebuffer
Date: Thu, 20 Jul 2017 17:33:07 +0300	[thread overview]
Message-ID: <87fudrnpp8.fsf@intel.com> (raw)
In-Reply-To: <dc901e7e-14d3-d9d9-6082-c64e28657fdc@onet.eu>


Moving to intel-gfx list, intel-gfx-bugs is mainly just for the
automated emails from bugzilla. And please let's keep the debugging in
the bug.

BR,
Jani.

On Thu, 20 Jul 2017, sdrb <sdrb@onet.eu> wrote:
> Hello,
>
> I have got some problems with intel drm frame buffer on Linux virtual 
> terminals.
>
> After I switch back from Xorg to VT I receive artifacts on one of the 
> monitors.
> Seems like there is "randr" somehow involved in this issue.
>
> I described this issue in more details in following bug report:
>
> https://bugs.freedesktop.org/show_bug.cgi?id=101772
>
> Is it known issue and is there any solution for it?
>
> _______________________________________________
> intel-gfx-bugs mailing list
> intel-gfx-bugs@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx-bugs

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

           reply	other threads:[~2017-07-20 14:33 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <dc901e7e-14d3-d9d9-6082-c64e28657fdc@onet.eu>]

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=87fudrnpp8.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sdrb@onet.eu \
    /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;
as well as URLs for NNTP newsgroup(s).