[Bug 40894] New: nv30-/temperature: Reverse engineer the temperature coefficients

* [Bug 40894] New: nv30-/temperature: Reverse engineer the temperature coefficients
@ 2011-09-14 22:30 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
       [not found] ` <bug-40894-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
  0 siblings, 1 reply; 5+ messages in thread
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ @ 2011-09-14 22:30 UTC (permalink / raw)
  To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW

https://bugs.freedesktop.org/show_bug.cgi?id=40894

           Summary: nv30-/temperature: Reverse engineer the temperature
                    coefficients
           Product: xorg
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: martin.peres-Iz16wY1oaNPLSKGbIzaifA@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

We currently have some bits of knowledge about temperature management on cards
up to nv40, but it doesn't seem to work on every card.

The work that needs to be done is understand how the temperature table entries
in the vbios influence the proprietary driver's temperature readings.

What is needed is to install the envytools
(https://github.com/pathscale/envytools/tree/), get your vbios using
nvagetbios, parse it with nvbios, get the address of the temperature table,
edit this table with an hex editor, upload it using nvafakebios, load the
nvidia module and then launch the blob and check how your changes affected the
temperature reading.

Then, exit X, rmmod nvidia and start again at the hex editor step ;)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 5+ messages in thread