| NeoChapay | lbt: ping | 06:07 |
|---|---|---|
| akaWolf | what is purpose of libhybris? | 11:56 |
| kimmoli | https://en.wikipedia.org/wiki/Hybris_(software) | 11:59 |
| akaWolf | so for what? | 12:00 |
| akaWolf | why we need to use libhybris? | 12:00 |
| mpol | to use android drivers for your hardware | 12:10 |
| akaWolf | what is android drivers? | 12:11 |
| akaWolf | what is difference with linux kernel drivers? | 12:11 |
| akaWolf | why not just to compile it for linux? | 12:11 |
| NeoChapay | it`s close source | 12:12 |
| mpol | akaWolf: you can compile a kernel from kernel.org, but you want get very far using your hardware | 12:12 |
| NeoChapay | and use android services like logd and bionc binder | 12:12 |
| akaWolf | why we need to use android services? | 12:13 |
| akaWolf | for example, rild | 12:13 |
| akaWolf | ofono have direct interface with at commands | 12:13 |
| akaWolf | IIRC | 12:13 |
| NeoChapay | and c library of andoid (bionic) not compatible with GNU C library | 12:13 |
| akaWolf | drivers using c library?... | 12:14 |
| NeoChapay | of course | 12:14 |
| akaWolf | how? | 12:14 |
| NeoChapay | and many android services | 12:14 |
| akaWolf | I though linux drivers can't use libc | 12:14 |
| akaWolf | and libc builded at top of linux kernel | 12:15 |
| NeoChapay | becouse drivers in android comprises ont only cernel module :) | 12:15 |
| NeoChapay | *kernel | 12:15 |
| akaWolf | so again.. what is android driver? | 12:16 |
| NeoChapay | some library or services who talk with kernel | 12:17 |
| akaWolf | so android driver != linux kernel driver? | 12:18 |
| NeoChapay | for exaple we have modem tty device and rild daemon who load librild-mtk.so and all functional of modem in library not in kernel | 12:19 |
| akaWolf | because linux kernel in Android have not so many differences | 12:19 |
| akaWolf | in that case we can use direct AT commands I think | 12:20 |
| NeoChapay | not only AT comands.... | 12:20 |
| akaWolf | hm? what else we need to drive GSM modem? | 12:21 |
| NeoChapay | you need load firmware for example | 12:22 |
| NeoChapay | and you don't know how talk with modem with AT comands | 12:23 |
| akaWolf | ofono knows | 12:23 |
| NeoChapay | no | 12:24 |
| NeoChapay | only in librild-*.so | 12:24 |
| akaWolf | okay, there can be difference between modems. but that means only that we need to write corresponding module for ofono for supporting that modem | 12:26 |
| akaWolf | why we need to use whole android infrastructure? | 12:27 |
| NeoChapay | and AT comands | 12:27 |
| NeoChapay | and logging | 12:27 |
| NeoChapay | and many different thinks | 12:27 |
| akaWolf | if there is no android infrastructure, then there is no need to logging :) | 12:28 |
| NeoChapay | logging is one of more android interfaces who COMPILED IN android drivers | 12:29 |
| NeoChapay | you can't say okay we remove logd - you driver say - ooops i don't have logd service i go out | 12:30 |
| akaWolf | for gsm we can write corresponding module in ofono and we can drop android drivers. which one android drivers we can't drop? | 12:31 |
| NeoChapay | WE DON'T KNOW HOW WE NEED TO TALK WITH MODEM! | 12:31 |
| NeoChapay | We can't drop rild becouse we don't have any docs and source of module | 12:32 |
| akaWolf | okay. I see | 12:32 |
| NeoChapay | And if we have some doc we need write drivers for ofono | 12:32 |
| akaWolf | it's definitely would be better choice over using android infrastructure :) | 12:33 |
| NeoChapay | we don`t have so many peeople for rewriting all android drivers | 12:35 |
| NeoChapay | if you can it`s will be good | 12:35 |
| locusf | you actually have to drop rild in order to use other custom drivers in ofono | 12:44 |
| locusf | at least with mer/sfos packaging | 12:44 |
| locusf | had to do that with a sim900 modem on sailpi | 12:45 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!