| 13:57 | KBme> | ok so instead of advising me to update the kernel to the new 4.xxx and have to update my whole userspace that goes with it, and adapt kodi to the retarded new graphics drivers that require patching anything, you could've just advised me to do this: https://gist.github.com/theojulienne/9251b79bcbd68b4e9240 to fix the ti-wifi MAC issue. |
| 13:58 | KBme> | or you could have just stopped distributing that buggy firmware file |
| 14:00 | KBme> | but I guess it's easier to advise someone to input months of work instead of fixing the actual issue. |
| 14:01 | KBme> | but who cares about me? I just payed 10k$ to add a friggin' sata connector to the board. |
| 15:57 | jnettlet[m]> | KBme: I am not sure where LibreElec gets their firmware. I am quite certain they don't use our BSP since we don't include that file. |
| 16:01 | KBme> | jnettlet[m], I mean, https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/ti-connectivity . it's there in the latest master. so I guess they get it from the official upstream, probably. |
| 16:02 | jnettlet[m]> | unfortunately TI stopped pushing firmware mainline. Most their recent firmware is released as service packs |
| 16:02 | KBme> | jnettlet[m], is mainline not updating the firmware? where are these service packs? |
| 16:04 | jnettlet[m]> | KBme: if you register on their developer site you can download them. I think our firmware files relatively up to date. I need to push a new BT firmware file. https://github.com/mxOBS/deb-pkg_cuboxi-firmware-wireless |
| 16:04 | jnettlet[m]> | I am recalibrating the latest firmware for our SOM |
| 16:06 | KBme> | jnettlet[m], so can I update the firmware from that repo then? will it work with the old 3.14 kernel? |
| 16:06 | jnettlet[m]> | yes it is kernel independent |
| 16:06 | KBme> | good. thanks. |
| 16:11 | KBme> | hohooo https://github.com/mxOBS/deb-pkg_imx-vpu |
| 16:12 | KBme> | gems lay within this mxOBS organization |
| 16:31 | jnettlet[m]> | KBme: that is our repo for our build-server |
| 16:31 | jnettlet[m]> | in theory we wanted it to be a shared service, that some others do contribute to, but generally it is mainly us |
| 16:32 | KBme> | jnettlet[m], ok, but are the packages available on a public url? like if I plug the $mirror variable with something (can I find that info anywhere at all?) will the urls work? |
| 16:32 | jnettlet[m]> | We are going to move some of our repos over to gitlab and when we do we will most likely migrate mxOBS over to there. |
| 16:33 | jnettlet[m]> | KBme: I believe the script works. Artox is actually the one who manages most of this. |
| 16:34 | jnettlet[m]> | If all you are looking for is LibreElec builds, it may make sense to just put together a Yocto build for customers to use. |
| 16:37 | jnettlet[m]> | oh there already is one and with a build of Kodi before they removed the imx support. https://github.com/alfonsotames/meta-kodi |
| 16:38 | KBme> | no, I am actually looking for sources of unfindable packages like the evil vivante binaries |
| 16:38 | jnettlet[m]> | it is usually easiest to look at the yocto recipes |
| 16:39 | jnettlet[m]> | meta-freescale is where they publish most the package name changes |
| 16:39 | KBme> | the problem is that I have a hard time finding the latest supported/official yocto recipes, end even if I find them, exctracting useful info like download url is very hard for me as I am not familiar with their build system |
| 18:03 | jnettlet[m]> | as do we all |
| 20:08 | KBme> | jnettlet[m], but you add stuff on top of meta-freescale, no? |
| 20:10 | jnettlet[m]> | KBme: yes we have our own meta layer that sits on top |
| 20:11 | KBme> | so then it's not just meta-freescale, it's meta-freescale plus the solidrun stuff on top |
| 20:11 | KBme> | but I have been doing that, yes. |