From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98505] [radeon, amdgpu] Regression introduced in 4.8-rc3
Date: Mon, 14 Nov 2016 15:12:43 +0000 [thread overview]
Message-ID: <bug-98505-502-kId64VuWuW@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98505-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1130 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98505
--- Comment #29 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Peter Wu from comment #23)
> Alex, I don't think that the minimum date should change in 4.8 (and 4.9?)
> due to the risk of breakage since it is not just limited to amdgpu/radeon.
> Another concern is that while the year seems a good heuristic, it does not
> match the checks that Windows 8 performs (which may or may not be an issue):
> https://msdn.microsoft.com/en-us/windows/hardware/drivers/bringup/firmware-
> requirements-for-d3cold
I agree that using the date is probably not a good idea, but it's what we have
now. Adjusting the date seems lower impact than changing the policy for these
kernels.
>
> I'll bring this up with linux-pci developers after the weekend. Should I
> proceed with proposing workaround amdgpu/radeon patches?
Sounds good. I generally don't like hacking around this in the driver, but I
guess it's better than nothing at this point. Thanks for your help with this.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2126 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:[~2016-11-14 15:12 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 16:48 [Bug 98505] [Topaz] Regression introduces in 4.8-rc3 bugzilla-daemon
2016-10-30 16:53 ` bugzilla-daemon
2016-11-01 13:29 ` bugzilla-daemon
2016-11-01 13:56 ` bugzilla-daemon
2016-11-01 18:26 ` bugzilla-daemon
2016-11-01 20:46 ` bugzilla-daemon
2016-11-01 20:49 ` bugzilla-daemon
2016-11-01 23:31 ` bugzilla-daemon
2016-11-02 6:07 ` bugzilla-daemon
2016-11-02 6:11 ` bugzilla-daemon
2016-11-02 16:35 ` bugzilla-daemon
2016-11-02 16:46 ` bugzilla-daemon
2016-11-02 16:55 ` bugzilla-daemon
2016-11-02 16:56 ` bugzilla-daemon
2016-11-04 0:08 ` bugzilla-daemon
2016-11-04 14:51 ` bugzilla-daemon
2016-11-04 15:04 ` bugzilla-daemon
2016-11-07 18:42 ` bugzilla-daemon
2016-11-11 17:56 ` bugzilla-daemon
2016-11-11 17:58 ` [Bug 98505] [radeon, amdgpu] Regression introduced " bugzilla-daemon
2016-11-11 18:14 ` bugzilla-daemon
2016-11-11 18:17 ` bugzilla-daemon
2016-11-11 18:49 ` bugzilla-daemon
2016-11-11 21:22 ` bugzilla-daemon
2016-11-12 23:40 ` bugzilla-daemon
2016-11-13 6:41 ` bugzilla-daemon
2016-11-13 11:24 ` bugzilla-daemon
2016-11-13 16:01 ` bugzilla-daemon
2016-11-13 16:02 ` bugzilla-daemon
2016-11-14 10:52 ` bugzilla-daemon
2016-11-14 15:12 ` bugzilla-daemon [this message]
2016-11-17 15:03 ` bugzilla-daemon
2016-11-19 0:22 ` bugzilla-daemon
2016-11-19 2:07 ` bugzilla-daemon
2016-11-19 2:08 ` bugzilla-daemon
2016-11-19 17:32 ` bugzilla-daemon
2016-11-19 19:21 ` bugzilla-daemon
2016-11-19 19:23 ` bugzilla-daemon
2016-12-05 13:49 ` bugzilla-daemon
2016-12-05 19:32 ` 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-98505-502-kId64VuWuW@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