sixwheeledbeast has quit [Server closed connection]
sixwheeledbeast has joined #maemo-leste
pigeons has quit [Ping timeout: 252 seconds]
parazyd has quit [Ping timeout: 255 seconds]
akossh has quit [Remote host closed the connection]
akossh has joined #maemo-leste
akossh has quit [Quit: Leaving.]
parazyd has joined #maemo-leste
Shock_ has quit [Server closed connection]
Shock_ has joined #maemo-leste
k1r1t0_N900 has quit [Ping timeout: 252 seconds]
ahmed_sam has joined #maemo-leste
ikmaak has quit [Ping timeout: 248 seconds]
ikmaak has joined #maemo-leste
k1r1t0_N900 has joined #maemo-leste
moparisthebest has quit [Quit: Gateway shutdown]
joerg has quit [Ping timeout: 255 seconds]
joerg has joined #maemo-leste
sch has quit [Ping timeout: 252 seconds]
moparisthebest has joined #maemo-leste
sch has joined #maemo-leste
ceene has joined #maemo-leste
Daanct12 has joined #maemo-leste
Twig has joined #maemo-leste
enyc has quit [Ping timeout: 252 seconds]
enyc has joined #maemo-leste
<sicelo>
so when the modem's gone, even reloading the drivers that seem to be related does not cause it to reappear
<sicelo>
i *think* it completely disappears off USB. didn't find time to try and toggle the USB bus directly. should try that next time
uvos has joined #maemo-leste
enyc has quit [Quit: Reconnecting]
enyc_ has joined #maemo-leste
enyc has joined #maemo-leste
enyc_ has quit [Ping timeout: 255 seconds]
arno11 has joined #maemo-leste
<uvos>
yeah try resetting the bus
<uvos>
if that dosent work there are really only two options: 1. android dosent suffer from this problem, somehow 2. android can reset the modem via tty or via some gpio pin
Pali has joined #maemo-leste
arno11 has left #maemo-leste [#maemo-leste]
pere has quit [Ping timeout: 255 seconds]
<Wizzup>
I did manage to get it back on usb btw
<sicelo>
mine didn't. weird. and this time i'm almost sure it's not power related. the device was on charger
<sicelo>
but i think we also need to find out why the icon is stuck on showing the bogus bars. modem is absent in ofono, so i guess there's a ModemRemoved signal we're not handling properly
<uvos>
sphone will also have this problem
<uvos>
it assumes the modem will stay for its lifetime
<uvos>
it allso wont realise when its back, except by accident, since its name will likely be the same
<sicelo>
i guess if the icon shows modem's gone, no one will mind too much that sphone doesn't know it is
<uvos>
sure, its still a bug
<sicelo>
yeah. i'll have a look at the icon thing sometime (but want to finish with the N900 ofono thing first)
<Wizzup>
sicelo: how did you try to bring it back?
<Wizzup>
uvos: yeah having that fixed would be nice. I think with the tp module this problem is gone at least
<Wizzup>
(there might be other problems :p)
<sicelo>
i tried to unload a couple of drivers i think are related, such as qmi_wwan, cdc_*
elastic_dog has quit [Ping timeout: 252 seconds]
pere has joined #maemo-leste
<Wizzup>
so
<Wizzup>
let me see if I can help
<Wizzup>
uvos: from /sys/bus/platform/drivers, I think we want to reset omap-usb2 yeah?
<Wizzup>
see ls /sys/bus/platform/drivers | grep usb
<uvos>
probubly, but im not not sure about the topology off hand
<Wizzup>
I'm trying to see if this can just be done via bind/unbind
<Wizzup>
so /sys/bus/platform/drivers/phy-mapphone-mdm6600 can be bound/unbound but that is on a too high level
<Wizzup>
unbinding cpcap-usb-phy.0 makes the kernel unhappy
<Wizzup>
and unbinding 4a064800.ohci from ohci-platform makes the device very unhappy ;)
elastic_dog has joined #maemo-leste
<Wizzup>
sicelo: in any case I think the idea is to 'powercycle' the usb layer that the modem is on
<sicelo>
i'll do that next time, yes. for the current issue (which was from yesterday, ended up rebooting)
xmn_ has quit [Ping timeout: 272 seconds]
peetah has quit [Server closed connection]
peetah has joined #maemo-leste
elastic_dog has quit [Ping timeout: 258 seconds]
elastic_dog has joined #maemo-leste
<sicelo>
in the meantime, i'll make a DCEW widget that checks if ofono still sees modem
<Wizzup>
sicelo: the status code should not be too hard to fix for this
<Wizzup>
I imagine I just didn't monitor for the modem disappearing and reappearing
<Wizzup>
probably worth fixing anyway
<sicelo>
yes, i looked casually in the past ... there are some mentions of ModemAdded and ModemRemoved, but I didn't go as far as checking how/if it's handled
pere has quit [Ping timeout: 246 seconds]
<Wizzup>
there is code for modem_removed_cb and modem_added_cb
Daanct12 has quit [Ping timeout: 272 seconds]
Daanct12 has joined #maemo-leste
k1r1t0 has quit [Ping timeout: 258 seconds]
pere has joined #maemo-leste
dos has quit [Ping timeout: 240 seconds]
dos has joined #maemo-leste
ahmed_sam has quit [Read error: Connection reset by peer]
Daanct12 has quit [Ping timeout: 255 seconds]
Daanct12 has joined #maemo-leste
ceene has quit [Ping timeout: 255 seconds]
Daanct12 has quit [Quit: WeeChat 4.1.1]
__20h__ has quit [Server closed connection]
__20h__ has joined #maemo-leste
k1r1t0 has joined #maemo-leste
k1r1t0_N900 has joined #maemo-leste
k1r1t0 has quit [Ping timeout: 246 seconds]
xmn has joined #maemo-leste
<norayr>
in postmarketos podcast episode from 2022 the phosh or phoc developer says that he was using neo freerunner and then n900 till the time he started to work for librem on phosh. not leste, but n900 with maemo.
<Wizzup>
makes sense
ahmed_sam has joined #maemo-leste
k1r1t0 has joined #maemo-leste
ahmed_sam has quit [Read error: Connection reset by peer]
Kabouik has quit [Remote host closed the connection]
Kabouik has joined #maemo-leste
Kabouik has quit [Changing host]
Kabouik has joined #maemo-leste
pere has quit [Ping timeout: 255 seconds]
pere has joined #maemo-leste
k1r1t0 has quit [Ping timeout: 246 seconds]
pere has quit [Read error: Connection timed out]
pere has joined #maemo-leste
k1r1t0 has joined #maemo-leste
k1r1t0 has quit [Remote host closed the connection]
<tmlind>
uvos: did you figure some solution to the pte_offset_map_lock() no longer being inlined to build pvr modules?
<tmlind>
actually __pte_offset_map_lock() no longer being inlined i mean
k1r1t0 has joined #maemo-leste
<tmlind>
hmm maybe follow_pte() can be used instead, will check
<freemangordon>
I am not sure what is the proper way to do that - per device seems an overkill to me
<freemangordon>
do you know some standard way to detect if GLX/destop GL is supported?
arno11 has joined #maemo-leste
<arno11>
Wizzup: sicelo: i made another PR for libcmtspeechdata: i found new values to improve/control latency. Now latency is really stable and similar for 2G and 3G.
<Wizzup>
great
<arno11>
sound was sometimes a bit distorted when the latency was too low
<arno11>
now latency stays @100-150ms
k1r1t0 has quit [Ping timeout: 240 seconds]
<Wizzup>
cooking atm, will merge in 30-45mins
k1r1t0_N900 has quit [Quit: k1r1t0_N900]
<arno11>
cool thx
k1r1t0_N900 has joined #maemo-leste
<arno11>
IMO calls are 98% working now :)
<uvos>
tmlind: no all i had to do is fix the ps_vma->vm_flags acesses to use the new vm_flags_set function
<uvos>
after that it compiled and worked perfectly fine
<uvos>
this was ontop of 6.6-rc4
<uvos>
freemangordon: the only way to know if dekstop gl is supported is to try and create a context unfortionatly
<uvos>
i gues we could write a tiny utility that dose that and sets the envvar
<uvos>
tmlind: ok thats not true
<uvos>
i examined the maemo-6.6 tree and these are the changes realted to pvr: