AMD Fusion / Bobcat Core - any plans?
-
- Posts: 19
- Joined: Sat 2. Oct 2010, 14:27
AMD Fusion / Bobcat Core - any plans?
AMD Fusion / Bobcat Core - Is there any chance that a new shiny processor family will also be supported in the near future? I know You guys work in spare time and support for the machine itself (amd family 14) is just coming but if anything I am willing to test any changes to the new module as I have just bougth new shiny Zacate E-350
Re: AMD Fusion / Bobcat Core - any plans?
If only I had the hardware to write it... I would really like to do that, maybe with your help in time I will be able to.
A bank is a place where they lend you an umbrella in fair weather and ask for it back when it begins to rain -- R. Frost
-
- Posts: 19
- Joined: Sat 2. Oct 2010, 14:27
Re: AMD Fusion / Bobcat Core - any plans?
sure I will help. I have few years of Gentooing behind me so applying patches and setting apropriate kernel options for testing and debuging should be of no problem.
Just let me know what You need
Just let me know what You need
-
- Posts: 19
- Joined: Sat 2. Oct 2010, 14:27
Re: AMD Fusion / Bobcat Core - any plans?
After testing stuff around with help from DavidG it turned out that current 0.4.4 alpha 2 driver works for newer family of AMD machnes as well. Reason is that the VID values are stored at exactly the same register in the same bits. One may be able to do some undervolting writing slightly higher values to /sys/devices/system/cpu/cpu*/cpufreq/phc_vids.
test results
hardware:
vendor_id : AuthenticAMD
cpu family : 20
model : 1
model name : AMD E-350 Processor
default:
echo "20 21 42" > /sys/devices/system/cpu/cpu0/cpufreq/phc_vids
reached safe levels:
echo "26 28 52" > /sys/devices/system/cpu/cpu0/cpufreq/phc_vids
setting any of the 3 values to even 1 digit higher resulted in crash after longer testing
test results
hardware:
vendor_id : AuthenticAMD
cpu family : 20
model : 1
model name : AMD E-350 Processor
default:
echo "20 21 42" > /sys/devices/system/cpu/cpu0/cpufreq/phc_vids
reached safe levels:
echo "26 28 52" > /sys/devices/system/cpu/cpu0/cpufreq/phc_vids
setting any of the 3 values to even 1 digit higher resulted in crash after longer testing