| 00:40 | foresto | The CuBoxTV overview page says "Operate your programs from your...wireless UPNP device." Does it include bluetooth or wifi? |
| 00:59 | wrexem | Just got Plex Media Server running on my hummingboard (i2ex) :) |
| 00:59 | wrexem | Igor's build, then followed these directions: https://bitbucket.org/inkubux/cubox-i/wiki/Plex%20Wheezy |
| 01:00 | wrexem | oh and: apt-get install libexpat1 |
| 01:00 | wrexem | that will let it transcode. |
| 01:03 | wrexem | also downloaded the most recent drobo build, instead of the one he linked. |
| 01:03 | wrexem | Enjoy! |
| 08:20 | topi` | are there any instructions, wiki page, etc. for getting the WiFi to work with jnettlet's 3.14.14+ kernel? |
| 08:21 | topi` | I'm especially interested in running wifi in Master mode (to build a base station) |
| 08:53 | cbxbiker61 | ping rabeeh |
| 08:54 | cbxbiker61 | are you looking for an ov5647 driver module? |
| 08:54 | cbxbiker61 | http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728_stripped/lichee/linux-3.4/drivers/media/video/sunxi-vfe/device/ov5647.c |
| 08:57 | jnettlet | cbxbiker61, we already have one. The driver isn't the issue it is the updated v4l2 infrastructure needed for the newer kernels. FSL uses the old subdev stuff which was removed after 3.10.xx |
| 08:58 | cbxbiker61 | ok, now i'm chomping at the bit to get video capture working on hummingboard, i want to use a hummingboard/octoprint for my printrbot |
| 08:58 | cbxbiker61 | i'll just use a r-pi until it's working, but the additional processing power of the hummingboard would be useful in that app |
| 09:00 | cbxbiker61 | thanksgiving in two days, i have to travel tomorrow |
| 09:24 | topi` | jnettlet: is there a wiki page describing how to get stuff (like wifi) working on 3.14.14+ kernel somewhere? if not, can I help write such a page? |
| 09:27 | jnettlet | topi`, not sure. I would assume there is. It should just be a matter of adding the firmware and nvram.txt |
| 09:28 | jnettlet | if there is nothing in the wiki then I am sure there are instructions in the forums |
| 09:28 | topi` | what is nvram.txt? |
| 09:28 | topi` | it's a bitch to try to search/google for some bit of information that is scattere throughout the forums. that's what the wikis are for! |
| 09:28 | jnettlet | it is a text file that loads chip specific nvram settings for the firmware. |
| 09:28 | topi` | I'm not a forum user, I'm mainly IRC driven :) |
| 09:29 | jnettlet | topi`, if you want to write a wiki page we would be very greatful. |
| 09:29 | topi` | the current solid-run wiki is focused on the old work (3.0 and 3.10+ kernels) |
| 09:30 | jnettlet | I believe that I don't think we updated it to 3.14.14, but the 3.10 info for most things is relevant to the 3.14.14 kernel |
| 09:30 | topi` | oh! |
| 09:32 | topi` | jnettlet: btw, why is the kernel version "stuck" in 3.14.14? There are some useful patches in .22 and between. |
| 09:36 | jnettlet | topi`, I am testing a rebase. There actually wasn't any relevant patches until .20. I don't update just to get a bigger number I evaluate each patchset and see if there is anything relevant |
| 09:36 | jnettlet | topi`, other distros that just keep updating seem to be introducing instabilities for mostly meaningless patch changes. |
| 09:38 | jnettlet | topi`, you have to remember LTS patches are considered "stable" for upstream work only. We carry quite a lot of non-upstream patches so before we pull in the patchsets we need to regression test. |
| 09:39 | topi` | I like to have the "newest" patch level just in case there's some critical bug fix to your network stack and that patch only applies to the newest patchlevel... |
| 09:39 | topi` | so it's kind of "good-to-have" |
| 09:41 | jnettlet | yes that is why I evaluate each LTS patchset when it is released. |
| 09:45 | sam_nazarko | jnettlet: while on that topic |
| 09:45 | sam_nazarko | jnettlet: do you maintain a diff against a vanilla kernel release anywhere? |
| 09:46 | jnettlet | sam_nazarko, ???? |
| 09:46 | sam_nazarko | when building cubox support for osmc |
| 09:47 | sam_nazarko | it would be good to pull 3.14 from kernel.org and apply diffs, than manually specify the downstream repo in git |
| 09:47 | jnettlet | I don't understand what you mean by vanilla kernel release |
| 09:48 | jnettlet | you do realize that my kernel carries over 1000 patches on top of 3.14.14 |
| 09:48 | sam_nazarko | i was not aware of this |
| 09:49 | sam_nazarko | that would be a very large diff |
| 09:49 | jnettlet | it includes a mixture of upstream and fsl patches. Favoring upstream patches to FSL ones. |
| 09:50 | sam_nazarko | i see |
| 09:51 | sam_nazarko | i will look more. I have worked on rebasing your changes to u-boot to 2014.10 |
| 09:51 | sam_nazarko | not sure if that's of any use to anyone, but it helps me where u-boot may be used other devices |
| 09:52 | jnettlet | does it include support for direct boot? |
| 09:53 | sam_nazarko | The SPL you mean? |
| 09:54 | sam_nazarko | I must admit I have only looked at U-Boot briefly and it's because there is another device with upstream support in a later version of U-Boot, so I want to use one codebase |
| 09:55 | sam_nazarko | I am building SPL file and u-boot.img |
| 09:56 | jnettlet | yes I have written directboot to skip second stage u-boot and allowing the SPL to load linux directly. It brings u-boot time down to .3 seconds...mostly just reading in the dtb and zImage from disk |
| 10:14 | topi` | jnettlet: can it read the kernel off of a MSDOS volume? |
| 10:14 | topi` | I guess FAT16 is pretty easy to support |
| 10:20 | jnettlet | topi`, yes it should be able to. |
| 10:20 | bencoh | jnettlet: disabling uboot timer was not enough ? |
| 10:23 | ralix | morning |
| 10:29 | topi` | bencoh: uboot does a lot of stuff besides just waiting 3 seconds... it needs to probe usb/sata/whatnot before it proceeds |
| 10:30 | topi` | probably takes 1-2 seconds in total |
| 13:15 | MarcusVinter | Morning :D |
| 16:46 | anaconda | so, this cuboxtv is an i4 with openelec pre-installed? |
| 16:50 | rabeeh | yes |
| 16:50 | rabeeh | 1GByte memory |
| 16:50 | kaipee | so does cuboxtv mean that all hardware issues are fixed and full acceleration works on the device? |
| 16:50 | rabeeh | but quad processor |
| 16:50 | rabeeh | most of the things |
| 16:50 | rabeeh | on the table with latest PR to Kodi is de-interlacing |
| 16:51 | rabeeh | there is a native 23.976fps feature we want to investigate too |
| 16:51 | anaconda | yeah, asking because the price is interesting |
| 16:51 | rabeeh | :) |
| 16:51 | rabeeh | interesting for good or bad? |
| 16:51 | anaconda | for good :-) |
| 16:52 | rabeeh | our operations is getting better everyday; and we want all to benefit from |
| 16:52 | kaipee | so would this mean the OpenELEC image is likely the most stable / functional for the cubox-i ? |
| 16:52 | rabeeh | OE-beta 4 has the latest and most stable things |
| 16:53 | rabeeh | i'v had long discussions with wolfgar and others - on the table 3 items - |
| 16:53 | rabeeh | 1. sometimes a gpu hang on boot (shows Kodi splash and no main menu) |
| 16:53 | kaipee | I haven't turned my cubox-i on in about 8 months. Got too busy to tinker with all the broken things |
| 16:53 | rabeeh | 2. de-interlacing (important mostly for Europe / Australia users) |
| 16:53 | rabeeh | 3. 23.976fps |
| 16:54 | rabeeh | kaipee: try Ignition then |
| 16:54 | rabeeh | CuBox-i and HummingBoard installer |
| 16:54 | kaipee | but are any of the images fully funtional with hardware accelration and CEC stable (not crashing) ? |
| 16:55 | rabeeh | yes |
| 16:55 | bencoh | what do you mean by "23.976" ? being able to trickplay at this framerate ? |
| 16:55 | rabeeh | besides the gpu hang that sometimes happens on boot |
| 16:55 | kaipee | great, I'll give the new Ignition script a try :) |
| 16:55 | rabeeh | 23.976 is a perfection level we want to achieve |
| 16:55 | bencoh | (I guess/hope it can play 25fps streams for now, otherwise it wont play european tv) |
| 16:56 | rabeeh | today 23.976fps content is played as 24fps; which means in every 40 seconds or so there is one frame that is presented twice |
| 16:56 | bencoh | oh, okay |
| 16:56 | bencoh | I see |
| 16:56 | bencoh | subtle judder and all :) |
| 16:57 | rabeeh | it will be mainly noticed by the folks that spent half of their like qualifying set top box chipset or TV chipsets :) |
| 16:57 | rabeeh | s/like/life |
| 16:57 | bencoh | ;) |
| 16:58 | rabeeh | but it's a perfection level that can be achieved; the edid of hdmi needs to be tweaked and the i.MX6 has a really good pll that can generate extremely accurate frequencies |
| 16:58 | rabeeh | the gpu hang issue is annoying |
| 16:59 | rabeeh | i think it's mainly on Kodi and not related to the kernel or drivers. |
| 17:05 | wrexem | Hello all, what's new, what's cool, what's everyone working on?? :) |
| 17:06 | kaipee | just a quick query : does the ignition.img need ot be resized to the full sdcard? |
| 17:07 | rabeeh | no need to resize ignition |
| 17:08 | kaipee | thanks, I was just wondering why that step was in the wiki |
| 17:08 | wrexem | Anyone else tried running Plex Media Server on their hummingboard? Mine runs quite well, if anyone was wondering. |
| 17:10 | rabeeh | wrexem: yeah. there is a long thread on the forums about plex |
| 17:11 | rabeeh | kaipee: where? |
| 17:11 | rabeeh | i don't see where it requires to be resized |
| 17:14 | wrexem | Does the fact that PMS is for "arm5" instead of arm7 make much difference do you think/ |
| 17:18 | kaipee | rabeeh http://www.solid-run.com/wiki/Flash_an_image |
| 17:18 | kaipee | actually http://www.solid-run.com/wiki/Flash_an_image#HOW-TO:_Extend_image_size_to_whole_SD_card_2 |
| 17:19 | kaipee | though I did just run into 3 problems with that Ignition installer |
| 17:19 | kaipee | 1 - when selecting 'show all distributions' ...nothing shows. You have to deselect for anything to show |
| 17:20 | kaipee | 1 - When I choose OpenELEC Beta (I think it was 5 something) I got presented with an empty error box |
| 17:21 | kaipee | 3 - When I choose OpenELEC stable, it popped up a box asking me to 'choose which one'...I have no idea which one what? The box pop-up was empty, but I just clicked OK and the display went black and nothing happened |
| 17:24 | rabeeh | hmm... |
| 17:24 | rabeeh | do you have CuBox-i connected to Ethernet? did it aquire and IP address? |
| 17:24 | kaipee | yup, ethernet 192.168.0.20 |
| 17:25 | rabeeh | when that happens then it will go to github and download a list of distros and present |
| 17:25 | rabeeh | did that happen? |
| 17:25 | kaipee | it displayed a list of KitKat...something else and 2 OpenELEC versions |
| 17:25 | kaipee | wel...firstly it showed nothing |
| 17:25 | kaipee | then I selected 'show all distrbutions'...but nothing showed |
| 17:25 | kaipee | so I unticked then it displayed those listed above |
| 17:32 | rabeeh | kaipee: just updated OE to beta-4 |
| 17:32 | rabeeh | can you please try? |
| 17:32 | rabeeh | just click on 'sync' in Ignition |
| 17:32 | kaipee | yeah I did but those issues are what happened |
| 17:32 | kaipee | I'm currently re-writing the ignition.img to sdcard and expanding to fill the disk |
| 17:34 | rabeeh | no need to expand |
| 17:34 | rabeeh | actually things might happen if you expand since it's a FAT32 |
| 17:35 | kaipee | well I haave to let it finish now anyway |
| 17:36 | kaipee | brb |
| 18:57 | Humpelstilzchen | uhm....ok the wifi in the Cubox-i is really really bad |
| 19:11 | kaipee | rabeeh managed to get the OpenELEC beta-4 image installed |
| 19:11 | kaipee | had to click 'Install' 5 times, but it's working now |
| 19:11 | kaipee | everything seems to be functioning well :) |
| 19:26 | malte | u can also use win32diskimager and flash an .img file to your sd card |
| 19:27 | MarcusVinter | Thanks for the email malte, I await a reply from rabeeh. |
| 19:27 | malte | okay |
| 19:27 | MarcusVinter | I appricaite that :D |
| 19:28 | malte | :) |