ChanServ changed the topic of #linux-cros-arm to:
hexdump0815 has joined #linux-cros-arm
hexdump01 has quit [Ping timeout: 480 seconds]
hexdump0815 has quit [Quit: WeeChat 3.8]
hexdump0815 has joined #linux-cros-arm
<hexdump0815> jenneron[m]: very nice - this makes those old machines still quite useable for even more things
KieranBingham[m] has joined #linux-cros-arm
<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. My Google-fu failed me
<javierm> KieranBingham[m]: no worries, I've shared in both channels in case other folks were also interested
<jenneron[m]> Kieran Bingham: there is qcom-camms driver in mainline, some people tried getting cameras working on some phones, but i think the problem was userspace
<jenneron[m]> hexdump0815: btw do you have a chance to test pmOS on mt8186 device? we got it merged as well as mt8192/mt8195
<KieranBingham[m]> jenneron: yes but there are still some complications with camss at the moment if the device is using c-phy instead of d-phy which I suspect the trogdors are indeed using. and we need to know more about the actual cameras connected if we're going to declare them in the DT. The userspace part is what we want to fix, there's soon to be a "softISP" in libcamera which will get through the lack of (full) isp