embedded-linux

Zero shutter lag in Android camera

由 ▼魔方 西西 提交于 2019-12-07 03:38:55
问题 In normal shutter lag,sensor driver give the caputured image buffer to v4l2 layer and here jpeg(hardware) header adds some extra data(exif info and thumbnail) and this layer give the image buffer to preview heap(In HAL layer) for further processing. but what is the process of taking picture in case of zero shutter lag.Is this same as normal shutter lag? How to reduce the time between take picture call and image processing. if not than explain . 回答1: To achieve zero shutter lag, the camera

Multiple files created by arecord

由 对着背影说爱祢 提交于 2019-12-07 02:32:46
问题 I've made custom distribution using buildroot, with hard-flow for ARMv7 processor. Everything is working except.... # arecord -D hw:0,0 -fdat -d 5 test.wav This makes multiple files. Thousands of them. -rw-r--r-- 1 root root 958508 Jan 1 00:19 test-01.wav -rw-r--r-- 1 root root 44 Jan 1 00:19 test-02.wav -rw-r--r-- 1 root root 44 Jan 1 00:19 test-03.wav -rw-r--r-- 1 root root 44 Jan 1 00:19 test-04.wav -rw-r--r-- 1 root root 44 Jan 1 00:19 test-05.wav -rw-r--r-- 1 root root 44 Jan 1 00:19

Using Wt with Qt

由 心不动则不痛 提交于 2019-12-07 01:38:37
问题 I'm working on a project to develop a web application for controlling some machinery and visualising sensor data. It is deployed on a single board computer running a custom linux distro. We have a large existing code base from a previous version of the project that is based on a standalone Qt app. With the new software we are moving towards a web based interface using Wt. At the moment we are trying to re-use the Qt code which interfaces with some system services, while hosting and

Why are i2c_smbus function not available? (I2C – Embedded Linux)

由 廉价感情. 提交于 2019-12-06 22:41:37
问题 There are many references to using i2c_smbus_ functions when developing embedded Linux software to communicate on the I2C bus. When i2c_smbus functions such as i2c_smbus_read_word_data are referenced in software project for ARM8 processor errors such as ‘ i2c_smbus_read_word_data’ was not declared in this scope are generated at compile. Investigation of the following header files indicate the absence of most i2c_smbus function definition. /usr/arm-linux-gnueabi/include/linux/i2c.h /usr/arm

YOCTO : can't insert linux module to the kernel : versions are different

由 。_饼干妹妹 提交于 2019-12-06 16:18:16
I'm using YOCTO PROJECT to build a linux os for my embedded board. I have a module named uleds which i want insert to my kernel so i taped this insmod command: insmod /lib/modules/4.14.73-linux4sam-6.0-dirty/kernel/drivers/leds/uleds.ko But an errors comes out : uleds: version magic '4.14.88-01445-g234c56a01768-dirty mod_unload ARMv7 p2v8 ' should be '4.14.73-linux4sam-6.0-dirty mod_unload ARMv7 p2v8 ' uleds: version magic '4.14.88-01445-g234c56a01768-dirty mod_unload ARMv7 p2v8 ' should be '4.14.73-linux4sam-6.0-dirty mod_unload ARMv7 p2v8 ' insmod: can't insert '/lib/modules/4.14.73

i2c probe not being called…not sure where to call i2c_register_board_info

由 半腔热情 提交于 2019-12-06 14:05:28
问题 I have an Intel systems. I am trying to load at24.ko and i2c-mux-pca9541.ko. both modules have probe functions which are not being called. according to the Documentation, i need to call i2c_registetr_board_info in the arch_init. but I am not sure where to do that for the Intel system (ie which files). I do not see any examples anywhere on the internet. can someone provide a pointer to the file that i add this call. if this is not the right approach, please let me know. thank you in advance.

Compile parameters for MIPS based codesourcery toolchain?

由 怎甘沉沦 提交于 2019-12-06 13:14:47
I installed codesourcery cross compile toolchain for mips32 architecture on my WIN 7 machince. I want to first compile a simple 'factorial' binary for my router which is based on MIPS32. From little search on the internet, I found it is based on MIPS32 big-endian. #cat /proc/cpuinfo system type : 96338W2 processor : 0 cpu model : BCM6338 V1.0 BogoMIPS : 239.20 wait instruction : no microsecond timers : yes tlb_entries : 32 extra interrupt vector : yes hardware watchpoint : no unaligned access : 1269919 VCED exceptions : not available VCEI exceptions : not available # cat /proc/version Linux

How to write own package for recipe in arago project build

由 半世苍凉 提交于 2019-12-06 12:45:51
How can i write own package for recipe in arago project build? I know little bit that it can be bitbake files. But how can i write, no idea. I searched on internet, but failed to find any good source to start. can someone provide me link or example to start? Regards Linux Learner. Create own recipe with Yocto using Bitbake: Use Yocto Project for Embedded systems. It's documentation and support is awesome. You can get started Yocto Project . Build your own recipe(for the first time build takes quiet good amount of time) Getting Yocto Project: Follow step-by-step procedure given Gumstix

Intel chipset - GPIO programming

由 别说谁变了你拦得住时间么 提交于 2019-12-06 11:35:43
问题 From the spec, I knew the following information: JGPIO1 PIN# :10 SoC GPIO # : 71 USE select: IO 0x532[7] ( 0 = native function, 1 = GPIO ) IO select: IO 0x536[7] (0 = output, 1 = input ) Level: IO 0x540[7] ( 0 = low, 1= high ) In this case, I want to program GPIO pin # 10. Is there any example or sample code I can refer to ? I can do this thorugh RW-everything [1]. However, this is in Windows. I want to do this in C and in linux environment. Please advise. ====================================

back trace for ulibc in arm

由 强颜欢笑 提交于 2019-12-06 09:13:00
I wanted to know if any porting is available for back trace implementation for uclibc in arm that I can use in my signal handler to debug segmentation faults. I did come across a useful code here and tried using it inside my signal handler but it fails at the first check and returns from there. I also tried a recurcive backtrace function which simply recursed using (current_frame_p)-3) till it was NULL and printed (current_frame_p)-1). This too seems to give me issues. All I get is the address of the handler and some garbage big address (I assume it might be the signal address). But I don't go
订阅 embedded-linux