george

Just revert the last commit and rebuild it

LOL, nothing to see here. I found it after some more digging: /etc/default/ap6212

Hello, I have a couple of NEO Pi Air's and they show up as the same device in LightBlue. After a bit of digging, I noticed that the BD addr of the devices are the same. hci0: Type: BR/EDR Bus: UART BD Address: 43:29:B1:55:01:01 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:6552 acl:180 sco:0 events:373 errors:0 TX bytes:6809 acl:180 sco:0 commands:248 errors:0 Is there any way to change the address?

I've been doing a bit of work to get gstreamer-1.0 working with my Nano Pi NEO Air (AW H3). I can pull in about 11fps at 1920x1080 and 30fps at 1280x720 with CAM500B (OV5640) using the following command: GST_PLUGIN_PATH=/usr/local/lib/gstreamer-1.0 gst-launch-1.0 -vem v4l2src ! video/x-raw,format=NV12,width=1920,height=1080,framerate=30/1 ! cedar_h264enc ! h264parse ! fpsdisplaysink text-overlay=false video-sink=testsink gst-plugin-cedar modifications are here: https://github.com/gtalusan/gst-plugin-cedar sun8i kernel modification here: https://github.com/gtalusan/sun8i-linux-kernel I've submitted a pull request to Armbian too here: https://github.com/igorpecovnik/lib/pull/655 Right now the V4L2 buffers are backed by a DMA buffer as far as I can tell. This is mmap'd into userspace memory and then memcpy'd into another DMA buffer for VPU/VFE/ION H264 encoding. The memcpy could maybe disappear if the physical address of the DMA buffer was passed along via V4L2 API, but I haven't found a clean way to do that. FFMPEG-Cedrus also has the same problem. Commenting out the memcpy in gst-plugin-cedar (and hence H264 encoding garbage) drops my CPU load down to about 5-10% so there's definitely room for improvement if the DMA buffers can be shared.

Thanks for the reply. I got the camera detected again. It helps to change the /boot/bin/nanopiair.fex instead of /boot/bin/nanopineo.fex. Nothing to see here

Hi there, I recently purchased a NanoPi NEO Air from FriendlyElec with a CAM500B module. It works alright with the mjpg-streamer and their provided Ubuntu Core. I built an Arabian 5.27 Nano Pi Air Debian Jessie image with the default kernel and the device is no longer found. I've forced the load of ov5640 and vfe_v4l2 in /etc/modules, but /dev/video0 isn't appearing. The kernel log has this in it when the module is loaded: [ 116.519650] [OV5640@lex]init_sensor - frame_rate: 0, max_win_size: 11 If I boot back to Ubuntu Core via SD, the camera is back.