How Do You Over / Under Clock On R198? Options

[scrapheap]

I have been setting up r198 to my liking, but I have not figured out how to over/under clock the zaurus (c1000) in this version. It used to be adjusting the VCORE file in /proc/zaurus/ but I can't see that here. Is there a different method for this versionl?

[ecc_hy]

In fact, it is total different.
r198 use ioctl()

[scrapheap]

OK, I guess I had better figure out how ioctl() works then.

[ecc_hy]

/sys/devices/system/cpu/cpu0/cpufreq/cpu-voltage
/dev/ipmc

[scrapheap]

Is it possible to use dvfm (I have seen it mentioned on a few pages when googling for information about ioctl with /dev/ipmc)

[Meanie]

Is it possible to use dvfm (I have seen it mentioned on a few pages when googling for information about ioctl with /dev/ipmc)

try looking at cpuoverclock.py

it uses dvfm to overclock/underclock the system, although, it does not adjust the voltage properly so expect lockups ...

[shula]

#This script serves me well on my C860:
#/bin/bash
#
# overclocking from the command line, by 'shula'
#
echo overclocking...

if grep -q 161 /proc/cccr_change ; then echo status: normal
elif grep -q 162 /proc/cccr_change ; then echo status: high
elif grep -q 141 /proc/cccr_change ; then echo status: low
fi

changed=0
case $1 in
normal)
echo 161 > /proc/cccr_change
echo 100 > /proc/driver/w100/fastsysclk
echo changing to $1
changed=1
;;
over|high)
echo 162 > /proc/cccr_change
echo 100 > /proc/driver/w100/fastsysclk
echo changing to high
changed=1
;;
under|low)
echo 141 > /proc/cccr_change
echo 100 > /proc/driver/w100/fastsysclk
echo changing to low
changed=1
;;
esac

if test 0 -eq $changed ; then
echo 'usage: overclock [normal|high|low]'
fi

[shula]

CODE

#This script serves me well on my C860:
#/bin/bash
#
# overclocking from the command line, by 'shula'
#
echo overclocking...

if grep -q 161 /proc/cccr_change; then  echo status: normal
elif grep -q 162 /proc/cccr_change; then  echo status: high  
elif grep -q 141 /proc/cccr_change; then  echo status: low
fi

changed=0
case $1 in
   normal)
       echo 161 > /proc/cccr_change
       echo 100 > /proc/driver/w100/fastsysclk
       echo changing to $1
       changed=1
      ;;
   over|high)
       echo 162 > /proc/cccr_change
       echo 100 > /proc/driver/w100/fastsysclk
       echo changing to high
       changed=1
      ;;
   under|low)
       echo 141 > /proc/cccr_change
       echo 100 > /proc/driver/w100/fastsysclk
       echo changing to low
       changed=1
      ;;
esac

if test 0 -eq $changed; then
   echo 'usage:  overclock [normal|high|low]'
fi

[Meanie]

CODE

#This script serves me well on my C860:
#/bin/bash
#
# overclocking from the command line, by 'shula'
#
echo overclocking...

if grep -q 161 /proc/cccr_change; then  echo status: normal
elif grep -q 162 /proc/cccr_change; then  echo status: high  
elif grep -q 141 /proc/cccr_change; then  echo status: low
fi

changed=0
case $1 in
   normal)
       echo 161 > /proc/cccr_change
       echo 100 > /proc/driver/w100/fastsysclk
       echo changing to $1
       changed=1
     ;;
   over|high)
       echo 162 > /proc/cccr_change
       echo 100 > /proc/driver/w100/fastsysclk
       echo changing to high
       changed=1
     ;;
   under|low)
       echo 141 > /proc/cccr_change
       echo 100 > /proc/driver/w100/fastsysclk
       echo changing to low
       changed=1
     ;;
esac

if test 0 -eq $changed; then
   echo 'usage:  overclock [normal|high|low]'
fi

make sure you don't use those values in the script. a c1000 needs different values.

[louigi600]

If someone gives me the values that should be used on all the different models I could make the script autosense model from /proc/cpuinfo and apply the correct values for it.
We could then have one script that serves well all models ;-)

[Meanie]

If someone gives me the values that should be used on all the different models I could make the script autosense model from /proc/cpuinfo and apply the correct values for it.
We could then have one script that serves well all models ;-)

see cpuoverclock.py for all the required values...

[louigi600]

In /usr/bib/cpuoverclock.py only pxa270 is implemented (which I guess id for C1000/3x00 models), therefor I guess that values for C860 are good for all pxa255 based models (750,760,860).
What about c700, its a pxa250 will pxa255 settings be good for pxa250 too ?
I've no idea what the 7500 has inside ;-)

Not sure what to do for 6000, 5600 and 5500 they are not supported by pdaxrom current.

[Meanie]

In /usr/bib/cpuoverclock.py only pxa270 is implemented (which I guess id for C1000/3x00 models), therefor I guess that values for C860 are good for all pxa255 based models (750,760,860).
What about c700, its a pxa250 will pxa255 settings be good for pxa250 too ?
I've no idea what the 7500 has inside ;-)

Not sure what to do for 6000, 5600 and 5500 they are not supported by pdaxrom current.

check cpuoverclock.py for pdaXrom classic. it has the values for 6000, and according to that, c700 is a pxa250, c7500 and 6000 are pxa255

[louigi600]

I dont have any of the older pdaxrom versions (and it's a good waste of time to install it just for that).
If someone is so kind as to post them I'd appreciate.
If noone posts them I'll go snooping for them in the IPK's from the feeds.
But will the older versuons running 2.4 kernels be doing the same stuff that is done in 2.6 kernels ?

Anyway I've only Cx60 and C1k so I guess I'll be fine anyway ;-)

[T3_slider]

Here's the cpuoverclock.py from pdaXrom beta 3. It seems to have all of the required values (I'm too lazy to paste just the required contents as I'm posting this from my Z).

Hope this helps.

Attached File(s)

 cpuoverclock.py.txt ( 5.71K ) Number of downloads: 24