dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 16140] [RADEON:KMS:RV250:RESUME] suspend to RAM resume broken
Date: Tue, 8 Mar 2011 18:32:39 GMT	[thread overview]
Message-ID: <201103081832.p28IWdLA030230@demeter2.kernel.org> (raw)
In-Reply-To: <bug-16140-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=16140


Michael Long <harn-solo@gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Kernel Version|2.6.29 - 2.6.36-rc4-git3    |2.6.29 -
                   |                            |2.6.38-rc7-00163-gfb62c00




--- Comment #41 from Michael Long <harn-solo@gmx.de>  2011-03-08 18:32:33 ---
Jérôme, unfortunately I can only confirm what Sedat reported previously.
I was testing it with the most recent git-kernel.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2011-03-08 18:32 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-16140-2300@https.bugzilla.kernel.org/>
2010-06-23 17:09 ` [Bug 16140] Suspend To RAM/ Resume broken - Radeon KMS on RV250 bugzilla-daemon
2010-06-23 17:20 ` bugzilla-daemon
2010-06-23 21:02 ` bugzilla-daemon
2010-06-23 21:14 ` bugzilla-daemon
2010-06-23 21:17 ` bugzilla-daemon
2010-06-24 17:20 ` bugzilla-daemon
2010-08-13  9:43 ` bugzilla-daemon
2010-08-13  9:48 ` bugzilla-daemon
2010-08-28 12:35 ` bugzilla-daemon
2010-08-28 12:36 ` bugzilla-daemon
2010-08-28 12:43 ` bugzilla-daemon
2010-09-17 11:30 ` bugzilla-daemon
2010-09-17 11:34 ` bugzilla-daemon
2010-09-17 11:35 ` bugzilla-daemon
2010-09-17 11:36 ` bugzilla-daemon
2010-09-17 15:58 ` bugzilla-daemon
2010-09-20 19:45 ` bugzilla-daemon
2010-10-07 21:28 ` bugzilla-daemon
2010-10-07 21:28 ` bugzilla-daemon
2010-10-07 21:29 ` bugzilla-daemon
2010-10-07 21:30 ` bugzilla-daemon
2010-10-07 21:31 ` bugzilla-daemon
2010-10-07 21:32 ` bugzilla-daemon
2010-10-07 21:38 ` bugzilla-daemon
2010-10-07 22:31 ` bugzilla-daemon
2010-10-07 22:32 ` bugzilla-daemon
2010-10-08  9:00 ` bugzilla-daemon
2010-10-08  9:01 ` bugzilla-daemon
2010-10-08  9:02 ` bugzilla-daemon
2010-10-08 11:52 ` bugzilla-daemon
2010-10-08 11:56 ` bugzilla-daemon
2010-10-08 11:59 ` bugzilla-daemon
2010-10-08 12:00 ` bugzilla-daemon
2010-10-08 17:49 ` bugzilla-daemon
2010-10-08 17:52 ` bugzilla-daemon
2010-10-10 13:41 ` bugzilla-daemon
2010-10-10 23:16 ` bugzilla-daemon
2010-10-29 18:00 ` bugzilla-daemon
2010-11-16 22:55 ` bugzilla-daemon
2010-12-04 16:22 ` bugzilla-daemon
2010-12-13  5:27 ` bugzilla-daemon
2011-03-07 18:49 ` [Bug 16140] [RADEON:KMS:RV250:RESUME] suspend to RAM resume broken bugzilla-daemon
2011-03-07 20:09 ` bugzilla-daemon
2011-03-07 20:24 ` bugzilla-daemon
2011-03-08 18:32 ` bugzilla-daemon [this message]
2011-03-08 18:34 ` bugzilla-daemon
2011-03-22  8:38 ` bugzilla-daemon
2011-08-29  3:45 ` bugzilla-daemon
2012-02-09  4:08 ` bugzilla-daemon
2012-02-09 13:54 ` bugzilla-daemon
2012-02-09 16:12 ` bugzilla-daemon
2012-02-09 16:42 ` bugzilla-daemon
2012-11-23 18:33 ` bugzilla-daemon
2013-12-10 21:43 ` 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=201103081832.p28IWdLA030230@demeter2.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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