nela4 has joined #maemo-leste
nela has quit [Ping timeout: 264 seconds]
nela4 is now known as nela
diejuse has joined #maemo-leste
inky has quit [Ping timeout: 255 seconds]
inky has joined #maemo-leste
antranigv has quit [Quit: ZNC 1.8.2 - https://znc.in]
inky has quit [Ping timeout: 260 seconds]
mdz has quit [Ping timeout: 264 seconds]
kona has joined #maemo-leste
antranigv has joined #maemo-leste
inky has joined #maemo-leste
k1r1t0 has quit [Ping timeout: 246 seconds]
<tmlind> freemangordon: ok interesting, one of the phy-mapphone-mdm6600 gpios is supposed to wake it up
elastic_dog has quit [Ping timeout: 240 seconds]
elastic_dog has joined #maemo-leste
<tmlind> freemangordon: maybe check if you get phy_mdm6600_wakeirq_thread() to trigger on notifications with autosuspend enabled, maybe that needs to do something to wake the usb ohci host too
<tmlind> freemangordon: ohci-platform.c is the usb host driver in this case
diejuse has quit [Quit: Client closed]
<tmlind> freemangordon: if the oob gpio does not trigger and phy_mdm6600_wakeirq_thread() does not run with autosuspend enabled, then maybe the phy-mapphone-mdm6600 needs to implement something for the usb resume k state
<tmlind> actually the k-state handling would have to be implemented in omap-usb-host.c as that handles the signals
huntersb has joined #maemo-leste
parazyd has quit [Ping timeout: 264 seconds]
<tmlind> freemangordon: here's the old patch series to implement remote wake-up for omap-usb-host.c, might be simpler to do now
<tmlind> basically nowadays we'd set up linux generic wakeirq for the omap-usb-host.c phy pads
<tmlind> then the k-state would get detected, and the wakeirq would pm runtime reumse omap-usb-host.c
<tmlind> but i'd check the phy_mdm6600_wakeirq_thread() stuff first as that is oob
_3xistence has quit [Ping timeout: 264 seconds]
huntersb has quit [Quit: Connection closed]
joerg has quit [Ping timeout: 255 seconds]
joerg has joined #maemo-leste
exolight has joined #maemo-leste
ceene has joined #maemo-leste
parazyd has joined #maemo-leste
k1r1t0 has joined #maemo-leste
<freemangordon> tmlind: yeah, I suspect usb remote wake-up does not work
<freemangordon> and I end up in the same patchs that's still missing :)
<freemangordon> phy_mdm6600_wakeirq_thread() gets called when there is something for the UART part
<freemangordon> not for usb
<freemangordon> so I don;t think it is correct to wait for serial OOB notification to wake USB
<freemangordon> that *might* work but it is still a hack
<freemangordon> for example - if I disable RSSI reporting over gsmmix (+SCRN=0) I still get NAS events over qmi
<tmlind> freemangordon: ok so i'll take a look at adding wakeirq support for the omap-usb-host.c pads when i get a chance, might be a while
* tmlind oob today
<freemangordon> tmlind: I looked at those series yesterday, didn; look like something complicated
<freemangordon> so I may try to prepare something as well
<freemangordon> just want to know - do sysc driver sets WAKE_EN on the pads in suspend? like, do I need to have separate set of pinctrl-simple pads like in th epatch?
Langoor has quit [Quit: No Ping reply in 180 seconds.]
Langoor has joined #maemo-leste
<tmlind> freemangordon: in the dts, add pinctrl pins for the omap-usb-host.c, and an irq named wakeirq, then in omap-usb-host.c call dev_pm_set_dedicated_wake_irq()
<tmlind> in dts the wakeirq is offset from the padconf base for one of the phy pads
duuude has joined #maemo-leste
f_ has quit [Ping timeout: 252 seconds]
f_ has joined #maemo-leste
diejuse has joined #maemo-leste
jk_000 has joined #maemo-leste
<jk_000> hello 0/
<jk_000> i was trying to install sshfs on a droid4 stable and it needs to replace fuse with fuse3 making some packages loose its dependencies
<jk_000> does anyone of you use sshfs?
<jk_000> i want to sshfs-mount my music files to the droid4 over my wlan
<jk_000> :)
<jk_000> ... gotta go. ciao
jk_000 has left #maemo-leste [#maemo-leste]
<Wizzup> let me check
<Wizzup> huh, in latest devel we loose the hildon menu indicator arrow?
<Wizzup> jk_000 I have sshfs installed and no issues
Juest has quit [Ping timeout: 256 seconds]
Juest has joined #maemo-leste
ceene has quit [Ping timeout: 252 seconds]
<freemangordon> tmlind: I think I have the .c part, but not sure what I have to do about .dts part :(
peetah has quit [Quit: -]
duuude has quit [Ping timeout: 256 seconds]
<freemangordon> should't we have wakeirq per port, not one for omap-usb-host.c?
duuude has joined #maemo-leste
k1r1t0 has quit [Ping timeout: 240 seconds]
k1r1t0 has joined #maemo-leste
diejuse has quit [Quit: Client closed]
diejuse has joined #maemo-leste
<diejuse> Hello. I have uploaded a video to YouTube demonstrating the use of the Onboard keyboard that I have been adapting to Maemo Leste for the last few days. I am satisfied that I managed to achieve (more or less) the idea I had in mind of being able to write documents or program or play games like I do on my computer but without a physical keyboard. I
<diejuse> have also documented its installation on my github.
<diejuse> Sorry. The video is this: https://youtu.be/0rS_sP_NXAo
<freemangordon> diejuse: wow, that's cool
<diejuse> freemangordon Thank you. I'm glad you like it :)
<Wizzup> music is good too :D
<diejuse> Wizzup :p
<diejuse> It would be nice if someone tested the installation script I made to see if it works well in native Maemo.
duuude has quit [Ping timeout: 256 seconds]
<Wizzup> and also to be able to test your work on some android phones
duuude has joined #maemo-leste
<diejuse> At the moment I have only put the installation of the basic version on github. I have to add the plus version that adds keyboard repositioning and switching from one keyboard to another from the keyboard itself.
<Wizzup> ok
<diejuse> Wizzup Yes, I have several to try but I'm sure they will work the same, starting with Android 8.
<Wizzup> btw, I think someone also emailed me about keyboard and hildon
<Wizzup> is this the guy who works on the keyboard you're showing?
<Wizzup> I still have to reply to him
<diejuse> I also talk frequently with that guy Inky introduced me to. His keyboard is called "coolkbd" and the one I show in the video is "onboard".
<Wizzup> ok, yeah, he emailed me
<diejuse> They are different investigations. At the moment the "onboard" keyboard has more functionality for a user. But yours will be better if you achieve certain challenges that you are now trying to solve
<diejuse> *yours -> him
<diejuse> his
<diejuse> he achives*
peetah has joined #maemo-leste
diejuse96 has joined #maemo-leste
<Wizzup> ok
diejuse96 has quit [Quit: Client closed]
diejuse7 has joined #maemo-leste
diejuse7 has quit [Client Quit]
duuude has quit [Ping timeout: 255 seconds]
duuude has joined #maemo-leste
diejuse16 has joined #maemo-leste
diejuse16 has quit [Client Quit]
diejuse has quit [Quit: Client closed]
duuude has quit [Ping timeout: 256 seconds]
duuude has joined #maemo-leste
diejuse has joined #maemo-leste
duuude has quit [Ping timeout: 255 seconds]
duuude has joined #maemo-leste
diejuse has quit [Quit: Client closed]
akossh has joined #maemo-leste
nela has quit [Ping timeout: 264 seconds]
xmn has joined #maemo-leste
diejuse has joined #maemo-leste
mdz has joined #maemo-leste
jrayhawk has quit [Ping timeout: 256 seconds]
diejuse has quit [Quit: Client closed]
jrayhawk has joined #maemo-leste
diejuse has joined #maemo-leste
duuude has quit [Read error: Connection reset by peer]
duuude has joined #maemo-leste
<duuude> Wizzup: the battery remains "charging" when it is full