IRC log of #maemo-ssu for Friday, 2013-03-29

DocScrutinizer05I had even told user about that fact, if usage() been defined anywhere ;-)00:02
keriohelp()00:02
DocScrutinizer05obviously it's implicitly defined by import getopts00:02
keriooh i misunderstood you00:02
kerioDocScrutinizer05: actually, no00:03
keriothat shit won't work00:03
keriothere should be a NameError whenever it reaches that point00:04
DocScrutinizer05o.O00:04
DocScrutinizer05nfc00:04
DocScrutinizer05as mentioned above... "stolen"00:04
DocScrutinizer05it did what I expected it to do00:04
DocScrutinizer05CBa about the rest00:04
*** _rd has quit IRC00:05
kerioDie temperature: 571.4 C00:07
kerio...hm00:07
kerioi dun goofd00:07
DocScrutinizer05oooh, did I already mention that I have no clue about python? ;-P00:07
*** jon_y has joined #maemo-ssu00:07
DocScrutinizer05o.O00:08
merlin1991I could help00:08
DocScrutinizer05>>registers["TEMP"] = registers["TEMP"] / 4 + 273.15<< looks about correct00:09
DocScrutinizer05err nope, actually not ;-P00:09
DocScrutinizer05registers["TEMP"] = registers["TEMP"] / 4 - 273.1500:09
kerio/o\00:09
* kerio is most definetely *not* a physicist00:09
DocScrutinizer05hehe00:09
DocScrutinizer05YAY, MT is alive!00:11
DocScrutinizer05UGH! and has way too much time at hand to write too long tmo posts ;-P00:11
merlin1991DocScrutinizer05: btw getopts is so oldfashioned00:16
merlin1991the cool kids use argparse these days ;)00:16
DocScrutinizer05mhm00:16
DocScrutinizer05maybe that's caused by the code I "stole" is some years old00:17
kerioi'm not quite sure argparse is in 2.5.200:17
kerionope, New in version 2.7.00:17
merlin1991afaik it's a pure python module, so you should be able to distribute it with your script for < 2.7 :D00:18
kerioit was added for python 3.2, it's probably full of py3kisms00:19
kerioand it barely runs on 2.700:19
merlin1991just adds to the fun ;)00:19
*** phr3akDom has joined #maemo-ssu00:21
*** Phr3D has joined #maemo-ssu00:24
*** Phr3D has quit IRC00:24
*** unclouded has joined #maemo-ssu00:24
keriomy name is Ozymandias, king of kings00:25
keriolook on my works, ye mighty, and despair!00:26
keriohttp://pastebin.mozilla.org/225495800:26
kerio(merlin1991: yes, i'm using zip instead of izip - add python3 to the repos instead of complaining)00:27
merlin1991oh shit00:27
merlin1991that print is evil :D00:27
merlin1991also not python3 save ;)00:27
keriowhy?00:27
kerioah right00:27
kerio2to3 will take care of that :P00:28
*** phr3akDom has quit IRC00:28
merlin1991actually building python3 should not be that hard00:28
merlin1991at least I've built it in sb2 quite some times already :D00:28
keriosharing is caring!00:29
merlin1991wasn't for maemo though00:29
keriomaemo is caring!00:29
keriomerlin1991: http://pastebin.mozilla.org/2254959 fixed00:29
kerioDocScrutinizer05: real men print like ^this00:29
merlin1991err you only added a comment00:30
merlin1991and imported print_function00:30
keriono, there's light green parentheses :)00:30
merlin1991ah00:31
merlin1991ninja parentheses00:31
merlin1991but you're fucked anyways00:31
merlin1991#!/usr/bin/env python2.700:31
kerioheh00:31
keriocan't quite fix that00:31
merlin1991true that :/00:32
kerioregardless of what archlinux says, python 3 should *not* be installed as /usr/bin/python00:32
*** BCMM has joined #maemo-ssu00:34
*** BCMM has quit IRC00:44
*** xes has quit IRC00:49
*** NIN101 has quit IRC00:57
*** Pali has quit IRC00:59
*** jon_y has quit IRC01:09
*** Martix_ has quit IRC01:13
*** LauRoman has quit IRC02:37
*** M4rtinK has quit IRC02:46
*** unclouded has quit IRC02:55
*** sunny_s has quit IRC02:56
*** sunny_s has joined #maemo-ssu03:00
*** Estel^ has quit IRC03:16
*** Estel_ has joined #maemo-ssu03:17
*** Estel_ has quit IRC03:17
*** Estel_ has joined #maemo-ssu03:17
*** arcean has quit IRC03:36
*** LaoLang_cool has joined #maemo-ssu04:12
*** kolp_ has joined #maemo-ssu04:12
*** kolp has quit IRC04:15
*** LaoLang_cool has quit IRC04:18
*** futpib has joined #maemo-ssu04:58
*** nox- has quit IRC05:29
*** unclouded has joined #maemo-ssu05:34
*** amiconn_ has joined #maemo-ssu05:37
*** amiconn has quit IRC05:37
*** amiconn_ is now known as amiconn05:37
*** DocScrutinizer05 has quit IRC06:03
*** DocScrutinizer05 has joined #maemo-ssu06:03
*** Milhouse has joined #maemo-ssu06:08
*** discopig has quit IRC06:37
*** discopig has joined #maemo-ssu06:38
*** discopig has joined #maemo-ssu06:38
*** M13 has joined #maemo-ssu06:49
*** futpib has quit IRC06:56
*** discopig has quit IRC08:06
*** discopig has joined #maemo-ssu08:06
*** discopig has quit IRC08:06
*** discopig has joined #maemo-ssu08:06
*** kolp_ has quit IRC08:17
*** Pali has joined #maemo-ssu08:38
*** freemangordon has quit IRC09:16
*** freemangordon has joined #maemo-ssu09:24
*** Martix_ has joined #maemo-ssu10:19
*** LauRoman has joined #maemo-ssu10:50
*** Martix_ has quit IRC10:55
*** Martix_ has joined #maemo-ssu10:58
kerioDocScrutinizer05: i'm not sure why i'm wasting time with this, but do you think that i should keep the raw registers somewhere, and store the converted data somewhere else?11:51
kerioShadowJK: why is the conversion of ILMD done with 913920 instead of 914000?12:01
keriooh i see, it's not really 914uVh, it's the high byte of 3.57uVh12:14
*** jon_y has joined #maemo-ssu12:18
*** futpib has joined #maemo-ssu12:21
*** NIN101 has joined #maemo-ssu12:45
*** unclouded has quit IRC12:49
*** futpib_ has joined #maemo-ssu12:57
*** futpib has quit IRC12:58
kerioah what the hell, "°" isn't ascii?13:05
DocScrutinizer05man ascii13:05
DocScrutinizer05man iso_8859-113:07
DocScrutinizer05260   176   B0     °     DEGREE SIGN13:07
kerioso... it's not ascii :P13:08
kerioanyway, i'm parsing EEPROM too now13:09
keriois TAPER 102.8mA realistic?13:09
DocScrutinizer05http://privatepaste.com/b9d424a14d13:14
DocScrutinizer05haha, I been lazy and haven't decoded TAPER/AEE13:16
kerioyeah >:c13:16
keriois it called AEE?13:16
kerioit doesn't have a shorthand in the datasheet13:16
kerioi also don't know what to do with MODE and CTRL13:18
DocScrutinizer05mode and ctrl are really status registers only needed for writing to chip13:20
DocScrutinizer05you could e.g. reset the chip via those registers13:21
DocScrutinizer05but we have simpler methods for that ;-P13:22
keriothere's WRTNAC that seems useful13:23
DocScrutinizer05you'll have to study the datasheet to learn about the last secrets of bq27200 ;-)13:24
DocScrutinizer05yeah, WRTNAC could be very useful13:25
DocScrutinizer05dunno why I never investigated it. ShadowJK iirc said it doesn't work, I don't believe that13:25
DocScrutinizer05of course you need to stop bme before you do anything like that13:26
DocScrutinizer05because of conflicting I2C access and the commands to write to bq27200 mustn't get interrupted by bme reading from chip13:27
*** arcean has joined #maemo-ssu13:32
DocScrutinizer05kerio: btw RBI is bq27200's "backup-battery", my early-morning math says: current <1nA, buffer C: 100nF => buffer time >>100s during which bq27200 holds register content when battery removed13:53
DocScrutinizer05(programming bq27k EEPROM) you need 20..22V for that, applied for 10..100ms to pin10. Current needed: 15mA :-o14:06
DocScrutinizer05attention! EEPROM can get programmed only TEN times!14:08
DocScrutinizer05so a hw mod to integrate a prommer is probably a rather nonsensicel execise ;-)14:09
kerioShadowJK: why doesn't WRTNAC work?14:12
ShadowJKwrtnac?14:28
kerioin bq27k MODE14:28
keriolike, write new NAC to AR, set WRTNAC bit in MODE, set CTRL to magic number14:29
ShadowJKyeah, I've done that14:29
keriodoes it work?14:30
ShadowJKya14:31
ShadowJKnac gets the value from ar, rsoc/csoc is set to 100 and vdq goes high14:31
kerio"high"?14:33
ShadowJK114:34
kerioso it's basically something that you do right once you finish charging?14:34
kerioor... no, actually not14:34
kerioyou can do it wherever14:34
keriojust do a calib cycle right afterwards14:34
ShadowJKyes14:37
* DocScrutinizer05 curses insane ILMD - if they had chosen 100 instead 2000mAh, it could have learned-up to correct value during a single learning cycle. Restriction to 1/8 change is only for learn-down14:42
DocScrutinizer05that's what you get if you buy surplus chips left over from a really huge customer14:44
keriohaha14:44
keriowell, the easiest way to fix that is to make a 2Ah bl-5j14:44
kerio:P14:44
DocScrutinizer05:-D14:44
keriois there no restriction on learn-up?14:44
DocScrutinizer05according to datasheet, there's none14:44
keriowhy do people always have problems when calibrating those dual batteries?14:45
DocScrutinizer05which makes sense14:45
DocScrutinizer05nfc14:45
DocScrutinizer05do they?14:45
DocScrutinizer05I guess that's about bme "calibration"14:46
kerioShadowJK: could you confirm or deny?14:48
DocScrutinizer05stskeeps once told me he had a look at bme sourcecode and it made his eyes bleed and he felt an urge to kill himself. IIRC he also said Nokia has no inhouse competence regarding bme which would mean they outsourced it14:48
DocScrutinizer05bme evidently accessing register #48 of the 6 registers ob bq is another indication about quality of bme code X-P  (numbers made up)14:50
kerio#48?14:50
DocScrutinizer05yeah14:50
keriowhat's 48?14:50
DocScrutinizer05nonexistent XP14:50
keriobetter question, what's 48 in hex?14:50
DocScrutinizer05meh, maybe it been 0x4814:51
DocScrutinizer05numbers made up, see?14:51
keriostill RESERVED14:51
DocScrutinizer05no, this been of bq2415014:51
kerioi see14:51
DocScrutinizer05which actually has only 6 or 8 registers14:51
kerionice14:51
DocScrutinizer05iirc they wrap around14:52
DocScrutinizer05incomplete addr decoder14:52
DocScrutinizer05but that's probably no guaranteed property of the chip14:52
DocScrutinizer05usually with 6 registers, you have 0x0 .. 0x5 defined, 0x6 and 0x7 undefined, and 0x8 == 0x0 a.s.o14:54
DocScrutinizer05anyway with a patched i2c.ko we traced all bq24150 access, and bme accessed a register way out of the existing addr range14:55
DocScrutinizer05Nokia trusting this crap more than community driven efforts to do a bme replacement is pretty embarrassing14:58
DocScrutinizer05for Nokia, for us it's an insult14:58
DocScrutinizer05maybe they got a contract with a subcontractor that includes full liability for any mass recall and killed users, so I'd maybe forgive them for not wanting to touch it15:00
keriohmm, will setting NAC also set LMD?15:09
DocScrutinizer05most likely not15:11
keriobut is NAC used when calibrating?15:11
DocScrutinizer05which is what relativates the usefulness15:11
keriootherwise, that WRTNAC is kinda useless15:12
kerioeven from a manifacturer's point of view15:12
DocScrutinizer05I guess it's meant to get used for batteries with multicells with balanced charging, or sth like that15:13
DocScrutinizer05you could adjust the N900 bq27200 to match the real current capacity of a newly inserted battery15:13
DocScrutinizer05given you know what capacity this battery is at right at this moment15:14
DocScrutinizer05look, you got a spare battery with you that you know is 100% charged. Swapping batteries would leave your bq27200 at 10% or 0% or whatever your depelted battery been at15:15
keriooic15:15
DocScrutinizer05s/with/which/15:15
infobotDocScrutinizer05 meant: look, you got a spare battery which you that you know is 100% charged. Swapping batteries would leave your bq27200 at 10% or 0% or whatever your depelted battery been at15:15
DocScrutinizer05meh, no15:15
DocScrutinizer05wait, what did ShadowJK say?15:18
DocScrutinizer05<ShadowJK> nac gets the value from ar, rsoc/csoc is set to 100 and vdq goes high15:18
DocScrutinizer05means you set a certain NAC as 100% and start a valid learning cycle. Depleting your swappend in battery to EDV1 would learn the capacity of that new battery15:19
keriobut will it use the NAC you set as a starting point?15:20
DocScrutinizer05yes, starting point of rsoc/csoc to calculate TTE and %15:20
DocScrutinizer05after reaching EDV1 it will adjust due to measured coloumb that the battery delivered15:21
DocScrutinizer05so e.g setting NAC to 100mAh will make your battery display drop to 0% rather rapidly, then it stays there for a long while til EDV1 is reached, and at that point LMD will get set to actual measured total capacity during last discharge aiui15:23
DocScrutinizer05while setting NAC to 3000mAh will cause your device shutdown at capacity-display=60%15:24
DocScrutinizer05or rather, it first will jump from 60% to 0% at reaching EDV1, then it completes learning cycle, then it may shut down15:25
DocScrutinizer05kerio: all roger?15:26
kerioyeah15:26
DocScrutinizer05fine15:26
kerioit's still unclear to me if that can be used to get around the learn-down limits15:26
DocScrutinizer05no it can't15:26
DocScrutinizer05learn-down linitation is during storing new LMD to LMD-register. It checks for old content and if that's way higher than new content, it will adjust new content to 7/8 of old content, then store it to LMD-register15:28
DocScrutinizer05at least that's my take on it15:29
DocScrutinizer05iirc there is NO way to store a new arbitrary value to LMD15:29
DocScrutinizer05except copy ILMD from EEPROM to register15:30
keriobut you can only program the EEPROM 10 times :(15:30
DocScrutinizer05yep15:30
DocScrutinizer05the bq27x00 are meant for integration into battery pack. Nokia abused them15:31
DocScrutinizer05and if their EE were alert, they had programmed ILMD to 10015:32
DocScrutinizer05but probably they simply didn't care since the whole thing been meant to read out voltage and current-now only15:32
DocScrutinizer05they simply thought the rest of data was useless in that particular circuit anyway15:33
DocScrutinizer05but then they could've saved the buffer capacitor at BRI X-P15:34
DocScrutinizer05well, even Nokia EE are not inerrant15:36
ShadowJKor then they really meant to use a bigger battery15:42
ShadowJKor set it high enough that NAC would never reach 0, so that they could read nac once a minute to derive current now instead of reading AI every 5s15:44
keriohow about just using the chip for what it was, instead? :s15:45
DocScrutinizer05that would have required an alternative battery to the BL-5J15:47
DocScrutinizer05with bq27000 integrated15:47
DocScrutinizer05see openmoko gta02 smartbattery15:48
DocScrutinizer05*we* (openmoko) were able to pull that off15:48
DocScrutinizer05Nokia obviously been reluctant15:49
keriomaybe it was a good thing, though15:49
kerioBL-5Js are used in quite a lot of nokia phones15:50
keriothe 5800 is quite popular15:50
DocScrutinizer05http://maemo.cloud-7.de/share-service/20130329_001.jpg   DAMN!15:57
keriohaha15:58
DocScrutinizer05btw it's fully compatible to bp-5c15:58
kerioyou trolly you15:58
kerioalso, 1200mAh?15:58
DocScrutinizer05Nokia could've done same for BL-4J15:58
kerioit's... smaller than bl-5j, isn't it15:58
DocScrutinizer05err BL-5J15:58
DocScrutinizer05way smaller, that's why I uttered "DAMN"15:59
kerioi meant capacity-wise15:59
keriothe current bl-5js are 140015:59
DocScrutinizer051200mAh, bq27000 integrated, mechanically compatible to Nokia BP-5C15:59
*** jon_y has quit IRC15:59
*** jon_y has joined #maemo-ssu16:00
DocScrutinizer05well, that GTA02 battery is like 5 years old16:00
DocScrutinizer05and it actually had ~1200mAh, according to LMD16:01
ShadowJKbl-5c started out as 800mAh, iirc, and technolgy improvements have taken it further since :)16:02
*** kolp has joined #maemo-ssu16:04
DocScrutinizer05http://wiki.openmoko.org/wiki/Battery_Questions_and_Answers#Do_other_BL-5.2F6C_compatible_batteries_fit.3F16:06
*** Martix_ has quit IRC16:07
kerioi have no good way of doing two's complement in python :(16:09
kerioi need a 3-bit-wide datatype16:09
DocScrutinizer05huh?16:11
kerioto parse BOFF16:11
kerio(in python)16:11
DocScrutinizer05how about basic integer math and boolean?16:11
kerio...i know how to do that, i didn't /want/ to if there was a better way16:12
DocScrutinizer05hehe16:12
DocScrutinizer05sure there is (dunno if in python though): enum16:12
kerioi don't think there's a good way that lets you avoid checking the sign bit16:12
DocScrutinizer05you just need to normalize/mask the relevant bits out of your original 8/16bit value16:13
DocScrutinizer05If python can't do boolean AND / OR, you're probably in a pinch16:14
keriodon't be silly16:15
kerioit's not lua16:15
DocScrutinizer05you have to do integer math then, which becomes nasty16:15
kerio[0, 1, 2, 3, -4, -3, -2, -1][(bq27k["PKCFG"] & 0b00011100) >> 2]16:15
kerio:D16:15
DocScrutinizer05lua? meh! don't know lua to make sense of what you said16:15
keriolua has a single "number" type16:16
kerioand it's float16:16
DocScrutinizer05great16:16
kerio"In the interest of simplicity"16:16
DocScrutinizer05idiots16:16
DocScrutinizer05well, maybe they have a byte or word type then16:17
kerionope16:17
DocScrutinizer05ypur codeline above is puzzling16:18
kerioaccess the ((bq27k["PKCFG"] & 0b00011100) >> 2)th element of the [0, 1, 2, 3, -4, -3, -2, -1] list16:18
DocScrutinizer05I gather that's some special list operation stuff in python?16:18
keriolist access is hardly special16:18
DocScrutinizer05yeah16:18
DocScrutinizer05well, the only lists I ever use are linked lists ;-D16:19
DocScrutinizer05single or double linked16:20
keriofun fact: "list" in python is, internally, an auto-resizing array16:20
DocScrutinizer05yeah16:20
DocScrutinizer05think I heard about that16:20
keriothe only linked list i can think of in python is collections.deque16:20
DocScrutinizer05I seem to recall lists in python perform like my ass with obstipation16:22
keriowhen doing what?16:22
DocScrutinizer05when doing usual list operations like instantiate, append, insert, delete16:23
kerioinsert and delete aren't usual array operations16:23
DocScrutinizer05whatever, I seem to recall performance optimizations by factor 1000 over the whole program, by simply an experienced coder replacing some list crap in some newbie's python code by basic datatypes16:25
keriowrong datatypes tend to do that, yeah16:26
kerioalso, when you have dict, everything *does* look like a hashmap16:27
DocScrutinizer05but anyway, for this particular project it doesn't matter I guess16:28
DocScrutinizer05>> EDV detection has a dynamically adjusted delay of up to 21.5 s with RSOC ≥ 6% an ddown to 3 s when RSOC = 0%.<<16:32
*** _rd has joined #maemo-ssu16:34
DocScrutinizer05kerio: ^^^ is a scheme that's probably adoptable to bme-replacement shutdown-threshold-detection as well16:35
DocScrutinizer05at very least it gives a hind about minimum guard time to be used for that detection in bme-repl16:36
DocScrutinizer05hint*16:36
DocScrutinizer05minimum guard time is 30s16:37
DocScrutinizer05kerio: FYI: >>measured LMD value (for a learning cycle) is determined by *measuring* the *capacity* *delivered* from the battery from NAC = LMD (aka "full") until VOLT = EDV1, plus LMD/16 to account for the 6.25% capacity remaining below the EDV1 threshold.<<16:40
*** arcean_ has joined #maemo-ssu16:41
*** arcean has quit IRC16:41
*** futpib_ has quit IRC16:44
*** futpib_ has joined #maemo-ssu16:47
DocScrutinizer05kerio: actually LMD gets not calculated from NAC at all, there's obviously a dedicated computation register called Learning Count Register (LRC) for that16:49
DocScrutinizer05see "figure 4"16:50
*** _rd has quit IRC16:57
keriohrmpf, how should i store DCOFF?16:57
*** sunny_s has quit IRC17:06
DocScrutinizer05what's DCOFF?17:09
DocScrutinizer05nm17:09
DocScrutinizer05what do you mean by "how to store"?17:18
kerioit's a value that can be 0, C/2, C/4, C/817:18
DocScrutinizer05yes17:18
kerioi decided that i'm lazy and i'm actually storing it as 0, 1, 2, or 317:18
DocScrutinizer05I'd store it as 0, 0.5, 0.25, 0.12517:19
DocScrutinizer05or at very least as 1,2,3,817:20
DocScrutinizer05err17:21
DocScrutinizer05pretty inconvenient17:21
DocScrutinizer05let's put this straight: it's the current above which CAC starts to differ from NAC17:21
DocScrutinizer05it's calculated as percent of LMD, in ampere17:22
DocScrutinizer05there are the possible values 0%, 12.5%, 25%, 50%17:23
kerioclearly it's a job for fractions.Fraction17:25
keriobut actually no, floats represent binary fractions exactly :)17:26
kerioThe equation for programming the value is:17:27
kerioTOFF[3:0] = Design Temp Compensation Offset (°K) – 27317:28
keriodafuq17:28
kerioso... Design Temp Compensation Offset (°C) then17:28
DocScrutinizer05so for AI > LMD * ^^^DCOFF%, the compensated AI gets calculated as CAI = AI + ((AI - (AI * DCOFF%)) * (0.39% * DCGN))17:28
kerioit's 0 for the n900, isn't it?17:29
DocScrutinizer05for me DCOFF is 617:29
DocScrutinizer05and DCGN is 2517:29
keriooh17:30
DocScrutinizer05sorry17:30
DocScrutinizer05DCOF is 217:30
DocScrutinizer05and my formula above seems also not quite correct17:31
DocScrutinizer05so for AI > LMD * ^^^DCOFF%, the compensated AI gets calculated as CAI = AI + ((AI - (LMD * DCOFF%)) * (0.39% * DCGN))17:32
DocScrutinizer05the term AI - (LMD * DCOFF%) never must be negative17:33
DocScrutinizer05this is guaranteed by applying the compensation only when AI > LMD * ^^^DCOFF%17:34
kerioDCOFF 0.25, DCGN 6.25%17:39
DocScrutinizer05if [ ${AI} -ge $(( LMD * DCOFF_IN_permille / 1000 )) ]; then CAI = ...17:39
DocScrutinizer05yes17:39
DocScrutinizer05so I'd store it like 250 to DCOFF_IN_permille17:40
kerionope, 0.25 is perfectly fine :)17:40
kerioor maybe percentage, like everything else17:40
DocScrutinizer05err btw why 6.25% DCGN?17:41
kerioDCGN[5:0] = 2.56 * Design discharge compensation gain %17:41
DocScrutinizer05~66/417:41
infobot16.517:41
kerio~66/2.5617:42
infobot25.7812517:42
keriowat17:42
kerio~25/2.5617:42
infobot9.76562517:42
kerioi don't know why 6.25% DCGN17:42
DocScrutinizer05ummm17:42
DocScrutinizer0566=0b0110011017:43
DocScrutinizer05>>217:43
DocScrutinizer050b0001100117:43
DocScrutinizer059+16=2517:44
DocScrutinizer05~25*0.3917:44
infobot9.7517:44
DocScrutinizer05   0x7E:        66 DCOMP Discharge Rate Compensation Constants17:45
keriothat's split in two17:45
DocScrutinizer05BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT  017:46
DocScrutinizer05NAME DCGN[5] DCGN[4] DCGN[3] DCGN[2] DCGN[1] DCGN[0] DCOFF[1] DCOFF[0]17:46
DocScrutinizer05thus >>217:46
DocScrutinizer05DCGN[5:0]=0b0001100117:47
DocScrutinizer05=0x19=2517:47
kerio66 == 0b0100001017:48
DocScrutinizer05WUT?17:48
DocScrutinizer05dang!!17:48
DocScrutinizer05I need more coffee17:48
DocScrutinizer05of course you're right17:49
kerio~kerio17:49
infobotit has been said that kerio is <DocScrutinizer05> kerio is right17:49
DocScrutinizer05~19*0.3917:51
infobot7.4117:51
DocScrutinizer05I really need more coffee17:53
DocScrutinizer05and a better calculator, kcalc is da crap17:54
DocScrutinizer05so finally 0x7e:66 means DCGN=16dez17:57
DocScrutinizer05~16*0.3917:57
infobot6.2417:57
DocScrutinizer05so finally 0x7e:66 means DCOFF=1dez which maps to C/2 aka 50%17:59
kerioDCOFF = 2 which maps to C/418:00
DocScrutinizer05yes, again18:00
DocScrutinizer05a pair value can't have LSB=118:01
DocScrutinizer05seems I should go back to my bed18:01
keriohm, i'm missing the energy stuff in the output18:02
DocScrutinizer05*shrug*18:02
DocScrutinizer05it's a simple multiplication I'd guess18:03
keriothey're stored in separate registers though18:03
kerioSAE and AP18:03
DocScrutinizer05yeah sure18:03
keriobut yeah, it's a multiplication18:04
DocScrutinizer05~1245 mAh / 418:04
DocScrutinizer05~1245  / 418:04
infobot311.2518:04
kerio"The host system has read-only access to this register pair."18:04
kerioif only18:04
kerioi2cset a trillion joules18:04
kerioand solve the energy crisis18:05
keriook, let's check for joergthon compatibility18:06
kerioDocScrutinizer05: http://pastebin.mozilla.org/225692618:06
*** _rd has joined #maemo-ssu18:06
DocScrutinizer05kerio: moeoeoep :o) 0x7C:        67 PKCFG Pack Configuration Values18:07
DocScrutinizer05DCFIX Fixed discharge compensation  == 118:07
DocScrutinizer05>>If this bit is set to 1, the device assumes a fixed value of 0x42 for DCOMP, giving a discharge rate compensation gain of 6.25% with a compensation threshold of C/4. <<18:09
kerioalso, my PKCFG is 67, not 6618:09
DocScrutinizer050x7E:        66 DCOMP Discharge Rate Compensation Constants,18:10
keriowhat the hell, why is my TCFIX set18:10
DocScrutinizer050x7C:        67 PKCFG Pack Configuration Values18:10
keriooic18:10
kerioyeah but don't get distracted, check for SyntaxComplicated18:11
*** M13 has quit IRC18:16
DocScrutinizer05well, your bq27k["DCOFF"] will probably fail for 0%18:17
*** _rd has quit IRC18:18
DocScrutinizer05well, maybe not18:18
*** M13 has joined #maemo-ssu18:19
DocScrutinizer05anyway DCFIX = 1 means 0x7e is an identification byte only, which makes me start to wonder what ID "66" means18:23
DocScrutinizer05kerio: s/ # registers for us/ # registers for us, which actually is a rather nonsensical thing but done anyway/18:29
DocScrutinizer05kerio: otherwise, this code makes me love python18:31
DocScrutinizer05I'd actually be temped to do what I always do: "steal" it and hack in my nasty little tweaks18:32
DocScrutinizer05but then, it's based on sysfs nodes so basically useless for my purposes18:33
DocScrutinizer05W*T*F?!!18:39
DocScrutinizer05> >CYCT is the cycle count since a full reset. A full reset clears this register. Each count indicates a cumulativ edischarge equal to the Design Capacity (256 * ILMD). The host system has read-only access to this register pair.<<   ILMD!!! Design capacity!18:39
DocScrutinizer05so we need to compensate this by  CCYCT = CYCT / LMD * ILMD18:41
keriono we don't18:41
keriowhile a cycle counter might be cute to have, bq27k will still use the real CYCL18:41
DocScrutinizer05for a meaningful value to display to user we do, for sysfs nodes exposing raw register values we obviously don't since there's no CCYCT register anyway18:42
DocScrutinizer05WAAAAIIIT19:09
DocScrutinizer05reading thru "Programming the EEPROM" section, it occurs to me that you *can* overwrite values in EEPROM (like ILMD) with a new value. It needs the programming voltage pulse only for flashing that to EEPROM to make it persistent across chip resets19:12
*** M13 has quit IRC19:13
ShadowJKoh?19:13
DocScrutinizer05maybe I hope for too much, but it *might* work to write a new value to e.g. ILMD just like to any other RAM register, and it *might* stay on that value until next chip reset19:13
ShadowJKcan we change edv1 :)19:13
kerio:O19:13
*** M13 has joined #maemo-ssu19:13
kerioDocScrutinizer05: chip reset, or full reset?19:14
ShadowJKYou mean you hope it's got sram, and copies eeprom to sram on start?19:14
ShadowJKinstead of always reading from eeprom19:14
DocScrutinizer05the recommended procedure to flashh EEPROM: "enable, write data to X, *read data from X*, apply flash pulse" suggests to me that the data is sticky in that location at least for one read19:15
DocScrutinizer05if it works for one read, why should it fail for 2nd read?19:16
DocScrutinizer05ShadowJK: exactly19:16
keriowhy "read data from X"?19:16
DocScrutinizer05because it's written in datasheet19:16
keriojust read it once? or read and check that it's the written one?19:17
kerioanyway, /me will not risk his only n90019:17
DocScrutinizer05see p.23 "Programming the EEPROM"19:17
kerioDocScrutinizer05: use your 74th n900 maybe19:17
DocScrutinizer05DANG!!19:18
DocScrutinizer05chip does POR on leaving programming mode19:18
DocScrutinizer05it's neither defined in DS what happens when writing to the EEPROM locations without enabling programming mode, nor is there any warning that programming mode MUST get exited by > >Write data 0x00 t oaddress 0x6E<< or otherwise chip wouldn't work19:20
*** futpib__ has joined #maemo-ssu19:21
*** futpib_ has quit IRC19:22
DocScrutinizer05so we can test 2 possible scenarios: try writing to ILMD without enabling prog mode by > >Write data 0xDD to address 0x6E<< and see if that changes anything. And second: > >Write data 0xDD to address 0x6E<< then write new value to ILMD or EDV1 and see how chip behaves when we do NOT > >Write data 0x00 t oaddress 0x6E<< after that19:23
DocScrutinizer05btw there's a huge range of "RESERVED" register addr that might (and actually do) hold valuable data and might even be writable19:25
kerioDocScrutinizer05: well, nothing *can* go wrong, right?19:26
kerioat worst you unplug the battery and wait some time19:26
DocScrutinizer05yes, that's what I think, unless you write to RESERVED registers and something terrible goes wrong inside chip (extremely unlikely, like "I would bet my life on it, when I could win a 1000$")19:28
DocScrutinizer05nevertheless, act on own peril, no warranties19:29
DocScrutinizer05if an aborted "programming" sequence, even without VPP applied, could go awry, the datasheet for sure should have a HUGE warning about that. And a pointer to the scientific report explaining that miracle19:31
kerioDocScrutinizer05: was your idea to change eeprom parameters and then do a full reset?19:32
DocScrutinizer05no19:32
keriohow is the chip supposed to "reload" the parameters then?19:33
DocScrutinizer05a full reset restores EEPROM parameters to ram, and we can't change EEPROM values without applying VPP19:33
DocScrutinizer05while normal operation would most likely use the ram register copies of the values19:34
keriohm19:34
DocScrutinizer05for ILMD that's rather useless anyway19:34
kerioi was hoping that the ram copies would persist until a power off19:34
DocScrutinizer05since ILMD gets used only when doing a full reset19:34
DocScrutinizer05AAAAND for cycle calculation ;-D19:35
DocScrutinizer05kerio: power off *is* the usual cause for a full reset19:35
keriothere is a real full reset19:35
keriowrite the appropriate bits to MODE and CTRL19:36
DocScrutinizer05yeah, but what for??19:36
keriobecause we could hope it's less full than removing power to the chip :)19:36
DocScrutinizer05meh, it isn't19:36
DocScrutinizer05why the heck do you want to reset anyway?19:36
keriobecause you just "wrote" a new ILMD, maybe :D19:37
DocScrutinizer05heck!!! ILMD is only useful for full reset aka power-off. We don't need it for anything else (except cycle calculation)19:38
DocScrutinizer05and for cycle calculation I guess we don't need any reset to make a change in ILMD get effective19:38
keriobattery swapping?19:38
* DocScrutinizer05 shakes head19:38
DocScrutinizer05WHAT?? why? what are you trying to get done?19:39
ShadowJKi thought cycles were counted against lmd19:39
DocScrutinizer05no, ILMD :-S19:39
kerioDocScrutinizer05: write known LMD and NAC right after you inserted the new battery19:39
DocScrutinizer05[2013-03-29 17:39:46] <DocScrutinizer05> > >CYCT is the cycle count since a full reset. A full reset clears this register. Each count indicates a cumulativ edischarge equal to the Design Capacity (256 * ILMD). The host system has read-only access to this register pair.<<   ILMD!!! Design capacity!19:40
kerio"live" battery swap with correct-ish capacity measurement19:40
DocScrutinizer05why bother about LMD when swapping battery?19:40
DocScrutinizer05and how's that related to ILMD?19:41
DocScrutinizer05which evidently we can't change for battery swap19:42
DocScrutinizer05> >The POR status bit is set to 1 by the bqJUNIOR following a Power on Reset. This is a flag to th ehost that VCC was less than V(POR) and caused a reset. The bit is cleared to 0 by the bqJUNIO Rwhen a full charge condition is reached or it may be cleared by the host. The bit is also cleared to  0after exiting from EEPROM programming or ship. The host may set this bit, but it has no effect o nthe bqJUNIOR operation. The user should19:44
DocScrutinizer05keep this bit set or cleared as desired when other bits i nthis register are set.<<19:44
DocScrutinizer05^^^ useless (for this purpose)19:44
DocScrutinizer05(but actually I think chip does no full reset on exiting prog mode. I confused stuff here)19:45
keriowhere's that status bit? MODE?19:45
DocScrutinizer05> >Full reset. This command bit requests a full reset. A full reset reinitializes all RAM registers ,including the NAC, LMD, and FLAGS registers. This command is intended for manufacturing use.<<19:46
DocScrutinizer05^^^ most probably including reading back EEPROM values to RAM19:46
DocScrutinizer05if you want to write new values to LMD (not ILMD) I bet you have to write to one of the RESERVED registers. If they are not write protected19:48
DocScrutinizer05I bet those are the complete memory of that microcontroller mapped to I2C addresses19:49
DocScrutinizer05incl timer, auxiliary registers, PC, SP, stack and all19:50
keriowhy would they be i2c-writable?19:51
DocScrutinizer05because nobody bothered to make them r/o, if we're lucky19:52
DocScrutinizer05read-only just might mean that on next internal program cycle those registers are refreshed to a calculated/derived value and nobody cares about what you write to them19:54
*** kolp has quit IRC19:55
DocScrutinizer05hey, this is I2C, drivers are supposed to act according to DS specs. Why would a chip manuf bother to spend work, chip real estate, money, yield, on implementing a write protection for registers marked "RESERVED"?19:56
ShadowJKprobably temporary storage for calculations and stuff20:00
kerioclearly we should port uClinux to the bq2720020:05
*** arcean_ is now known as arcean20:12
*** Pali has quit IRC20:21
*** Pali has joined #maemo-ssu20:22
*** andre__ has quit IRC20:33
*** kolp has joined #maemo-ssu20:43
*** andre__ has joined #maemo-ssu21:02
*** M4rtinK has joined #maemo-ssu21:07
*** andre__ has quit IRC21:09
*** Estel_ has quit IRC21:21
*** Estel^ has joined #maemo-ssu21:22
*** Estel^ has joined #maemo-ssu21:22
Estel^ShadowJK, kerio, DocScrutinizer05, there is a limit for capacity-up learning21:22
*** Vlad_on_the_road has joined #maemo-ssu21:23
Estel^if, for example, you would have ilmd as 100 mA, after 100 mA used capacity and vdq=1 would stay for some time/mAh spent...21:23
Estel^and, after certain ammount of Mah spent or time in 6%, vdq got spoiled to 021:23
Estel^thats why people calibrating for dual batteries need to go by steps21:23
Estel^from my experience, capacity gain of 800 mAh is about ok for single cycle, duinno if it depends on LMD (so % of last discharge)21:24
Estel^from ~1300, one may jump to ~2300 max21:24
Estel^er, in fact it might have been 1300->1800->2300, so 500 mA gain21:25
Estel^haven't done it for some time, usually I'm jumping from 2048 mAh to ~3400 mAh in 2 or 3 cycles21:25
Estel^well, two, as it's definitelly possible to go from 2000 mAh to 2800 mAh21:25
Estel^so it may be % related - 1300 allow only ~650 mAh gain, 2000 doesn't have problem with 1000 probably, I suspect (assumption) max 50% gain in caapcity, since vdq get spoiled21:26
Estel^definitelly iot's higher than learn-down limit, but it's there too, for 100%21:26
Estel^best wishes to some responsible chanop, that keeps my main registered nick (Estel_) at +q state, btw. Kudos.21:27
* Estel^ waves and goes for some pleasant RL21:27
*** M13 has quit IRC21:31
*** futpib__ has quit IRC21:49
*** nox- has joined #maemo-ssu21:53
*** sunny_s has joined #maemo-ssu22:11
*** ChanServ sets mode: +o DocScrutinizer0522:14
*** DocScrutinizer05 sets mode: -b Estel_!*@*22:15
*** DocScrutinizer05 sets mode: -q Estel_!*@*22:15
*** ChanServ sets mode: -o DocScrutinizer0522:15
*** sunny_s has quit IRC22:38
*** unclouded has joined #maemo-ssu22:49
Estel^<#maemo-ssu> [21:15] DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg) changed mode: -b Estel_!*@*22:51
Estel^<#maemo-ssu> [21:15] DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg) changed mode: -q Estel_!*@*22:51
Estel^how funny. you're luycky, that I have sense of humour and self-distance ;)22:51
Estel^lucky, even22:51
Estel^kerio, following our conversation about u-boot - I'm all reeady for it, got rid of multiboot, ensured that /sbin/preinit is default one (well, with Mentalist's Traceur's recovery shell, but that's irrelevant here), got flash-ask installed, u-boot-tools, u-boot bootimage, ignore u-boot flasher22:52
Estel^wanting to go the way you've described - only u-boot in nand, reading kernels. Now, i've been through documentation, but it's a mess, it speaks about writing own scripts for u-boot bootmenu, then, few lines later, warnj to nbot write own scripts...22:53
DocScrutinizer05listen buddy, if you got something to complain no matter what I'm doing, then i happily will revert everything22:53
DocScrutinizer05pathetic troll22:54
Estel^DocScrutinizer05, sorry, in my mind -b was +b22:54
Estel^so i took it for -q +b, which would be quite funny22:54
Estel^apologies.22:54
Estel^doesn't need to call names, really *gives DocScrutinizer05 some sweet pink flowers with Satan inside*22:55
*** zogg_ has joined #maemo-ssu22:55
*** LauRoman has quit IRC22:56
Estel^going back to u-boot case - simple question, how to properly generate scripts for u-boot menu, that will make it boot my kp52 as default one without u-boot menu, and display u-boot menu only if <something> is done22:57
Estel^to call for it22:57
*** ZogG has quit IRC22:57
DocScrutinizer05ever wondered how often you suffer from similar distortions of your reality and nobody helps you out on it?22:57
Estel^as for u-boot image flashed to nand, I'll do it either from device or from desktop flasher, that part is clear22:57
Estel^DocScrutinizer05, all perceived reality is a disortion of our brain ;)22:58
Estel^thats why we get along with some people very well, and some (me & you) just don't transmit on same frequency, no matter how hard trying. Keeping ZEN is only solution ;)22:58
Estel^people mean well, pink flowers, etc.22:59
Estel^I/m pretty sure that we would be in much better terms on IRc if you wouldn't have chanop to (ab)use, but that's different thing23:00
kerioEstel^: if you don't mind the "boot from attached kernel" entry that doesn't work in the menu, it's just a matter of doing ln -s /etc/bootmenu.d/*power* /etc/default/bootmenu.item23:01
kerioand then u-boot-update-bootmenu23:01
Estel^thanks, sounds simple enough. And if I mind it?23:01
keriothen your best bet is to edit away the part that adds the attachboot entry in /ust/bin/u-boot-update-bootmenu23:01
Estel^ok, device will boot normally, and show u-boot menu only when what? keyboard slided-out?23:02
DocScrutinizer05or edit the original file, instead of patching the editor23:02
DocScrutinizer05;-P23:02
Estel^resulting file, you mean? After editor creates it?23:02
Estel^it was hiogh enough time to get rid of multiboot. My only excuse for wqaiting so long was that In fact, I have never ever used it to boot anything else than kernel already flashed in nand :P23:03
Estel^=never used it, in reality23:03
DocScrutinizer05honestly, feels like I'm supposed to write bund of sed scripts to create my letter, and if the result isn't like it should, then edit sed itself to fix that23:03
*** Vlad_on_the_road has quit IRC23:03
DocScrutinizer05bunch even23:03
Estel^well, used it to get into backupmenu, but that doesn't count, as it doesn't flash nand23:04
Estel^ough23:04
DocScrutinizer05~trout kerio23:04
* infobot slaps kerio around a bit with a large trout!23:04
kerioDocScrutinizer05: it's not my fault pali hasn't upstreamed my patch yet23:05
Estel^kerio, so, summing it up, u-boot menu is triggered by (what?) and otherwise device boots default thing which is (what?)? I need to keep that default thing - kp52 in (what directory)?23:05
DocScrutinizer05hehehe23:05
Estel^kerio, I agree23:05
Estel^btw23:05
Estel^hey, maybe I shgould just use your patched u-boot-update-bootmenu23:05
kerionah, it's awful23:06
Estel^christ, my typos. *should23:06
Estel^what's is so awful about it?:P23:06
kerioit needs a better way to detect if there's actually an attached kernel23:06
Estel^whatever, gimme it to me *gollum's face*23:06
kerionope23:06
Estel^gimme it, even23:06
Estel^gimme it, or I will dig up the link that you've posted some weeks ago, which contain exactly thaT :p23:07
keriothat would involve 0 effort on my part23:07
kerioi'm ok with that23:07
Estel^hehe23:07
*** Vlad_on_the_road has joined #maemo-ssu23:07
Estel^pastebin /usr/bin/u-boot-update-bootmenu is slightly low effort... Think about it, We will save more Co2 if you do that simple command, instead of me waking up google advanced search to find it23:08
Estel^sustainable economy, etc23:08
Estel^ok, but I still don't get how u-boot menu is triggered. It appears always, or when keyboard is slided out, or bysome configurable thing, or?...23:09
keriothe menu appears when the keyboard is open as you boot23:09
* Estel^ doesn't like idea of having some timeout menu on every boot, would rather like device to boot default kernel image, and show u-boot only, when requested 'somehow'23:09
Estel^OK23:09
Estel^ah, so if I want exercise for sake of exercise, I may practice sliding keyboard out just after kernel gets loaded, to get backupmenu from bootmenu, but without getting u-boot menu23:10
* Estel^ likes the idea23:10
kerioi hope you realize that you can just leave the kbd slider open23:10
Estel^sure23:10
Estel^that's why I've said ''exercise for sake of exercise''23:11
Estel^+10 k20 coolnes of using N900 when you slide out just in time23:11
Estel^egoboost23:11
Estel^I hope you realize ammount of irony here :P anyway, now the ultimate question - when I decide to have possibility of running somwthing like arch linux or whatever, how to prepare "thing" and trigger u-boot-update-bootmenu to make it available from u-boot menu?23:12
Estel^how it will know what is default and what isn't?23:12
Estel^I suppose ln -s /etc/bootmenu.d/*power* /etc/default/bootmenu.item is default23:13
Estel^s/is default/define default thing/23:13
infobotEstel^ meant: I suppose ln -s /etc/bootmenu.d/*power* /etc/default/bootmenu.item define default thing23:13
Estel^so how about non-default one, that should get available from u-boot menu?23:13
kerioyeah, the non-default ones will be available from the uboot menu23:13
kerioas will the default one23:13
Estel^so /etc/bootmenu.d/ things are considered by u-boot-update-menu?23:14
kerioif there's no default, the default is the first one23:14
kerioif you leave the attachboot entry in, that's the first one23:14
keriootherwise, it's the first in alphabetical order of the uboot entries in /etc/bootmenu.d23:14
Estel^...which wouldn't work, as I won't attach kernel to it, due to it having no sense, so surely, i'll kick attached from u-boot menu23:14
*** Vlad_on_the_road has quit IRC23:15
Estel^so using u-boot is as simple as having proper things in /etc/bootmenu.d and matching images in approriate place, then, running u-boot-update-menu?23:15
Estel^mkimage and such things can go screw themselves?23:15
Estel^... Whoa, shitload of things in my /etc/bootmenu.d/, that are nto actual23:16
Estel^not*23:16
Estel^including backupmenu, which shouldn't sit there, methinks?23:16
kerioEstel^: that's right, as a user you shouldn't be aware of the existance of mkimage23:17
kerioand that directory is shared by fanoush's bootmenu23:18
Estel^oh, great, so how to have famoush bootmenu things like backupmenu, and u-boot without broken entries, at the same time?23:18
Estel^"fire, fire, carrier under fire" - first of all, I got styrangte problems after uninstalling bootmenu, and while using backupmenu (which implies using bootmenu). When booting with keyboard slided out, my arrows works only for split second, then, I can't select anything in bootmenu (which is visible, though), and thing like "cannot open /dev/fbd0" spams my fbcon23:20
Estel^wtf?23:20
Estel^now when it boots, "Warning: Unable to open initial console"23:21
Estel^Console: Switching to colour frame buffer device 100x3023:22
Estel^Kernel panic - not syncing: Attempted to kill init23:22
Estel^then shutdown. heh23:22
kerioidk23:22
Estel^fun fact, if i bash "return" to use that split second when bootmenu works, device boots normally23:23
kerioso you have a bootmenu problem23:23
Estel^yep.23:23
kerioapt-get install --reinstall getbootstate23:23
Estel^I would say some multiboot remnants fucked it up, but i vaguely remember smth like that happening one on device, where multiboot wasn't present at any point in time, just bootmenuy instalkled on vanilla system23:24
kerioapt-get install --reinstall bootmenu-n90023:24
kerioer, sorry, bootmenu23:24
Estel^iirc, when i managed to boot ok, all future boots will work OK. Strange things. If not, i'll try reinstalling, indeed23:24
Estel^kerio, me wonders why u-boot bootimage adds file 30-U-Boot-2012.12-rc3-1.item to /etc/bootmenu.d/23:29
DocScrutinizer05((<kerio> and that directory is shared by fanoush's bootmenu)) which is the great design mistake in that whole thing23:30
keriobecause the bootimage is not what you want, really23:30
Estel^kerio, I wanted bootimage to extraxt u-boot zimage from it and flash it to nand23:30
keriowhy didn't you download the deb somewhere else23:30
Estel^btw, what is potential use case to have u-boot item in bootmenu.d?23:30
keriomultiboot, probably23:30
Estel^because I haven't expected it to do irrational things23:31
Estel^lol23:31
Estel^u-boot .item for multiboot sounds... fun. Just fun.23:31
Estel^like using bicycle dynamo to power initial ignition of 2012 hybrid car23:31
Estel^kerio, DocScrutinizer05, I agree that sharing directory with fanoush bootmenu sounds like basic design mistake23:32
kerioit's for backwards-compatibility with multiboot23:32
keriowhich uses /etc/bootmenu.d and /etc/multiboot.d23:33
Estel^anyway, any ideas how to have working backupmenu from fanoush's bootmenu (after kernel is loaded) and u-boot menu without broken entries, considering, that backupmenu.item sits in bootmenu.d ?23:33
kerioEstel^: just ignore the errors u-boot-update-bootmenu gives you23:33
kerio(another design mistake)23:33
Estel^ah, it will give errors? I thought it will make fubar entries to u-boot menu23:33
keriono, no23:33
kerioit's kinda easy to distinguish between what has a kernel entry and what doesn't :)23:33
Estel^3th. why won't anyone fill a bug against that design mistakes to Pali?23:34
Estel^yea23:34
DocScrutinizer05I'd honestly patch u-boot-update-bootmenu to use *its* *own* directory, like /etc/uboot.d23:34
Estel^well, I guewss I;'ll extract u-boot zimage, then aplt-get purge u-boot-bootmenu23:34
kerioDocScrutinizer05: and symlink the shit out of every -bootimg?23:34
DocScrutinizer05then just _maybe_ copy etc/bootmenu to etc/uboot.d23:34
kerioand by symlink i mean dpkg-divert23:35
Estel^hehe, I feel another kerio's fork is going to appear. Pali will just lvoe you ;-)23:35
Estel^s/lvoe/love/23:35
infobotEstel^ meant: hehe, I feel another kerio's fork is going to appear. Pali will just love you ;-)23:35
Estel^ffs23:35
Estel^this whole u-boot thing confused me enough, to try installing it without doing backup23:36
Estel^*desperado mode on*23:36
Estel^what can go wrong, in desperado mode, we're immortal ;)23:36
Estel^erm, what was that thing, that need to sit on MyDocs, or something in u-boot won't work as it should?23:37
keriobootmenu.src and bootmenu.d23:37
keriothey're the script and the directory that contains the uimages23:38
Estel^w-what? bootmenu.d wasn't on /etc/bootmenu.d/?!23:38
keriopay attention, this is MyDocs/bootmenu.d23:38
Estel^or is it created by u-boot-update-menu automagically on mydocs?23:38
keriowhich contains the automatically-created and automatically-converted uboot images of every kernel and initrd referenced by the .item files23:38
Estel^wonderful, I don't even want to ask what would happen, if I wouldn't have mydocs as /dev/mmcblk0p1, and would want to boot from sd, for example23:39
kerioif uboot doesn't know what to do, it gives you a console23:39
Estel^would need to enter u-boot console and do all shit manually to boot from sd, eh?23:39
Estel^hehe23:39
Estel^see? desperado mode gives +100 to intuition23:39
kerioi'm not sure if anything is loaded automatically from the sd23:39
DocScrutinizer05select bootimage_to_add in /boot/*-bootimg*; do install-uboot-entry $(basename $bootimage_to_add) $bootimage_to_add; done23:39
kerioDocScrutinizer05: 50% of the times, it works 100% of the times23:40
Estel^my super-zipper-you-'re-not-a-david-bowie intution tells me, that u-boot console isn't full-fledged termijnal, just itnernal u-boot tool?23:40
Estel^internal/iternal/s/ or smth loike that23:40
kerioconsidering that linux hasn't even entered the picture at that point...23:41
Estel^right. Well, rationale doesn't enter picture at point of intuitional feeling ;_P23:41
*** wmarone__ has joined #maemo-ssu23:47
Estel^now, we only need to convince good'old'lennart to write poette-boot, and push it to be used as one and only (tm) thing by every board manufacturers, that will contain whole linux substitute bundled in u-boot (poette-boot)...23:47
*** wmarone_ has quit IRC23:47
Estel^...so we will have proper terminal instead of u-boot console and unified enviromnent (tm)23:47
Estel^;)23:47
DocScrutinizer05kerio: find /boot /mnt/mmc/boot -iname "*bootimg*" -exec "echo 'install uboot entry for' {} ' ? (^C for no, enter for this name, or enter an alternative text for menu entry):' read -i {} && install-uboot-entry $REPLY" ;23:52
kerioeven then, it actually doesn't work23:52
DocScrutinizer05meh!23:53
kerioto boot a kernel you need 1) a kernel, and 2) a cmdline23:53
DocScrutinizer05then use asm! ;-P23:53
kerioand sometimes 3) an initrd23:53
DocScrutinizer05an initrd?23:53
kerioan initrd!23:54
DocScrutinizer05what for? filesystem not available in the kernel?23:54
kerio*coff coff rescueos coff coff*23:54
DocScrutinizer05cofcoff not meant to ever get installed coffcoff23:55
kerio"meant" my ass23:55
kerioit works perfectly23:55
DocScrutinizer05actually that's the only reason why it needs an initrd23:55
kerioand it's probably indistinguishable from when you boot it from flasher23:55
DocScrutinizer05anyway nothing that couldn't get handled inside install-uboot-entry23:56

Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!