IRC log of #maemo-ssu for Thursday, 2013-10-10

*** NIN101 has quit IRC00:08
*** xes has joined #maemo-ssu00:29
*** nox- has joined #maemo-ssu00:29
*** usakc has quit IRC00:58
*** Martix has joined #maemo-ssu01:24
*** xes has quit IRC01:32
*** jonwil has joined #maemo-ssu02:10
*** MohammadAG has quit IRC02:37
*** trx has quit IRC03:05
*** trx has joined #maemo-ssu03:06
*** trx has joined #maemo-ssu03:06
*** Martix has quit IRC03:08
*** DrCode has quit IRC03:18
*** kolp has quit IRC03:21
*** DrCode has joined #maemo-ssu03:29
*** DrCode has quit IRC04:05
*** DrCode has joined #maemo-ssu04:09
*** nox- has quit IRC04:13
*** dos1 has quit IRC04:31
*** LauRoman has quit IRC05:35
*** amiconn_ has joined #maemo-ssu05:41
*** amiconn has quit IRC05:41
*** amiconn_ is now known as amiconn05:41
*** trx has quit IRC07:39
*** DrCode has quit IRC08:31
*** DrCode has joined #maemo-ssu08:34
*** luf has joined #maemo-ssu08:56
*** DrCode has quit IRC08:59
*** DrCode has joined #maemo-ssu09:01
*** freemangordon_ has joined #maemo-ssu09:07
*** freemangordon has quit IRC09:07
*** tom has quit IRC09:18
*** tom has joined #maemo-ssu09:39
*** DrCode has quit IRC09:41
*** DrCode has joined #maemo-ssu09:42
*** LauRoman has joined #maemo-ssu10:02
*** tom has quit IRC10:17
*** tom has joined #maemo-ssu10:17
*** X-Fade has quit IRC10:32
*** Martix has joined #maemo-ssu10:38
*** LauRoman has quit IRC10:41
*** Pali has joined #maemo-ssu10:49
DocScrutinizer05http://talk.maemo.org/showthread.php?p=1372710#post137271010:52
*** Martix has quit IRC10:53
*** MohammadAG has joined #maemo-ssu11:03
FatPhilDamn, a second of my n900s has a broken USB :(11:22
*** X-Fade has joined #maemo-ssu11:24
FatPhil"What we need for infra are volunteers, raw manpower" - such as?11:30
*** dhbiker has quit IRC11:38
*** dhbiker has joined #maemo-ssu11:43
*** joshgillies has joined #maemo-ssu11:43
joshgilliesanyone in here developing on an ARM chromebook?11:44
joshgillieslooking for pointers toward getting the sdk up and running11:45
Palino chromebook here11:48
freemangordon_Pali: we have a problem with omapfb :(11:48
freemangordon_and dss driver too11:48
Paliwhich problem?11:48
Palicma not working?11:49
freemangordon_CMA actually doesn;t seem to work reliably, so it can't allocate framebuffer memory11:49
*** freemangordon_ is now known as freemangordon11:49
freemangordonPali: yes11:49
Paliand why preallocate without cma not working?11:50
freemangordonPali: it is removed ;)11:50
freemangordonno more vram= boot parameter11:50
Paliah...11:50
freemangordonand dss:11:50
freemangordonJan  1 06:35:24 Nokia-N900 kernel: [ 2172.539093] omapdss DISPC error: horizontal timing too tight11:50
freemangordonJan  1 06:35:24 Nokia-N900 kernel: [ 2172.545074] omapdss APPLY error: dispc_ovl_setup failed for ovl 111:50
freemangordonthis happens for both 720p and lower res videos11:51
freemangordon(in case CMA succeeds :D )11:51
freemangordonPali: but on the bright side, seems DSP is tock stable11:52
freemangordon*rock11:52
Paliok, so if you disable cma low res videos working?11:55
freemangordonPali: makes no difference, as then memory cannot be allocated because of the fragmentation11:55
freemangordonso CMA is the way, but it seems broken11:56
Paliand reverting preallocate?12:00
freemangordondidn't try it, but I guess it will fix the problem12:02
*** LaoLang_cool has joined #maemo-ssu12:26
*** LaoLang_cool has quit IRC12:32
*** kolp has joined #maemo-ssu12:43
*** Pali has quit IRC13:09
DocScrutinizer05FatPhil: such as somebody looking into tmo karma and fixing it13:28
kolpI wonder if the size of the current active community really necessitates the existence of a community-voted council. Wouldn't it be enough to have an admin team appointed by HiFo org? Just musing... :)13:31
kolpHm, wrong channel..13:32
*** lizardo has joined #maemo-ssu13:37
*** joshgillies has quit IRC13:45
*** joshgillies has joined #maemo-ssu13:53
*** Pali has joined #maemo-ssu15:25
*** LauRoman has joined #maemo-ssu15:39
*** joshgillies has quit IRC15:49
freemangordon~ping16:13
infobot~pong16:13
freemangordonPali: how am I supposed to report that omapfb problem on lkml?16:26
jonwilok, so at this point for audio, there are 4 things I dont know and want to know, firstly is how the audio system (PulseAudio specifically) knows the difference between e.g. music playback and VoIP audio, second is how the Bluetooth audio is fed into PulseAudio (or fed out of PulseAudio), the third is how the FMTX/FMRX audio is fed into/out of PulseAudio and the last is whether there exists a...16:34
jonwil...nice "Pulseaudio for Dummies" type book out there :)16:35
Palifreemangordon: run ./scripts/get_maintainers.pl -f /path/to/omapfb and check who is maintainer16:42
Paliand send email to maintainers plus maybe cc lkml16:42
freemangordonPali: ok, thanks16:42
Palijonwil: first: it using library libplayback16:43
Paliin this library you can tell type (voice call, music, other...)16:43
Palilibplayback using dbus to inform ohmd about type and also set some PA property on used PA stream16:44
freemangordonPali: hmm, do we have anything major but cameras that doesn't work in 3.12?16:44
Palijonwil: second: via native bluetooth PA plugin16:45
PaliPA somehow connect to bluetoothd (dbus/socket)16:45
jonwilso libplayback specifically talks to pulseaudio?16:45
Palithis is fully documented somewhere and it is standard solution on linux desktop16:45
jonwilor does ohmd talk to pulseaudio somewhere?16:46
Palijonwil: probably yes16:46
jonwilok16:46
Paliohmd can talk to PA16:46
Paliand also libplayback can talk too16:46
Palifreemangordon: camera, sound, maybe jack16:46
jonwilwhat about FM?16:47
Paliand fmtx/fmrx is not tested16:47
jonwilok16:47
Palibut drivers are there16:47
freemangordonPali: I was able to get sound through BT :) some days ago16:47
Palifmrx driver is same as in fremantle kernel16:47
Pali(I checked it)16:47
jonwilI mean how does FMTX/FMRX end up in PulseAudio?16:48
Paliand bluetooth driver was tested by skry and it worked16:48
freemangordonPali: though I see lots of "unrecognized HCI packet)16:48
Palijonwil: fm and PA on n900 is totally unknown for me16:48
jonwilok16:48
jonwilFMTX goes though fmtx-middleware16:48
jonwilso I should probably start there16:49
freemangordonjonwil: RE fmtxd :)16:49
Palibut I do not understand why middleware is needed16:49
Palifmtx should be /dev/radio device16:49
freemangordonPali: it controls stuff like USB cable connected, etc16:49
Paliand alsa has radio plugin16:49
freemangordonalso regional frequencies16:49
Paliso PA can use normal alsa interface for radio support16:50
Paliand it should act as sound card...16:50
Palifreemangordon: only that? or it also routing audio?16:50
Palifreemangordon: also need to test bluetooth if working16:50
freemangordonnot sure, but I *think* it is not fmtxd to route. might be wrong, didn;t look at it16:51
Paliand need to test if wifi adhoc mode working16:51
Paliall audio on maemo is big mess16:51
jonwilbtw, I have thought a bit and have realized that the idea to pretend that the Option modem audio is voip and not cellular audio (at least to Pulseaudio) is a good idea.16:51
Palialsa, PA, PA modules, alsa policy, PA policy, alsaped, pasr, ohmd, ohm plugins, libplayback, swi-prolog, prolog code, dresd, dres daemon...16:53
Paliand other stuff which I forgot16:53
jonwilbtw pali are you 100% sure that your decompile of the policy-settings-rx51 prolog code is functionally identical to the stock compiled prolog code?16:55
PaliI'm 99% sure16:55
jonwilok, in that case all we need to do is to write a decompiler for policy.dresc :)16:56
freemangordonhttp://talk.maemo.org/showpost.php?p=1379819&postcount=7216:56
Palithere is 1% chance that I forgot something (some non predicate prolog code)16:56
Palijonwil: do we need it?16:56
freemangordonfeel free to correct me if I've write something which is not correct16:56
freemangordon*written16:57
Palijonwil: one nokia dev wrote on TMO some info about dres and dres compiler16:57
jonwilyes he did16:57
jonwilI remember it16:57
Palijonwil: you can try contact him again, if he does not have any usefull stuff (e.g. decompiler :-))17:01
kolpGetting rid of prolog sounds like a worthwile goal :)17:01
jonwilI doubt he would have a decompiler as there would be no reason to write one17:01
FatPhilfreemangordon: where can I pull your kernel?17:01
Palijonwil: instead writing decompiler it should be easier to load that dres binary file into dres VM and dump factoid info into debug console17:02
Palijonwil: if I remember correctly in dres file are only some functions and lot of static data...17:03
Paliand that debug dump command doing some "disassembling" of current memory state17:04
Paliand dres VM is stack based - this could help you17:04
Palifreemangordon: what is needed is to patch all maemo daemons to work without that kernel patch for sysfs17:06
freemangordonPali: which patch?17:06
freemangordongpio?17:06
freemangordonooh17:06
Palino select syscall17:06
freemangordonyeah17:07
freemangordonFatPhil: a second17:07
Palibut that omap platform gpio driver too17:07
Palineeds to be rewritten17:07
Palior removing using it from maemo apps...17:07
freemangordonFatPhil: this is upstream (Pali :P ) https://gitorious.org/linux-n900/linux-n900/source/683cc15ed3e6bceb51472a530244f72fa8d40b52:17:07
freemangordonFatPhil: this is mine tree ( a little bit ahead) https://gitorious.org/linux-n900/freemangordons-linux-n900/source/777f4ace4c58799575391833db48050ceefe6fd6:17:08
jonwilWhich maemo apps are using this particular driver?17:08
jonwilthe GPIO one17:08
Palijonwil: sscd :-(17:08
jonwilugh17:08
Palimce17:08
Palipreinit17:08
freemangordonPali: sscd is small binary17:09
freemangordonand we know what it does17:09
Palisscd is using it for cmt_ gpios for init17:09
freemangordonmce... well... :)17:09
freemangordonPali: :nod:17:09
jonwilI wouldn't call 100k a small binary in my book17:09
freemangordonjonwil: sscd is 100K?17:09
Paliand every app which using any gpio directly17:10
jonwilyes its 108,836 bytes17:10
freemangordonomg, my bad17:10
Pali(do not know which other)17:10
freemangordonPali: well, I guess we can live with that gpio17:10
Palijust call grep /sys/something on maemo17:10
Paliok17:10
freemangordonfor the select thingie, we can LD_PRELOAD17:11
Paliok17:11
Palifreemangordon: what is problem with front camera?17:12
Palistill green rectangle?17:12
freemangordonyep17:13
Palior something changed after fixing IRQ?17:13
freemangordonnothing17:13
freemangordonISP irqs are just fine17:13
freemangordonit is something in the ISP driver, I hope sailus ti help us find it17:13
Palifreemangordon: I remember that somebody wrote that camera worked on meego with meego 37+ kernel17:13
Palimaybe looking into meego n900 kernel tree...17:14
freemangordonPali: there is a long way between 2.6.37 and 3.12 as you probably know :P17:14
Paliyes17:14
freemangordonPali: looked, the driver is the same17:14
Palibut checking if we not miss some patch which is not in upstream...17:14
Paliok17:14
freemangordonPali: well, it is possible I've missed something17:15
freemangordonPali: BTW 3.12 boots the screen in 32bpp by default :)17:17
*** dos1 has joined #maemo-ssu17:17
freemangordonI have fix, still not pushed17:17
Paliand what should be correct?17:17
freemangordon1617:17
freemangordonor even 15, not sure17:18
Pali~seen pavelm17:18
infobotpavelm <~pavel@199.214.broadband13.iol.cz> was last seen on IRC in channel #maemo, 246d 1h 59m 41s ago, saying: 'Wow. Thanks a lot, it is installing now,'.17:18
freemangordonPali: we need omapfb.mode=lcd:848x480-16 in cmdline17:18
Palicannot be mode passed from board data?17:19
freemangordonwhat about DT? :P17:19
Palior DT?17:19
freemangordonnot sure about DT17:19
PaliI think resolution is already in board file17:20
freemangordonI dont see it https://gitorious.org/linux-n900/freemangordons-linux-n900/source/777f4ace4c58799575391833db48050ceefe6fd6:arch/arm/mach-omap2/board-rx51-video.c17:21
freemangordonPali: BTW leds still doesn't work17:24
freemangordonwell, RGB led17:24
freemangordonPali: and we have a problem that after rebooting from 2.6.28 to 3.12 it seems one of the i2c busses doesn't work, at least cameras and audio drivers refuse to load17:26
jonwilok, I think my next target is to figure out whats going on inside libplayback. Which might not be that hard since its got x86 binaries plus a -dev package that contains a libplayback.a static librariy17:30
jonwillibplayback-1.a that is17:30
jonwiland the x86 binary .so file is only 21k17:31
jonwilall I have to figure out now is if there is any useful debugging info in that .a file17:31
Palijonwil: if you RE libplayback please write some documentation...17:34
Palisee maemo wiki, there are already some links for libplayback17:35
Palifreemangordon: I will look on led driver17:35
freemangordonFatPhil: but in order to boot maemo you need some userspace packages installed from cssu-devel and some help from Pali :)17:45
freemangordonand maybe from me17:45
Palis/some/all/17:46
freemangordon:D17:46
freemangordonPali: well, clock-ui is not needed I guess.17:46
jonwilgod I hate when libraries have an internal data structure and just pass around pointers to it.17:48
Paliwelcome to OOP world :-)17:49
jonwilinteresting, libplayback says call and voip audio are the same thing. So how does pulseaudio know whether to route audio to the cellular modem or through the voip logic?17:50
Paliapplication name...17:51
jonwilwhat handles that though? pulseaudio? ohm/policy/prolog? something else?17:51
Paliwe already know that application with name "mediaplayer" can something do what other cannot17:52
Paliif I remember it is alsaped together with prolog and dres17:52
Paliand there also is some config ini file where is mediaplayer written17:52
freemangordonhmm, there is a huge plicy file somewhere in /etc17:52
freemangordon*policy17:52
Palijonwil: and maybe really voip and gsm calls are same for PA17:53
jonwilno they are not, PA needs to know the difference to know whether to feed the audio to libcmtspeech or not17:53
jonwilaha, Policy-application-detector relates to this17:54
Paliright that detector is other audio application17:54
jonwilits what grabs the name and feeds it to the policy ststem17:54
jonwilsystem17:54
Palijonwil: if I remember correctly it talk to some udp port on localhost to ohmd17:54
Paliand it is small daemon17:54
Palican you look if you can RE it?17:55
jonwilI will look17:55
jonwilaha, the big conf file you mentioned looks like xpolicy.conf17:55
Paliit sending something like "pop up" or "pop down" via udp17:55
Paliand it checking for X window number...17:56
Palithat config file is maybe in git repo where is decompiled prolog file17:56
Paliand I think I already modified it17:57
jonwilok, yeah the file is definatly xpolicy.conf17:59
jonwilgoing to look at policty-application-detector18:00
jonwilok, app-detect seems to be looking for rtcom-call-ui and systemui by name18:01
jonwilits sending to port 3001 and 300218:04
Paliyou can download ohms sources (+ plugins)18:06
Palilook at fremantle closed packages for correct git commit18:06
Paliand you can see what ohmd doing with it18:06
jonwilyes I know18:09
jonwilok, looks like I will need to find a good tutorial or guide on sources and sinks in pulseaudio18:19
*** jonwil has quit IRC18:19
FatPhilPali: I'm going to reserve one of my "junker" n900s for kernel hacking. I'll nuke it before I do anything - what FIASCOs should I start with?18:29
* FatPhil is unhappy that 2 of his n900s are "junker"s :-( But at least one is fine for dev work presently.18:31
freemangordonFatPhil: flash it with stock pr1.3, install cssu-testing(or -thumb) and use Pali's script to copy maemo to /home/maemo518:31
*** LaoLang_cool has joined #maemo-ssu18:31
FatPhilfreemangordon: OK, I'll get back to you in a few hours...18:32
FatPhilWhat's the week/release number of "stock" pr1.3?18:32
freemangordonFatPhil: oh, and before executing Pali's copy script, enable cssu-devel repo and do apt-get update/upgrade18:32
freemangordon2-36 iirc18:32
freemangordonor was it 36-2?!?18:32
*** XDS2010 has quit IRC18:33
freemangordonFatPhil: keep in mind that both trees (mine and Pali's) lack an et8ek8 patch, i'll provide it to you via pastebin18:33
kolp36-218:33
*** LaoLang_cool has quit IRC18:34
freemangordonFatPhil: http://pastebin.com/Xw71qprL18:34
*** lenoch has joined #maemo-ssu18:35
FatPhilI swear I did that on my daily device, but can't find the fiascos now18:36
FatPhilbrain (or filesystem) like a sieve18:36
freemangordonflashing18:38
freemangordon~flashing18:38
infobotit has been said that maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware18:38
Palitablets-dev.nokia.com18:38
FatPhilwhich would you prefer I do, -thumb, or non-thumb?18:38
freemangordonFatPhil: -thumb is faster18:38
FatPhilI'd rather be at the cutting edge, so -thumb18:38
freemangordonotherwise it doesn;t really matter18:38
*** NIN101 has joined #maemo-ssu18:39
FatPhilIT would be good to test on both thumb and non-thumb, I'll try to find (or solder together) another dev device so I can do both18:39
freemangordonFatPhil: test what?18:40
freemangordonit is not even in alpha stage (kernel)18:40
FatPhiltest the kernel, test it boots to /init, after that, the kernel's job is over ;-)18:50
FatPhilUserspace is evil and should be killed!18:50
freemangordonwith fire :D18:52
FatPhilwith signal number 9, why give it any warning!?18:56
FatPhilThis is going to sound silly - how do you flash a device that's got uboot on it? Flasher never sees the USB device, it just boots to userspace18:59
freemangordonFatPhil: hmm, u-boot is after nolo so it shouldn't make any difference19:00
freemangordonFatPhil: do as I say:19:01
freemangordon1. remove the battery19:02
freemangordon2: plug the USB cable19:02
freemangordonpress'n'hold U19:02
FatPhilI'm on the jig, so battery removal is a switch19:02
FatPhilooooh19:02
freemangordon4. insert the batteru19:02
freemangordonmissing the 'U' step?19:02
FatPhilwhat R&D flag state should I be in?19:04
freemangordondoesn;t matter iirc19:04
FatPhilU's not making any difference19:05
FatPhilAH - cold flash!19:05
FatPhilI'd forgotten about thayt19:05
freemangordonwhy cold flash?19:05
freemangordonyour NOLO is broken?19:05
FatPhilHmm, I don't have a signed second19:06
FatPhilNot sure, but flashing ain't working19:06
freemangordonFatPhil: if flasher can;t see it, try another USB port or even USB hub19:06
FatPhilflasher can read the R&D flags19:07
freemangordonbut,but... then it sees it, what is the problem?19:07
FatPhilit doesn't see it when I try to flash19:07
freemangordonwrong flasher parameters?19:07
freemangordonflasher -F fiasko -f -R19:08
freemangordon(iirc)19:08
FatPhilyeah19:08
freemangordondoesn;t make any sense19:08
Palinolo checking for BSI of battery19:08
freemangordonoh :)19:08
Paliand if BSI or charge level is loo low refuse flashing19:09
* freemangordon thinks Pali is a smart guy 19:09
freemangordon:D19:09
Palis/charge level/voltage level/19:09
infobotPali meant: and if BSI or voltage level is loo low refuse flashing19:09
PaliI wrote new version of 0xFFFF flasher :-)19:10
freemangordonPali: hmm, IMO those checks are sane19:10
Palibut if you load NOLO from cold flash, then it disable these checks19:10
freemangordonwe don;t know what will happen if you run out of juice in the middle of cmt FW flashing19:11
freemangordonbroken BB5 I guess19:11
FatPhilyeah, I it doesn't always do the query-rd-mode either19:13
FatPhil[   0.145] Battery voltage 4.104 V, BSI: 102119:14
FatPhilhmm, well, that's a jig19:15
FatPhilANyone got a copy of secondary for a cold flash?19:15
kolpWhen flashing the N9 the flasher waits and charges the battery for a while if it doesn't have enough juice. Is there any chance something like that can be done for the N(eo)900 in the future?19:16
*** luf has quit IRC19:16
freemangordonFatPhil: secondary is in fiasko, you can extract it19:17
dos1kolp: NOLO is propertary, so "nope" for N90019:18
dos1but in Neo900, whole stack will be open as in GTA04, so it will be there if someone implements it19:18
kolpOh, it's a nolo thing19:18
kolpOk, thx :)19:18
FatPhilI think it's dodgy USB connector :-(19:27
kerio:(19:32
FatPhilNP, I never gave my g/f her replacement device - I've just made it my dev device!19:33
FatPhilI've promised to do surgery to her device to put a new screen and frame on it, as otherwise her device is fine19:34
FatPhilI'd like to dedicate this flashing to my ex-boss, Timo Jokiaho, who sold me this device for 8 (rather good) beers!19:35
FatPhilHe doesn't have to worry about any of his personal information still being on it anywhere, put it that way19:36
merlin1991well for that you'll have to flash emmc aswell19:36
freemangordonmerlin1991: hi!19:37
freemangordonmerlin1991: nuw cssu soon?19:37
freemangordon*new19:37
Palimerlin1991 are you alive? :-)19:38
freemangordonPali: that could be bot19:38
merlin1991Pali: I've been reading this channel regulary since a week or so19:38
FatPhilmerlin1991: did that first19:38
merlin1991never had a point though where I could jump in :D19:38
merlin1991for new cssu I'll start gathering stuff this weekend19:39
freemangordonPali: lets use turing test on him :)19:39
merlin1991my storage unit isn't endless19:39
Palituring test has nothing with storage size :-)19:39
freemangordon:nod:19:40
freemangordon~turing19:40
infobot...but I *AM* Turing complete!!!!19:40
merlin1991iirc If a machine is turing complete you still need storage for instructions relative to the complexity of your problem19:40
freemangordoninfobot: no, you are not19:40
infobotfreemangordon: I think you lost me on that one19:40
freemangordonmerlin1991: turing test doesn;t mean turing complete (iirc)19:41
freemangordonhttp://en.wikipedia.org/wiki/Turing_test19:41
Paliin turing test you have to decide if you are talking with robot or real peron19:41
merlin1991was turing test then the one with humans?19:41
merlin1991ah yep :)19:41
freemangordonyep19:41
merlin1991btw all this kernel hacking, do you plan on bringing our userspace running on upstream+patches, or what is the ultimate goal19:45
freemangordonI guess19:45
freemangordonmerlin1991: *if* we had to support neo900, I don;t see why we shouldn't support n900 as well19:46
freemangordonnot to say it will be much easier19:46
freemangordonmerlin1991: does it make sense to you?19:47
merlin1991in a way19:47
freemangordonmerlin1991: I really hope neo900 will bring some developers back to fremantle19:48
merlin1991heh, I'd happily go back to a n900 that is faster19:48
merlin1991I'd finally have my openvpn relay again, proper ssh with a keyboard, ...19:48
freemangordonmerlin1991: whaaat? n900 is not your primary device ?!?19:49
merlin1991nope I'm on the dark side (n9)19:49
freemangordonhmm, this isn't dark side IMO, this is grey side19:50
merlin1991it's almost black hat xD19:50
freemangordonyou have the worst from the both worlds :D19:50
merlin1991my main reason for using the n9 is, that the modem in there still works properly :D19:50
merlin1991with my n950, and all 3 n900s I loose connection all the time19:51
freemangordonmerlin1991: but wy don;t buy another n900, those are cheap these days, I heard of people getting one fo a couple of beers :D19:51
freemangordonmerlin1991: hmm, tried to change the SIM?19:51
merlin1991I have 2 sims, both work fine in the n9 but fail in all the others19:52
freemangordonweird19:52
FatPhilMy daily device was bought for 7 beers, the development device was bought for 8. ~30e each in real money19:53
freemangordonwhat?!? 4 euros a beer19:53
FatPhilYEah, I bought them in Estonia rather than Finland.19:55
* FatPhil spent 120e on beer on thursday night (last but one day at work in Finland)19:56
FatPhilstill got to work bright and early on my last day, clearly didn't drink enough19:56
freemangordon:D19:56
merlin1991hm 120€ in beer19:57
merlin1991I'd be dead if I try that here19:58
freemangordonwell, what are friends for?19:58
merlin1991that would be like 40 beers19:58
freemangordon(about 120 here :P)19:58
freemangordonina abar19:59
FatPhilFancy imported beers, up to 25e a bottle19:59
freemangordonOMG19:59
FatPhilWelcome to Finland20:00
merlin1991been there, saw the prices :D20:00
FatPhilAre devices with broken USB of use to any developers? How do you flash if not over USB? (there ought to be a SSD boot!)20:02
dos1µsd boot works with u-boot20:04
dos1(but probably not with fremantle :))20:04
merlin1991I still need to fix my sisters usb port, so I can get my only functioning n900 back xD20:05
merlin1991I have the parts, but not the soldering equipment :/20:06
FatPhilme too. now have 1 broken, and 1 very dodgy usb device20:08
Palithere should be way to flash device via serial console20:17
*** X-Fade has quit IRC20:17
Paliat least flasher-3.5 has support for it20:17
Paliflasher-3.5 can cold flash device via serial console20:17
Palibut it maybe needs some (unreleased) 2nd x-loader image which can load secondary (nolo) image via serial port too (and not via usb which doing normal cold flashing)20:19
FatPhilWell, in order to dick with package repo's easily, I'm gonna need wifi, and that means a pub!20:30
FatPhilPali: gonna have to look into that. Not sure how to control flasher, it asks for USB ids.20:32
*** XDS2010 has joined #maemo-ssu20:33
sixwheeledbeastdid someone say pub? :P20:33
Paliyou need to use cold flashing (-c param)20:35
DocScrutinizer05Pali: I guess xloader is capable of serial, but I dunno for NOLO20:52
DocScrutinizer05ooh wait, freemangordon told me it's a combo-xloader-nolo image that gets simply extended on loading20:53
DocScrutinizer05or was it jacekowski?20:54
Palicold flashing: omap bootrom will do handshake via usb with computer and then computer send signed bootable image (2nd) and boot it20:55
Pali2nd will read from usb secondary image which will flash to nand20:55
Paliand then also boot it and do not check voltage and bsi20:56
Paliand immediately enter to flashing mode (no need for U key)20:56
Paliomap bootrom support more boot methods (nand, mmc, usb) and one is also serial console20:57
Palithis is written somewhere in public trm20:57
freemangordonat the end :D20:58
PaliI used all this info when I was implementing cold flasher in 0xFFFF flasher20:58
Paliand if I remember it is possible to change order of booting20:58
Paliso maybe we can boot (signed) xloader from eMMC/SD20:59
DocScrutinizer05you can't change boot order. it's "hardwired"21:00
Palibut due to that there is no doc for HS devices we do not know format in which xloader needs to be stored (and where)21:00
Palifor GP devices you *can* configure boot orde21:00
Paliit is written in trm21:00
DocScrutinizer05and we know that xloader needs to be signed, so any docs on format are useless21:00
Palibut do not know if this also work for HS21:01
Palino we need docs where and how to store signed xloader21:01
DocScrutinizer05afaik "bootorder" is a few bits in EFUSE21:01
DocScrutinizer05only relecant for BOOTROM21:01
Palifor example for GP devices, bootloader needs to be stored on mmc first fat partion under name MLO21:02
DocScrutinizer05yes, that will be same I guess21:02
Palibut I think for HS devices it will be another name...21:02
DocScrutinizer05and not mmc, but uSD21:02
Paliin trm was any mmc device21:03
DocScrutinizer05no, it only checks mmc121:03
Palimmc1 is eMMC21:03
DocScrutinizer05which happens to be uSD, for exactly this reason21:03
DocScrutinizer05no, mmc1 is uSD21:03
Palimmc0 is SD21:03
DocScrutinizer05it gets renamed later21:04
Palionly maemo has swapped it21:04
DocScrutinizer05hw its mmc1 and mmc221:04
DocScrutinizer05iirc21:04
Paliok, maybe numbering starts from 1 (and not 0)21:04
DocScrutinizer05anyway bootrom looks on FIRST mmc jw interface for a file called MLO21:04
Palibut first is SD card21:04
Paliin trm is written that it can load also from raw partition21:05
DocScrutinizer05maybe21:05
DocScrutinizer05the EE design rationale been that you can boot from uSD21:06
DocScrutinizer05that's why first mmc hw interface is uSD and not eMMC21:06
Palivia usb you can tell omap bootrom to load/boot from mmc21:06
Palilike to load image via usb21:07
DocScrutinizer05via USB you can't tell anything, you just can load xloader from USB21:07
Palimaybe we can try to dd xloader to mmc as raw partition if it work...21:07
Paliyou can do it!21:07
*** X-Fade has joined #maemo-ssu21:07
Palilook at my cold flasher source code and comments21:07
Paliand trm21:08
DocScrutinizer05BOOTROM simply checks the "hardwired" (by EFUSE) devices for xloader, and loads the fist it finds21:08
DocScrutinizer05first*21:08
DocScrutinizer05everything beyond that is a matter of xloader you load, afaik21:08
Palibut before that it waits some time for usb commands21:08
DocScrutinizer05sure you can load an xloader that tries to load NOLO via WIFI21:09
freemangordonand that is how coldflashing works21:09
Palino no21:09
DocScrutinizer05basically, if xloader wasn't that tiny21:09
Paliyou can tell bootrom before booting xloader to change boot order21:09
Paliand boot from other device21:09
freemangordonPali: no? in coldfalshing mode n900 appears like some strange USB device21:09
DocScrutinizer05I had an extensive look at TRM21:09
Paliand if you want to load image via usb, you send command via usb thay you want to boot from usb21:10
PaliI written that code in 0xFFFF, so I know it21:10
DocScrutinizer05and at http://www.omappedia.org/wiki/Bootloader_Project21:10
Paliand know how cold flashing work21:11
freemangordonok :)21:11
DocScrutinizer05SYSBOOT Pins21:11
freemangordonI was under impression that coldflashing is doen with the help of bootrom, obviously wrongly :)21:12
DocScrutinizer05The internal ROM Code can attempt to boot from several different peripheral and memory devices, including, but not limited to: Serial (UART3), SD Card, eMMC, NAND, and USB. The order in which these devices are searched for a valid first-stage booting image (x-loader) is determine by a set of GPIO configuration pins referred to as SYSBOOT.21:12
DocScrutinizer05so not even EFUSE21:12
DocScrutinizer05actually hardwired21:12
Palibut before that is used usb!21:12
DocScrutinizer05nothing you can 2tell it2 via USB21:12
Paliand if you send usb command it can overwrite that is in sysboot21:13
DocScrutinizer05no21:13
Paliyes21:13
freemangordonPali: wait, it could be hardwired to try USB first21:13
Palidid you programmed already that?21:13
DocScrutinizer05[citation needed]21:13
PaliI yes21:13
freemangordonor there is a backdoor which is not in publick TRM21:14
Paliit was written in version of trm which I read when I worked on 0xFFFF21:14
DocScrutinizer05I never heard of such command, nowhere21:14
Palidownload 0xFFFF sources21:14
freemangordonPali: which TRM is that?21:14
Paligo to src/cold-flash.c21:14
DocScrutinizer05and I read the TRM as well as pages like http://www.omappedia.org/wiki/Bootloader_Project21:14
Palithere should be written version of TRM21:14
Paliand also all commands for usb!!!21:15
DocScrutinizer05ROMBOOT doesn't take commands21:15
Palias #define21:15
DocScrutinizer05that's maybe xloader, or more likely even NOLO21:15
Palitry to find in trm something like peripheral booting21:15
Paliit is not xloader/nolo21:16
DocScrutinizer05I *READ* peripheral booting in TRM21:16
Paliit is bootrom and how coldflash working21:16
Palifind something like "boot next"21:16
DocScrutinizer05it has a weird device table21:16
Palithere is "boot next" command which skip entry from device table21:17
DocScrutinizer05so what for? our first entry is uSD anyway21:17
Palifind big diagram in trm21:18
DocScrutinizer05see our particular wiring of SYSBOOT pins21:18
Palithere was also written how sysboot pin cn be skipped21:18
DocScrutinizer05WHAT FOR???21:18
Paliand start booting from device specified by usb command21:18
DocScrutinizer05even if such thing exists, it's vastly useless21:19
DocScrutinizer05since we already have boot sequence USB,MMC1,NAND21:19
DocScrutinizer05but that's for xloader only21:19
DocScrutinizer05and it's hardwired21:20
DocScrutinizer05oops21:21
DocScrutinizer05sys_boot[5:0]: 0x1021:21
DocScrutinizer05Boot order: OneNAND USB UART3 MMC1 --21:21
Pali /* Omap MMC/SD2 boot message */ # static const uint32_t omap_mmc2_msg = 0xF0030506;21:21
DocScrutinizer05IroN900:~# omap34xx-boot-order21:21
DocScrutinizer05sys_boot[5:0]: 0x1021:21
DocScrutinizer05Boot order: OneNAND USB UART3 MMC1 --21:21
Pali /* Omap Peripheral boot message */ static const uint32_t omap_peripheral_msg = 0xF0030002;21:23
Palihere are two usb commands for omap bootrom21:24
Paliusb commands exists!!!!21:24
PaliOmap Boot Messages: spruf98v.pdf (page 3444): OMAP35x Technical Reference Manual - 25.4.5 Periheral Booting21:25
Palithis is in 0xFFFF comments21:26
DocScrutinizer05gosub @gc; POP; POP; print " anyway my original statement that you can boot a device with broken USB from uSD been incorrect, as far as xloader goes "21:27
DocScrutinizer05Pali: I stand corrected21:27
DocScrutinizer05spruf98v? W*T*F??21:28
DocScrutinizer05I know rev F maybe, not V21:28
Palithis is what I found and used when worked on 0xFFFF21:28
Paliand USB in bootorder is probably usb flash disk connected in usb host mode21:29
Palinot usb in peripheral mode...21:29
Palibut do not remember21:29
FatPhil[in pub] hmmm, cant' connect to any of the default repos (e.g. nokia and extras)21:30
FatPhilhowever, I'm doin the CSSU installation without them21:30
Palichange time back to year 201021:30
DocScrutinizer05Pali: do you know which version of ROMBL this refers to? and which version N900 has?21:31
Paliotherwise nokia repo will not work21:31
FatPhilsome SSL negotiation issue21:31
PaliDocScrutinizer05: do not know version21:31
Paliand I cannot opat that big pdf on n900...21:31
FatPhilPali: can you add that to the wiki if it's not there21:32
PaliFatPhil: maybe you need to activate internet via web browser?21:32
*** LauRoman has quit IRC21:32
PaliFatPhil: I'm on n900 and copy/paste lot of parts of text is hard here...21:33
DocScrutinizer05Pali: I still think I haven't noticed those commands in SPRUF98D21:33
DocScrutinizer05they *might* be a feature of later ROMBL versions21:33
PaliDocScrutinizer05: I tested that peripheral command and it worked and also next command worked21:33
DocScrutinizer05or I ignored them since I thought they're useless21:33
DocScrutinizer05ooooh :-D21:34
Paliperipheral command is used for cold flashing21:34
Paliand next to skip cold flashing21:34
Palihttps://gitorious.org/0xffff/0xffff/source/master:src/cold-flash.c21:35
DocScrutinizer05hah. awesome21:35
Palilook at cold flash source code21:35
Paliand you can see what is handled by omap bootrom and what by xloader21:35
DocScrutinizer05/note to self: don't mess with Pali ;-)21:36
FatPhilPali: internet's flakey, but I managed to browse to the wiki, install the repo installer, and download 50MB of CSSU, which is happily installing currently21:36
Palido you know if it is possible to detect from asis id (sent by omap bootrom) if device is n900 or not?21:39
DocScrutinizer05Pali: is result of omap34xx-boot-order binary correct?21:39
DocScrutinizer05or is that somehow covered/obfuscated when system got booted up?21:40
Palion GP device should be21:40
Palibut I think it could be correct also on HS21:40
PaliI think that obfucation does not make sense21:41
Palistill it allow booting only signed image...21:41
*** dos1 has quit IRC21:42
*** LauRoman has joined #maemo-ssu21:44
*** LauRoman has quit IRC21:46
DocScrutinizer05ah, maybe some memory re-mapping kicks in after some crap in HS been set21:47
DocScrutinizer05who knows, I don't21:47
DocScrutinizer05Boot order: OneNAND USB UART3 MMC1 --    makes no sense to me21:47
*** Vlad_on_the_road has joined #maemo-ssu21:47
DocScrutinizer05lemme check the damn schematics21:48
Paliwhy?21:49
Paliits ok21:49
Paliit booting from onenand21:49
DocScrutinizer05sys_boot4:1  6:1  5:BOOTMODE21:49
Paliusb peripheral boot for cold flash is started by special usb command before that boot order21:50
DocScrutinizer05hmm, makes sense then21:50
Paliand usb in that boot order is probably booting from usb flash disk in host mode21:51
DocScrutinizer05LOL, 5:BOOTMODE is determined by CHRG_IND21:51
Paliwhich cannot work on n900 where is no usb host mode port21:51
DocScrutinizer05:nod:21:52
kolpWill anything break if I switch on host mode while wall-charging, without having anything else connected to the usb port?21:54
DocScrutinizer05IOW CPU cant boot "normal" as long as steady yellow emergency chage indicator. It's not CPU bootup that stops emergency chaging, it's emergency charging end that boots CPU21:54
FatPhilDocScrutinizer05: you understand correctly21:55
FatPhilyellow = NOLO charging, and it won't exit that till it's happy21:55
Paliwhere you found that? "DocScrutinizer05: LOL, 5:BOOTMODE is determined by CHRG_IND"21:57
DocScrutinizer05schem p. 4 & 6 &21:58
DocScrutinizer05SoC sys_boot:5 -> (BOOT_MODE) -> N130221:59
DocScrutinizer05-> (CHRG_IND) -> N1140 bq2415022:00
DocScrutinizer05CHRG_IND also directly drives red and green (=yellow) indicator LED22:00
DocScrutinizer05as long as BQ24150 is in emergency charge mode, CPU can't boot "normally"22:01
*** lenoch has quit IRC22:02
Paliand when bq2415x is in emergency mode?22:02
Paliwhen timer is not resetted in 30s?22:02
DocScrutinizer05yes, and when battery voltage below 3.7V or sth22:05
DocScrutinizer05and for max 30min22:05
DocScrutinizer05FatPhil: I wouldn't call that NOLO charging, since it's an autonomous mode of BQ24150 charger chip, CPU not involved22:07
DocScrutinizer05maybe "NOLO tolerated autonomous hw charging"22:08
FatPhilthere's a bq24150 driver in it, I presume nolo sets it up, and lets it run22:08
FatPhilhas anyone decompiled nolo?22:09
Palijacekowski only some small parts22:11
Paliits funny that nolo cannot change battery when you want to enter flash mode...22:12
Palibut has charging driver...22:12
Paliso driver is either useless or not used22:12
Palior not working22:12
Palior need to send some special command to start it?22:13
DocScrutinizer05~bootloop22:18
infoboti heard bootloop is when your device has broken rootfilesystem, so during reboot it fails on some service startup or kernel module load and thus reboots. This *drains* battery! And you can't reflash to stop bootloop when battery is drained. Recharge your battery by other means before reflashing.22:18
DocScrutinizer05~flatbatrecover22:18
infobotRemove battery for 1 minute. Insert battery. Plug powered ***NOKIA WALLCHARGER*** to device. Watch steady amber. Let sit and charge. Do NOT try to boot. After 30 min, you got either a) a booted up N900, b) flashing amber which means you can boot, c) steady amber going off - in this case start over again with ~flatbatrecover. CAVEAT! Only works when ~rootfs is OK (no ~bootloop)!.22:18
kolpDocScrutinizer05: in Neo900, would it be possible to export the root fs via USB when powered down?22:20
kolpHm, prolly not because of nand or whatever22:21
DocScrutinizer05that's a fptf question and issue22:21
kolpA software thing only?22:21
DocScrutinizer05no hw can export anything when "powered down"22:21
Paliif you use uboot, then yes22:21
kolpAh, well, wrong terminology then22:21
Paliuboot can support "reverse flash"22:22
Palibut uboot does not have working support for n900 onenand yet...22:22
DocScrutinizer05Pali: are you sure N900 NOLO has anything to do with bq24150?22:22
kolpWould be useful for fixing bootloops if you could access the root fs without booting to UI22:23
kolpAnd a security issue...22:23
PaliI know that n900 NOLO cannot fix dead battery22:23
Paliand cause bootloops instead charging enough for flashing22:23
PaliDocScrutinizer05: this is why i wrote that nolo bq support is useless...22:24
FatPhilPali, I may be thinking of nolo-h, not nolo-r22:24
DocScrutinizer05Pali: I doubt there *is* *any* bq24150 support in N900 NOLO22:25
DocScrutinizer05kolp: rescueOS can be booted from USB to RAM, and access maemo rootfs22:26
DocScrutinizer05allegedly rescueOS even can charge a battery22:26
DocScrutinizer05and also allegedly it can get ram-loaded even when nolo refuses to enter normal flashing mode22:27
DocScrutinizer05I don't see that22:27
DocScrutinizer05FatPhil: bq24150 doesn't need setup for emergency charging22:28
DocScrutinizer05that's the whole point of that mode22:29
DocScrutinizer05as soon as anything talks to bq24150 via i2c, emergency charging is stopped22:29
DocScrutinizer05and will resume only on chip reset, due to reset command or i2c watchdog (32s) timeout22:30
FatPhil~bootloop22:30
infobotbootloop is, like, when your device has broken rootfilesystem, so during reboot it fails on some service startup or kernel module load and thus reboots. This *drains* battery! And you can't reflash to stop bootloop when battery is drained. Recharge your battery by other means before reflashing.22:30
DocScrutinizer05~factinfo bootloop22:30
infobotDocScrutinizer05: there's no such factoid as bootloop22:30
DocScrutinizer05sucker??!22:30
DocScrutinizer05~bootloop22:30
infoboti heard bootloop is when your device has broken rootfilesystem, so during reboot it fails on some service startup or kernel module load and thus reboots. This *drains* battery! And you can't reflash to stop bootloop when battery is drained. Recharge your battery by other means before reflashing.22:30
DocScrutinizer05~literal bootloop22:30
infobot"#maemo bootloop" is "when your device has broken rootfilesystem, so during reboot it fails on some service startup or kernel module load and thus reboots. This *drains* battery! And you can't reflash to stop bootloop when battery is drained. Recharge your battery by other means before reflashing."22:30
DocScrutinizer05~factinfo #maemo bootloop22:31
infobot#maemo bootloop -- created by DocScrutinizer05 <~saturn@openmoko/engineers/joerg> at Thu Oct  3 14:52:17 2013 (7 days); last modified at Thu Oct  3 15:06:02 2013 by DocScrutinizer05!~saturn@openmoko/engineers/joerg; it has been requested 4 times, last by DocScrutinizer05, 17s ago.22:31
DocScrutinizer05FatPhil: ok, it's a bit fuzzy - actually emergency charging *will* work even with broken rootfs, but it will not result in NOLO allowing you to flash22:32
DocScrutinizer05since NOLO threshold to allow flashing > bq24150 threshold to stop emergency charging22:33
DocScrutinizer05iirc!22:34
Palinolo is not signed... so maybe we can try to find hex number of that value and change it?22:34
DocScrutinizer05yes, I suggested that several times22:35
Palibut there is another problem which I tested:22:35
Palinolo loaded by cold flashing (it always enter to flash mode!!) has unstable usb when battery is too empty22:36
Paliwhich caused that I was not able to flash22:36
DocScrutinizer05quite possible22:36
Palibecause usb transfer was not possible22:36
DocScrutinizer05:nod:22:36
Paliso hexchaning it will not help22:36
Paliwe need either proper charning in nolo or increase bq treshold22:37
DocScrutinizer05NOLO should learn my dirt-simple bq24150-charging22:37
*** xes has joined #maemo-ssu22:37
DocScrutinizer055 i2c commands to configure, one timer plus one i2c infinite loop to tickle WD22:38
Palibut omap bootrom was still able to transfer 2nd and secondary image and boot it!22:38
DocScrutinizer05bq24150 is sane and safe22:38
DocScrutinizer05weird22:38
Paliso if we are able to write ASM code for charning we can send 2nd and that asm code instead nolo22:39
DocScrutinizer05maybe because ROMBL doesn't initialize RAM and stuff22:39
Paliand 2nd image can boot it22:39
Palibecause nolo is not signed22:39
DocScrutinizer05:nod:22:39
Palibut somebody must write that pure ASM code for bq charging22:39
DocScrutinizer05sounds feasible22:39
DocScrutinizer05that isn't hard22:39
Paliplus in this state lot of hw parts are not initialized22:40
DocScrutinizer05i2c is a hw interface22:40
Paliand need to stop twl watchdog22:40
DocScrutinizer05:nod:22:40
PaliDocScrutinizer05: are you able to do it?22:40
DocScrutinizer05and possible even BB5 WD22:40
DocScrutinizer05I'm _able_ to do that, but no time atm22:40
Paliin uboot I turned off only twl22:41
Paliand no reset anymore22:41
DocScrutinizer05ok22:41
DocScrutinizer05then BB5 only gets upset after it got initialized22:41
DocScrutinizer05sounds ane22:41
DocScrutinizer05sane even22:42
Paliand thanks to bq24150 support in qemu we can debug code :-)22:42
DocScrutinizer05there's a reset wire from cpu to bb5, and one line the opposite direction22:42
Palicheck and dump bq registers from qemu22:42
DocScrutinizer05you already have all that in my charge draft, which ShadowJK based his charge21.sh on22:43
DocScrutinizer05it's dirt simple22:43
DocScrutinizer05main obstacle is talking to I2C IP lowlevel22:44
Palibut my low level hw programming skills are not good...22:44
DocScrutinizer05on register level22:44
PaliI never wrote any i2c driver in asm22:44
DocScrutinizer05I guess you first need to initialize it22:44
DocScrutinizer05speed and power22:44
DocScrutinizer05then simply read buffer, or write buffer22:44
DocScrutinizer05rest is hw22:45
DocScrutinizer05I never looked into ABI/API of I2C IP22:45
DocScrutinizer05but I'm EE for knowing how it must look like22:46
DocScrutinizer05some 2..5 registers22:46
Palianybody who is able to do that and has time?22:46
DocScrutinizer05btw you wouldn't need asm, use C and get the asm intermediate22:46
DocScrutinizer05or use C straight away22:47
DocScrutinizer05C obj code22:47
DocScrutinizer05C is (and always been) a glorified macro assembler22:47
Paliyou also need linker scripts/hacks to generate noloscnd header plus start code at specific address22:48
DocScrutinizer05no clue about that22:48
Palior code must be position independent22:48
DocScrutinizer05it is22:48
Paliin asm you can add .ascii "noloscnd"22:49
DocScrutinizer05some 50 ARM opcodes22:49
DocScrutinizer05you can use ASM in C22:49
DocScrutinizer05inline22:49
DocScrutinizer05don't ask me how, last I did this been 199022:50
DocScrutinizer05last I seen this must be 2 years ago22:50
DocScrutinizer05you frequently see this stuff in highly optimized low level hw drivers22:52
DocScrutinizer05but nowadays you almost don't need it anymore, with all that new smart stuff that C allows, like defining absolute addr or register for variables22:53
DocScrutinizer05Pali: check SPRUF98 for I2C hw block (IP), if any questions how to handle it, ask me22:54
DocScrutinizer05I can tell you what to do with it once you found out (with a little help from my side) _how_ to talk to I2C22:55
PaliDocScrutinizer05: I cannot look now (opening that pdf on n900 is impossible) and also Impossible) I do not have time for writing that code...22:55
DocScrutinizer05the "code" is dirt simpla. I2C is dirt simple. You send chip addr, then send register addr<<1&(read?0:1), then write or read the register value22:58
DocScrutinizer05or was it chipaddr<<1&(read?0:1), then register addr22:59
Paliand for charging you need to enable some gpio23:00
DocScrutinizer05anyway a register write are three atomic elementary writes to the i2c hw interface, a register read are two writes and one read23:00
Palitx reset or something...23:00
DocScrutinizer05huh?23:01
Palisome gpio, freemangordon already wrote it here...23:01
Palilook into log23:01
Palisome #define23:01
DocScrutinizer05sorry, I didn't get it when fmg asked you about that23:02
DocScrutinizer05and I don't get it now23:02
DocScrutinizer05there is no GPIO I know of that needs to get set for charging23:02
DocScrutinizer05there is some nasty foo for detecting charger23:03
DocScrutinizer05charging is only bq24150, and that is only attached to CPU via I2C23:04
DocScrutinizer05and it needs only I2C commands to this chip to keep it charging23:04
DocScrutinizer05~5 for setting up max voltage, max USB current, trickle charge, etc, and one recurring register access for tickling WD, every 15s23:05
DocScrutinizer05that's all it needs23:05
DocScrutinizer05~50 ARM opcodes23:05
DocScrutinizer05incl setup of the I2C hw interface in SoC23:06
DocScrutinizer05more if you want to do this in a multitasking way, allowing other tasks while tickling WD23:06
*** Pali has quit IRC23:44
FatPhilDoes the bot have a way of remembering messages for people who've left the channel...23:45
FatPhilhe says glaring at Pali...23:45
*** Vlad_on_the_road has quit IRC23:46
FatPhiloi, silly bot, tell Pali about this: http://www.spinics.net/lists/linux-omap/msg11786.html23:46
*** xes has quit IRC23:48
*** lizardo has quit IRC23:55
FatPhilANyone know what http://elinux.org/N900 and https://gitorious.org/linux-n900/linux-n900 are ?23:55

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