| *** futpib has quit IRC | 01:28 | |
| *** Pali has quit IRC | 03:39 | |
| *** LauRoman has joined #maemo-ssu | 03:45 | |
| *** LauRoman|Alt has quit IRC | 03:46 | |
| *** infobot has quit IRC | 09:17 | |
| *** macmaN has quit IRC | 10:46 | |
| *** sparetire_ has quit IRC | 11:19 | |
| *** futpib has joined #maemo-ssu | 11:34 | |
| *** Pali has joined #maemo-ssu | 11:56 | |
| *** LauRoman has quit IRC | 12:24 | |
| Pali | merlin1991: ping | 12:42 |
|---|---|---|
| Pali | merlin1991: what to do with TI DSP codecs? | 12:42 |
| kerio | host em | 12:47 |
| kerio | yolo | 12:47 |
| kerio | how do you uninstall the old codecs, though? i thought HAM didn't like Conflicts/Breaks | 12:48 |
| Pali | kerio: package upgrade | 12:53 |
| Pali | normally | 12:53 |
| kerio | yeah but they're different packages | 12:53 |
| kerio | aren't they | 12:53 |
| Pali | ?? | 12:53 |
| kerio | aren't you repackaging the HARM codecs | 12:54 |
| kerio | er | 12:54 |
| kerio | rehosting | 12:54 |
| Pali | repackage of course | 12:54 |
| kerio | meh | 12:54 |
| * kerio is disappoint | 12:54 | |
| Pali | hm? | 12:54 |
| kerio | well i'll have to uninstall the real packages | 12:54 |
| Pali | I added conflics & replaces line against harmattan packages | 12:55 |
| Pali | so if you use apt-get upgrade for upgrading it should work | 12:55 |
| kerio | yay ^_^ | 12:55 |
| *** arcean has joined #maemo-ssu | 13:05 | |
| Pali | merlin1991: more extras applications depends on package liblzo2-2 which is only in nokia SSU repository | 13:12 |
| Pali | that package liblzo2-2 is open source library, so can you upload it directly to maemo extras? | 13:12 |
| Pali | it is also in Fremantle SDK | 13:13 |
| Pali | we just need same DEB version (sha/md5 sum) so once it appear in extras people will not receive update | 13:13 |
| DocScrutinizer05 | did you check the nokia liblzo is identical with the FOSS version? | 13:31 |
| Pali | DocScrutinizer05: seems to be: http://repository.maemo.org/pool/maemo5.0/free/l/lzo2/ | 15:15 |
| Pali | it is under GPLv2 license | 15:16 |
| Pali | Sicelo, kerio: new version of getbootstate is in cssu-devel | 15:16 |
| Pali | ready for testing | 15:16 |
| DocScrutinizer05 | Pali: great! | 15:17 |
| Pali | bootmenu, recoverymode are working and also supports stock kernel, kernel-power and 4.2-rc1 kernel | 15:17 |
| DocScrutinizer05 | and R&D mode? ;-) | 15:17 |
| Pali | infrastructure for booting upstream kernel is there | 15:17 |
| Pali | DocScrutinizer05: both normal and R&D mode | 15:18 |
| DocScrutinizer05 | with LEDs? | 15:18 |
| Pali | I reverted to old nokia behaviour of that keyboard led | 15:18 |
| DocScrutinizer05 | :-))) | 15:18 |
| kerio | Pali: does 4.2-rc1 do anything | 15:18 |
| Pali | kerio, see #neo900 | 15:18 |
| DocScrutinizer05 | Pali: good man | 15:18 |
| Pali | http://irclog.whitequark.org/neo900/2015-07-11 | 15:19 |
| kerio | you can uninstall the package that provides the welcome screen | 15:19 |
| Pali | I'm not going to break Maemo system :-) | 15:19 |
| Pali | basically what is supported by kernel now should work on Maemo | 15:20 |
| Pali | we just need more hackers and testers | 15:21 |
| *** infobot has joined #maemo-ssu | 15:22 | |
| *** ChanServ sets mode: +v infobot | 15:22 | |
| Pali | getboostate and preinit now should work even if they do not have special nokia /sys and /proc and /dev files | 15:22 |
| Pali | if raw file /proc/atags is provided, getboostate parse it and read information from that | 15:22 |
| Pali | if even if /proc/atags is not there, then default values are used (bootmode=normal, bootreason=powerkey, etc) | 15:23 |
| Pali | sane default values instead MALF | 15:23 |
| Pali | MALF is when kernel provides interface to read data && data are bad | 15:24 |
| kerio | do i yolo upgrade | 15:40 |
| kerio | i don't think i yolo upgrade | 15:40 |
| kerio | meh whatever | 15:40 |
| kerio | YOLO | 15:40 |
| Sicelo | thanks pali. will test :) | 15:57 |
| kerio | Pali: how can i add an entry to the uboot menu to power off? | 16:14 |
| Pali | kerio: uboot does not have code to power off rx51 board | 16:15 |
| kerio | ...but i did "reset" and it powered it off | 16:15 |
| Pali | if you have time, you can implement power of function | 16:15 |
| Pali | reset just reset board | 16:15 |
| kerio | i swear to god it's powered off | 16:16 |
| kerio | i can turn it on with the button | 16:16 |
| kerio | it does the light thing | 16:16 |
| Pali | maybe nolo decided to poweroff after reboot | 16:16 |
| kerio | fucking magnets | 16:16 |
| kerio | how do they work | 16:16 |
| kerio | Pali: haven't tested r&d mode but recovery console and backupmenu are both accessible | 16:17 |
| Pali | ok | 16:17 |
| kerio | fuck i lost the time | 16:17 |
| Sicelo | loose battery? | 16:22 |
| kerio | no, resetting uboot :> | 16:23 |
| Sicelo | has never happened to me .. with reset | 16:23 |
| Pali | so... who is going to implement power off in uboot? :-) | 16:27 |
| Pali | just need to reuse code from linux kernel... | 16:27 |
| Pali | it is some i2c call to twl4030 chip | 16:27 |
| * Sicelo points at Pali :D | 16:39 | |
| drathir | Pali: nice gz... | 17:17 |
| DocScrutinizer05 | Pali: uboot knows to do I2C, no? even from "commandline" | 17:39 |
| Pali | yes, uboot support i2c | 17:40 |
| Pali | do not know if from cmdline | 17:40 |
| DocScrutinizer05 | how's "charging" implemented? | 17:40 |
| Pali | but code from linux kernel should be easily to reused | 17:40 |
| Pali | no charging is implemented | 17:40 |
| DocScrutinizer05 | duh! | 17:40 |
| Pali | just I do not have time for it | 17:41 |
| kerio | i don't think we need charging in uboot | 17:41 |
| kerio | beyond the basic flatbat recovery | 17:41 |
| Pali | both should be simple, just i2c_read i2c_write | 17:41 |
| DocScrutinizer05 | flatbat recovery is in hw | 17:41 |
| kerio | exactly | 17:41 |
| DocScrutinizer05 | it doesn't fix the no-flashing deadlock | 17:41 |
| kerio | yeah but if your uboot is working you can load rescueOS from a µsd | 17:42 |
| DocScrutinizer05 | thus proper charging in uBoot would be extremely nice | 17:42 |
| DocScrutinizer05 | yes, that's a comlicated but working method | 17:42 |
| kerio | now, ACT_DEAD fully implemented in uboot would be cool | 17:42 |
| kerio | Pali: does your uboot load a script from microsd if the emmc is hosed? | 17:43 |
| DocScrutinizer05 | uBoot already is 95% "ACT_DEAD" | 17:43 |
| kerio | DocScrutinizer05: no alarms, though | 17:44 |
| DocScrutinizer05 | yep | 17:44 |
| DocScrutinizer05 | an alarm elapsing durning uBoot active might go unnoticed | 17:45 |
| kerio | Pali: also, can uboot do stuff in the background? | 17:45 |
| kerio | or would the charging thing be a separate boot entry | 17:45 |
| DocScrutinizer05 | good point, does uBoot "OS" support multitasking? | 17:46 |
| kerio | DocScrutinizer05: it's kind of irrelevant, though | 17:46 |
| kerio | if you *are* booting something, you'll lose control over bq24k very quickly | 17:46 |
| DocScrutinizer05 | yep | 17:46 |
| kerio | if you're not, you don't need the charging to be backgrounded | 17:46 |
| DocScrutinizer05 | :nod: | 17:47 |
| DocScrutinizer05 | anyway afaik uBoot *can* do "multitasking" at least to tickle watchdog | 17:47 |
| kerio | now... should the behaviour of uboot started in ACT_DEAD mode be to start charging, or to boot linux? | 17:48 |
| DocScrutinizer05 | define >>uboot started in ACT_DEAD mode<< | 17:48 |
| kerio | charger plugged in | 17:48 |
| kerio | as opposed to pressing the power button | 17:49 |
| DocScrutinizer05 | charger plug in should not invoke uBoot menu automatically | 17:49 |
| kerio | so still pretend that uboot doesn't exist and boot the default OS? alright | 17:50 |
| Pali | kerio: bootmenu script is loaded only from MyDocs eMMC, but if there is no bootmenu script, uboot will pre-generate some menu entries to boot some uboot scripts or kernels from uSD and emmc | 19:23 |
| kerio | alright, close enough | 19:24 |
| Pali | DocScrutinizer05: do not know if uboot support normal multitasking, but there is something which "force" uboot to call watchdog function | 19:24 |
| Pali | which periodically kick watchdog | 19:24 |
| kerio | Pali: how powerful is uboot scripting? | 19:24 |
| Pali | so for charging, this function can be extended to reset also bq timer | 19:25 |
| kerio | can it do a for loop? | 19:25 |
| Pali | kerio: it is hush shell | 19:25 |
| Pali | IIRC there is while | 19:26 |
| DocScrutinizer05 | Pali: similar "watchdog" function would suffice for charging | 19:32 |
| DocScrutinizer05 | actually it's the watchdog timer in bq24150 that needs some handling, the rest is pretty simple | 19:33 |
| kerio | don't you need actual math | 19:42 |
| DocScrutinizer05 | nope, zilch | 19:42 |
| DocScrutinizer05 | http://talk.maemo.org/showthread.php?p=658278#post658278 | 19:43 |
| DocScrutinizer05 | while sleep 15; do i2cset -y -m 0x80 2 0x6b 0x00 0x80; done | 19:45 |
| DocScrutinizer05 | plus a few lines init before that | 19:46 |
| DocScrutinizer05 | init by const values | 19:46 |
| kerio | oh, is that just a slowish charge up to not quite full battery | 20:00 |
| *** RedW has quit IRC | 20:01 | |
| *** RedW has joined #maemo-ssu | 20:02 | |
| DocScrutinizer05 | that depends on init data | 20:57 |
| DocScrutinizer05 | i'd recommend 500mA USB current limit and a 4.1V batt end voltage and no charge termination current threshold | 20:58 |
| DocScrutinizer05 | unlress uBoot charging was a dedicated mode that can't accept any further commands, in which case I'd use the standard charge end threshold, and check for battery-full with "while [ $(i2cget -y 2 0x6b 0x00) = 0x90 ]..." then boot to linux after that, or shutdown | 21:01 |
| DocScrutinizer05 | particularly smart: check statuscode with $(i2cget -y 2 0x6b 0x00) and boot to linux when battery-full, shut down when other "error" caused stop of charging | 21:04 |
| DocScrutinizer05 | (other error) e.g. removal / unplug of charger | 21:05 |
| *** sparetire_ has joined #maemo-ssu | 21:26 | |
| *** arcean has quit IRC | 22:43 | |
| *** APic has quit IRC | 22:48 | |
| *** LauRoman|Alt has joined #maemo-ssu | 22:51 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!