Pali has quit [Quit: Pali]
akossh has quit [Quit: Leaving.]
diejuse has quit [Quit: Client closed]
parazyd has quit [Ping timeout: 246 seconds]
joerg is now known as Guest2567
joerg has joined #maemo-leste
Guest2567 has quit [Ping timeout: 240 seconds]
ikmaak has quit [Ping timeout: 246 seconds]
ikmaak has joined #maemo-leste
duuude has joined #maemo-leste
<freemangordon> tmlind: heh, I think I found the missing events issue :) . here https://github.com/maemo-leste-upstream-forks/ofono/blob/maemo/chimaera-devel/plugins/udevng.c#L410
<duuude> U-Boot with kernel 2.6.28-omap1 won't get installed
<duuude> it violates "third party package policy"
<duuude> what to exactly do now?
<freemangordon> it takes the last wdm device (cdc-wdm3). if I change that to use first device (cdc-wdm0), at least NAS and SMS notifications are comming
<tmlind> freemangordon: oh nice :)
<freemangordon> this is for device in BP mode
<freemangordon> but I assume it will be the same if we boot leste
<tmlind> should be yeah :)
<freemangordon> will test that later on
<freemangordon> also, I have upstream ofono working with it, without gsmmux
<freemangordon> is it needed for voica calls, right?
<freemangordon> or, is it?
<freemangordon> if qmimodem in ofono support voice calls over qmi, do we need gsmmux?
<tmlind> for voice call routing and mixer we need something for alsa
<freemangordon> but do we need gsmmux?
<tmlind> gnss should be doable over qmi too
<freemangordon> cool
<tmlind> you can use the tool i did to dump and diff the modem nvram and attempt to replicate the same with qmi commands
<freemangordon> wait, WTYM? qmi interface is standard
<tmlind> alsa needs some notification, but that might be doable with the audiocalld or whatever the newish daemon was called
<tmlind> motorola implemented some custom calls that likely just tweak some nvram options and the modem firmware then sets things as requested
<tmlind> the qmi calls also mostly just set nvram values fyi
<freemangordon> are you sure motorola implementd custom qmi calls? what for?
<tmlind> for their audio setup i think
<freemangordon> I just doubt that motorola had to do it besides perhaps some FW download
<freemangordon> hmm
<freemangordon> ok, will see
<tmlind> anyways, you can diff the nvram values with https://github.com/tmlind/tcmdrw
xmn has quit [Quit: ZZZzzz…]
<tmlind> maybe you can dump the nvram over qmi too, don't know
<freemangordon> me neither
<freemangordon> qmicli is far from being complete
<freemangordon> but I found qmi specs over the inet
<tmlind> anyways, if you got the qmi notifications working for incoming sms, we can get pretty far with not gsmmux stuff
<freemangordon> yes, I sent sms and saw the notification
<tmlind> great
<freemangordon> tmlind: https://pastebin.com/AAHkamJQ
<tmlind> anyways, if we end up adding the gsmmux stuff to ofono later on, it should be implemented with raw read and write using ell
<freemangordon> but we still need the kernel driver, right?
<tmlind> no need to try to use atmodem stuff for it
<tmlind> right, kernel driver or the userspace tool that won't work with pm
<tmlind> whatever attach it was called
<freemangordon> ok I lack teh details here
<tmlind> cool nice to hear you figured out the missing notifications
<tmlind> anyways, i agree with you, let's try to use mainline ofono with qmi where possible and then patch in the gsmmux if and when needed
<freemangordon> :nod:
duuude has quit [Ping timeout: 256 seconds]
<freemangordon> I'll try to prepare and send patches for upstreaming of motmdm
<tmlind> for the voice call alsa driver, don't recall if we need to do some gsmmux modem commands beyond mixer and dtmf
<freemangordon> I have no clue
<freemangordon> but anyways we need qmi voice calls working in upstream first
<tmlind> it could be we're only configuring the mcbsp and pmic for the tdm use for voice call
<freemangordon> mhm
<freemangordon> but you do that in the driver
<tmlind> yeah
<freemangordon> which looks like a hack as well, but that's another story :)
<tmlind> right, it should be the whatever voicecallaudiod doing it nowadays and that likely already has qmi support
<freemangordon> ok, thanks! will keep you informed on the progress.
<freemangordon> bbl
<tmlind> ok great, ttyl
<sicelo> note that voicecallaudiod might not have a future ... there's talk to drop it once pipewire can handle some of those things by itself
duuude has joined #maemo-leste
<tmlind> oh ok good to know, anyways nice to hear there's some kind of userspace path for dealing with these things
xmn has joined #maemo-leste
xmn has quit [Quit: ZZZzzz…]
<duuude> U-Boot with kernel 2.6.28-omap1 won't get installed
<duuude> it violates "third party package policy"
<duuude> what to exactly do now?
<duuude> Wizzup freemangordon
<duuude> it wasn't like this the year before or at least I don't remember such a thing.
<sicelo> i said install it with apt. did you try that?
xmn has joined #maemo-leste
<duuude> sicelo: I probably wasn't online when you said that
<duuude> though, I found an apt command from postmarketos' gitlab issues which also didn't work
xmn has quit [Quit: ZZZzzz…]
<sicelo> what command was it?
<duuude> apt install uboot-menu? was something like this
xmn has joined #maemo-leste
<sicelo> maybe share the link :-) ... there's no 'apt install' in maemo fremantle
<duuude> I don't know what was the problem the first time (I had entered "apt-get") but it worked this time: apt-get install u-boot-flasher u-boot-tools u-boot-bootimg
<duuude> sicelo: how to enable on-screen keyboard? I can't enter ">"
<duuude> these weren't problems the first time
<sicelo> what device?
<duuude> n900
<duuude> on the terminal
<sicelo> Fn+Ctrl, i think ... the standard way in Fremantle
xmn has quit [Quit: ZZZzzz…]
<freemangordon> tmlind: why not using AT interface for voice calls?
<freemangordon> I tried and got NO CARRIER, but this could be because I didn;t set-up the modem properly
parazyd has joined #maemo-leste
<duuude> I got stuck in "Welcome to Leste"
<duuude> it doesn't seem to take input
<duuude> it somehow went away, but looking frozen isn't good ux
<sicelo> i think on first boot, N900 just can't handle the amount of stuff happening in the background. using a fast SD card helps somewhat
<Wizzup> freemangordon: great @ ofono
sarah_ has joined #maemo-leste
<sarah_> duuude: see leste n900 wiki: https://leste.maemo.org/Nokia_N900#Tips_.2F_Tweaks (SD card and first boot)
sarah_ is now known as arno11
arno11 has left #maemo-leste [#maemo-leste]
arno11 has joined #maemo-leste
duuude has quit [Ping timeout: 268 seconds]
<arno11> btw "Welcome to Leste" seems to be a problem on N900 and a bit annoying for users
<arno11> if you click nowhere for at least 3 min once H-D is visible, everything is fine then. Otherwise N900 is slowing down a lot and users think Leste is really slow and unusable on N900...
<Wizzup> we could have a splash screen, or ry to emit the h-d is ready signal later
duuude has joined #maemo-leste
<arno11> a splash screen could be cool
uvos__ has joined #maemo-leste
<arno11> btw there is quite a similar issue with 'pin entry code' applet: N900 is unusable until the applet appears on the screen. Not a major concern but also annoying for new users.
<arno11> bbl
arno11 has left #maemo-leste [#maemo-leste]
xmn has joined #maemo-leste
diejuse has joined #maemo-leste
duuude has quit [Ping timeout: 268 seconds]
duuude has joined #maemo-leste
<duuude> sicelo, Wizzup: addition of a text "(the freeze is normal)" could be nice.
<duuude> would leste dry up the battery to the last second like before?
eval has quit [Ping timeout: 256 seconds]
diejuse has quit [Quit: Client closed]
gnarface has quit [Ping timeout: 256 seconds]
nohit has quit [Ping timeout: 246 seconds]
eval has joined #maemo-leste
nohit has joined #maemo-leste
eval has quit [Ping timeout: 268 seconds]
gnarface has joined #maemo-leste
eval has joined #maemo-leste
antranigv_ has joined #maemo-leste
antranigv has quit [Ping timeout: 240 seconds]
TheTechRobo has quit [Ping timeout: 264 seconds]
eval has quit [Ping timeout: 256 seconds]
antranigv_ is now known as antranigv
TheTechRobo has joined #maemo-leste
eval has joined #maemo-leste
ceene has quit [Ping timeout: 260 seconds]
nela has quit [Ping timeout: 264 seconds]
diejuse has joined #maemo-leste
uvos__ has quit [Quit: Konversation terminated!]
uvos__ has joined #maemo-leste
<uvos__> the greeting text is common to all devies
<uvos__> only the n900 has issues so its not so easy
<uvos__> if it really is unresponsive for 3 minutes i dont think a splash screen is enough really
<uvos__> that calls for at least a thobber otherwise people will think its frozen
diejuse has quit [Quit: Client closed]
diejuse has joined #maemo-leste
<tmlind> freemangordon: well the at interface is buggy from what i recall..
<tmlind> freemangordon: also, if you're booting to bp mode with m-l kernel, the gsmtty kick might cause the qmi notifications to happen for you on your x86 vm..
<uvos__> tmlind: sweet :)
<sicelo> for the first boot on N900, maybe let's introduce a lysti LED pattern, in a fast heartbeart, to signal to user that *something* is happening
<tmlind> i've moved to mostly automated git email scripts, currently missing option to add a manual cc list..
<bencoh> sicelo: why not a "please wait while bootstrapping" message on first boot then?
<sicelo> because, ... 17:11 < uvos__> that calls for at least a thobber otherwise people will think its frozen
<bencoh> ah, so you mean both, nevermind
nela has joined #maemo-leste
<uvos__> a pattern would work yeah
nela has quit [Quit: bye]
nela has joined #maemo-leste
ungeskriptet has quit [Ping timeout: 252 seconds]
ungeskriptet has joined #maemo-leste
diejuse has quit [Quit: Client closed]
<sicelo> freemangordon: "I want to discuss with
<sicelo> the author of QMI voice calls support in PMOS" ... who's that?
<freemangordon> tmlind: I am booting from power-off and d4 is attached to my ubuntu laptop :)
TheTechRobo has quit [Ping timeout: 256 seconds]
<freemangordon> I am not sure what you meant
TheTechRobo has joined #maemo-leste
<freemangordon> qmi notifications didn't happen in that setup until I changed to /dev/cdc-wdm0
<freemangordon> this https://pastebin.com/qwnjSXmG is how things look like with upstream ofono and d4 modem attached in BP only mode
<freemangordon> only qmi interface is used, not AT, no MUX (gsmtty)
<freemangordon> not sure how to test gps though
<freemangordon> BTW, what is the 'official' name of the modem? m6600?
diejuse has joined #maemo-leste
<uvos__> freemangordon: if you use bp mode from the bootloader the deivce routes out the usb interface of the modem
<uvos__> freemangordon: if you then boot the leste kernel it might affect the result because it uses the gsmtty interface
<uvos__> is what he is saying
<freemangordon> uvos__: I understand that, but I think the plan is to try to not use gsmtty. Also, I doubt I will lose notifications in qmi because of gsmtty. However, will test on the device in couple of minutes and will see
<freemangordon> also, we'll have issue with notifications as currently I am not aware of any way to disable them (on qmi interface that is) outide of ofono
<freemangordon> and ofono does not expose any interface for doing that
<uvos__> sure @plan, no idea at if gsmtty use by ofono on device affects qmi connected to the host
<freemangordon> it should not, but... who knows :)
<freemangordon> oh, but ofono *does not* use gsmtty
<freemangordon> well, the upstream one
<freemangordon> not what we have currently in leste
<uvos__> sure but what we have in leste ist running in this configuration
<uvos__> also mce kicks gsmtty
<freemangordon> but I will replace ofono on my d4 with upstream one
<uvos__> right ok
<uvos__> mce still kicks gsmtty iirc
<freemangordon> yeah
<freemangordon> do disable RSSI on display off, right?
ungeskriptet has quit [Quit: The Lounge - https://thelounge.chat]
<uvos__> yeah and it just kicks it too
<freemangordon> why?
<uvos__> for some reason doing open() and then close() on the if gets the modem "unstuck"
<uvos__> the modem gets stuck in some wierd state where it uses more power
ungeskriptet has joined #maemo-leste
ungeskriptet has quit [Client Quit]
<uvos__> for reasons unkown
<uvos__> as a workaround we do that every 10 min or so
ungeskriptet has joined #maemo-leste
duuude has quit [Ping timeout: 272 seconds]
uvos__ has quit [Ping timeout: 264 seconds]
<freemangordon> uvos__: by 'modem' you mean AT modem, right?
<tmlind> freemangordon: so best to run your tests with no ofono running on d4 while testing :)
<tmlind> freemangordon: the modem name is mdm6600
<freemangordon> tmlind: why no ofono (upstream)?
<freemangordon> it does not touch either AT modem (/dev/ttyUSBn) or gsmmux
<tmlind> freemangordon: only run ofono on your x86 during the test, not on d4 to avoid d4 patched ofono kicking the usb interface
<freemangordon> nothing more to test on x86
<freemangordon> and I will replace ofono on d4 with upstream one
<tmlind> ok yeah interesting to see what happens :)
<freemangordon> mhm
<freemangordon> besides missing voice call it should work, in theory
<tmlind> Wizzup: i think your usb hang may be reproducable with something like this: mosh or ssh over usb doing dmesg -w, then unblank the lcd
<tmlind> so usb traffic while tiler doing something maybe?
<tmlind> at least i can hang the device pretty easily with that, no oops logs so far though
uvos__ has joined #maemo-leste
diejuse has quit [Quit: Client closed]
<tmlind> hehe yup, i've had two of these now:
<tmlind> dmm 4e000000.dmm: timed out waiting for done
<tmlind> omapdrm omapdrm.0: could not unpin pages: -110
<tmlind> dmm 4e000000.dmm: timed out waiting for done
<tmlind> omapdrm omapdrm.0: could not pin: -110
<tmlind> dmm 4e000000.dmm: timed out waiting for done
<tmlind> PVR_K:(Error): DmaBufImportAndAcquirePhysAddr: dma_buf_map_attachment failed: -110
<tmlind> PVR_K:(Error): PVRSRVMapDmaBufKM: Failed to get dma-buf phys addr
<tmlind> PVR_K:(Error): PVRSRVMapDmaBufBW: Failed to map dma-buf handle
<tmlind> ...
<tmlind> and then bad things happen and device will reboot quit soon
diejuse has joined #maemo-leste
<tmlind> i'll try enabling i878 workaround in omap_dmm_tiler.c, let's see if that helps
<freemangordon> ok, upstream ofono (with motmdm ported) works in leste, besides there is some issue with reporting RAT
<tmlind> cool
<tmlind> enabling i878 workaround does not help with the "timed out waiting for done" errors
<tmlind> freemangordon: so you got sms receiving working with just qmi?
<freemangordon> yes
<tmlind> freemangordon: and you get a qmi notification on disconnecting from a network with tin foil? :)
<freemangordon> tmlind: seems only RSSI and SMS notifications work properly so far
<tmlind> freemangordon: ok
<freemangordon> but this is a matter of fixing here and there, not some general issue
<tmlind> ok great
<freemangordon> hmm... actually
<freemangordon> I had to kick it
<freemangordon> maybe gsmtty behaves
<freemangordon> anyway, have to run now, bbl
<tmlind> yeah me too later
nela has quit [Ping timeout: 240 seconds]
diejuse has quit [Quit: Client closed]
diejuse has joined #maemo-leste
akossh has joined #maemo-leste
nela has joined #maemo-leste
k1r1t0_ has joined #maemo-leste
arno11 has joined #maemo-leste
diejuse has quit [Quit: Client closed]
arno11 has left #maemo-leste [#maemo-leste]
nela has quit [Quit: Ping timeout (120 seconds)]
nela has joined #maemo-leste
<freemangordon> tmlind: if I rmmod n_gsm, would that release gsmtty?
Langoor has quit [Ping timeout: 264 seconds]
diejuse has joined #maemo-leste
nela has quit [Ping timeout: 256 seconds]
nela has joined #maemo-leste
Juest has quit [Ping timeout: 255 seconds]