If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Aside:
I've also started the beginnings of a radeon performance profile-setting GUI as a way to teach myself GTK. I'll be poking around at this one in my spare time over the next few weeks, and hopefully by the end I'll have something to show for it. Currently targeting only radeons (r100+), but if I can find the right sysfs nodes for Nouveau/Intel/others (PTS can probably show me the way here), there's no reason I couldn't handle them all.

Current features targeted: Change CPU/memory clocks/profiles, report temperatures/frequencies. Eventually, maybe add support for setting fan profiles/speeds when applicable. I'll leave DPMS to KDE/Gnome/etc. X.org feature settings (2D tiling, etc) will probably be left out for now, but might be added in the future.

Please make the user interface portable to other tool kits. I will happily try my coding skills with QT, once I learn enough C++ .

Readers should be aware that the llano is slightly gimped based on the ram used. I don't know what speed he used (1333/1600 possible?) I get much higher results with 1866. If I am wrong then there is something else gimping his speeds considering this was a budget pc for under $400 and I get better results I can't imagine what.

Please make the user interface portable to other tool kits. I will happily try my coding skills with QT, once I learn enough C++ .

I'll see what I can do. I've at least separated the back-end library and the GUI into separate object files, so you could attach a Qt GUI to the back-end library without too much hassle. I'll look up a Qt tutorial and see what I can do to abstract away the GUI enough that it could handle both GTK/Qt. *NIX GUI programming is completely new to me, and I only know C (not C++), so expect some road bumps

Once I get the GTK GUI functional, I'll post the source location for others to download/hack on.

Mostly, because the tool that I'm writing only targets the sysfs interfaces exposed by the radeon kernel driver. It's a run-time tool, and in its initial form, it will not persist settings across reboots. Most of the options that are disabled by default (2D tiling, PCIe 2, etc) are either kernel parameters or X.org configuration options. If I screw up writing kernel parameters for the user, I can hose a system, make it unbootable, and piss people off. Kernel parameter setting is also distro dependent (grub, lilo, etc). Same argument goes for overriding X.org settings (assuming the system even has an xorg.conf). I can document what settings need to be set, but those already are documented in various Wiki's and man pages, and just need to be summarized.

The sysfs nodes are much safer to read/set, which is why I'm starting there.

I'll see what I can do. I've at least separated the back-end library and the GUI into separate object files, so you could attach a Qt GUI to the back-end library without too much hassle. I'll look up a Qt tutorial and see what I can do to abstract away the GUI enough that it could handle both GTK/Qt. *NIX GUI programming is completely new to me, and I only know C (not C++), so expect some road bumps

Once I get the GTK GUI functional, I'll post the source location for others to download/hack on.

Thanks. My primary concern for it is unnecessary lock-down with abuse of GTK for doing the low level things. The separation of GUI from library is sufficient to ensure portability. I am not sure how soon I will be able to learn it, but I want to play with QML. This means I probably will write the interface from scratch.

What i am still waiting for are xserver 1.11 stabily fixes - when you use kde 4.x and use disable composite for fullscreen apps your xserver can crash or you get completly distorted gfx until you disable composite effects. That problem is not seen on ubuntu 12.04 because they use a frankenstein 1.11 xserver with lots of patches from 1.12. But as debian wheezy/sid does not use those patches it is unstable there. When you don't use that function it is ok, but when you know that on laptops composite is usally disabled when running low on battery and enabled when you connect power again this is definitely bad.