• Posts

  • Joined

  • Last visited

xenpac's Achievements

  1. so the csi camera is now working in mainline kernel? woow The device tree stuff is implemented,csi, i2c and clock are supported? as to this vfe_v4l2 driver, this confuses me too, i think it originates from qualcomm. (video front end), rather complicated. mainline uses the videobuf2 interface, so drivers need to be modified, i guess.
  2. orange pi 4g-iot, This board looks interesting :-) MT6737. might do a cell-phone with it. or Osmocom ? existing smartphones are based on that chip . Would be a nice devel platform,...
  3. Hi jiapei100, yes i should have named it "sun4i_csi" so one can easier clone it under .../drivers/media/video/sun4i_sci... and yes you shall have an allwinner/lemaker based kernel sourcecode on your Bananapi with its uImage being booted. Last week i checked this one and it works: https://github.com/nisenbeck/linux-bananapi unfortunate i found no armbian kernel on github, but this works with patches only i guess. Under /lib/modules/.. you find the module tree for each kernel that ever resided on your system. So..install: goto cd .../drivers/media/video/ , rm -r sun4i_csi to remove the whole driver. git clone https://github.com/xenpac/OV5640-Sunxi-A20.git now u have this "ov5640-sunxi-a20" directory under video. rename it: mv ov5640-sunxi-a20 sun4i_csi goback to your source root: make modules make modules_install reboot if you specified ov5640 as default camera in your fex file you are all set, else you have to modprobe the right one. i used "guvcview" app for testing which worked fair, cheese did not. another good test app is "qv4l2", apt-get install qv4l2 ! though video output is slow but controls work exact. in the "docu" directory there are some scripts to easy change your camera device and also a "vt" commandline tool that also outputs video. the other camera drivers in "device" are all ov5640 with some different setups, read first line in file. i will update some changes shortly.
  4. Does that mean it also stops all the updating? So you just compile your changes locally?
  5. Just as a thought....if to integrate that into mainline..... is there any CSI support in mainline? (if not, we put it right into the Cam driver. as no one else is using CSI-0 and 1). plus supporting videobuf2. I think the Clock module is there as well as the I2C. ps. just wonder what other chips have compatible CSI port ???
  6. Hi ?Alex Yes, kernel version is 3.4.112, i guess (not having it on desk) actual source code was: https://github.com/LeMaker/linux-sunxi It seems the CSI driver did not change over the last years. If u check it out, disable the DEBUG output in the source files (forgot that) addendum: the device driver files are all for ov5640, but different setups: - ov5640.c = standard the others have features like autofocus, crobbing, scaling. so just to be be able to easy switch to explore features. In ..docu/ there is a util "vt" to measure framerate with no output and also set resolutions.
  7. i worked on the BPI M1 Board (the first one) for quite a while now improving or more or less rewriting the A20 CSI camera driver. there are no more artifact-ghost-frames any more. The framerate goes from 5fps(full) to 120fps(crobbed small) i also modified the camera-device driver for the ov5640. disadvantage: existing camera device drivers would not be compatible any more. maybe someone wants to give it a try and check it out. it can be found here: https://github.com/xenpac/OV5640-Sunxi-A20
  8. I have tried to get a grip on device trees.......it is so chucking complicated. I wish we had a standardized BIOS for all ARM Hardware. ! ? ...
  9. Is there a way to just compile the modified driver resulting in a .ko file, so i can substitute it on the target? with make? this is just for testing...
  10. happy new year :-) almost actually i just want to work on a driver code and just compile that to get a .ko file. Using the script "compile.sh" AND CREATE_PATCHES="no" will create a patch from my changes....and will apply it? but i already changed the source code? sounds complicated.
  11. Hi, my name is Tom and i am an embedded developer. I am aiming to dig into the CSI0 camera interface for the bananapi. Admittedly, i am new to the linux way of coding and compilation. Thus far for armbian, i realized,... ....compilation by script "compile.sh"...which checks all needed tools, code, updates...downloads everything...runs a config screen to select target, platform, ...and yeah..it works. When i run the script two times ...it keeps compiling again. hmm+ My experience is, that i do have the sourcecode, a compiler script/makefile....and it will just update the changes i did on the source. (old scool:-) so if i have the source in a directory local on the computer (after a one time compile with compile.sh), .. then modifying the code..if i run compile.sh again, will it overwrite my changes by downloading again? Also i do see "patches". So patches (diff files to the original source files) are ?? uploaded to the git...and ?? will be applied during the compilation?? As you can tell, linux devel-newbi:-) So..how do i work on the sourcecode locally on my computer...ie. run the compiler, and finally supply "patches" then when i found a solution? Please give me a little guideline on local development the armbian source. (quick and easy...not long) regards Tom
  12. Well Hello Armbians, ( i just joined today, was on BPI before) Actually the original Wallpaper isnt that bad. My personal opinion, i dont like the standard linux penguin animal motive. The universe...well, sdcards..no. i like #29 pretty well. (high-rise buildings with electronics) reduce text to just- Armbian ARM-Linux