One of my friends asked me to get working a Geovision GV-800(S) DVR card with zoneminder.
According to the google results several people succeed with this subject. For e.g.:
http://siripong-computer-tips.blogspot. ... linux.html

I have installed a n Ubuntu 12.04 server, and the necessary packages. This distribution shuiips with a relatively new kernel (3.5.0) which means that the necessary bttv modules were included fine. The device had shown up fine: I had 4 v4l2 devices with 4 channels per each (Composite0-4). I have added these channels as sources to the Zoneminder but I have not been able to get image from them. After several trials I have installed XFCE and XAWTV. I have not been able to get image with that tool too, and at the channel changes I got I/O errors and the software claimed about invalid framebuffer address on startup.

As final trying I have installed a Windows XP to the box, and installed the Geovision software. The device had shown up in the device manager fine, but there were a yellow exclamation points next to the devices with Device cannot started message. I have seen that card working in different computer.

As a last trial we have decided to try to upgrade the BIOS, and that solved the problem.

Really!
It must have the letters in lowercase.

I have started to develop to Android on Ubuntu.
At my first attempt when I have tried run my app on the device, the device shown up as ?????????? in the Android Studio Choose Device dialog.

The problem root cause is the access rights around the device descriptors.

The ADB daemon is started with the user's permissions, so I had created an udev rule to get access to the device:

mm@lapos:/opt/android-studio/bin$ cat /etc/udev/rules.d/51-android.rules
# Concorde tablet (18d1:0003)
ATTR{idVendor}=="18d1",ATTR{idProduct}=="0003" MODE="0666"


After upgrading my system to kUbuntu 13.04 Raring Ringtail the delays in my avr-gcc compiled binaries had been gone.
After reading the #include <util/delay.h> documentation my eyes cached the __DELAY_BACKWARD_COMPATIBLE__ macro. After defining it the delays are working.

Workaround:

#define F_CPU 16000000UL
#define __DELAY_BACKWARD_COMPATIBLE__
#include <util/delay.h>
#include <avr/io.h>

int main(void
{
DDRB = 0xFF;
while (1) {
PORTB = ~PORTB;
_delay_ms(1000);
}
}



In my last post I have been blogged about a Hisilicon HI3515 based DVR recorder.

The device itself functioning well, except the web interface which requires ActiveX control installation which is unavailable for my system.
After a quick look at the u-boot I have figured out that we can boot the kernel through tftp without hurting the Flash device.

The first interesting project is the ezbox:
https://code.google.com/p/ezbox/

The project itself is very strange.
It provides a buiold system for different embedded devices (AR7240 based routers, HI3515 based Multimedia Processing Platform, x86 based CNC controller)

It includes the liloutdistro for a Hisilicon HI3515 MPPP Multimedia Procesing Platform.

This also includes some binary kernel blobs for handling the HI3515 peripherials:
https://code.google.com/p/ezbox/source/browse/#svn%2Ftrunk%2Fpool%2Fpackages%2F3rd-party%2Fhisilicon

There are serveral sample programs including binary only libraries in the distro also, but without source.
https://code.google.com/p/ezbox/source/browse/#svn%2Ftrunk%2Fpool%2Fpackages%2F3rd-party%2Fhisilicon%2Fhisilicon-hi35xx-mpp%2Ffiles%2Fhi3515%2Fsample

So we are blessed with some binary only stuffs around for the 2.6.24 kernel only without any examples. Don't panic, use the google-fu.

First interestingstuff is this SDK from our chinese friends:
http://www.pudn.com/downloads111/source ... 62702.html

The second one is the smartmind project:
http://smartmind.googlecode.com/svn-his ... 1x_device/

And the last one:
http://code.google.com/p/fvp/source/bro ... k%2F%20fvp