| 06:32 | sanjeevs | ping jnettlet |
| 06:32 | jnettlet | sanjeevs, pong |
| 06:32 | sanjeevs | how are you doing ? |
| 06:32 | jnettlet | fine thanks |
| 06:33 | sanjeevs | we had some time back discussion on linux kernel upgradation to version 3.14 |
| 06:33 | sanjeevs | Look like you finally able to stablize the 3.14 kernel tree |
| 06:35 | sanjeevs | please let me know stable /official version of kernel and bootloader for humming board |
| 06:35 | sanjeevs | HummingBoard Base (in latest documents is stated that this board will only work up to dual) is this correct statement ? |
| 06:36 | jnettlet | the kernel will always be a wip in progress, but we already have customers deploying with it. |
| 06:37 | jnettlet | the HB Base is only sold as a package with the HB dual-core. All microsoms work with all our carriers |
| 06:38 | sanjeevs | You mean to say if we are not going for package then we can take SOM module and HB base module seperately |
| 06:39 | jnettlet | yes, that is the purpose of the microsom :) |
| 06:39 | sanjeevs | is there any integration required for that ? |
| 06:40 | sanjeevs | I mean to say will it be straight forward in term of usage or anything special required to merge both module |
| 06:40 | jnettlet | no all our device-tree integration is based on the microsom not the carrier. You will get a few warning messages on boot because devices don't exist but everything works as it should. |
| 06:42 | sanjeevs | Ok so hardware wise no problem, only Carrier need to be fit in dedicated slot |
| 06:42 | jnettlet | yes |
| 06:42 | sanjeevs | Conclusion: HB Base can be used with SOM i4Pro |
| 06:43 | jnettlet | yes. |
| 06:44 | sanjeevs | Lets come to Kernel,I had an long discussion with mk01 on kernel tree you are maintaining https://github.com/SolidRun/linux-fslc ,I believe you had already gone through our conversation |
| 06:44 | jnettlet | what is the discussion about? |
| 06:45 | sanjeevs | I was trying to understand how this kernel is different from FSL kernel |
| 06:46 | sanjeevs | my assumption is that https://github.com/SolidRun/linux-fslc kernel looks like similar copy of linux-fsl kernel except 1)defconfig 2)dts file for the humming board correct ? |
| 06:46 | jnettlet | because I have fixed all the horrendous bugs in their kernel |
| 06:46 | jnettlet | no, there are over 1000 patches on top of the linux-fsl kernel |
| 06:47 | sanjeevs | Bugfixes/features ? |
| 06:47 | jnettlet | freescale pushed their 3.14.xx_ga kernel with no less than 3 major data corrupting bugs in it |
| 06:47 | sanjeevs | is this kernel is sync with FSL 3.14.28 BSP ? |
| 06:47 | jnettlet | we maintain our own bsp. |
| 06:48 | mWaltari | btw... Are those patches coming to us regular Joes anytime soon? (Or any kernel updates) |
| 06:48 | jnettlet | we only upgrade once we have proven the binaries provided by FSL are stable. |
| 06:48 | jnettlet | mWaltari, I am not sure what you mean? Everything is on github |
| 06:49 | mWaltari | Ready to run Build that I could flash? and does these buble into the distros like OpenELEC? |
| 06:49 | sanjeevs | I can understand that BSP is your own but fork of this kernel is Freescale kernel right |
| 06:50 | sanjeevs | will I get same feature/driver Freescale bsp provides |
| 06:50 | jnettlet | sanjeevs, well I dropped my previous work to rebase upon Freescale's released kernel with hopes it would be less work to maintain. |
| 06:50 | jnettlet | ultimately we were horribly wrong. the freescale kernel is released in such bad shape that it took much longer to properly fix everything. |
| 06:51 | jnettlet | mWaltari, we are starting to build images. https://images.solid-build.xyz/ |
| 06:51 | jnettlet | my upgraded OpenElec will be out very soon. It is a very large rework and optimization. |
| 06:51 | sanjeevs | hmmm so you were not aware that Freescale has lot of issue |
| 06:52 | sanjeevs | so now your new kernel is based on Freescale 3.14.28 verison and on top of it you have bugfixes with respect to humming board |
| 06:52 | jnettlet | the bug fixes and optimizations are applicable to all iMX6 based boards. |
| 06:53 | sanjeevs | yes i.e true |
| 06:53 | sanjeevs | Can I use imx6 kernel/Boundary device kernel for your Boards |
| 06:53 | jnettlet | if you look through the commits you will find that many people with other hardware vendors board submit patches for my kernel |
| 06:53 | mWaltari | jnettlet : Thanks! |
| 06:54 | jnettlet | sanjeevs, you can do whatever you would like. We will not support it of course. |
| 06:54 | sanjeevs | hmm that make sense |
| 06:55 | sanjeevs | Btw I am going to use humming board and in that case It would be better if we can use your official version of kernel and booloader |
| 06:56 | sanjeevs | Let me know your official version for Bootloader |
| 06:57 | jnettlet | sanjeevs, it is the u-boot repository on our github.com account |
| 06:57 | jnettlet | we do not recommend using upstream as it has bugs regarding our hardware. |
| 06:57 | sanjeevs | I do provide some suggestion andf bugfixing in Boundary device kernel and work with Troy/Eric.Also in your kernel I can contribute |
| 06:58 | sanjeevs | Ok |
| 06:58 | jnettlet | thanks, pull requests are always welcome |
| 06:58 | sanjeevs | grea8 |
| 06:58 | sanjeevs | Btw I am maintaing my own 3.14.28 kernel based on Linus tree for imx6 soc |
| 06:59 | sanjeevs | But for some urgent requirement we need to use humming Board |
| 06:59 | sanjeevs | for couple of month I will be in sync with you or may need support for humming Board |
| 07:01 | jnettlet | well I am off and on this channel depending on workload, traveling etc. You can use the community forums and support solidrun channels |
| 07:01 | sanjeevs | Do you know if these board can be readily available in India also.I know you have some partner like Tenet and Zwave |
| 07:01 | sanjeevs | OK Do you available on Skype too |
| 07:01 | jnettlet | We are closing in on a stable debian jessie image and our own yocto meta-layer. We would recommend you use these as they will be supported by SolidRun |
| 07:01 | jnettlet | I don't do Skype sorry. |
| 07:02 | sanjeevs | ok |
| 07:02 | jnettlet | Any questions like availability should be directed to the sales address. I know nothing of that. |
| 07:03 | sanjeevs | ok Thanks |
| 07:03 | sanjeevs | Bfn |
| 07:03 | jnettlet | np |
| 07:15 | sanjeevs | Hello jnettlet |
| 07:16 | sanjeevs | HB base support · SD Card (booting) · HDMI · I2C1 (Touch Input) · Ethernet · Audio Out |
| 07:22 | jnettlet | yes, the differentiating features between the Base and the Pro is that the Pro model has mini pcie, msata, ir, sgtl5k codec, lvds, additional usb header. |
| 07:23 | jnettlet | sanjeevs, actually what audio out do you need? |
| 07:23 | jnettlet | the Base carrier does not have an onboard codec for analog audio out. It only supports HDMI and SPDIF audio |
| 07:52 | sanjeevs | ok |
| 07:52 | sanjeevs | It support PWM Mono output correct |
| 07:54 | jnettlet | yes, PWM Mono output |
| 07:54 | sanjeevs | Thanks |
| 07:55 | sanjeevs | Use case:I need to hear audio using Headphone and that can be fullfilled |
| 08:18 | cbxbiker61 | jnettlet, i built up a 3.14.xx from the 3.14-1.0.x-mx6-sr tree, installed galcore userspace libs, i'm getting "unable to handle kernel paging request" when starting up kodi |
| 08:18 | cbxbiker61 | galcore 5, that is |
| 08:22 | jnettlet | cbxbiker61, which galcore libs, and which kernel config did you use? |
| 08:22 | jnettlet | I have separated my driver out from the default FSL version to make merges easier |
| 08:23 | jnettlet | and I am have not updated my driver api up to the latest v5 driver version that was just released. |
| 08:23 | jnettlet | CONFIG_VIVANTE_GALCORE is the correct kernel config to use. |
| 08:26 | cbxbiker61 | http://sources.openbricks.org/3.1/imx-gpu-viv-5.0.11.p4.5-sfp+hfp.tar.xz |
| 08:26 | cbxbiker61 | http://sources.openbricks.org/3.1/imx-vpu-5.4.28.tar.xz |
| 08:26 | cbxbiker61 | http://sources.openbricks.org/3.1/libfslvpuwrap-1.0.58.tar.xz |
| 08:26 | cbxbiker61 | those are the userspace libs i used |
| 08:27 | jnettlet | cbxbiker61, those look correct. |
| 08:27 | cbxbiker61 | yeah, i've got the CONFIG_VIVANTE_GALCORE set |
| 08:55 | jnettlet | cbxbiker61, sorry I was getting my hair cut :) |
| 08:55 | cbxbiker61 | heh |
| 08:56 | jnettlet | cbxbiker61, with the current kernel you will need a patched version of kodi. This is the current patchset. https://github.com/mk01/xbmc/commits/treeJnettlet |
| 08:57 | jnettlet | I have not tested with a default tree, I should do that. |
| 08:57 | jnettlet | When the rendering got switched with kodi things got a bit regressed. |
| 08:58 | cbxbiker61 | is there a simple way to pull the patches out, so i can apply on top of kodi 15.2? |
| 08:59 | cbxbiker61 | 15.2 is performing great in general on my systems |
| 09:03 | vpeter | Mhm, so my problem could be kodi related too. |
| 09:06 | jnettlet | cbxbiker61, I have them rebased on stable for OpenElec. I will get them published this afternoon |
| 09:06 | vpeter | Nice. Then I will wait. |
| 09:10 | jnettlet | vpeter, which distribution are you using? |
| 09:10 | vpeter | OpenELEC :) |
| 09:11 | jnettlet | oh that is it? okay then I will have you test the new builds |
| 09:13 | vpeter | I would like to sync dts from official kernel and send it to you :) |
| 09:14 | vpeter | This is my last part. |
| 09:14 | jnettlet | yeah with device-tree changes you should be able to use our kernel unmodified |
| 09:14 | vpeter | That's my idea. |
| 09:16 | vpeter | Now that we are talking about kernel: Which kernel should be used next for OpenELEC? This one you are working on or something else. Maybe sraue would use it already in OpenELEC 6.0 which is on the way. |
| 09:16 | jnettlet | probably this one, but I owe him lots of patches |
| 09:17 | vpeter | for? |
| 09:18 | jnettlet | openelec in general |
| 09:18 | jnettlet | should have been done weeks ago but I am still tackling a few issues. |
| 09:18 | jnettlet | and have been pulled off OE duty for other higher priority things for a bit |
| 09:19 | vpeter | I see. Fyi: All the extra patches oe has for linux are applied to this kernel cleanly. |