#apertus IRC Channel Logs

off to bed now ... have a good one everyone!

I'm eyeing for a Black Magic Pocket Cinema 4k for the larger (demo) project, as I won't have the funds for my "clone" of the Axiom (with a Genesys 2 devboard to adapt the sensor to QSFP+), and would like to work on the software while saving up for the "final" hardware (I hope to make use of the 300 fps the fancier axiom-clone could capture).

hi Y_G, how is it going?

you can of course simplify it, as we don't need to replicate scripts 1:1, different purpose and so

another task is to check on direct register configuration of CMV12000, it was implemented, but not tested, especially with DaemonCLI

The code for `i2cget` and `i2cset` that has been used in the scripts is already available here "https://fossies.org/linux/i2c-tools/"

A very basic Adapter would look something like this "https://www.kernel.org/doc/Documentation/i2c/dev-interface"

So This should be working

Y_G: most of the scripts are using the i2c functions defined in i2c*.func

Hi BAndiT1983 , I went through your mail, I am clear about how static allocator should be used.

so we have to change them, Am i right in that repect

This is my approach for implementation, Kindly check it : 1) implementation of static allocator 2) use static allocator to load frames 3) bring silders to control loading of frames

implement a simple playback first, before you try to access sliders and whatnot

Ok vup ,Thanks

Y_G, check the scripts and what they do

Have not tried that ,will do after the base setup

Y_G, do you have any other questions at the moment?

Having some problems implementations wise,as all implementations online use a package called libi2c-dev which is not available for arch.It has a similar thing called i2c-tools so figuring out how to use that only

do we need this packages?

Everywhere I read it says it's preferred that SMBus commands like `i2c_smbus_read_word_data()` should be used for reading and writing

source : "https://www.kernel.org/doc/Documentation/i2c/dev-interface"

Y_G, could you test and if required fix the config register for CMV?

sudo modprobe i2c-dev

On Debian, <linux/i2c-dev.h> still declares i2c_smbus_write_word_data and others - but on Arch Linux that is simply not the case.

ok, do i2c first, will test it tomorrow or so, at least for usability, as the guys planned some tests, but you can check afterwards if it safe and stable

but after i2c we could check advanced scripts like color matrix etc.

Y_G, focus on your current work

ok ,Off for now

good noght

Y_G, according to this you can copy the methods you miss -> https://github.com/hallard/ArduiPi_OLED/issues/15

newer interfaces?

you can alos inspect this or similar -> https://github.com/amaork/libi2c

what could help is raspberry pi forum, as they also are using a lot of i2c

here i don't see any lib at first

check 2 lines above ;)

first question is: what do we want to get from i2c or what do we want to set?

i would like to keep some low-level things out of daemon, otherwise it would get rather complex to handle correct timings and other stuff