2010/5/10 Andy Furniss :
>> The module parameter is obsolete. you can enable it dynamically via
>> sysfs (power_method). ?The default pm method is profile.
>
> OK, I know dynpm was removed - but this is dynclks are the two the same?
dynclks is for disabling clocking unused blocks. It means you don
Alex Deucher wrote:
> Send me a copy of your vbios, I may need to adjust the profile table
> for rv670. As root:
> cd /sys/bus/pci/devices/
> echo 1> rom
> cat rom> /tmp/vbios.rom
> echo 0> rom
Sent
>> One separate question - do I need to use the module param dynclks=1 or is it
>> the defau
Alex Deucher wrote:
> The "profile" method exposes 4 profiles that can be selected from:
> 1. "default"
> 2. "auto"
> 3. "low"
> 4. "high"
> Select the profile by echoing the selected profile to
> /sys/class/drm/card-0/device/power_profile.
Testing on a rv670 desktop it seems that low does not fo
On Mon, May 10, 2010 at 12:04 PM, Andy Furniss wrote:
> Alex Deucher wrote:
>
>> The "profile" method exposes 4 profiles that can be selected from:
>> 1. "default"
>> 2. "auto"
>> 3. "low"
>> 4. "high"
>> Select the profile by echoing the selected profile to
>> /sys/class/drm/card-0/device/power_p
2010/5/10 Andy Furniss :
>> The module parameter is obsolete. you can enable it dynamically via
>> sysfs (power_method). The default pm method is profile.
>
> OK, I know dynpm was removed - but this is dynclks are the two the same?
dynclks is for disabling clocking unused blocks. It means you don
Alex Deucher wrote:
Send me a copy of your vbios, I may need to adjust the profile table
for rv670. As root:
cd /sys/bus/pci/devices/
echo 1> rom
cat rom> /tmp/vbios.rom
echo 0> rom
Sent
One separate question - do I need to use the module param dynclks=1 or is it
the default?
The mod
On Mon, May 10, 2010 at 12:04 PM, Andy Furniss wrote:
> Alex Deucher wrote:
>
>> The "profile" method exposes 4 profiles that can be selected from:
>> 1. "default"
>> 2. "auto"
>> 3. "low"
>> 4. "high"
>> Select the profile by echoing the selected profile to
>> /sys/class/drm/card-0/device/power_p
Alex Deucher wrote:
The "profile" method exposes 4 profiles that can be selected from:
1. "default"
2. "auto"
3. "low"
4. "high"
Select the profile by echoing the selected profile to
/sys/class/drm/card-0/device/power_profile.
Testing on a rv670 desktop it seems that low does not force the car
On Sat, 8 May 2010 11:29:10 -0400
Alex Deucher wrote:
> On Sat, May 8, 2010 at 7:14 AM, Klaus Doblmann B.A.
> wrote:
> > the profile setting works but I can't check which clock speeds are
> > set as I don't get any feedback (dmesg) anymore (Someone have any
> > input on this?). The temps are un
On Fri, 7 May 2010 17:16:11 -0400
Alex Deucher wrote:
> This set of patches applies on top of the code in drm-radeon-testing.
>
> I've been testing this code pretty hard this week and it's been solid.
> In addition to some fixes on top of what's in d-r-t, it also reworks
> the pm code to suppor
On Sat, 8 May 2010 11:29:10 -0400
Alex Deucher wrote:
> On Sat, May 8, 2010 at 7:14 AM, Klaus Doblmann B.A.
> wrote:
> > the profile setting works but I can't check which clock speeds are
> > set as I don't get any feedback (dmesg) anymore (Someone have any
> > input on this?). The temps are un
On Sat, May 8, 2010 at 7:14 AM, Klaus Doblmann B.A.
wrote:
> On Fri, ?7 May 2010 17:16:11 -0400
> Alex Deucher wrote:
>
>> This set of patches applies on top of the code in drm-radeon-testing.
>>
>> I've been testing this code pretty hard this week and it's been solid.
>> In addition to some fixe
On Sat, May 8, 2010 at 7:14 AM, Klaus Doblmann B.A.
wrote:
> On Fri, 7 May 2010 17:16:11 -0400
> Alex Deucher wrote:
>
>> This set of patches applies on top of the code in drm-radeon-testing.
>>
>> I've been testing this code pretty hard this week and it's been solid.
>> In addition to some fixe
On Fri, 7 May 2010 17:16:11 -0400
Alex Deucher wrote:
> This set of patches applies on top of the code in drm-radeon-testing.
>
> I've been testing this code pretty hard this week and it's been solid.
> In addition to some fixes on top of what's in d-r-t, it also reworks
> the pm code to suppor
On Fri, May 07, 2010 at 05:16:11PM -0400, Alex Deucher wrote:
> "auto" selects between low and high power states based on the whether the
> system
> is on battery power or not. Even lower power states are selected when the
> monitors
> are in the dpms off state.
Beyond the constraints imposed
On Fri, May 07, 2010 at 05:16:11PM -0400, Alex Deucher wrote:
> "auto" selects between low and high power states based on the whether the
> system
> is on battery power or not. Even lower power states are selected when the
> monitors
> are in the dpms off state.
Beyond the constraints imposed
On Fri, May 7, 2010 at 5:23 PM, Matthew Garrett wrote:
> On Fri, May 07, 2010 at 05:16:11PM -0400, Alex Deucher wrote:
>
>> "auto" selects between low and high power states based on the whether the
>> system
>> is on battery power or not. ?Even lower power states are selected when the
>> monitor
This set of patches applies on top of the code in drm-radeon-testing.
I've been testing this code pretty hard this week and it's been solid.
In addition to some fixes on top of what's in d-r-t, it also reworks
the pm code to support two basic methods:
1. "dynpm"
2. "profile"
You can select the m
On Fri, May 7, 2010 at 5:23 PM, Matthew Garrett wrote:
> On Fri, May 07, 2010 at 05:16:11PM -0400, Alex Deucher wrote:
>
>> "auto" selects between low and high power states based on the whether the
>> system
>> is on battery power or not. Even lower power states are selected when the
>> monitor
This set of patches applies on top of the code in drm-radeon-testing.
I've been testing this code pretty hard this week and it's been solid.
In addition to some fixes on top of what's in d-r-t, it also reworks
the pm code to support two basic methods:
1. "dynpm"
2. "profile"
You can select the m
20 matches
Mail list logo
