Month: November 2009

Analyzing X resource consumption

xrestop is useful tool to analyze resource (mem) used by application running over X Window System:

xrestop - Display: :0.0
          Monitoring 28 clients. XErrors: 1
          Pixmaps:    8813K total, Other:      94K total, All:    8908K total

res-base Wins  GCs Fnts Pxms Misc   Pxm mem  Other   Total   PID Identifier    
3200000   229  567    1  506  265     4376K     25K   4402K  3747 69% of 1 file - Downloads
0000000     1    0    2    0  143     1280K      5K   1285K   ?   
1400000     8   36    1    6   18     1281K      2K   1284K  3581 x-nautilus-desktop
2e00000     0    0    0    1    0     1280K      0B   1280K   ?   
1c00000    94   57    1   70   60      526K      5K    532K  3732 Inbox for Thunder
1200000    47   65    0   21   68       56K      4K     61K  3580 Panel
1000000    14   28    2   10  630       13B     17K     17K  3579 metacity
1800000    19   66    1    4   15        8K      3K     12K  3588 Twitux
2c00000     3   25    0    1  489        4B     12K     12K  3737 gnome-screensaver

Configuring git to send email to mailing list

This is process I did to get git sending email to mailing list:

First you need to install git-email in your distro (I am using Ubuntu):

$ sudo apt-get install git-email

Now configure your personal information:

$ git config --global user.name "Your (un)Real Name"
$ git config --global user.email user@gmail.com

Now we will configure git to use Gmail:

$ git config --global sendemail.smtpserver smtp.gmail.com
$ git config --global sendemail.smtpserverport 587
$ git config --global sendemail.smtpencryption tls
$ git config --global sendemail.smtpuser your_email@gmail.com
$ git config --global sendemail.smtppass your_password

Configure the mailing list you want send to (i.e.: Linux ARM):

$ git config sendemail.to linux-arm-kernel@lists.infradead.org

Source: http://morefedora.blogspot.com/2009/02/configuring-git-send-email-to-use-gmail.html

Adding a new ARM board on the Linux kernel

Today I started adding our board to mainline kernel. First thing you need to have is a machine ID. To get this machine ID you need to register and enter all information at this page:

http://www.arm.linux.org.uk/developer/machines/?action=new

After doing that you need to create a basic configuration file to your board, basically:
arch/arm/configs/YOURBOARD_defconfig
arch/arm/mach-YOURPROCESSOR/Kconfig
arch/arm/mach-YOURPROCESSOR/Makefile
arch/arm/mach-YOURPROCESSOR/YOURBOARD.c

How to find the I2C device address

Normally you will find the I2C slave address in datasheet (i.e.: PCA9557) like this:

0 0 1 1 A2 A1 A0 R/W

At first glance you will think the address is 0x30 (0011-0000) (case A2, A1 and A0 be 0). This it is wrong because the least significant bit needs to be eliminated.

Then it will become 0x18 (0001-1000).

Using i2cdetect I could to figure out my fault.