| 14:23 | Dom__ | mk01_: are oyu here? |
| 15:11 | jmontleon | Artox, did the build system change names or something? |
| 15:11 | jmontleon | malte, ^ |
| 15:12 | Artox | jmontleon: |
| 15:12 | Artox | sorry |
| 15:12 | Artox | it died |
| 15:12 | Artox | and malte is on holidays |
| 15:12 | Artox | I can tell you exactly when once I find my mail |
| 15:13 | Artox | my nameservers simply stopped to resolve the name |
| 15:13 | Artox | no clue why |
| 15:13 | Artox | malte will be back next week |
| 15:13 | Artox | and the thing should be back up soon after |
| 15:13 | jmontleon | no worries. is it accessible by ip address until then, or has something worse happened than just a dns resolution issue? |
| 15:14 | Artox | (it happened less than 24 hours after I wrote a post on forums about it .....) |
| 15:14 | Artox | the question is: what is the ip |
| 15:14 | jmontleon | I see |
| 15:14 | Artox | thats what the dyndns was for |
| 15:14 | jmontleon | timing is everything :) |
| 15:14 | jmontleon | ok, well, I won't worry until next week then :) |
| 15:18 | mk01_ | Dom__: yes |
| 15:19 | Artox | since dec. 26, 14:15 ECT its offline, jmontleon |
| 15:23 | Dom__ | mk01_: do you have experience in adding driver to the kernel? |
| 15:23 | mk01_ | heh |
| 15:23 | mk01_ | you cant add the bikers file ? :) |
| 15:23 | mk01_ | no problem |
| 15:24 | mk01_ | tell me |
| 15:24 | mk01_ | what category it is i2c |
| 15:24 | mk01_ | ? |
| 15:24 | Dom__ | no, i want to add my own file |
| 15:24 | mk01_ | ok |
| 15:24 | Dom__ | :) |
| 15:24 | mk01_ | better |
| 15:24 | mk01_ | ;) |
| 15:24 | mk01_ | tell me |
| 15:25 | Dom__ | i created the file in drivers/media/i2c/soc_camera |
| 15:25 | mk01_ | ok |
| 15:25 | Dom__ | and added the Config flag to the .config file |
| 15:25 | mk01_ | and you want to SEE |
| 15:25 | mk01_ | if it gets loaded |
| 15:25 | Dom__ | and added cofig part in Kconfig in drivers/media/i2c/soc_camera/ |
| 15:25 | mk01_ | right ? |
| 15:26 | Dom__ | first i want to compile it |
| 15:26 | mk01_ | Makefile |
| 15:26 | mk01_ | under soc_camera |
| 15:26 | Dom__ | if i ran make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- modules LOCALVERSION="-cubox", the module isn't compiled |
| 15:26 | mk01_ | re-using your CONFIG_ from Kconfig |
| 15:26 | mk01_ | yes |
| 15:26 | mk01_ | Makefile |
| 15:27 | Dom__ | it's already added |
| 15:27 | mk01_ | show me |
| 15:27 | Dom__ | obj-$(CONFIG_SOC_CAMERA_OV5647) += ov5647.o |
| 15:27 | mk01_ | ok |
| 15:27 | mk01_ | and Kconfig |
| 15:27 | Dom__ | config SOC_CAMERA_OV5647 tristate "ov5647 camera support" depends on SOC_CAMERA && I2C help This is a V4L2 camera driver for the OmniVision OV5647 sensor |
| 15:28 | mk01_ | and you selected it in make menuconfig, yes ? |
| 15:28 | mk01_ | so its in .config |
| 15:28 | Dom__ | yes |
| 15:29 | mk01_ | ok |
| 15:29 | mk01_ | file is called ov5647.c ? |
| 15:29 | Dom__ | in .config: CONFIG_SOC_CAMERA_OV5647=y |
| 15:29 | mk01_ | perfect |
| 15:29 | mk01_ | file name ? |
| 15:30 | Dom__ | -rw-r--r-- 1 root root 24087 Dez 31 15:04 ov5647.c |
| 15:30 | mk01_ | ok |
| 15:30 | Dom__ | in drivers/media/i2c/soc_camera/ |
| 15:30 | mk01_ | clearly |
| 15:30 | mk01_ | thats bad |
| 15:30 | Dom__ | do i need a module clean or something else? |
| 15:31 | mk01_ | no |
| 15:31 | mk01_ | try |
| 15:31 | mk01_ | touch ov5647.c |
| 15:31 | mk01_ | it will reset mod timestap |
| 15:31 | mk01_ | to NOW |
| 15:31 | mk01_ | run make modules again |
| 15:31 | mk01_ | nope |
| 15:31 | mk01_ | you have in .config |
| 15:31 | mk01_ | =y |
| 15:31 | mk01_ | that's inkernel |
| 15:32 | mk01_ | so will compile durin |
| 15:32 | mk01_ | make zImage |
| 15:32 | mk01_ | for make modules |
| 15:32 | mk01_ | it would need to be =m |
| 15:34 | Dom__ | ah ok |
| 15:35 | Dom__ | now it is compiled :) |
| 15:35 | Dom__ | thanks |
| 15:37 | Dom__ | is your code from dave mcmordie? |
| 16:09 | mk01_ | original 56somethng was from someone |
| 16:09 | mk01_ | whose info I kept |
| 16:10 | mk01_ | if it is mcmordie then he is funny guy :)) |
| 21:28 | nexace | hello |
| 21:29 | nexace | i have recently purchase a Cubox-i4Pro, and was wondering if it is possible to connect an external TV antennae to my Cubox and watch live local TV in that manner? |
| 21:36 | Devrr | nexace, no that is not possible. There isn't anywhere you can connect the antenna to. An antenna would attach to a TV tuner |
| 21:37 | Devrr | There may be TV tuners that you could attach to the cubox-i via USB. But I have no knowledge or experience with that. |
| 21:39 | nexace | well there are coax to usb converters |
| 21:39 | nexace | but the Cubox doesnt have a native "tv tuner"? |
| 21:42 | Devrr | I do not see one specified on the specs page: http://www.solid-run.com/products/cubox-i-mini-computer/cubox-i-specifications/ |
| 21:44 | forest | nexace, there is no TV tuner in the CuBox-i. You might consider using an external tuner like a SiliconDust HDHomeRun, and accessing it through a media center like Kodi. http://kodi.wiki/view/HDHomeRun |
| 21:45 | nexace | thank you both |
| 21:45 | nexace | ill research the HDHomeRun |
| 21:46 | Meech | Hey everyone, I am looking at drawing openGL directly into framebuffer without Xorg, has anyone had any expereince doing this? |
| 21:51 | nexace | forest, can you describe how the HDHomeRun would be interfaced through Kodi? how would the user experience the channels provided by the HDHomeRun? |
| 22:33 | forest | nexace, I've not done it myself, and it's a bit off-topic here, but it seems to be a pretty popular approach to live tv among kodi/xbmc users. I suggest you do some searches for xbmc (or kodi) and hdhomerun. Here's one of the hits I got: https://www.youtube.com/watch?v=KlDu5YIPBWc |