Welcome to Pandora's Box(Why)

Keep It Simple, Stupid!

Fork me on GitHub

Playing With Kinect for Windows Using OpenNI and SensorKinect Under Ubuntu 12.04 LTS

| Comments

Just a quick recap to make myself feel better after such a struggle for 1 day and hopes it does some help to those who tries to bring Kinect For Windows work under Linux, here Ubuntu especially.

Hardware Device

Kinect for Windows, not Kinect for XBox, so this post is kind of limited to some senarios. And I’m currently using Kinect For Windows Version 1, not the fasion V2.


| Comments


我想说什么呢?蜕变是一个过程,最直观的比喻便是“破茧成蝶”,经历了磨砺和长时间的积累,才终有之后绚丽的身姿;蜕变也是一种选择,最近老在想,通过观察,也察觉到,这个世界和社会真的是缤纷多彩(乱七八槽),每一个独立的个体都面临着各种各样的选择,把选择简化一下,用几对词来描述,可以有好几个方面的分析,积极 V.S. 消极,向上 V.S. 退后,大局 V.S. 个人,克服 V.S. 退缩,责任 V.S. 散漫,蜕变 V.S. 自缚!

Getting Started With ElasticSearch and Plugin Development

| Comments

Coming across to ElasticSearch when preparing for the programming chanllege held by WorksApplications in Tokyo Event, and falling love with her after then. Well, with no much new techonoligies involved, ElasticSearch is definitely a beautiful piece of software and a successful product. Claimed that with the core search engine powered by Lucene, providing RESTful interface and born as a distributed and scheme-free search oriented product, ElasticSearch has boosted the huge business of Github with billions of lines and Stackoverflow with billions of Q&A.

After digging some 101 tutorials around, I found it easy to set up ES(abbreviated for ElasticSearch and will use afterwards) and begin to play in 10 minutes. However, to understand what is going on underhood and what is the most tricy and interesting part, also to those who try to develop plugins to enpower ES, I will share something which would be useful for newbies. There are already tons of tutorials online, to same your time, please see elasticsearch-getting-started hosted on my github for a good cheat sheet.

KGTP中增加对GDB命令“set Trace-buffer-size”的支持 - Week 4

| Comments

CSDN开源夏令营 – 第四周工作总结

本周主要是在回顾“set trace-buffer-size”完成通信的基础上,对于指定参数size的处理,比如指定-1或者unlimited的时候,在KGTP端该如何做解析,以及该如何处理此时的buffer size。同时,根据“开题报告”的进度,中期检查的任务已经完成。对Trace Buffer的实现,做了初步的调研。

1. GDB和KGTP通信实现的回顾

利用GDBRSP,即GDB Remote Serial Protocol,GDB远程串行通信协议。简单来说,用于GDB远程调试发包,但是也支持File I/O和Console,而KGTP正是利用了GDBRSP对于File I/O的支持,完成GDB和KGTP的通信,在接受到GDB发送的Packet后,KGTP进行解析。而通信的介质则是通过debugfs或者其他kernel space和user space进行数据交换的接口进行的。 具体实现,可以参考上一篇博文[1]。

KGTP中增加对GDB命令“set Trace-buffer-size”的支持 - Week 3

| Comments

CSDN开源夏令营 – 第三周工作总结

这一周主要实现了“set trace-buffer-size”实现的数据通信部分,即完成了GDB和KGTP的数据交互部分,下面简单分析一下实现。在说代码实现之前,还是简单地回顾一下,如何摸清KGTP的脉络。

1. 如何跟踪KGTP


make D=1
sudo insmod gtp.ko
sudo gdb /usr/lib/debug/lib/modules/3.14.8-200.fc20.x86_64/vmlinux -ex 'target remote /sys/kernel/debug/gtp'