ITOP-4412 Development Board peer-to video

Overall framework:

First, the sending side

1, the camera through the V4l2 interface to get YUV video format, can be played on the Win7 with Yuvplayer

2, using the 4412 Hardware Encoding module MFC provides the interface for hardware coding, get. 264 file, can be played on the Win7 with VLC.

3. Stream the. 264 file through the live555.

Second, the receiving end

1. Use the live555 to receive the. 264 file with the send-side connection.

2, with 4412 Hardware Encoding module MFC provides the interface for hardware decoding, to get the YUV format.

3. Use QT display video.

Note The main points:

To use the Samsung hardware encoding module, In the linux3.0 version provided in 4412, not only requires the Development Board system to load the MFC firmware after booting, in the use of MFC provided by the API also requires the MFC header files and source files to use the API, these files are not provided on the board of the Linux kernel files, and in the corresponding Android code of the kernel, you can use Li The find directive in Nux finds the correct source file in the selection. To use the MFC module in this project, there are two methods of the MFC module header files, the source files are placed in the project folder, in the project to be included. The other is to put the header file on the compiler's default lookup path, such as if it is local development, then the local compiler will go to the/usr/include directory lookup, and if it is cross-compiled, the cross-compiler will also need a root file system, the root filesystem/usr/ The Include directory goes down to find the header file, and the root file system directory of the cross-compilation toolchain created with BuildRoot is buildroot-2014.05/output/host/usr/arm-gainuo-linux-gnueabihf/ sysroot/, of course, can also add additional parameter I to GCC at compile time, specifying the header file lookup path. And if there is no source file because of commercial problems only provide the link library file, then the same as the same header file, you can place the link library file on the connector default lookup path, or add the L parameter to gcc to specify the library path. But the general board vendor provides the compiler is unable to find the root file system path (I do not know how to do, if the cross-compilation tool chain and the local toolchain shared the root file system path of the host, it is very likely because the version of the problem caused the header file incompatibility problem, more cumbersome).

Then how is the sender and receiver in the above steps in fact integrated, but they are not dependent on each other, parallel to the two process just.

There is how to send the end of the three steps and the receiving end of the three steps together, do not use the file as a relay instead of directly using memory data, do not read and write files, wasting time.

There is a problem of rate matching in each step of the string.

Finally, the C language should be rewritten as much as C + + interface

ITOP-4412 Development Board peer-to video