| ecrn | how does halium-based sailfish os porting work? just like any other base, but the halium tree is used instead of aosp/lineage/...? | 00:12 |
|---|---|---|
| ecrn | or, is it lxc container with halium instead of droid-hal-init service then? | 00:13 |
| mal | afaik it's container and no droid-hal build, not sure about details | 00:34 |
| ecrn | as the ubports port is nearing completion, I'd like to go on with sailfish port now | 00:36 |
| ecrn | and since there is no lineage os port for the device | 00:36 |
| ecrn | it probably would be similar work to port halium (instead of using generic halium) as to port the hybris-... (lineage based?) tree | 00:38 |
| ecrn | and I'm not sure what to pick | 00:38 |
| ecrn | I quite like the idea of putting the android bits in a container which separates fs tree from them | 00:40 |
| ecrn | there is a lot of proprietary code so that seems wiser | 00:41 |
| mal | maybe ask @adampigg about halium based porting, some other may have done those also | 00:47 |
| ecrn | @adampigg: any resources porting sailfishos using halium in a container? | 01:07 |
| ecrn | s/porting.regarding porting/ | 01:08 |
| ecrn | s/porting/regarding porting/ | 01:08 |
| T42 | <birdzhang> Take a look at https://github.com/hellovolla?q=halium&type=all&language=&sort= you can find some clue | 02:04 |
| ecrn | nice, thanks | 02:18 |
| *** Mister_Magister_ is now known as Mister_Magister | 03:14 | |
| ecrn | https://github.com/HelloVolla/local_manifests not quite sure if it is supposed to be used with halium-9.0 as a base, or hybris-16 | 03:48 |
| ecrn | "For building Sailfish OS adaptation, use hybris-16.0 branch and follow the official Hardware Adaptation Development Kit guide." | 03:48 |
| ecrn | but there is hybris-16.0 branch in the local_manifests repository, and there is probably hybris-16.0 in mer-hybris/android as well | 03:49 |
| ecrn | but if the mer-hybris/android would be used as a base, how is that halium then? | 03:49 |
| ecrn | hmm, ok, perhaps this repository is not relevant to the droid-config-halium repositories on this github | 03:51 |
| T42 | <Umeaman> Kind of offtopic, but in terms of porting SFOS to new devices, is this good or bad? | 04:47 |
| T42 | <Umeaman> | 04:47 |
| T42 | <Umeaman> https://www.bloomberg.com/news/articles/2024-12-20/qualcomm-wins-licensing-fight-with-arm-over-chip-designs | 04:47 |
| T42 | <Danct12> it doesn't mean anything (re @Umeaman: Kind of offtopic, bu...) | 05:09 |
| T42 | <adampigg> ecrn: See https://build.sailfishos.org/project/show/nemo:devel:hw:volla:halium-mimameid for device package, and https://build.sailfishos.org/project/show/nemo:devel:hw:halium:12 for the halium generic packages | 08:18 |
| T42 | <adampigg> all you will need to build is the boot.img | 08:18 |
| T42 | <adampigg> for image building, see https://gitlab.com/sailfishos-porters-ci/halium-mimameid-ci | 08:19 |
| T42 | <adampigg> this image build does some custom stuff to package into the super.img, you may or may not need that | 08:20 |
| T42 | <adampigg> if you prefer to build on GH, copy this project https://github.com/HelloVolla/sailfish-release-halium-vidofnir | 08:20 |
| T42 | <adampigg> it would be good to put together a doc with some intructions for this, i just do it now from memory, and help from @notkit! | 08:30 |
| T42 | <K31j0> Are there any experimental branches for lineage 21? | 13:26 |
| T42 | <elros34> yes in mal's hdd:) | 13:30 |
| mal | sorry, forgot about, will check that tonight | 13:36 |
| *** deathmist1 is now known as deathmist | 19:43 | |
| ecrn | @adampigg: thanks | 20:53 |
| ecrn | I think I will need some changes in the kernel building script as well. because it uses split boot/vendor_boot | 20:53 |
| ecrn | but should be able to figure that ouy | 20:54 |
| ecrn | out | 20:54 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!