IRC log of #cubox of Thu 03 Aug 2017. All times are in CEST < Back to index

16:36 crazystick> Anyone here have a Humminboard i2eX running kernel 4.x?
17:31 jnettlet[m]> yes
17:35 crazystick> jnettlet[m]: can you tell me if the top USB port has power for you?
17:35 jnettlet[m]> yes. but what 4.x kernel are you running?
17:36 crazystick> Arch 4.12.4
17:37 jnettlet[m]> most likely broken.
17:37 crazystick> didn't work on any i tried so far
17:37 crazystick> what kernel do you have where it works?
17:38 jnettlet[m]> I have a mainline kernel with a patch series I am working on mainlining.
17:39 jnettlet[m]> however because of all our board variants I am having to work with them to minimize the device-tree maintenance. So a lot is getting moved into device-tree overlays
17:40 crazystick> i also tried taking the dtb from the forum thread here http://www.xilka.com/kernel/4/4.12/4.12.1/release/1/
17:43 crazystick> it had more than the one from ALARM which i think is also a mainline kernel with some patches
17:49 crazystick> anyway, I'm not sure of the best way to move forwards now, I'm stuck on 3.14.53 as everything after that has compatibility problems with my mSATA card
17:51 crazystick> I own 50 of these things now, really need to be able to see a way forwards...
18:40 jnettlet[m]> crazystick: sorry had to step away. There are problems with both mainline and most derivative kernels. The way forward will be a mainline kernel (I am working on a patchset to be pushed) and mainline u-boot that does the device-tree overlay merging.
18:40 jnettlet[m]> besides that I am working on providing the NXP drivers that aren't mainlined as a set of kernel modules.
18:41 jnettlet[m]> We will update these to be compatible with each LTS kernel
18:43 jnettlet[m]> this accomplishes 2 goals. customers have the option to use a mainline kernel and the full OSS stack. If they need the FSL bsp support they can use the fbdev, v4l, vpu, galcore media drivers with newer LTS kernels than NXP is supporting.
18:49 crazystick> and do you have any timeframe on when that is likely to be complete?
18:51 jnettlet[m]> very soon. The mainline bits I am hoping to make it into this release cycle. The additional drivers after that, since they all depend on each other.
18:53 crazystick> ok, sounds good. In the meantime, are you able to provide dtsi files that I can use to build the dtbs? or is there more to it than that?
18:53 jnettlet[m]> although with the HB i2ex upstream should be working. I will check. I is most likely because the u-boot version is borked somehow.
18:54 jnettlet[m]> depends if you just need I/O or if you need accelerated graphics and multimedia
18:55 crazystick> I don't need the video stuff. i2c, spi and working usb would do very nicely.
18:56 crazystick> i2c and spi are missing from the ALARM kernel, but they exist in that xilka one I mentioned earlier, I don't understand why though.
19:05 jnettlet[m]> well I am only focused on mainline I can't comment on their variations.
19:08 crazystick> sure. I've added spi and i2c support to the dtbs in 3.x kernels, so maybe i can figure it out again, it was more by trial and error than understanding what was going on though
19:10 jnettlet[m]> crazystick: I am working on the armada boards right now. Can you ping me over the weekend or Monday and I will gladly work this out for you.
19:13 crazystick> sure thing. monday i can do some more work on this.
19:14 crazystick> thanks