ChanServ changed the topic of #linux-msm to:
hexdump0815 has joined #linux-msm
hexdump01 has quit [Ping timeout: 480 seconds]
marvin24 has joined #linux-msm
marvin24_ has quit [Ping timeout: 480 seconds]
svarbanov has quit [Ping timeout: 480 seconds]
animist1 has quit [Remote host closed the connection]
animist1 has joined #linux-msm
svarbanov has joined #linux-msm
pespin has joined #linux-msm
svarbanov has quit [Read error: Connection reset by peer]
svarbanov has joined #linux-msm
mripard has quit [Quit: mripard]
pespin_ has joined #linux-msm
pespin has quit [Read error: Connection reset by peer]
<javierm> bamse: any thoughts on https://github.com/andersson/rmtfs/pull/19 ? A rmtfs package and deps landed in Fedora, the only bit missing for Chromebooks is a systemd service that could start rmtfs with -o
<javierm> I would prefer to not ship a Fedora specific unit file but one that could come from rmtfs upstream
<bamse> javierm: would it make sense to make it a runtime thing instead?
<bamse> javierm: something where we look for partitions and fall back to the path?
<javierm> bamse: I thought about that, but didn't know a) how to properly check and b) what path should be used
<bamse> javierm: okay, let me take another look when my mind is in the right place...
<javierm> bamse: because the instructions I got was to use https://gitlab.com/postmarketOS/msm-cros-efs-loader (which I already packaged in Fedora) and that populates a /var/lib/rmtfs/ dir
<javierm> but didn't know if that's a convention or just the path that tool uses...
<javierm> bamse: I plan to write a Fedora wiki page explaining that one has to run ms-cros-efs-loader once, so that the FCG data is taken from the ChromeOS eMMC boot partition and then enable the rmtfs-dir.service
<javierm> for WoA I would mention that only enabling rmtfs.service should be enough
<javierm> *FSG
<bamse> javierm: my desire is that we can always launch rmtfs.service and it will just work, even in the case where we don't have a modem...so that we don't need to have device-specific configuration
<bamse> javierm: right now rmtfs fails if i don't have a modem remoteproc, in which case the entire systemd boot is marked as "failed"
<javierm> bamse: yeah, I see that in HP X2 Chromebook (without my patch) and systemct status says State: degraded
<javierm> bamse: if rmtfs can be made more smart and figure out what has to do (instead of the user telling it with -P or -o), that you be even better
<javierm> then we could just have a systemd preset file and enable the service by default
<javierm> bamse: but I didn't know how to do that, hence my patch to add another systemd service unit
<javierm> bamse: and that's the reason why I for now just ship rmtfs v1.0 without any additional patches, even when that's not helfpul for my use case :)
<bamse> javierm: i'll try to find some time to think this through properly
<javierm> bamse: awesome, thanks a lot!
<javierm> bamse: that's exactly why I opened that PR, so that you could chime in and tell me what's the proper approach. But unfortunately I'm not that familiar with QC platforms to figure out myself
pespin_ has quit [Remote host closed the connection]
hexdump0815 has quit [Quit: WeeChat 3.8]
<KieranBingham[m]> I've seen mention of "sc7180-trogdor-mipi-camera.dtsi" on patches posted to the kernel regarding Chromebooks. But I can't find any public reference to this file.
<KieranBingham[m]> Does anyone know if the definition of how cameras are connected on QCOM chromebooks at all is public anywhere?
<KieranBingham[m]> I understand the ISP being out at the moment but if we can configure in passthrough, we can look at testing with the soft ISP in libcamera
<KieranBingham[m]> Thanks. I tried different branches, and Google (search) didn't help
<KieranBingham[m]> There's not a lot to go on in there is there. They must even handle the cameras in userspace. I'm curious to figure out if they're using c-phy or dphy on this platform
<javierm> KieranBingham[m]: yeah, I don't know tbh
<KieranBingham[m]> If I can get the i2c interfaces up I think we can query the cameras... Maybe ... But ugh ... There's a lot of obfuscation going on.
<javierm> KieranBingham[m]: yeah. That's what eballetbo did for the BeaglePlay, where the ISP seems to be implemented in user-space using some GStreamer elements
<javierm> but he was able to get camera frames using just the CSI-2 and the i2c camera sensors
<javierm> KieranBingham[m]: maybe you can also get a BeaglePlay for your softisp testing ?
<KieranBingham[m]> Bah where's the fun in that :-)
<javierm> KieranBingham[m] :D
xtex_ has joined #linux-msm
xtex has quit [Read error: Connection reset by peer]
xtex_ is now known as xtex