I've been spending a lot of time profiling DRI drivers for Gallium 3D. I've tried gprof, valgrind, and finally oprofile. Oprofile seems the best in my opinion for this purpose. More details on the DRI Wiki.
I also wrote a script to generate a time-colored call graph from oprofile output, using graphviz. See an output example of profiling glxgears on Gallium 3D:
The hotter the colour of a function is, more time is spent on that function and its children.
I've never learned to use Emacs. I love vim, but it doesn't scale for me when editing more than three files at the same time or projects with more than one directory. After two years using Eclipse for Python and Windows C++ development, I've been using almost exclusively Eclipse for X.Org/Mesa/DRI development during the last three months.
I think Eclipse is really a pleasant development environment:
Also, the CDT (the C/C++ Development Plugin for Eclipse) folks are now actively working to get Eclipse not only to debug remote applications, but also build remotely, which will greatly simplify testing on multiple software/hardware configurations.
The thing I miss the most is better git integration. Of course, it is advisable to have a big screen and lots of memory.
For those interested, I've wrote some instructions to get you started on the X.Org Wiki.
In Debian/Ubuntu, when logging from gdm your ~/.bash_profile or even ~/.bash_rc are loaded, preventing you to set environment variables for all your session. The reason is that gdm starts /usr/bin/x-session-manager directly.
There are many ways to get ~/.bash_profile loaded. Many of which are wrong.
I found that a very simple way to loading ~/.bash_profile when starting X is to write the following ~/.xsession script:
#!/bin/bash --login exec /usr/bin/x-session-manager
One can easily add new actions in Nautilus context menu by adding shell scripts to ~/.gnome2/nautilus-scripts . Below is a script for mass file renaming, using Perl's rename utility and zenity. Add it to ~/.gnome2/nautilus-scripts/Mass Rename.
#!/bin/sh
# Nautilus script for mass file renaming
set -e
TITLE=`basename "$0"`
# Path to perl's rename
RENAME=/usr/bin/rename
rename_all() {
IFS=$'\n'
for FILE in $NAUTILUS_SCRIPT_SELECTED_FILE_PATHS
do
cd "`dirname "$FILE"`"
"$RENAME" "$@" "$EXPR" -- "`basename "$FILE"`"
done
}
EXPR="s///"
while true
do
EXPR=`zenity --title "$TITLE - expression" --entry --text "Specify the Perl expression for modifying the filenames." --entry-text "$EXPR"` || exit
rename_all -n | sed -e 's/^\(.*\) renamed as \(.*\)$/\2\n\1/' | zenity --list --width 800 --height 600 --title "$TITLE - Preview" --text "" --column "New name" --column "Old name" && break
done
rename_all
Here are some screenshots:
The latest version of this script can be found here.
A lot of hard work from Martin Michlmayr which provided quite an interesting reading.
XML + a XSLT toolchain is an excellent way to maintain your Curriculum Vitae, supporting several languages and several formats with minimum effort. I've been using the XML Résumé Library for my CV for a while, but the lack of recent updates and a slight unsatisfaction with the look of the PDF output made me want to take a peek on what else is out there.
Didn't find much though: the overall feeling I get is that, though not perfect, the XML Résumé Library seems to be the safest bet out there.
The sole exception worth mention is the work done by David Sora for a subject of his masters degree. He designed a XSD schema together with HTML and PDF XSLT stylesheets for CVs based upon the Europass Curriculum Vitae layout. His report is written in portuguese, but an example CV and XSLT are available for english too (in the parent directory of the report). This might not be picked up a community (such as the one behind XML Résumé Library), but the schema is complete and the output looks nice. Also the layout of the Europass CV is comprehensive and professional — as you'd expect from an initiative backed by the European Union. So definitelyinetly something to look upon whenever I need to tweak or drop the XML Résumé Library.
Technorati Tags: xml, xslt, cvudev has replaced hotplug in the Debian distribution. However not all hotplug's functionality is available (or at least simple to use): with hotplug one could easily write scripts which processed add and remove events, while with udev that has proved to be quite an ordeal.
The device I wanted to detect was the SpeedTouch USB ADSL modem. The first problem I ran into was that "sysfs values are not readable at remove, because the device directory is already gone". The solution is either using an environment variable with the DEVPATH (which didn't work for me), or matching the device with the reduced information available (my only remaining option). Thankfully there was this PRODUCT environment variable which could precisely match the device. This is how the udev rules look:
# /etc/udev/rules.d/z80_speedtch.rules
BUS=="usb", SUBSYSTEM=="usb", SYSFS{idVendor}=="06b9", SYSFS{idProduct}=="4061", ACTION=="add", RUN+="/bin/sh -c '/usr/local/sbin/speedtouch &'"
BUS=="usb", SUBSYSTEM=="usb", ENV{PRODUCT}=="6b9/4061/0", ACTION=="remove", RUN+="/bin/sh -c '/usr/local/sbin/speedtouch &'"
The actions I wanted to take was to start/stop the ppp interface. The second problem is that the above rules matched many add/remove events (driver, and several USB subdevices). To ensure only one add/remove action is taken, a solution is to use the SEQNUM environment variable, whose value is a always increasing integer, and keep track of its value when the device first got inserted. This is how /usr/local/sbin/speedtouch looks like:
#!/bin/sh
RUN=/var/run/speedtouch.seqnum
TIMEOUT=60
# test whether the device is currently added or not
device_added () {
test -e $RUN && test `cat $RUN` -lt $SEQNUM
}
# wait for the "ADSL line is up" kernel message to appear
wait_for_adsl_up () {
local TIME
dmesg -c > /dev/null
TIME=0
while ! dmesg | grep -q 'ADSL line is up'
do
sleep 1
TIME=$(($TIME+1))
test $TIME -ge $TIMEOUT && return 1
done
}
case $ACTION in
add)
# ignore repeated "add" actions
device_added && exit
echo $SEQNUM > $RUN
wait_for_adsl_up
ifup ppp0
;;
remove)
# ignore repeated "remove" actions
device_added || exit
rm -f $RUN
ifdown ppp0
;;
esac
The script has a bit more magic for waiting for the ADSL line is up, which was taken from the SpeedTouch Linux kernel driver homepage.
Technorati Tags: linux, debian, shell scripts