| *** rajm has joined #cip | 06:05 | |
| *** tpollard has joined #cip | 08:29 | |
| *** tpollard has quit IRC | 09:59 | |
| *** tpollard has joined #cip | 09:59 | |
| *** tpollard has quit IRC | 12:11 | |
| *** CTtpollard has joined #cip | 12:11 | |
| *** CTtpollard is now known as tpollard | 12:58 | |
| *** patersonc has quit IRC | 13:46 | |
| *** yoshidak[m] has quit IRC | 13:46 | |
| *** dineshk[m] has quit IRC | 13:46 | |
| *** yoshidak[m] has joined #cip | 14:06 | |
| *** patersonc has joined #cip | 14:22 | |
| *** dineshk[m] has joined #cip | 14:22 | |
| *** nkambo has joined #cip | 15:02 | |
| *** mablabs has joined #cip | 15:27 | |
| *** mablabs changes topic to "cip" | 15:56 | |
| * mablabs waves hello to everyone! | 15:57 | |
| patersonc | Hello mablabs | 15:57 |
|---|---|---|
| mablabs | Hello! I joined this IRC as recommended by the CIP talk given at the ELC, as getting involved | 15:58 |
| patersonc | Fantastic | 15:59 |
| patersonc | Is there anything specifically you're interested in? Or anything you'd like to know more about? | 15:59 |
| mablabs | Would like to understand the best way to dive in to make any contributions, even if it's documentation or similar grunt work. I have experience in BSP customization, Linux drivers, u-boot, etc. | 16:01 |
| *** wens changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/" | 16:02 | |
| patersonc | Sounds great. I suggest you ping an email to the cip-dev mailing list (https://lists.cip-project.org/g/cip-dev) to say hi. You'll reach a larger audience | 16:02 |
| patersonc | Then I guess pick an area. We do a lot of code reviews on the LTS Kernels for each stable-rc release. We are gradually ramping up our automated testing. We are working on our "cip-core" debian-based reference filesystem. SW updates, Security | 16:04 |
| patersonc | Lots to get involved in :) | 16:04 |
| patersonc | There are also patches submited to cip-dev from various sources that need reviewing before we add them into the SLTS kernel(s) | 16:06 |
| patersonc | These are maininly for adding new platform support (as the usual bug/security fixes go into the stable branches and CIP takes them from there) | 16:06 |
| mablabs | Cool. Sounds exciting. Are there an overarching list of requirements that define the acceptance criteria? | 16:08 |
| patersonc | Somewhere on the wiki | 16:08 |
| * patersonc starts trawling... | 16:08 | |
| patersonc | mablabs: https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance | 16:08 |
| mablabs | Reviewing platform support sounds appealing | 16:10 |
| patersonc | Great. Patches aren't too frequent though. | 16:12 |
| patersonc | We have a patchwork site, but tbh I'm not sure how up to date it is: https://patchwork.kernel.org/project/cip-dev/list/ | 16:12 |
| mablabs | Is the iWave RZ/G1M Qseven Development Kit necessary for meaningful development? It's a bit pricey, but if there's no way around it for testing, then I might be able to justify the expense. | 16:25 |
| patersonc | It's just one of the supported reference platforms | 16:27 |
| patersonc | We also support these: https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/cipreferencehardware | 16:27 |
| patersonc | The BeagleBone black being fairly affordable | 16:27 |
| patersonc | We also have remote testing infrastructure containing all of the reference platforms | 16:28 |
| mablabs | Cool, I have a DE1-SoC laying around from previous work. The only difference between that and the Nano are the peripherals. | 16:36 |
| mablabs | Also, is there some history as to why Deby was used instead of Yocto? | 16:37 |
| patersonc | Mainly because Yocto doesn't (or didn't at the time) have any form of LTS, where as Debian ELTS supports up to 6 years | 16:40 |
| mablabs | Yeah, this link is actually a pretty good overview: https://www.yoctoproject.org/learn-items/deby-reproducible-and-maintainable-embedded-linux-environment-with-poky/ | 16:40 |
| patersonc | yea | 16:41 |
| patersonc | CIP has two 'profiles' for it's reference filesystem. 'tiny' which is based on Deby, and 'generic' which is based on ISAR | 16:42 |
| patersonc | ISAR is another approach to build Debian based OS's leveraging bitbake etc. | 16:43 |
| tpollard | is the tiny from deby meant as a similar to poky tiny? | 16:45 |
| patersonc | No, it's just a small selection of packages that CIP aims to support long term. The bare essentials | 16:46 |
| patersonc | The image is about 2MB I think | 16:46 |
| mablabs | This issue also looks appealing and is inline with my experience: https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/-/issues/8 | 16:48 |
| mablabs | Do I just send an email to the mailing list? | 16:48 |
| mablabs | To get started | 16:48 |
| patersonc | Sure. I'd recommend it. Just in case plans have changed or in case someone has already started to look into it. Plus everyone would love to say hi etc. :) | 16:49 |
| tpollard | patersonc: the last time I checked the rootfs of pony tiny was 3MB, so not far off :) | 16:53 |
| tpollard | s/pony/poky | 16:53 |
| tpollard | although not as small as it's name would suggest | 16:54 |
| patersonc | hehe | 16:54 |
| patersonc | The poky FS I normally use is something like 180MB | 16:54 |
| *** tpollard has quit IRC | 17:26 | |
| dineshk[m] | Frequent buffering during yoshi talk | 20:58 |
| patersonc | I had a lot of audio issues for both of them :) | 20:58 |
| dineshk[m] | Same here | 21:58 |
| *** rajm has quit IRC | 22:08 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!