| *** frinring_ is now known as frinring | 02:57 | |
| martinst11 | Hi. Is this the right place to ask a few beginners questions regarding App development on sailfishOS? | 10:23 |
|---|---|---|
| bencoh | I'd say #sailfishos is a better place for that - #mer is more about the Mer core | 10:26 |
| martinst11 | alright. Thanks! | 10:29 |
| skorpeo | Hi I just came accross your project. I was able to install sailfish on my nexus 5x. There are a lot of arm versions of linux distributions such as fedora, I was wondering is it possible to load let's say fedora using arm rootfs on a android device? | 11:35 |
| r0kk3rz | sure | 11:40 |
| r0kk3rz | it wont be easy, i suggest you take a look at the postmarketos project instead | 11:40 |
| skorpeo | well nothing worthwhile is easy | 11:42 |
| skorpeo | i am able to run in chroot currently | 11:42 |
| r0kk3rz | yeah chroot is fine | 11:42 |
| r0kk3rz | but getting it to run properly will require porting debian to the hardware | 11:43 |
| skorpeo | i would be cool with just using userspace tools but i'm not sure if I can do the surgery to sailfish os as i would on normal arm based system | 11:44 |
| r0kk3rz | the sailfish image you've got will be using libhybris, debian wont be integrated with that | 11:44 |
| r0kk3rz | what sort of surgery do you want to do? | 11:44 |
| skorpeo | well usually i would use the vendor kernel and boot loader but use other rootfs | 11:45 |
| r0kk3rz | its not that simple | 11:45 |
| skorpeo | i c so u don;t think it would be possible to somehow replace the sailfish rootfs with other one and keep the relevant parts to boot? | 11:47 |
| r0kk3rz | boot, sure, actually work? not really | 11:47 |
| r0kk3rz | but the adaptation for that device is open, you need to device whether you want to use libhybris | 11:47 |
| r0kk3rz | *decide | 11:48 |
| r0kk3rz | the 'rootfs' is kept in .stowaways in home folder | 11:51 |
| r0kk3rz | and used with overlayfs | 11:51 |
| skorpeo | it seems to be the best solution i've seen so far albeit i dont understannd it lol | 11:51 |
| skorpeo | yes i have been lookinng at it | 11:51 |
| skorpeo | i just don't know what is essential i guess | 11:51 |
| r0kk3rz | ok, in a nutshell it allows us to use android userspace drivers for hardware support | 11:51 |
| r0kk3rz | because all android devices use userspace blobs, and not kernel drivers | 11:52 |
| skorpeo | yes i got that and i think it';s awesome | 11:52 |
| r0kk3rz | the issue here, is that 'normal arm systems' expect kernel interfaces | 11:52 |
| r0kk3rz | the big one is the graphics drivers | 11:53 |
| skorpeo | i c so i guess libhybris isn't a "transparent" layer, i.e somehow emulating kernel interface? | 11:55 |
| r0kk3rz | no | 11:55 |
| r0kk3rz | the rootfs will need to be adapted to it | 11:56 |
| skorpeo | sorry if i sound like a dummy but this is way out of my league but it's kind of a dream to have linnux runnign with hardware support on these things lol | 11:56 |
| r0kk3rz | check out the halium project, they're trying to standardize some of this hybris stuff | 11:56 |
| r0kk3rz | so you can just swap rootfs and continue on | 11:56 |
| r0kk3rz | its used by things like ubuntu touch and plasma mobile | 11:57 |
| skorpeo | will do really appreciate it | 11:57 |
| skorpeo | looks like theres stuff to get my hands dirty with | 12:06 |
| skorpeo | thx! | 12:06 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!