while (true) { ; }

Sentiment Analysis LOL

noreply@blogger.com (Anonymous) — Fri, 12 Feb 2016 15:42:00 +0000

Try Sentiment Analysis from Achemy

from alchemyapi import AlchemyAPI

alchemyapi = AlchemyAPI()

options = {}
options['knowledgeGraph'] = '1'
response = alchemyapi.faceTagging("image", "/home/hieult/Downloads/hieult3.jpg", options)

print response

C array

noreply@blogger.com (Anonymous) — Sun, 20 Dec 2015 05:34:00 +0000

True

#include

int main() {

char a[20];

a[3] = 'x';

4[a] = 'y';

printf("a[3] = %c\n", a[3]);

printf("a[4] = %c\n", a[4]);

return 0;

}

Rendering issue with Firefox 27.0.1

noreply@blogger.com (Anonymous) — Wed, 26 Feb 2014 07:36:00 +0000

If you have issue with rendering on Firefox 27.0.1, go to about:config and change "layers.acceleration.disabled" to true to turn off acceleration.

NFS server on Mac OS

noreply@blogger.com (Anonymous) — Sat, 14 Dec 2013 18:37:00 +0000

Edit /etc/exports: sudo vi /etc/exports Add a line like the following (presuming your home network is using the 192.168 private network. You could also use 172.17 or 10.):

/Users -network 192.168.0.0 -mask 255.255.0.0

Enable nfsd: sudo nfsd enable

Test your work: showmount -e

JIRA listener script to add assignee into Summary field

noreply@blogger.com (Anonymous) — Fri, 08 Nov 2013 15:56:00 +0000

A little script to help the life better. This script is a Listener which update the summary of JIRA issue to add assignee info. I'm using JIRA Agile and its board doesn't show the assignee name so I create this script to display it in the summary field.

Code as following, save it with .groovy extension and then put it into atlassian-jira/WEB-INF/classes/com/xxx/listeners and then configure JIRA to use com.xxx.listeners.UpdateAssigneeSummaryListener as class

import com.atlassian.jira.event.issue.AbstractIssueEventListener;
import com.atlassian.jira.event.issue.IssueEvent;
import org.apache.log4j.Category;
import com.atlassian.jira.event.type.EventType;
import com.atlassian.jira.issue.Issue;
import com.atlassian.jira.issue.MutableIssue;
import com.atlassian.jira.issue.IssueManager;
import com.atlassian.jira.user.util.UserManager;
import com.atlassian.jira.event.type.EventDispatchOption;
import com.atlassian.jira.component.ComponentAccessor;

class UpdateAssigneeSummaryListener extends AbstractIssueEventListener {
    Category log = Category.getInstance(UpdateAssigneeSummaryListener.class)

    @Override
    void workflowEvent(IssueEvent event) {
        Issue issue = event.getIssue();
        Long eventTypeId = event.getEventTypeId();
        if ((eventTypeId.equals(EventType.ISSUE_ASSIGNED_ID) || eventTypeId.equals(EventType.ISSUE_CREATED_ID)) && issue.getResolutionDate() == null)
        {
            def test = (issue.getSummary() =~ /^\[([A-Za-z]+)\]/)
            def summary
            def assignee = issue.getAssigneeId()
            if (test.getCount() != 0)
            {
                // Replace the user in bracket.
                summary = (issue.getSummary() =~ /\[([A-Za-z]+)\]/).replaceFirst("[${assignee}]")
            }
            else
            {
                summary = "[${assignee}] ${issue.getSummary()}"
            }

            MutableIssue mutableIssue = (MutableIssue)issue;
            mutableIssue.setSummary(summary);
            IssueManager issueManager = ComponentAccessor.getIssueManager();
            UserManager userManager = ComponentAccessor.getUserManager();
            issueManager.updateIssue(event.getUser(), mutableIssue, EventDispatchOption.DO_NOT_DISPATCH, false)
        }
    }
}

Should we move to KVM?

noreply@blogger.com (Anonymous) — Tue, 22 Oct 2013 02:12:00 +0000

The virtualization wars between VMWare and KVM is not over. KVM is recently adapted by many companies such as IBM,.

Should we migrate to KVM? It's free/low cost than VMWare but show better results than VMWare...Hmmm....

http://openvirtualizationalliance.org/blog
ftp://public.dhe.ibm.com/linux/pdfs/Clabby_Analytics_-_VMware_v_KVM.pdf
http://www.scalecomputing.com/files/documentation/whitepaper-vmware-vs-scale-computing.pdf

Upnp URL

noreply@blogger.com (Anonymous) — Tue, 03 Sep 2013 12:00:00 +0000

http://miniupnp.free.fr/
http://linux-igd.sourceforge.net/
http://www.upnp-hacks.org/faq.html

NRDP

noreply@blogger.com (Anonymous) — Tue, 27 Aug 2013 07:08:00 +0000

Looks good to me.
http://videotechnology.blogspot.com/2011/08/netflix-ready-device-platform-nrdp.html

How to fake the LSB release

noreply@blogger.com (Anonymous) — Mon, 19 Aug 2013 13:26:00 +0000

On Fedora, edit the /etc/redhat-release as following

[hieult@hieuletrung ti-sdk-am335x-evm-06.00.00.00]$ cat /etc/redhat-release
Ubuntu 10.04 release 10.04 (lucid)

Then install the lsb_release package

On Ubuntu, edit the /etc/lsb-release as following
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION="Ubuntu lucid (development branch)"

Howto: Porting the GNU Debugger

noreply@blogger.com (Anonymous) — Mon, 19 Aug 2013 04:07:00 +0000

http://www.embecosm.com/appnotes/ean3/html/index.html

Add icon to new GNOME desktop toolbar (FC16)

noreply@blogger.com (Anonymous) — Sun, 18 Aug 2013 12:52:00 +0000

Alt+Right Click to add icon to Gnome toolbar in new Gnome desktop version

Debug corrupt stack

noreply@blogger.com (Anonymous) — Sun, 18 Aug 2013 11:29:00 +0000

From http://fragglet.livejournal.com/19646.html

How to coerce gdb into giving a backtrace

When debugging with gdb, I sometimes encounter a problem in getting it to recognise a stack trace. Sometimes it only gives a few function calls, or none at all. Here's an example:

(gdb) bt
#0  0xb7886424 in __kernel_vsyscall ()
#1  0xb7559163 in ?? () from /lib/i686/cmov/libc.so.6
#2  0xb74f1387 in ?? () from /lib/i686/cmov/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

This obviously isn't a very useful backtrace. At this point it can be useful to have a look at the registers and the contents of the stack.

(gdb) info registers
eax            0xfffffe00 -512
ecx            0x80 128
edx            0x2 2
ebx            0xb75c33a0 -1218694240
esp            0xbfe55018 0xbfe55018    <= stack pointer on x86 
ebp            0xbfe55048 0xbfe55048
esi            0x0 0
edi            0x0 0
eip            0xb7886424 0xb7886424 <__kernel_vsyscall>
eflags         0x202 [ IF ]
cs             0x73 115
ss             0x7b 123
ds             0x7b 123
es             0x7b 123
fs             0x0 0
gs             0x33 51
(gdb) x/64x $sp
0xbfe55018: 0xbfe55048 0x00000002 0x00000080 0xb7559163
0xbfe55028: 0xb75c33a0 0xb75c1ff4 0x09ec0470 0xb74f1387
0xbfe55038: 0xb77c4afd 0xb782199c 0xb782199c 0x09ec0478
0xbfe55048: 0xbfe55078 0xb77c4bf4 0x09ec0478 0xb782199c
0xbfe55058: 0x0000ffff 0xb75c3438 0xbfe55098 0xb789a240
0xbfe55068: 0x00000000 0xb782199c 0x0000ffff 0xb75c3438
0xbfe55078: 0xbfe55098 0xb7818736 0x09ec0478 0x00000000
0xbfe55088: 0xb77c50cd 0xb782199c 0xb7818709 0xb782199c
0xbfe55098: 0xbfe550b8 0xb77c54ad 0x00000000 0x00000000
0xbfe550a8: 0x0000000b 0xb75c3438 0xb77c5449 0xb782199c
0xbfe550b8: 0xbfe550c8 0xb77bb7dd 0xb782199c 0x0000000b
0xbfe550c8: 0xbfe550e8 0xb77bb84e 0x0000ffff 0xb789a240
0xbfe550d8: 0x00000000 0xb77bb830 0xb77bb839 0xb782199c
0xbfe550e8: 0xbfe55108 0xb77bc08f 0x0000000b 0x00000000
0xbfe550f8: 0x00000000 0x00000010 0xb75c1ff4 0x3efafafb
0xbfe55108: 0xbfe556c8 0xb7886400 0x0000000b 0x00000033

The values in bold are the frame pointers, forming a linked list back up the stack. If you compiled with -fomit-frame-pointer things will be harder to figure out. In this case it certainly doesn't look like the stack is corrupt. Perhaps gdb is just confused.

Pick a location slightly further up the stack and set the $sp variable, and suddenly backtrace works!

(gdb) set $sp=0xbfe55048
(gdb) bt
#0  0xb7886424 in __kernel_vsyscall ()
#1  0xb782199c in ?? () from /usr/lib/libSDL-1.2.so.0
#2  0xb7818736 in ?? () from /usr/lib/libSDL-1.2.so.0
#3  0xb77c54ad in ?? () from /usr/lib/libSDL-1.2.so.0
#4  0xb77bb7dd in SDL_QuitSubSystem () from /usr/lib/libSDL-1.2.so.0
#5  0xb77bb84e in SDL_Quit () from /usr/lib/libSDL-1.2.so.0
#6  0xb77bc08f in ?? () from /usr/lib/libSDL-1.2.so.0
#7  
#8  0xb74ede80 in ?? () from /lib/i686/cmov/libc.so.6
#9  0xb74efc8c in malloc () from /lib/i686/cmov/libc.so.6
#10 0xb7764eec in ?? () from /usr/lib/libSDL_mixer-1.2.so.0
#11 0xb7765b98 in Mix_SetPanning () from /usr/lib/libSDL_mixer-1.2.so.0
#12 0x080828b1 in I_SDL_StartSound (id=-1218694088, channel=-1218699276, 
    vol=120, sep=38) at i_sdlsound.c:671
#13 0x08073e9b in S_StartSound (origin_p=0xb624f990, sfx_id=22)
    at s_sound.c:656
#14 0x08061459 in T_MoveFloor (floor=0xb63271b8) at p_floor.c:220
#15 0x0806d0ea in P_RunThinkers () at p_tick.c:119
#16 0x0806d161 in P_Ticker () at p_tick.c:153
#17 0x08052fb6 in G_Ticker () at g_game.c:1151
#18 0x0804dbf4 in D_DoomLoop () at d_main.c:437
#19 0x0804ecc0 in D_DoomMain () at d_main.c:1506
#20 0x08054d1c in main (argc=5, argv=0xbfe55d04) at i_main.c:152

And http://intquestion.wordpress.com/2008/09/14/how-to-debug-a-corrupted-stack/

Is the art to set the sp point to correct address and then we can get a backtrace?

We need to understand the stack pointer :-)

Spin Lock vs. Read-Write Lock

noreply@blogger.com (Anonymous) — Tue, 02 Jul 2013 10:39:00 +0000

http://locklessinc.com/articles/locks/

Make TMP36 work on Beaglebone Black

noreply@blogger.com (Anonymous) — Sun, 16 Jun 2013 01:42:00 +0000

Here is how to use the Adadfruit temperature sensor TMP36 (https://www.sparkfun.com/products/10988) on Beaglebone black for reading temperature
1) Wiring the TMP36 to BBB
Refer the following picture for TMP36 pin output

Then we need to
- Connect 1st pin to port 32 of P9 expansion slot (3.3V output)
- Connect 3rd pin to port 1 of P9 expansion slot
- Connect 2nd pin to port 39 (AIN0) of the P9 expansion slot
You can connect the 2nd pin to AIN another port, refer following image for how it is designed

2) Enable AIN on the BBB
We need to enable the AIN driver, by doing following command on the BBB console

# echo cape-bone-iio > /sys/devices/bone_capemgr.*/slots

The above might need a kernel module BONE_CAPE or bone_iio_helper

3) Read the input
Now we can read the AIN input by cat it, for example

root@arm:~# cat /sys/devices/ocp.2/helper.14/AIN0
287

But the AIN0 give me some weird value, I need to use the voltage0_raw under "/sys/bus/iio/devices/iio\:device0/in_voltage0_raw";

root@arm:~# cat /sys/bus/iio/devices/iio\:device0/in_voltage0_raw
1767

with a C application

#include <stdlib.h>
#include <stdio.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <unistd.h>

//const char AIN_DEV[] = "/sys/devices/ocp.2/helper.14/AIN0";
const char AIN_DEV[] = "/sys/bus/iio/devices/iio\:device0/in_voltage0_raw";

double CtoF(double c)
{
  return (c * 9.0 / 5.0) + 32.0;
}

double temperature(char *string)
{
  int value = atoi(string);
  double millivolts = (value / 4096.0) * 1800;
  double temperature = (millivolts - 500.0) / 10.0;
  return temperature;
}

int main()
{
  int fd = open(AIN_DEV, O_RDONLY);

  while (1)
  {
    char buffer[1024];
    int ret = read(fd, buffer, sizeof(buffer));
    if (ret != -1)
    {
      buffer[ret] = '\0';
      double celsius = temperature(buffer);
      double fahrenheit = CtoF(celsius);
      printf("digital value: %s  celsius: %f  fahrenheit: %f\n", buffer, celsius, fahrenheit);
      lseek(fd, 0, 0);
    }
    sleep(1);
  }

  close(fd);
  return 0;
}

The convert formula is as following

Step	Description	Example
1	Read the digital value from the ADC interface.	`#cat` /sys/devices/ocp.2/helper.14/AIN0 `1670`
2	Convert the digital value to millivolts. (value / 4096) * 1800mV	(1670 / 4096) * 1800mV = 733.8867mV
3	Convert the millivolts to Celsius temperature. (millivolts - 500mV) / 10	(733.8867mV – 500mv) / 10 = 23.38867°C
4	Convert Celsius to Fahrenheit. (Celsius * 9.0 / 5.0) + 32.0	(23.38867°C * 9 / 5) + 32 = 74.09961°F

And here is my wiring

Ref:

TMP36 datasheet: http://dlnmh9ip6v2uc.cloudfront.net/datasheets/Sensors/Temp/TMP35_36_37.pdf

Reading ADC: http://hipstercircuits.com/reading-analog-adc-values-on-beaglebone-black/

Build kernel for BBB: http://www.eewiki.net/display/linuxonarm/BeagleBone+Black

AM335x ADC driver guide: http://processors.wiki.ti.com/index.php/AM335x_ADC_Driver%27s_Guide

Beaglebone P8, P9 pin output (can be used for BBB): http://elinux.org/BeagleBone

Beaglebone Black

noreply@blogger.com (Anonymous) — Sun, 02 Jun 2013 18:28:00 +0000

What I bought
- Beaglebone Black
- Breadboard
- Wire
- TMP36
- MQ-3
- and a zigbee wireless sensor...

Setup poky development environment

noreply@blogger.com (Anonymous) — Sat, 22 Sep 2012 17:09:00 +0000

The following is to setup development environment for working on poky project.
1) Setup a working directory
mkdir data/poky -p

2) Check out the poky source code
cd data/poky
git init
git remote add yocto git://git.yoctoproject.org/poky.git
git remote update
git branch -b denzil yocto/denzil

3) Check out meta-intel for BSP developmen
mkdir data/poky/meta-intel -p
cd data/poky/meta-intel
git init
git remote add meta-intel git://git.yoctoproject.org/meta-intel.git
git remote update
git branch -b denzil meta-intel/denzil

4) Checkout poky-extras for kernel development
mkdir data/poky/poky-extras -p
cd data/poky/poky-extras
git init
git remote add poky-extras git://git.yoctoproject.org/poky-extras
git remote update
git checkout -b denzil poky-extras/denzil

5) Clone the kernel source code
cd data

git clone --bare git://git.yoctoproject.org/linux-yocto-3.2 linux-yocto-3.2.git

6) Then clone a local copy to make change on that kernel

git clone linux-yocto-3.2.git my-linux-yocto-3.2-work

6) Now we can start a yocto build and development. The layout should be
[hieult@hieuletrung data]$ tree -L 2
.
├── linux-yocto-3.2.git
│   ├── branches
│   ├── config
│   ├── description
│   ├── HEAD
│   ├── hooks
│   ├── info
│   ├── objects
│   ├── packed-refs
│   └── refs
├── my-linux-yocto-3.2-work
│   ├── arch
│   ├── block
│   ├── COPYING
│   ├── CREDITS
│   ├── crypto
│   ├── Documentation
│   ├── drivers
│   ├── firmware
│   ├── fs
│   ├── include
│   ├── init
│   ├── ipc
│   ├── Kbuild
│   ├── Kconfig
│   ├── kernel
│   ├── lib
│   ├── MAINTAINERS
│   ├── Makefile
│   ├── mm
│   ├── net
│   ├── README
│   ├── REPORTING-BUGS
│   ├── samples
│   ├── scripts
│   ├── security
│   ├── sound
│   ├── tools
│   ├── usr
│   └── virt
└── poky
    ├── bitbake
    ├── documentation
    ├── LICENSE
    ├── meta
    ├── meta-demoapps
    ├── meta-hob
    ├── meta-intel
    ├── meta-skeleton
    ├── meta-yocto
    ├── oe-init-build-env
    ├── poky-extras
    ├── README
    ├── README.hardware
    └── scripts

URL:

Get Firefox

noreply@blogger.com (Anonymous) — Sun, 16 Sep 2012 07:10:00 +0000

Instead of go to www.getfirefox.com, we can go to http://releases.mozilla.org/pub/mozilla.org/firefox/ and grab a correct version.

Ubuntu 12.04 NVIDIA 6 screens issue

noreply@blogger.com (Anonymous) — Sat, 04 Aug 2012 05:28:00 +0000

If you've installed Ubuntu 12.04 and has 6 screens issue on nvidia geforce card, follow this guideline http://ubuntuforums.org/showthread.php?t=1967161&page=2 to fix the issue

It works for me on Geforce G210M

What motivate me?

noreply@blogger.com (Anonymous) — Mon, 30 Jan 2012 11:07:00 +0000

Working in GCS for many years, I found some facts about GCSers at the moment. When you first join GCS

You don't know what should you do, still being with the university mindset or previous company.
Be assigned into a project and keep working daily.
You found that when you need to submit leave form go to QMS and only for leave form.
You don't know the requirement for your current role (i.e. Engineer). - If you know that it's still very ambiguous because it's not example specific and there's no mapping into your daily work.
CP4 is something really interested but HOW can you do that?
What motivate you to do good job? Salary?
Yes, everything is very confuse and you'll need a good leader to guide you :)

I think to solve this:

When a person first join GCS, we should have someone describe on their current role, the requirement for that role, who is his/her mentor, who will he/she report to, list of tools/resources that available to his/her job (Wiki?).
If he/she joins a project, the project should have a Getting Start Wiki so that everyone can know where to go and what should they do in project.

There's an issue with current EMB hiring model, that the new hired resource might not join a project but for a resource pool. For this we might think about R&D project, I think we should create an "Open Source department" so that,

we improve open-source project which is mostly used by us i.e. Android, Beagleboard, or some other open-source libraries...
the employee join this model can gain knowledge on specific library which can help him in his future work

For senior engineer, with current development environment inside GCS, we currently don't have a correct model/workflow yet so

if we developed on, we should collect all senior and teach them that new workflow so that they can follow up like orientation for new employee.
they've long lived so mindset might different from new one, motivation might be missing already :)
ask them HOW!
re-evaluate their skill so that we can match them with new model.

Is it true for you and your current work?

OLPC on QEMU

noreply@blogger.com (Anonymous) — Wed, 25 Jan 2012 11:41:00 +0000

Follow this guideline http://wiki.sugarlabs.org/go/QEMU

If it's not clear, here is it.

Install qemu: yum install qemu
Create a disk image: qemu-image create olpc.img
Download School Server (XS) iso: wget http://xs-dev.laptop.org/xs/OLPC_XS_LATEST.iso
Start qemu and install XS: qemu -hda olpc.img -cdrom OLPC_XS_LATEST.iso -m 512

Linaro development on Fedora

noreply@blogger.com (Anonymous) — Wed, 25 Jan 2012 09:58:00 +0000

Linaro currently mostly works on Ubuntu as its guideline. Here is some tips, not so much, for working on Fedora with Linaro

Follow this https://wiki.linaro.org/Platform/Android/Toolchain if you're working with Android

or a build from scratch https://wiki.linaro.org/WorkingGroups/ToolChain/Using/GCCNative

Or this https://wiki.linaro.org/WorkingGroups/ToolChain/Using/CrosstoolNg if you want a stand-alone toolchain that can be worked on other platform

Then you can use the toolchain to build the kernel, rootfs i.e. http://www.linaro.org/linaro-blog/2011/09/15/building-a-linaro-android-build-from-source/

Why don't we integrate it into Yocto or buildroot? Hmmm...

BTW, the linaro-image-tools didn't work with Python 2.5 ;-(

NULL vs. 0

noreply@blogger.com (Anonymous) — Mon, 23 Jan 2012 19:06:00 +0000

 char * p = 0; /* IS WRONG! DAMMIT! */
 int i = NULL; /* THIS IS WRONG TOO! */

and anybody who writes code like the above either needs to get out of the kernel, or needs to get transported to the 21st century.

NULL is a pointer, while 0 can never be.

LOL :-)

Tet 2012

noreply@blogger.com (Anonymous) — Wed, 18 Jan 2012 14:09:00 +0000

Tet holiday is coming here, what should I do?

Read a book
Find a project to contribute: OLPC, clutter, openkinect, glib, gtk, ...
Continue with beagleboard
Continue with CUDA
Doing work for GCS
xxx

Hmmmmmmmmm...let see

Valgrind XYZ

noreply@blogger.com (Anonymous) — Tue, 10 Jan 2012 06:48:00 +0000

To understand how things work, this is how valgrind starts up:

  - The valgrind launcher (/usr/bin/valgrind) is run.
  - The launcher decides which tool you want execs it to
    replace the launcher.
  - The tool binary loads at a high address then acts as
    an ELF loader and loads the target program into the
    same process, using LD_PRELOAD to try and inject a
    small amount of code into it.

Run "ld --verbose" to see the default linker script, and note the line
   . = 0x08048000 + SIZEOF_HEADERS;
This is the problem.  ld estimates SIZEOF_HEADERS, and sometimes guesses
low by 1 Elf32_Phdr (or by 2 in extremely rare cases).  A workaround is
to capture the default linker script "ld --verbose >script.lds", delete
the header and trailer lines [delimited by '====='], change the initial
address to ". = 0x08048000 + 52 + 8*32;" where 52 is sizeof(Elf32_Ehdr)
and 32 is sizeof(Elf32_Phdr), then use the resulting script to replace 
the default: "ld -T script.lds ..."

http://plash.beasts.org/wiki/Story16Notes

Here are some things to do:
o Study the info pages that come with ld.
  See ld.info, Node: Builtin Functions, SIZEOF_HEADERS. 
o Compare the elf linker scripts (probably in
  /usr/i486-suse-linux/lib/ldscripts/ on your system) against standard
  ones.  eg. from ftp.varesearch.com/pub/support/hjl/binutils/  If they
  are different, try the standard scripts.
o Delete SIZEOF_HEADERS from your linker script, and replace with a fixed
  number.  Try 1024.
o If all this fails, post a bug report to binutils@sourceware.cygnus.com

Strength of a workplace

noreply@blogger.com (Anonymous) — Mon, 02 Jan 2012 12:26:00 +0000

Is it true when the "First, Break all the rules" said that, a strength of a workplace can be inside 12 following questions

Do I know what is expected of me at work?
Do I have the materials and equipment I need to do my work right?
At work, do I have opportunity to do what I do best every day?
In the last seven days, have I received recognition or praise for doing good work?
Does my supervisor, or someone at work, seem to care about me as a person?
Is there someone at work who encourages my development?
At work, do my opinions seem to count?
Does the mission/purpose of my company make me feel my job is important?
Are my co-workers committed to doing quality work?
Do I have a best friend at work?
In the last six months, has someone at work talked to me about my progress?
This last year, have I had opportunities at work to learn and grow?

Hmm, nothing about benefits or salary...is it true for my current company, GCS? Maybe there's something to think about...