| kabouik | Wizzup: https://www.ebay.com/itm/334534048742 (good old Pro1 with msm8998, the one that boots mainline (with touch noise) | 00:57 |
|---|---|---|
| kabouik | The seller is willing to sell for $500 + shipping, seems in mint condition | 01:00 |
| kabouik | (Can be contacted on Discord directly) | 01:02 |
| kabouik | He's on the Pro1 server | 01:02 |
| kabouik | They* | 01:02 |
| buZz | i'm getting a green screen on a SDL application i compiled on the droid4 | 01:13 |
| buZz | might that be the same issue why we made our own libsdl some time ago? | 01:13 |
| Wizzup | kabouik: let me check it out | 09:28 |
| Wizzup | buZz: what app, what is the exact problem? | 09:28 |
| kabouik | If you are interested Wizzup, let me know, I think I can hook you up with the seller and avoid the eBay auction circus | 10:18 |
| Wizzup | kabouik: yes, I am interested I think | 11:01 |
| kabouik | Great, let me contact them and I'll be back to you when they reply | 11:29 |
| kabouik | Can I give them an email or another way to contact you besides IRC? I'm not sure the seller uses IRC> | 13:12 |
| Wizzup | pm'd you | 13:34 |
| Wizzup | any reason we don't just package the maemo ringtones? cc freemangordon | 13:34 |
| Wizzup | import the maemo ringtones package | 13:34 |
| Wizzup | ok, I think I know I how I can make the 3g data wait for the activation to finish | 13:42 |
| freemangordon | Wizzup: well, some legal reason? | 14:00 |
| freemangordon | but meh... | 14:00 |
| freemangordon | lets do it | 14:00 |
| Guest24 | What is the best forum to ask how to get connected to internet with 2G/3G with Leste? | 14:12 |
| Guest24 | I asked here: https://talk.maemo.org/showthread.php?p=1574542 | 14:16 |
| Guest24 | only helpful answer was to come ask here. | 14:17 |
| freemangordon | Guest24: from the connections menu? | 14:19 |
| freemangordon | Wizzup: ^^^ | 14:19 |
| Guest24 | Settings->Connections menu only define Wifi-Connections | 14:21 |
| Guest24 | and example if I start Application Manager and try to use connection. and come Select connection menu it shows No saved connections avaiblable. | 14:25 |
| freemangordon | Guest24: please wait for Wizzup to comment | 14:27 |
| Guest24 | ok..thanks. | 14:38 |
| Guest24 | I continue lurking this channel thru irclog | 15:23 |
| norayr | can someone share a link about martin leaving the pp community? | 17:11 |
| norayr | oh, let me search on fedi. | 17:12 |
| humpelstilzchen[ | It was on HN yesterday | 17:13 |
| dsc_ | https://lobste.rs/s/56hsi1/why_i_left_pine64 | 17:23 |
| dsc_ | eh | 17:23 |
| dsc_ | https://blog.brixit.nl/why-i-left-pine64/ | 17:23 |
| _uvos_ | Wizzup: screen timeout works fine for me | 17:33 |
| _uvos_ | are you sure you waited >1min? | 17:33 |
| _uvos_ | please note that when using tklock timeouts <1min are broken | 17:33 |
| _uvos_ | because of a fundamental desgin defficancy in freemantle systemui-mce dbus interfaces | 17:34 |
| _uvos_ | freemangordon: your scenario with the alarm would work fine | 17:35 |
| freemangordon | _uvos_: how is that? | 17:36 |
| _uvos_ | as charge-mode will exit on rtc alarm is a special status and a script runs | 17:36 |
| _uvos_ | this script currently just runs the dfault runlevel | 17:36 |
| _uvos_ | (ie boots) | 17:36 |
| freemangordon | hmm... | 17:36 |
| _uvos_ | and the alarm will then fire | 17:36 |
| _uvos_ | ofc it should boot some other runlevel | 17:37 |
| _uvos_ | (that currently duesent exist) | 17:37 |
| _uvos_ | that just shows the alarm | 17:37 |
| freemangordon | sure, but I am still not convinced you understand the use-case | 17:37 |
| freemangordon | anyway | 17:37 |
| _uvos_ | i dont see how you can do better | 17:37 |
| freemangordon | how does charge-mode knows it was rtc alarm power-on? | 17:37 |
| freemangordon | *know | 17:38 |
| _uvos_ | it checks when the rtc was set | 17:38 |
| freemangordon | when in fact it was USB cable connect that turned the device on | 17:38 |
| freemangordon | ok lemme explain the sequence again: | 17:38 |
| _uvos_ | if you mean when a alarm fires while in charge mode | 17:39 |
| _uvos_ | again it reads the rtc alarm | 17:39 |
| _uvos_ | and boots the next runlevel at that time | 17:39 |
| freemangordon | 1. power-off because of flat battery | 17:39 |
| freemangordon | 2. power-on because of electricity is restored | 17:39 |
| freemangordon | 3. charge mode | 17:39 |
| freemangordon | 4. rtc alarm is due | 17:39 |
| _uvos_ | works | 17:39 |
| freemangordon | ok | 17:40 |
| _uvos_ | Welle except leste dosent set rtc | 17:40 |
| _uvos_ | and rtc dosent work on d4 | 17:40 |
| _uvos_ | (no driver)p | 17:40 |
| _uvos_ | but thats not charge modes fault | 17:40 |
| freemangordon | well, how do you know it works then? | 17:40 |
| _uvos_ | i dont | 17:40 |
| _uvos_ | the code is there | 17:40 |
| _uvos_ | but its untested | 17:40 |
| freemangordon | maybe you mean "it should wotk, in theory"? | 17:40 |
| freemangordon | ok | 17:40 |
| _uvos_ | ok | 17:40 |
| freemangordon | ok, so the only usecase thats handled incorrectly is reboot, right? | 17:41 |
| _uvos_ | yess | 17:41 |
| freemangordon | ok | 17:41 |
| _uvos_ | well and wdt rebbot | 17:42 |
| freemangordon | yeah, that's not good | 17:42 |
| buZz | Wizzup: i'm trying moonlight-embedded | 17:42 |
| freemangordon | I think we shall support boot reason at some point | 17:42 |
| buZz | it seems to connect, mousecontrols from touch work, but screen is flat green | 17:42 |
| _uvos_ | supporting bootreason is pretty hard | 17:48 |
| _uvos_ | since its nonstandart | 17:49 |
| _uvos_ | we would need some scripting interface | 17:49 |
| _uvos_ | and the current fallback would still be needed | 17:49 |
| _uvos_ | for it we could fix clean reboots by telling charge-mode about it on shutdown | 17:50 |
| mighty17[m] | tmlind: I'm trying to clean up and bring these patches into ml, for which i have to change location of twl4030-power from mfd to drivers/power, it wants me to update the maintainers, so should i do it myself? https://lore.kernel.org/lkml/1459279341-17389-4-git-send-email-contact@paulk.fr/ | 18:15 |
| buZz | patch 4 of 8? dont you need the others aswell then? | 18:26 |
| mighty17[m] | buZz: Nope | 18:27 |
| mighty17[m] | The others are renaming if twl4030 to twl which isn't needed according to a comment | 18:28 |
| mighty17[m] | And patch 1 is related to pdta which is dropped | 18:28 |
| buZz | ah, ok | 18:32 |
| buZz | what device has twl4030 shutdown issues exactly? | 18:33 |
| mighty17[m] | buZz: Ah no issues, I'm adding support for twl6030 shutdown | 18:37 |
| mighty17[m] | Well the twl4030 driver is in mfd while it should be in power/reset | 18:37 |
| mighty17[m] | Thus i was asking | 18:37 |
| buZz | twl6030 is also a charger, it seems? | 18:38 |
| mighty17[m] | It's a pmic :) | 18:38 |
| buZz | and 'does usb otg'? :O | 18:38 |
| buZz | 17 channel ADC, gee | 18:38 |
| mighty17[m] | buZz: That does require charger support to give the power | 18:39 |
| buZz | i guess? seemingly it generates power for the OTG aswell | 18:39 |
| mighty17[m] | buZz: Hm that's unlikely | 18:40 |
| mighty17[m] | Where'd you find that | 18:40 |
| buZz | https://www.ti.com/product/TWL6030 | 18:46 |
| buZz | well https://www.ti.com/product/TWL6030#features | 18:46 |
| buZz | > Boost mode operation for USB OTG | 18:46 |
| buZz | > USB OTG module | 18:46 |
| buZz | > 3.3 V @ 35 mA USB LDO | 18:46 |
| mighty17[m] | ah right | 18:53 |
| mighty17[m] | well its the pmic tho :) dunno how that'd work | 18:53 |
| mighty17[m] | https://lore.kernel.org/lkml/1459279341-17389-7-git-send-email-contact@paulk.fr/ also here should i rename twl4030-pwrbutton to twl-pwrbutton? | 18:53 |
| buZz | mighty17[m]: you're mixing up two chips? | 18:55 |
| buZz | twl4030 vs twl6030? | 18:55 |
| mighty17[m] | nah nah | 18:55 |
| mighty17[m] | the implementation of twl4030 is generic enough that we can add support for 6030 on it | 18:55 |
| buZz | yeah it has no features | 20:23 |
| buZz | only 'poweroff' ? | 20:23 |
| buZz | or arent you talking about the driver | 20:23 |
| mighty17[m] | im confused | 20:26 |
| buZz | the patch you linked, implements no twl4030 features beside 'powering off device' | 20:27 |
| mighty17[m] | yup, the patch is focused on twl6030 not 4030 | 20:28 |
| buZz | yes the patch you linked, implements no twl6030 features beside 'powering off device' | 20:33 |
| buZz | i cant help you keep mixing the two names :P | 20:33 |
| mighty17[m] | ah yes lol | 20:34 |
| mighty17[m] | no other features yet | 20:34 |
| buZz | also doesnt help the patch is poor, and changes more lines just for 'style' | 20:35 |
| buZz | also its 6 years old? :O | 20:35 |
| mighty17[m] | yeah :( | 20:36 |
| buZz | heheh and inside their twl-pwrbutton.c its named twl4030-pwrbutton.c | 20:37 |
| mighty17[m] | buZz: well i aint applying thw twl4030 -> twl name changes | 20:37 |
| buZz | (C) nokia 2009 :D | 20:37 |
| mighty17[m] | only the driver mainly | 20:37 |
| mighty17[m] | yeah its just renamed that file :P | 20:37 |
| buZz | well, that renaming is to centralize the code that applies to both twl4030 and twl6030 | 20:37 |
| buZz | so the twl6030 device your working on doesnt have powerbutton on it? | 20:38 |
| mighty17[m] | it does | 20:43 |
| mighty17[m] | <buZz> "well, that renaming is to..." <- correct :D | 20:43 |
| buZz | so you dont want the twl4030 powerbutton code to work on your twl6030? | 20:44 |
| * buZz confused | 20:44 | |
| Wizzup | @guest24 - I'll try to answer on the forum thread later tonight | 21:49 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!