Differences between revisions 18 and 19
Revision 18 as of 2015-10-10 07:08:16
Size: 5147
Comment: fix small typos and expand to previous edit
Revision 19 as of 2015-10-30 10:34:35
Size: 5148
Comment: Patchwork lives now on Github
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
git clone git://ozlabs.org/home/jk/git/patchwork git clone git://github.com/getpatchwork/patchwork

Patchwork

Source

git clone git://github.com/getpatchwork/patchwork

Mailinglist/Maintainer/URL

Dependencies

Software

Version

X-( Wheezy

(./) unstable/sid

Phyton2 Interpreter

>= 2.7

(./) 2.7.3-4

(./) 2.7.3-4

Phyton-Django

>= 1.5

X-( 1.4.5-1+deb7u4

(./) 1.6.1-2

phyton-psycopg2 Bindings

>= 2.0

(./) 2.4.5-1

(./) 2.4.5-1

Apache2 Webserver

>= 2.2

(./) 2.22-13

(./) 2.4.7-1

or

lighttpd Webserver

>= 1.4

(./) 1.4.31-4

(./) 1.4.33-1

mta-transport-agent

-

-

-

modpython libapache2-mod-python

>= 3.3

(./) 3.3.1-9

(./) 3.3.1-9

libjs-jquery

>= 1.3

(./) 1.7.2+dfsg-1

(./) 1.7.2+dfsg-1

MySQL

>= 5.5

(./) 5.5.33+dfsg-1

(./) 5.5.35+dfsg-1

or

Postgres

>= 9.0

(./) 9.1.11-1

(./) 9.1.11-1

Bash (some scripts)

>= 3.0

(./)

(./)

ITP Request

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703226

Staging Area

https://github.com/tijuca/patchwork

Helpers

Plattform Specific Defines

As I always search for that while debugging KFreeBSD or Hurd build issues ...

gcc -dM -E -x c++ /dev/null # for C++
gcc -dM -E -x c /dev/null   # for C

Setting up Hooks with git-buildpackage

Every time I new set up my PC I also can't remember that. :-)

Setting up some global Hooks.

sudo mkdir /etc/pbuilder/hooks
cd !$
sudo ln -s /usr/share/doc/pbuilder/examples/C11screen
sudo ln -s /usr/share/doc/pbuilder/examples/D80no-man-db-rebuild

And enable them in the pbuilderrc.

sudo echo "HOOKDIR=/etc/pbuilder/hooks" >> /etc/pbuilderrc

Using OnBoard LED's on Cubieboard2

As the Allwinner OnBoard LED's are specific to the DTS implementation there is no Debian package or way to configure them. To use the LED's for anything useful you have to write the wished usage of them into a trigger file. The location of these files are predefined by the Device Tree definition, for the CB2 the location for the blue LED is in /sys/class/leds/cubieboard2:blue:usr/trigger and the green LED is triggered via /sys/class/leds/cubieboard2:green:usr/trigger.

There are various things on a CB2 that can be shown by a LED activity (other Allwinner devices may contain more options!).

  • rc-feedback -> activity by a IR remote control

  • nand-disk -> R/W activity on the NAND flash

  • cpu0 -> CPU activity on core 1

  • cpu1 -> CPU activity on core 2

  • mmc0 -> R/W activity on the MMC 1 (SD-Card 1)

  • none -> show nothing

To let the kernel show any specific action on than just write the keyword into the trigger file as root. For example if you want to see on the blue LED the activity of CPU0 and on the green LED R/W actions on the MMC1 put the following lines into /etc/rc.local before the exit 0 line.

....
echo cpu0 > /sys/class/leds/cubieboard2\:blue\:usr/trigger
echo mmc0 > /sys/class/leds/cubieboard2\:green\:usr/trigger
....

To enable/disable the LED activity without loosing the predefined action you can switch on/of the LED by writing into the brightness trigger as root.

echo 0 > /sys/class/leds/cubieboard2\:blue\:usr/brightness # switch of LED
echo 0 > /sys/class/leds/cubieboard2\:green\:usr/brightness # switch of LED

echo 1 > /sys/class/leds/cubieboard2\:blue\:usr/brightness # switch on LED, default state after boot
echo 1 > /sys/class/leds/cubieboard2\:green\:usr/brightness # switch on LED, default state after boot


CategoryHomepage