| T42 | <A_T_R> Where I can get 4.4.0.64 version of SDK,target and toolings ? | 05:08 |
|---|---|---|
| T42 | <A_T_R> Or install 4.4.0.58 version and upgrade to latest ? | 05:09 |
| *** Ischwitch is now known as Ingvix | 05:23 | |
| Thaodan | the latter | 05:24 |
| dcaliste | Hello porters, I've an open question : now that I'm using a X10 ii, I'm missing the FM receiver. Let's imagine I would like to get it working, what would it require me investigate ? In more details: | 08:00 |
| dcaliste | - I've followed HADK and should soon (tm) be able to compile the kernel for the device and create flashable image of it, | 08:01 |
| dcaliste | - I've never run the device with Android, but reading from the Internet, it seems that the device has hardware for FM receiver, So there is driver for it, at least in stock image. Is this driver existing in the AOSP source, I've no idea. | 08:02 |
| dcaliste | - imagining that the driver exists and I can compile it, I suppose it would require to write some binder code to expose its functionalities to the userland, right ? | 08:03 |
| dcaliste | - and then, kindly ask Jolla to get access to the media player sources to see how to make it work with the current UI. | 08:04 |
| abr | dcaliste: afaik the media player should show the FM radio if it's present. it's missing from the sony bits. | 08:05 |
| dcaliste | So let start with the first point : how to find if the driver exists in AOSP ? | 08:05 |
| dcaliste | Hello abr, thanks, indeed the /dev/msm_fm is missing. | 08:05 |
| dcaliste | I guess in android world, there is a driver for it. Maybe proprietary and not (source like in AOSP) distributed. But how to know ? | 08:07 |
| abr | I remember talking to Alin about it a long time ago. FM is a function of the bluetooth chip I think, and they had a better open-source bluetooth driver they could use instead of the buggy blobby one they had before, but it didn't have any FM support. | 08:07 |
| abr | I'm not sure if that's still true, but sony would be the place to look | 08:07 |
| dcaliste | Well, I grep the source of msm_seine kernel, but didn't find any trace of something close to msm_fm... Do you know where could I ask ? I mean Github page, or IRC channel, or what else ? | 08:09 |
| abr | i think this might be the old one? https://github.com/sonyxperiadev/vendor-broadcom-bt-fm | 08:09 |
| abr | and this is the new one: https://github.com/sonyxperiadev/vendor-qcom-opensource-bluetooth | 08:10 |
| abr | ...not much in that second one | 08:10 |
| dcaliste | That's my understanding also that the FM receiver fuunctionality is provided by bluetooth ship. Thank you for the first link. Even if old, it may at least provide some more clues where to look at or also to ask a question. | 08:11 |
| abr | I think from our side, it looks like something that upstream isn't interested in supporting, rather than something that we've chosen not to | 08:12 |
| dcaliste | Well, let's be optimistic and imagine that they have chosen so by lack of time but they would be open to contributions. Not that I'm in a position to do any at the moment by a lack of knowledge in the domain. But well, I could try. | 08:14 |
| dcaliste | Is your second link the current Bluetooth implementation for the seine devices ? (sorry, I'm really new to the kernel parts) | 08:16 |
| Nico | Sony also used to list on their website, what device supports FM with what firmware, but they seem to have stopped doing that. I.e. for the X Compact FM is not supported with the 4.4 kernel: https://developer.sony.com/develop/open-devices/get-started/supported-devices-and-functionality/current-platform-functionality-maintained/ | 08:27 |
| dcaliste | Thank you Nico. What I'm struggling with is to understand if there is a blocking reason for that (hardware or proprietary blobs) or just a software one that the code was not updated because of lack of man power or interest. In the first case, nobody can do anything about it, in the second, motivated enough community members may help. | 08:36 |
| dcaliste | It's just that I find all this hardware related parts so obscure. I mean, in the user land, if there is something that is not working, I know how to find the binary (and the code) that is faulty. I can compile it, debug it, test it on device and extend it if I like to. Here with drivers, I've no idea which sources are running and where to find their repos. | 08:38 |
| dcaliste | With the suggestions of abr, I'm reading these repos and try to find how to link them with the kernel sources... | 08:40 |
| Nico | I think it was just a lack of interest in FM with most users, so sony didn't go through the effort of supporting it anymore | 09:08 |
| dcaliste | Indeed. But from what I can see from https://github.com/sonyxperiadev/vendor-qcom-opensource-bluetooth, it seems to me that the whole Bluetooth implementation has been moved away from open source to binary blobs. Denying the possibility to contribute :/ | 09:14 |
| abr | it doesn't really deserve that 'opensource' in the repo name does it :D | 09:14 |
| abr | i think maybe it's todo, or something was there and got removed. either way that's why you don't see FM on sodp xperias I think | 09:15 |
| dcaliste | abr : indeed ! I'm becoming pessimistic with the possibility to contribute... | 09:15 |
| abr | i guess the only thing to do is bug them for it. if they realize people want it then they might be inspired to restore it? | 09:16 |
| abr | unless that blob is actually built from some foss qcom bt sources? | 09:17 |
| abr | but then why is it a blob here... | 09:18 |
| dcaliste | Yes, but having it open source would have made it easier that hoping for someone else, without interest in, to do the job. Well, you know about it. I'll try with an issue on qcom-(opensource)-bluetooth to get more details. | 09:19 |
| dcaliste | Let see if it brings me somewhere : https://github.com/sonyxperiadev/vendor-qcom-opensource-bluetooth/issues/4 | 09:27 |
| abr | i've asked on our channels we have with the sony guys if it's possible | 09:37 |
| abr | and passed on that link to your issue | 09:38 |
| abr | but otherwise, FM support is still working on non-xperia devices, so I should think if it gets added there then the rest of sfos would be happy to use it | 09:41 |
| dcaliste | abr, thanks a lot. About the user land part of the job, yes, I think it would be minimal : just adjust the user-land to the new kernel API (if any). | 09:44 |
| mal | just mentioning that even mainline kernel doesn't have fm radio support on those newer qcom devices even though bluetooth from the same chip is supported | 11:27 |
| dcaliste | Thanks mal for the info. | 11:29 |
| mal | the older devices used the iris radio driver in kernel and we were able to directly talk to that | 11:29 |
| mal | (I wrote the middleware for supporting such devices because I wanted fm radio on fp2 :) ) | 11:32 |
| dcaliste | Good, good. If it ever becomes available for qcom devices, then I know who to ask to if some wiring is required between kernel and user-land. Thank you mal. | 11:47 |
| poetaster | mal, fm on the fp2 was/is great | 12:28 |
| T42 | <A_T_R> need help for installing sdk-4.4.0.58 | 15:28 |
| T42 | <A_T_R> | 15:28 |
| T42 | <A_T_R> `Attention: If you chose PLATFORM_SDK_ROOT other than /srv/mer and your SDK version is 4.3.0.15 (check /etc/os-release inside), the following workaround is needed:` | 15:28 |
| T42 | <A_T_R> | 15:28 |
| T42 | <A_T_R> what is this means? | 15:28 |
| voidanix[m] | that you should ignore the workaround as you use 4.4.0.58 | 15:39 |
| T42 | <A_T_R> ok thanks | 15:39 |
| T42 | <A_T_R> `atr@atr-G41D3C:~$ cat .mersdk.profile | 15:39 |
| T42 | <A_T_R> PS1="PlatformSDK $PS1" | 15:39 |
| T42 | <A_T_R> [ -d /etc/bash_completion.d ] && for i in /etc/bash_completion.d/*;do . $i;done | 15:39 |
| T42 | <A_T_R> ` | 15:39 |
| T42 | <A_T_R> ``` | 15:40 |
| T42 | <A_T_R> atr@atr-G41D3C:~$ cat .mersdk.profile | 15:40 |
| T42 | <A_T_R> PS1="PlatformSDK $PS1" | 15:40 |
| T42 | <A_T_R> [ -d /etc/bash_completion.d ] && for i in /etc/bash_completion.d/*;do . $i;done | 15:41 |
| T42 | <A_T_R> ``` | 15:41 |
| T42 | <A_T_R> | 15:41 |
| T42 | <A_T_R> i have this is in .mersdk.profile - its okey | 15:41 |
| T42 | <A_T_R> ``` | 15:41 |
| T42 | <A_T_R> atr@atr-G41D3C:~$ cat .mersdk.profile | 15:41 |
| T42 | <A_T_R> PS1="PlatformSDK $PS1" | 15:41 |
| T42 | <A_T_R> [ -d /etc/bash_completion.d ] && for i in /etc/bash_completion.d/*;do . $i;done | 15:41 |
| T42 | <A_T_R> ``` | 15:41 |
| T42 | <A_T_R> | 15:41 |
| T42 | <A_T_R> i have this is in .mersdk.profile - do i have to extra commads to .mersdk.profile (edited) | 15:41 |
| voidanix[m] | should be good | 15:45 |
| T42 | <A_T_R> ``` | 15:46 |
| T42 | <A_T_R> atr@atr-G41D3C:~$ sfossdk | 15:46 |
| T42 | <A_T_R> Mounting system directories... | 15:46 |
| T42 | <A_T_R> Mounting /srv/sailfishos/targets as /srv/mer/targets | 15:46 |
| T42 | <A_T_R> Mounting /srv/sailfishos/toolings as /srv/mer/toolings | 15:46 |
| T42 | <A_T_R> Mounting / as /parentroot | 15:46 |
| T42 | <A_T_R> Mounting home directory: /home/atr | 15:46 |
| T42 | <A_T_R> User hook mount_sdk | 15:46 |
| T42 | <A_T_R> Entering chroot as atr | 15:46 |
| T42 | <A_T_R> Last login: Mon May 23 15:41:31 UTC 2022 on pts/1 | 15:46 |
| T42 | <A_T_R> bash: xport: command not found | 15:46 |
| T42 | <A_T_R> Env setup for x00td | 15:46 |
| T42 | <A_T_R> PlatformSDK atr@atr-G41D3C:~$ ``` | 15:46 |
| T42 | <A_T_R> | 15:46 |
| T42 | <A_T_R> | 15:46 |
| T42 | <A_T_R> bash: xport: command not found | 15:46 |
| T42 | <A_T_R> should i worry about this `bash: xport: command not found` | 15:46 |
| mal | do you have typo in one of the files, missing the first "e" from export in some line? | 15:50 |
| mal | for example in .hadk.env file | 15:50 |
| T42 | <A_T_R> export ANDROID_ROOT="$HOME/hadk" | 15:51 |
| T42 | <A_T_R> export VENDOR="asus" | 15:51 |
| T42 | <A_T_R> export DEVICE="x00td" | 15:51 |
| T42 | <A_T_R> export PORT_ARCH="aarch64" | 15:51 |
| T42 | <A_T_R> export HABUILD_DEVICE="X00TD" | 15:51 |
| T42 | <A_T_R> export RELEASE="4.4.0.58" | 15:51 |
| mal | some file has a typo, not sure which one | 15:52 |
| T42 | <A_T_R> thanks ,found missing "e" in .bashrc | 15:53 |
| T42 | <A_T_R> for final clarification | 15:57 |
| T42 | <A_T_R> below files are okey? | 15:57 |
| T42 | <A_T_R> | 15:57 |
| T42 | <A_T_R> ``` | 15:57 |
| T42 | <A_T_R> atr@atr-G41D3C:~$ cat .mersdkubu.profile | 15:57 |
| T42 | <A_T_R> function hadk() { source $HOME/.hadk.env; echo "Env setup for $DEVICE"; } | 15:57 |
| T42 | <A_T_R> export PS1="HABUILD_SDK [\${DEVICE}] $PS1" | 15:57 |
| T42 | <A_T_R> hadk``` | 15:57 |
| T42 | <A_T_R> | 15:57 |
| T42 | <A_T_R> | 15:57 |
| T42 | <A_T_R> ``` | 15:57 |
| T42 | <A_T_R> atr@atr-G41D3C:~$ cat .mersdk.profile | 15:57 |
| T42 | <A_T_R> PS1="PlatformSDK $PS1" | 15:57 |
| T42 | <A_T_R> [ -d /etc/bash_completion.d ] && for i in /etc/bash_completion.d/*;do . $i;done | 15:57 |
| T42 | <A_T_R> function hadk() { source $HOME/.hadk.env; echo "Env setup for $DEVICE"; } | 15:57 |
| T42 | <A_T_R> hadk``` | 15:57 |
| mal | please use pastebin or similar service when showing more than 3 lines | 15:59 |
| T42 | <A_T_R> oh sorry | 15:59 |
| mal | those look reasonable | 15:59 |
| T42 | <A_T_R> i have the hybris-17.1 source in .repo folder and how to extract the .repo contents into current directory (without downloading latest updates ) | 16:32 |
| T42 | <A_T_R> i got it ``` | 16:38 |
| T42 | <A_T_R> repo sync -l ``` | 16:38 |
| T42 | <A_T_R> | 16:39 |
| T42 | <A_T_R> -l, --local-only only update working tree, don't fetch | 16:39 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!