From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99528] Wine game doesn't redraw properly in fullscreen
Date: Sun, 05 Feb 2017 23:00:06 +0000 [thread overview]
Message-ID: <bug-99528-502-fhvN7u27NQ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99528-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 682 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99528
--- Comment #6 from Fabian Maurer <dark.shadow4@web.de> ---
(In reply to fin4478 from comment #4)
> Those stock kernels have very little new amdgpu and radeon drivers code
> (see diff in kernel.org), use latest drivers when you make bug reports. This
> kernel is latest and stable:
> https://cgit.freedesktop.org/~agd5f/linux/?h=drm-next-4.11-wip
Thanks, didn't know that. There's also
https://cgit.freedesktop.org/~airlied/linux/log/?h=drm-next
Which one of those should I chose, they both seem to be fairly recent. But why
is it 4.11?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1690 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-02-05 23:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 2:28 [Bug 99528] Wine game doesn't redraw properly in fullscreen bugzilla-daemon
2017-02-04 12:51 ` bugzilla-daemon
2017-02-04 13:19 ` bugzilla-daemon
2017-02-04 13:53 ` bugzilla-daemon
2017-02-05 18:40 ` bugzilla-daemon
2017-02-05 18:43 ` bugzilla-daemon
2017-02-05 23:00 ` bugzilla-daemon [this message]
2017-02-06 6:54 ` bugzilla-daemon
2018-07-04 23:01 ` bugzilla-daemon
2018-07-07 21:28 ` bugzilla-daemon
2018-08-02 0:55 ` bugzilla-daemon
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=bug-99528-502-fhvN7u27NQ@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@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;
as well as URLs for NNTP newsgroup(s).