dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26350] Single corruption (artifacts) on engine reclocking
Date: Sun, 31 Jan 2010 09:30:53 -0800 (PST)	[thread overview]
Message-ID: <20100131173053.447F813009D@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-26350-502@http.bugs.freedesktop.org/>

http://bugs.freedesktop.org/show_bug.cgi?id=26350





--- Comment #2 from Rafał Miłecki <zajec5@gmail.com>  2010-01-31 09:30:52 PST ---
Created an attachment (id=32949)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=32949)
Switch engine clock setting to registers operations

It may be good idea to perform sensible operations manually, without parsing
AtomBIOS commands. Unfortunately it needs rewriting AtomBIOS code for each GPU
generation.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

  parent reply	other threads:[~2010-01-31 17:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-31 17:17 [Bug 26350] New: Single corruption (artifacts) on engine reclocking bugzilla-daemon
2010-01-31 17:28 ` [Bug 26350] " bugzilla-daemon
2010-01-31 17:30 ` bugzilla-daemon [this message]
2010-01-31 17:39 ` bugzilla-daemon
2019-11-19  8:09 ` 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=20100131173053.447F813009D@annarchy.freedesktop.org \
    --to=bugzilla-daemon@freedesktop.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