12:55 | Exaga | malte: happy new year o/ |
12:55 | malte | Exaga: thank you - happy new year! |
12:56 | Exaga | all the best for 2015 malte :) |
12:56 | malte | for you too! |
12:57 | goetz | Happy new year. |
12:58 | Exaga | happy new year goetz :) |
14:11 | el8 | sup |
17:48 | Artox | ping jmontleon |
17:48 | Artox | good news, obs is still online |
18:00 | malte | https://opensuse.ddns.net/ |
20:46 | Dom__ | cbxbiker61: hi |
20:46 | cbxbiker61 | hi |
20:47 | Dom__ | yesterday i tried the driver again |
20:48 | Dom__ | the problem was, that the probe function was never be called, because the kernel doesn't know, which bus-address is for this driver |
20:49 | cbxbiker61 | so you have it recognizing the camera? |
20:50 | Dom__ | here is the docu about initiating an i2c device: https://www.kernel.org/doc/Documentation/i2c/instantiating-devices |
20:51 | Dom__ | i think this is missing. i used method 4 for testing, and the probe function was called |
20:51 | Dom__ | but returned with dev_err(&client->dev, "OV5647: missing platform data!\n"); |
20:51 | Dom__ | in the probe function |
20:57 | Dom__ | but now, i have some questions about the functionality of the driver. for all i know is that the camera would be controlled by i2c, but the images/video stream will be transfered by mipi/csi2. is this part missing completely in this driver? if the image/video stream is arrived in the soc, how will this stream be converted to jpeg for example? and how do we get this in the gpu? |
20:57 | Dom__ | i hope you understand my bad english :) |
20:58 | cbxbiker61 | when it works you should be able to get to it with v4l2 /dev/video0 |
20:59 | Dom__ | to the stream? |
20:59 | cbxbiker61 | right |
20:59 | Dom__ | how does v4l2 know, which address of the csi2 interface should be used? |
21:00 | Dom__ | does v4l2 has information about the csi2/mipi interface? |
21:01 | Dom__ | i'm asking, because i found another driver for the ov5647 in the web, which handles some conversions and the mipi interface |
21:02 | cbxbiker61 | does it work? |
21:03 | Dom__ | don't know, because i didn't get it compiling |
21:04 | cbxbiker61 | is it that android driver? that would be android specific |
21:05 | Dom__ | no, mk_ in this channel give me some version, which only works with the 3.10 kernel (i believe it was this version) |
21:05 | cbxbiker61 | yeah, that's the rub |
21:06 | Dom__ | i query you to give you some infos |