| 00:06.39 | *** join/#maemo-ssu trx (~ns-team@212.200.199.46) |
| 00:06.39 | *** join/#maemo-ssu trx (~ns-team@devbin/founder/trx) |
| 00:29.09 | *** join/#maemo-ssu DrCode (~DrCode@gateway/tor-sasl/drcode) |
| 01:09.04 | *** join/#maemo-ssu DrCode (~DrCode@gateway/tor-sasl/drcode) |
| 02:41.44 | *** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn) |
| 05:34.06 | *** join/#maemo-ssu DrCode (~DrCode@gateway/tor-sasl/drcode) |
| 05:56.21 | *** join/#maemo-ssu luf (~luf@80.188.29.62) |
| 06:01.35 | *** join/#maemo-ssu DrCode (~DrCode@gateway/tor-sasl/drcode) |
| 06:07.45 | *** join/#maemo-ssu freemangordon_ (~freemango@46.249.74.23) |
| 06:39.55 | *** join/#maemo-ssu tom (~tom@66.172.11.27) |
| 06:42.04 | *** join/#maemo-ssu DrCode (~DrCode@gateway/tor-sasl/drcode) |
| 07:02.54 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-91-21.residential.rdsnet.ro) |
| 07:17.41 | *** join/#maemo-ssu tom (~tom@66.172.11.27) |
| 07:38.27 | *** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 07:49.11 | *** join/#maemo-ssu Pali (~Pali@Maemo/community/contributor/Pali) |
| 07:52.26 | DocScrutinizer05 | http://talk.maemo.org/showthread.php?p=1372710#post1372710 |
| 08:03.14 | *** join/#maemo-ssu MohammadAG (~MohammadA@Maemo/community/contributor/MohammadAG) |
| 08:22.27 | FatPhil | Damn, a second of my n900s has a broken USB :( |
| 08:24.25 | *** join/#maemo-ssu X-Fade (~xfade@d5152FFD8.static.telenet.be) |
| 08:30.05 | FatPhil | "What we need for infra are volunteers, raw manpower" - such as? |
| 08:43.33 | *** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172) |
| 08:43.40 | *** join/#maemo-ssu joshgillies (~josh@ppp108-14.static.internode.on.net) |
| 08:44.54 | joshgillies | anyone in here developing on an ARM chromebook? |
| 08:45.10 | joshgillies | looking for pointers toward getting the sdk up and running |
| 08:48.13 | Pali | no chromebook here |
| 08:48.33 | freemangordon_ | Pali: we have a problem with omapfb :( |
| 08:48.39 | freemangordon_ | and dss driver too |
| 08:48.57 | Pali | which problem? |
| 08:49.08 | Pali | cma not working? |
| 08:49.22 | freemangordon_ | CMA actually doesn;t seem to work reliably, so it can't allocate framebuffer memory |
| 08:49.44 | freemangordon | Pali: yes |
| 08:50.13 | Pali | and why preallocate without cma not working? |
| 08:50.24 | freemangordon | Pali: it is removed ;) |
| 08:50.34 | freemangordon | no more vram= boot parameter |
| 08:50.37 | Pali | ah... |
| 08:50.48 | freemangordon | and dss: |
| 08:50.50 | freemangordon | Jan 1 06:35:24 Nokia-N900 kernel: [ 2172.539093] omapdss DISPC error: horizontal timing too tight |
| 08:50.50 | freemangordon | Jan 1 06:35:24 Nokia-N900 kernel: [ 2172.545074] omapdss APPLY error: dispc_ovl_setup failed for ovl 1 |
| 08:51.45 | freemangordon | this happens for both 720p and lower res videos |
| 08:51.59 | freemangordon | (in case CMA succeeds :D ) |
| 08:52.15 | freemangordon | Pali: but on the bright side, seems DSP is tock stable |
| 08:52.19 | freemangordon | *rock |
| 08:55.00 | Pali | ok, so if you disable cma low res videos working? |
| 08:55.45 | freemangordon | Pali: makes no difference, as then memory cannot be allocated because of the fragmentation |
| 08:56.14 | freemangordon | so CMA is the way, but it seems broken |
| 09:00.26 | Pali | and reverting preallocate? |
| 09:02.25 | freemangordon | didn't try it, but I guess it will fix the problem |
| 09:26.41 | *** join/#maemo-ssu LaoLang_cool (~LaoLang_c@218.107.16.197) |
| 09:43.11 | *** join/#maemo-ssu kolp (~quassel@212.255.30.22) |
| 10:28.49 | DocScrutinizer05 | FatPhil: such as somebody looking into tmo karma and fixing it |
| 10:31.41 | kolp | I 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... :) |
| 10:32.13 | kolp | Hm, wrong channel.. |
| 10:37.23 | *** join/#maemo-ssu lizardo (lizardo@nat/indt/x-crlgqczyrubvzhou) |
| 10:53.32 | *** join/#maemo-ssu joshgillies (~josh@ppp108-14.static.internode.on.net) |
| 12:25.34 | *** join/#maemo-ssu Pali (~Pali@Maemo/community/contributor/Pali) |
| 12:39.16 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-91-21.residential.rdsnet.ro) |
| 13:13.30 | freemangordon | ~ping |
| 13:13.30 | infobot | ~pong |
| 13:26.47 | freemangordon | Pali: how am I supposed to report that omapfb problem on lkml? |
| 13:34.59 | jonwil | ok, 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... |
| 13:35.01 | jonwil | ...nice "Pulseaudio for Dummies" type book out there :) |
| 13:42.18 | Pali | freemangordon: run ./scripts/get_maintainers.pl -f /path/to/omapfb and check who is maintainer |
| 13:42.34 | Pali | and send email to maintainers plus maybe cc lkml |
| 13:42.42 | freemangordon | Pali: ok, thanks |
| 13:43.20 | Pali | jonwil: first: it using library libplayback |
| 13:43.41 | Pali | in this library you can tell type (voice call, music, other...) |
| 13:44.26 | Pali | libplayback using dbus to inform ohmd about type and also set some PA property on used PA stream |
| 13:44.54 | freemangordon | Pali: hmm, do we have anything major but cameras that doesn't work in 3.12? |
| 13:45.05 | Pali | jonwil: second: via native bluetooth PA plugin |
| 13:45.30 | Pali | PA somehow connect to bluetoothd (dbus/socket) |
| 13:45.54 | jonwil | so libplayback specifically talks to pulseaudio? |
| 13:45.58 | Pali | this is fully documented somewhere and it is standard solution on linux desktop |
| 13:46.00 | jonwil | or does ohmd talk to pulseaudio somewhere? |
| 13:46.06 | Pali | jonwil: probably yes |
| 13:46.10 | jonwil | ok |
| 13:46.17 | Pali | ohmd can talk to PA |
| 13:46.26 | Pali | and also libplayback can talk too |
| 13:46.57 | Pali | freemangordon: camera, sound, maybe jack |
| 13:47.04 | jonwil | what about FM? |
| 13:47.12 | Pali | and fmtx/fmrx is not tested |
| 13:47.17 | jonwil | ok |
| 13:47.25 | Pali | but drivers are there |
| 13:47.42 | freemangordon | Pali: I was able to get sound through BT :) some days ago |
| 13:47.43 | Pali | fmrx driver is same as in fremantle kernel |
| 13:47.54 | Pali | (I checked it) |
| 13:48.02 | jonwil | I mean how does FMTX/FMRX end up in PulseAudio? |
| 13:48.07 | Pali | and bluetooth driver was tested by skry and it worked |
| 13:48.32 | freemangordon | Pali: though I see lots of "unrecognized HCI packet) |
| 13:48.38 | Pali | jonwil: fm and PA on n900 is totally unknown for me |
| 13:48.44 | jonwil | ok |
| 13:48.56 | jonwil | FMTX goes though fmtx-middleware |
| 13:49.00 | jonwil | so I should probably start there |
| 13:49.14 | freemangordon | jonwil: RE fmtxd :) |
| 13:49.18 | Pali | but I do not understand why middleware is needed |
| 13:49.33 | Pali | fmtx should be /dev/radio device |
| 13:49.38 | freemangordon | Pali: it controls stuff like USB cable connected, etc |
| 13:49.44 | Pali | and alsa has radio plugin |
| 13:49.47 | freemangordon | also regional frequencies |
| 13:50.03 | Pali | so PA can use normal alsa interface for radio support |
| 13:50.13 | Pali | and it should act as sound card... |
| 13:50.29 | Pali | freemangordon: only that? or it also routing audio? |
| 13:50.58 | Pali | freemangordon: also need to test bluetooth if working |
| 13:51.05 | freemangordon | not sure, but I *think* it is not fmtxd to route. might be wrong, didn;t look at it |
| 13:51.23 | Pali | and need to test if wifi adhoc mode working |
| 13:51.42 | Pali | all audio on maemo is big mess |
| 13:51.59 | jonwil | btw, 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. |
| 13:53.08 | Pali | alsa, PA, PA modules, alsa policy, PA policy, alsaped, pasr, ohmd, ohm plugins, libplayback, swi-prolog, prolog code, dresd, dres daemon... |
| 13:53.16 | Pali | and other stuff which I forgot |
| 13:55.19 | jonwil | btw pali are you 100% sure that your decompile of the policy-settings-rx51 prolog code is functionally identical to the stock compiled prolog code? |
| 13:55.40 | Pali | I'm 99% sure |
| 13:56.10 | jonwil | ok, in that case all we need to do is to write a decompiler for policy.dresc :) |
| 13:56.30 | freemangordon | http://talk.maemo.org/showpost.php?p=1379819&postcount=72 |
| 13:56.33 | Pali | there is 1% chance that I forgot something (some non predicate prolog code) |
| 13:56.52 | Pali | jonwil: do we need it? |
| 13:56.56 | freemangordon | feel free to correct me if I've write something which is not correct |
| 13:57.25 | freemangordon | *written |
| 13:57.33 | Pali | jonwil: one nokia dev wrote on TMO some info about dres and dres compiler |
| 13:57.39 | jonwil | yes he did |
| 13:57.44 | jonwil | I remember it |
| 14:01.03 | Pali | jonwil: you can try contact him again, if he does not have any usefull stuff (e.g. decompiler :-)) |
| 14:01.19 | kolp | Getting rid of prolog sounds like a worthwile goal :) |
| 14:01.37 | jonwil | I doubt he would have a decompiler as there would be no reason to write one |
| 14:01.55 | FatPhil | freemangordon: where can I pull your kernel? |
| 14:02.53 | Pali | jonwil: instead writing decompiler it should be easier to load that dres binary file into dres VM and dump factoid info into debug console |
| 14:03.30 | Pali | jonwil: if I remember correctly in dres file are only some functions and lot of static data... |
| 14:04.25 | Pali | and that debug dump command doing some "disassembling" of current memory state |
| 14:04.54 | Pali | and dres VM is stack based - this could help you |
| 14:06.15 | Pali | freemangordon: what is needed is to patch all maemo daemons to work without that kernel patch for sysfs |
| 14:06.36 | freemangordon | Pali: which patch? |
| 14:06.41 | freemangordon | gpio? |
| 14:06.48 | freemangordon | ooh |
| 14:06.57 | Pali | no select syscall |
| 14:07.00 | freemangordon | yeah |
| 14:07.09 | freemangordon | FatPhil: a second |
| 14:07.20 | Pali | but that omap platform gpio driver too |
| 14:07.26 | Pali | needs to be rewritten |
| 14:07.42 | Pali | or removing using it from maemo apps... |
| 14:07.43 | freemangordon | FatPhil: this is upstream (Pali :P ) https://gitorious.org/linux-n900/linux-n900/source/683cc15ed3e6bceb51472a530244f72fa8d40b52: |
| 14:08.22 | freemangordon | FatPhil: this is mine tree ( a little bit ahead) https://gitorious.org/linux-n900/freemangordons-linux-n900/source/777f4ace4c58799575391833db48050ceefe6fd6: |
| 14:08.23 | jonwil | Which maemo apps are using this particular driver? |
| 14:08.39 | jonwil | the GPIO one |
| 14:08.41 | Pali | jonwil: sscd :-( |
| 14:08.47 | jonwil | ugh |
| 14:08.50 | Pali | mce |
| 14:08.58 | Pali | preinit |
| 14:09.00 | freemangordon | Pali: sscd is small binary |
| 14:09.12 | freemangordon | and we know what it does |
| 14:09.32 | Pali | sscd is using it for cmt_ gpios for init |
| 14:09.36 | freemangordon | mce... well... :) |
| 14:09.40 | freemangordon | Pali: :nod: |
| 14:09.49 | jonwil | I wouldn't call 100k a small binary in my book |
| 14:09.58 | freemangordon | jonwil: sscd is 100K? |
| 14:10.03 | Pali | and every app which using any gpio directly |
| 14:10.10 | jonwil | yes its 108,836 bytes |
| 14:10.19 | freemangordon | omg, my bad |
| 14:10.23 | Pali | (do not know which other) |
| 14:10.44 | freemangordon | Pali: well, I guess we can live with that gpio |
| 14:10.53 | Pali | just call grep /sys/something on maemo |
| 14:10.56 | Pali | ok |
| 14:11.06 | freemangordon | for the select thingie, we can LD_PRELOAD |
| 14:11.37 | Pali | ok |
| 14:12.36 | Pali | freemangordon: what is problem with front camera? |
| 14:12.52 | Pali | still green rectangle? |
| 14:13.01 | freemangordon | yep |
| 14:13.10 | Pali | or something changed after fixing IRQ? |
| 14:13.22 | freemangordon | nothing |
| 14:13.30 | freemangordon | ISP irqs are just fine |
| 14:13.56 | freemangordon | it is something in the ISP driver, I hope sailus ti help us find it |
| 14:13.56 | Pali | freemangordon: I remember that somebody wrote that camera worked on meego with meego 37+ kernel |
| 14:14.18 | Pali | maybe looking into meego n900 kernel tree... |
| 14:14.29 | freemangordon | Pali: there is a long way between 2.6.37 and 3.12 as you probably know :P |
| 14:14.35 | Pali | yes |
| 14:14.48 | freemangordon | Pali: looked, the driver is the same |
| 14:14.54 | Pali | but checking if we not miss some patch which is not in upstream... |
| 14:14.59 | Pali | ok |
| 14:15.16 | freemangordon | Pali: well, it is possible I've missed something |
| 14:17.24 | freemangordon | Pali: BTW 3.12 boots the screen in 32bpp by default :) |
| 14:17.52 | *** join/#maemo-ssu dos1 (~dos@unaffiliated/dos1) |
| 14:17.55 | freemangordon | I have fix, still not pushed |
| 14:17.56 | Pali | and what should be correct? |
| 14:17.59 | freemangordon | 16 |
| 14:18.26 | freemangordon | or even 15, not sure |
| 14:18.30 | Pali | ~seen pavelm |
| 14:18.34 | infobot | pavelm <~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,'. |
| 14:18.57 | freemangordon | Pali: we need omapfb.mode=lcd:848x480-16 in cmdline |
| 14:19.31 | Pali | cannot be mode passed from board data? |
| 14:19.41 | freemangordon | what about DT? :P |
| 14:19.49 | Pali | or DT? |
| 14:19.58 | freemangordon | not sure about DT |
| 14:20.10 | Pali | I think resolution is already in board file |
| 14:21.23 | freemangordon | I dont see it https://gitorious.org/linux-n900/freemangordons-linux-n900/source/777f4ace4c58799575391833db48050ceefe6fd6:arch/arm/mach-omap2/board-rx51-video.c |
| 14:24.19 | freemangordon | Pali: BTW leds still doesn't work |
| 14:24.26 | freemangordon | well, RGB led |
| 14:26.10 | freemangordon | Pali: 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 load |
| 14:30.50 | jonwil | ok, 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 librariy |
| 14:30.59 | jonwil | libplayback-1.a that is |
| 14:31.18 | jonwil | and the x86 binary .so file is only 21k |
| 14:31.42 | jonwil | all I have to figure out now is if there is any useful debugging info in that .a file |
| 14:34.56 | Pali | jonwil: if you RE libplayback please write some documentation... |
| 14:35.14 | Pali | see maemo wiki, there are already some links for libplayback |
| 14:35.39 | Pali | freemangordon: I will look on led driver |
| 14:45.08 | freemangordon | FatPhil: but in order to boot maemo you need some userspace packages installed from cssu-devel and some help from Pali :) |
| 14:45.27 | freemangordon | and maybe from me |
| 14:46.01 | Pali | s/some/all/ |
| 14:46.10 | freemangordon | :D |
| 14:46.43 | freemangordon | Pali: well, clock-ui is not needed I guess. |
| 14:48.01 | jonwil | god I hate when libraries have an internal data structure and just pass around pointers to it. |
| 14:49.04 | Pali | welcome to OOP world :-) |
| 14:50.08 | jonwil | interesting, 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? |
| 14:51.18 | Pali | application name... |
| 14:51.57 | jonwil | what handles that though? pulseaudio? ohm/policy/prolog? something else? |
| 14:52.01 | Pali | we already know that application with name "mediaplayer" can something do what other cannot |
| 14:52.16 | Pali | if I remember it is alsaped together with prolog and dres |
| 14:52.40 | Pali | and there also is some config ini file where is mediaplayer written |
| 14:52.46 | freemangordon | hmm, there is a huge plicy file somewhere in /etc |
| 14:52.46 | freemangordon | *policy |
| 14:53.17 | Pali | jonwil: and maybe really voip and gsm calls are same for PA |
| 14:53.52 | jonwil | no they are not, PA needs to know the difference to know whether to feed the audio to libcmtspeech or not |
| 14:54.00 | jonwil | aha, Policy-application-detector relates to this |
| 14:54.23 | Pali | right that detector is other audio application |
| 14:54.24 | jonwil | its what grabs the name and feeds it to the policy ststem |
| 14:54.26 | jonwil | system |
| 14:54.50 | Pali | jonwil: if I remember correctly it talk to some udp port on localhost to ohmd |
| 14:54.59 | Pali | and it is small daemon |
| 14:55.08 | Pali | can you look if you can RE it? |
| 14:55.22 | jonwil | I will look |
| 14:55.31 | jonwil | aha, the big conf file you mentioned looks like xpolicy.conf |
| 14:55.40 | Pali | it sending something like "pop up" or "pop down" via udp |
| 14:56.18 | Pali | and it checking for X window number... |
| 14:56.55 | Pali | that config file is maybe in git repo where is decompiled prolog file |
| 14:57.08 | Pali | and I think I already modified it |
| 14:59.08 | jonwil | ok, yeah the file is definatly xpolicy.conf |
| 15:00.34 | jonwil | going to look at policty-application-detector |
| 15:01.46 | jonwil | ok, app-detect seems to be looking for rtcom-call-ui and systemui by name |
| 15:04.26 | jonwil | its sending to port 3001 and 3002 |
| 15:06.04 | Pali | you can download ohms sources (+ plugins) |
| 15:06.17 | Pali | look at fremantle closed packages for correct git commit |
| 15:06.28 | Pali | and you can see what ohmd doing with it |
| 15:09.17 | jonwil | yes I know |
| 15:19.27 | jonwil | ok, looks like I will need to find a good tutorial or guide on sources and sinks in pulseaudio |
| 15:29.59 | FatPhil | Pali: 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? |
| 15:31.22 | FatPhil | is unhappy that 2 of his n900s are "junker"s :-( But at least one is fine for dev work presently. |
| 15:31.37 | freemangordon | FatPhil: flash it with stock pr1.3, install cssu-testing(or -thumb) and use Pali's script to copy maemo to /home/maemo5 |
| 15:31.38 | *** join/#maemo-ssu LaoLang_cool (~LaoLang_c@218.107.16.197) |
| 15:32.05 | FatPhil | freemangordon: OK, I'll get back to you in a few hours... |
| 15:32.25 | FatPhil | What's the week/release number of "stock" pr1.3? |
| 15:32.26 | freemangordon | FatPhil: oh, and before executing Pali's copy script, enable cssu-devel repo and do apt-get update/upgrade |
| 15:32.33 | freemangordon | 2-36 iirc |
| 15:32.46 | freemangordon | or was it 36-2?!? |
| 15:33.48 | freemangordon | FatPhil: keep in mind that both trees (mine and Pali's) lack an et8ek8 patch, i'll provide it to you via pastebin |
| 15:33.53 | kolp | 36-2 |
| 15:34.53 | freemangordon | FatPhil: http://pastebin.com/Xw71qprL |
| 15:35.42 | *** join/#maemo-ssu lenoch (~lenoch@152.198.broadband11.iol.cz) |
| 15:36.20 | FatPhil | I swear I did that on my daily device, but can't find the fiascos now |
| 15:36.35 | FatPhil | brain (or filesystem) like a sieve |
| 15:38.16 | freemangordon | flashing |
| 15:38.16 | freemangordon | ~flashing |
| 15:38.16 | infobot | it has been said that maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware |
| 15:38.27 | Pali | tablets-dev.nokia.com |
| 15:38.32 | FatPhil | which would you prefer I do, -thumb, or non-thumb? |
| 15:38.45 | freemangordon | FatPhil: -thumb is faster |
| 15:38.48 | FatPhil | I'd rather be at the cutting edge, so -thumb |
| 15:38.53 | freemangordon | otherwise it doesn;t really matter |
| 15:39.49 | *** join/#maemo-ssu NIN101 (~NIN@p5DD2875D.dip0.t-ipconnect.de) |
| 15:39.56 | FatPhil | IT 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 both |
| 15:40.15 | freemangordon | FatPhil: test what? |
| 15:40.39 | freemangordon | it is not even in alpha stage (kernel) |
| 15:50.42 | FatPhil | test the kernel, test it boots to /init, after that, the kernel's job is over ;-) |
| 15:50.56 | FatPhil | Userspace is evil and should be killed! |
| 15:52.09 | freemangordon | with fire :D |
| 15:56.10 | FatPhil | with signal number 9, why give it any warning!? |
| 15:59.53 | FatPhil | This 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 userspace |
| 16:00.28 | freemangordon | FatPhil: hmm, u-boot is after nolo so it shouldn't make any difference |
| 16:01.54 | freemangordon | FatPhil: do as I say: |
| 16:02.03 | freemangordon | 1. remove the battery |
| 16:02.11 | freemangordon | 2: plug the USB cable |
| 16:02.23 | freemangordon | press'n'hold U |
| 16:02.24 | FatPhil | I'm on the jig, so battery removal is a switch |
| 16:02.29 | FatPhil | ooooh |
| 16:02.46 | freemangordon | 4. insert the batteru |
| 16:02.59 | freemangordon | missing the 'U' step? |
| 16:04.14 | FatPhil | what R&D flag state should I be in? |
| 16:04.28 | freemangordon | doesn;t matter iirc |
| 16:05.22 | FatPhil | U's not making any difference |
| 16:05.30 | FatPhil | AH - cold flash! |
| 16:05.34 | FatPhil | I'd forgotten about thayt |
| 16:05.44 | freemangordon | why cold flash? |
| 16:05.49 | freemangordon | your NOLO is broken? |
| 16:06.20 | FatPhil | Hmm, I don't have a signed second |
| 16:06.38 | FatPhil | Not sure, but flashing ain't working |
| 16:06.48 | freemangordon | FatPhil: if flasher can;t see it, try another USB port or even USB hub |
| 16:07.06 | FatPhil | flasher can read the R&D flags |
| 16:07.22 | freemangordon | but,but... then it sees it, what is the problem? |
| 16:07.34 | FatPhil | it doesn't see it when I try to flash |
| 16:07.51 | freemangordon | wrong flasher parameters? |
| 16:08.05 | freemangordon | flasher -F fiasko -f -R |
| 16:08.09 | freemangordon | (iirc) |
| 16:08.14 | FatPhil | yeah |
| 16:08.24 | freemangordon | doesn;t make any sense |
| 16:08.44 | Pali | nolo checking for BSI of battery |
| 16:08.55 | freemangordon | oh :) |
| 16:09.04 | Pali | and if BSI or charge level is loo low refuse flashing |
| 16:09.24 | freemangordon | thinks Pali is a smart guy |
| 16:09.27 | freemangordon | :D |
| 16:09.29 | Pali | s/charge level/voltage level/ |
| 16:10.04 | Pali | I wrote new version of 0xFFFF flasher :-) |
| 16:10.33 | freemangordon | Pali: hmm, IMO those checks are sane |
| 16:10.57 | Pali | but if you load NOLO from cold flash, then it disable these checks |
| 16:11.06 | freemangordon | we don;t know what will happen if you run out of juice in the middle of cmt FW flashing |
| 16:11.30 | freemangordon | broken BB5 I guess |
| 16:13.47 | FatPhil | yeah, I it doesn't always do the query-rd-mode either |
| 16:14.50 | FatPhil | [ 0.145] Battery voltage 4.104 V, BSI: 1021 |
| 16:15.11 | FatPhil | hmm, well, that's a jig |
| 16:15.46 | FatPhil | ANyone got a copy of secondary for a cold flash? |
| 16:16.11 | kolp | When 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? |
| 16:17.14 | freemangordon | FatPhil: secondary is in fiasko, you can extract it |
| 16:18.06 | dos1 | kolp: NOLO is propertary, so "nope" for N900 |
| 16:18.37 | dos1 | but in Neo900, whole stack will be open as in GTA04, so it will be there if someone implements it |
| 16:18.51 | kolp | Oh, it's a nolo thing |
| 16:18.57 | kolp | Ok, thx :) |
| 16:27.55 | FatPhil | I think it's dodgy USB connector :-( |
| 16:32.05 | kerio | :( |
| 16:33.57 | FatPhil | NP, I never gave my g/f her replacement device - I've just made it my dev device! |
| 16:34.40 | FatPhil | I've promised to do surgery to her device to put a new screen and frame on it, as otherwise her device is fine |
| 16:35.46 | FatPhil | I'd like to dedicate this flashing to my ex-boss, Timo Jokiaho, who sold me this device for 8 (rather good) beers! |
| 16:36.06 | FatPhil | He doesn't have to worry about any of his personal information still being on it anywhere, put it that way |
| 16:36.29 | merlin1991 | well for that you'll have to flash emmc aswell |
| 16:37.40 | freemangordon | merlin1991: hi! |
| 16:37.56 | freemangordon | merlin1991: nuw cssu soon? |
| 16:37.58 | freemangordon | *new |
| 16:38.06 | Pali | merlin1991 are you alive? :-) |
| 16:38.22 | freemangordon | Pali: that could be bot |
| 16:38.32 | merlin1991 | Pali: I've been reading this channel regulary since a week or so |
| 16:38.36 | FatPhil | merlin1991: did that first |
| 16:38.42 | merlin1991 | never had a point though where I could jump in :D |
| 16:39.11 | merlin1991 | for new cssu I'll start gathering stuff this weekend |
| 16:39.12 | freemangordon | Pali: lets use turing test on him :) |
| 16:39.28 | merlin1991 | my storage unit isn't endless |
| 16:39.57 | Pali | turing test has nothing with storage size :-) |
| 16:40.03 | freemangordon | :nod: |
| 16:40.23 | freemangordon | ~turing |
| 16:40.23 | infobot | ...but I *AM* Turing complete!!!! |
| 16:40.44 | merlin1991 | iirc If a machine is turing complete you still need storage for instructions relative to the complexity of your problem |
| 16:40.47 | freemangordon | infobot: no, you are not |
| 16:40.47 | infobot | freemangordon: I think you lost me on that one |
| 16:41.17 | freemangordon | merlin1991: turing test doesn;t mean turing complete (iirc) |
| 16:41.36 | freemangordon | http://en.wikipedia.org/wiki/Turing_test |
| 16:41.43 | Pali | in turing test you have to decide if you are talking with robot or real peron |
| 16:41.45 | merlin1991 | was turing test then the one with humans? |
| 16:41.49 | merlin1991 | ah yep :) |
| 16:41.50 | freemangordon | yep |
| 16:45.26 | merlin1991 | btw all this kernel hacking, do you plan on bringing our userspace running on upstream+patches, or what is the ultimate goal |
| 16:45.39 | freemangordon | I guess |
| 16:46.24 | freemangordon | merlin1991: *if* we had to support neo900, I don;t see why we shouldn't support n900 as well |
| 16:46.38 | freemangordon | not to say it will be much easier |
| 16:47.10 | freemangordon | merlin1991: does it make sense to you? |
| 16:47.21 | merlin1991 | in a way |
| 16:48.13 | freemangordon | merlin1991: I really hope neo900 will bring some developers back to fremantle |
| 16:48.40 | merlin1991 | heh, I'd happily go back to a n900 that is faster |
| 16:48.59 | merlin1991 | I'd finally have my openvpn relay again, proper ssh with a keyboard, ... |
| 16:49.15 | freemangordon | merlin1991: whaaat? n900 is not your primary device ?!? |
| 16:49.27 | merlin1991 | nope I'm on the dark side (n9) |
| 16:50.00 | freemangordon | hmm, this isn't dark side IMO, this is grey side |
| 16:50.11 | merlin1991 | it's almost black hat xD |
| 16:50.21 | freemangordon | you have the worst from the both worlds :D |
| 16:50.52 | merlin1991 | my main reason for using the n9 is, that the modem in there still works properly :D |
| 16:51.08 | merlin1991 | with my n950, and all 3 n900s I loose connection all the time |
| 16:51.30 | freemangordon | merlin1991: but wy don;t buy another n900, those are cheap these days, I heard of people getting one fo a couple of beers :D |
| 16:51.52 | freemangordon | merlin1991: hmm, tried to change the SIM? |
| 16:52.29 | merlin1991 | I have 2 sims, both work fine in the n9 but fail in all the others |
| 16:52.39 | freemangordon | weird |
| 16:53.04 | FatPhil | My daily device was bought for 7 beers, the development device was bought for 8. ~30e each in real money |
| 16:53.49 | freemangordon | what?!? 4 euros a beer |
| 16:55.39 | FatPhil | YEah, I bought them in Estonia rather than Finland. |
| 16:56.07 | FatPhil | spent 120e on beer on thursday night (last but one day at work in Finland) |
| 16:56.43 | FatPhil | still got to work bright and early on my last day, clearly didn't drink enough |
| 16:56.54 | freemangordon | :D |
| 16:57.55 | merlin1991 | hm 120€ in beer |
| 16:58.04 | merlin1991 | I'd be dead if I try that here |
| 16:58.17 | freemangordon | well, what are friends for? |
| 16:58.17 | merlin1991 | that would be like 40 beers |
| 16:58.54 | freemangordon | (about 120 here :P) |
| 16:59.02 | freemangordon | ina abar |
| 16:59.03 | FatPhil | Fancy imported beers, up to 25e a bottle |
| 16:59.09 | freemangordon | OMG |
| 17:00.29 | FatPhil | Welcome to Finland |
| 17:00.43 | merlin1991 | been there, saw the prices :D |
| 17:02.32 | FatPhil | Are devices with broken USB of use to any developers? How do you flash if not over USB? (there ought to be a SSD boot!) |
| 17:04.25 | dos1 | µsd boot works with u-boot |
| 17:04.39 | dos1 | (but probably not with fremantle :)) |
| 17:05.55 | merlin1991 | I still need to fix my sisters usb port, so I can get my only functioning n900 back xD |
| 17:06.06 | merlin1991 | I have the parts, but not the soldering equipment :/ |
| 17:08.17 | FatPhil | me too. now have 1 broken, and 1 very dodgy usb device |
| 17:17.03 | Pali | there should be way to flash device via serial console |
| 17:17.17 | Pali | at least flasher-3.5 has support for it |
| 17:17.49 | Pali | flasher-3.5 can cold flash device via serial console |
| 17:19.10 | Pali | but 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) |
| 17:30.50 | FatPhil | Well, in order to dick with package repo's easily, I'm gonna need wifi, and that means a pub! |
| 17:32.57 | FatPhil | Pali: gonna have to look into that. Not sure how to control flasher, it asks for USB ids. |
| 17:33.12 | *** join/#maemo-ssu XDS2010 (uid1218@gateway/web/irccloud.com/x-dmpzzuohfsbneaqm) |
| 17:33.27 | sixwheeledbeast | did someone say pub? :P |
| 17:35.08 | Pali | you need to use cold flashing (-c param) |
| 17:52.36 | DocScrutinizer05 | Pali: I guess xloader is capable of serial, but I dunno for NOLO |
| 17:53.47 | DocScrutinizer05 | ooh wait, freemangordon told me it's a combo-xloader-nolo image that gets simply extended on loading |
| 17:54.06 | DocScrutinizer05 | or was it jacekowski? |
| 17:55.07 | Pali | cold flashing: omap bootrom will do handshake via usb with computer and then computer send signed bootable image (2nd) and boot it |
| 17:55.43 | Pali | 2nd will read from usb secondary image which will flash to nand |
| 17:56.00 | Pali | and then also boot it and do not check voltage and bsi |
| 17:56.45 | Pali | and immediately enter to flashing mode (no need for U key) |
| 17:57.35 | Pali | omap bootrom support more boot methods (nand, mmc, usb) and one is also serial console |
| 17:57.58 | Pali | this is written somewhere in public trm |
| 17:58.27 | freemangordon | at the end :D |
| 17:58.30 | Pali | I used all this info when I was implementing cold flasher in 0xFFFF flasher |
| 17:58.57 | Pali | and if I remember it is possible to change order of booting |
| 17:59.28 | Pali | so maybe we can boot (signed) xloader from eMMC/SD |
| 18:00.08 | DocScrutinizer05 | you can't change boot order. it's "hardwired" |
| 18:00.10 | Pali | but due to that there is no doc for HS devices we do not know format in which xloader needs to be stored (and where) |
| 18:00.43 | Pali | for GP devices you *can* configure boot orde |
| 18:00.49 | Pali | it is written in trm |
| 18:00.55 | DocScrutinizer05 | and we know that xloader needs to be signed, so any docs on format are useless |
| 18:01.02 | Pali | but do not know if this also work for HS |
| 18:01.22 | Pali | no we need docs where and how to store signed xloader |
| 18:01.35 | DocScrutinizer05 | afaik "bootorder" is a few bits in EFUSE |
| 18:01.46 | DocScrutinizer05 | only relecant for BOOTROM |
| 18:02.00 | Pali | for example for GP devices, bootloader needs to be stored on mmc first fat partion under name MLO |
| 18:02.24 | DocScrutinizer05 | yes, that will be same I guess |
| 18:02.45 | Pali | but I think for HS devices it will be another name... |
| 18:02.51 | DocScrutinizer05 | and not mmc, but uSD |
| 18:03.06 | Pali | in trm was any mmc device |
| 18:03.21 | DocScrutinizer05 | no, it only checks mmc1 |
| 18:03.35 | Pali | mmc1 is eMMC |
| 18:03.43 | DocScrutinizer05 | which happens to be uSD, for exactly this reason |
| 18:03.53 | DocScrutinizer05 | no, mmc1 is uSD |
| 18:03.55 | Pali | mmc0 is SD |
| 18:04.02 | DocScrutinizer05 | it gets renamed later |
| 18:04.03 | Pali | only maemo has swapped it |
| 18:04.19 | DocScrutinizer05 | hw its mmc1 and mmc2 |
| 18:04.22 | DocScrutinizer05 | iirc |
| 18:04.48 | Pali | ok, maybe numbering starts from 1 (and not 0) |
| 18:04.54 | DocScrutinizer05 | anyway bootrom looks on FIRST mmc jw interface for a file called MLO |
| 18:04.56 | Pali | but first is SD card |
| 18:05.24 | Pali | in trm is written that it can load also from raw partition |
| 18:05.39 | DocScrutinizer05 | maybe |
| 18:06.01 | DocScrutinizer05 | the EE design rationale been that you can boot from uSD |
| 18:06.24 | DocScrutinizer05 | that's why first mmc hw interface is uSD and not eMMC |
| 18:06.51 | Pali | via usb you can tell omap bootrom to load/boot from mmc |
| 18:07.01 | Pali | like to load image via usb |
| 18:07.24 | DocScrutinizer05 | via USB you can't tell anything, you just can load xloader from USB |
| 18:07.33 | Pali | maybe we can try to dd xloader to mmc as raw partition if it work... |
| 18:07.40 | Pali | you can do it! |
| 18:07.56 | *** join/#maemo-ssu X-Fade (~xfade@d5152FFD8.static.telenet.be) |
| 18:07.56 | Pali | look at my cold flasher source code and comments |
| 18:08.01 | Pali | and trm |
| 18:08.12 | DocScrutinizer05 | BOOTROM simply checks the "hardwired" (by EFUSE) devices for xloader, and loads the fist it finds |
| 18:08.18 | DocScrutinizer05 | first* |
| 18:08.49 | DocScrutinizer05 | everything beyond that is a matter of xloader you load, afaik |
| 18:08.53 | Pali | but before that it waits some time for usb commands |
| 18:09.11 | DocScrutinizer05 | sure you can load an xloader that tries to load NOLO via WIFI |
| 18:09.13 | freemangordon | and that is how coldflashing works |
| 18:09.20 | Pali | no no |
| 18:09.23 | DocScrutinizer05 | basically, if xloader wasn't that tiny |
| 18:09.50 | Pali | you can tell bootrom before booting xloader to change boot order |
| 18:09.56 | Pali | and boot from other device |
| 18:09.58 | freemangordon | Pali: no? in coldfalshing mode n900 appears like some strange USB device |
| 18:09.59 | DocScrutinizer05 | I had an extensive look at TRM |
| 18:10.21 | Pali | and if you want to load image via usb, you send command via usb thay you want to boot from usb |
| 18:10.43 | Pali | I written that code in 0xFFFF, so I know it |
| 18:10.44 | DocScrutinizer05 | and at http://www.omappedia.org/wiki/Bootloader_Project |
| 18:11.03 | Pali | and know how cold flashing work |
| 18:11.12 | freemangordon | ok :) |
| 18:11.56 | DocScrutinizer05 | SYSBOOT Pins |
| 18:12.11 | freemangordon | I was under impression that coldflashing is doen with the help of bootrom, obviously wrongly :) |
| 18:12.19 | DocScrutinizer05 | The 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. |
| 18:12.25 | DocScrutinizer05 | so not even EFUSE |
| 18:12.31 | DocScrutinizer05 | actually hardwired |
| 18:12.51 | Pali | but before that is used usb! |
| 18:12.59 | DocScrutinizer05 | nothing you can 2tell it2 via USB |
| 18:13.09 | Pali | and if you send usb command it can overwrite that is in sysboot |
| 18:13.11 | DocScrutinizer05 | no |
| 18:13.15 | Pali | yes |
| 18:13.33 | freemangordon | Pali: wait, it could be hardwired to try USB first |
| 18:13.38 | Pali | did you programmed already that? |
| 18:13.41 | DocScrutinizer05 | [citation needed] |
| 18:13.50 | Pali | I yes |
| 18:14.16 | freemangordon | or there is a backdoor which is not in publick TRM |
| 18:14.16 | Pali | it was written in version of trm which I read when I worked on 0xFFFF |
| 18:14.19 | DocScrutinizer05 | I never heard of such command, nowhere |
| 18:14.34 | Pali | download 0xFFFF sources |
| 18:14.38 | freemangordon | Pali: which TRM is that? |
| 18:14.42 | Pali | go to src/cold-flash.c |
| 18:14.52 | DocScrutinizer05 | and I read the TRM as well as pages like http://www.omappedia.org/wiki/Bootloader_Project |
| 18:14.54 | Pali | there should be written version of TRM |
| 18:15.01 | Pali | and also all commands for usb!!! |
| 18:15.18 | DocScrutinizer05 | ROMBOOT doesn't take commands |
| 18:15.26 | Pali | as #define |
| 18:15.49 | DocScrutinizer05 | that's maybe xloader, or more likely even NOLO |
| 18:15.54 | Pali | try to find in trm something like peripheral booting |
| 18:16.03 | Pali | it is not xloader/nolo |
| 18:16.11 | DocScrutinizer05 | I *READ* peripheral booting in TRM |
| 18:16.18 | Pali | it is bootrom and how coldflash working |
| 18:16.44 | Pali | find something like "boot next" |
| 18:16.45 | DocScrutinizer05 | it has a weird device table |
| 18:17.12 | Pali | there is "boot next" command which skip entry from device table |
| 18:17.39 | DocScrutinizer05 | so what for? our first entry is uSD anyway |
| 18:18.04 | Pali | find big diagram in trm |
| 18:18.09 | DocScrutinizer05 | see our particular wiring of SYSBOOT pins |
| 18:18.21 | Pali | there was also written how sysboot pin cn be skipped |
| 18:18.30 | DocScrutinizer05 | WHAT FOR??? |
| 18:18.39 | Pali | and start booting from device specified by usb command |
| 18:19.14 | DocScrutinizer05 | even if such thing exists, it's vastly useless |
| 18:19.37 | DocScrutinizer05 | since we already have boot sequence USB,MMC1,NAND |
| 18:19.59 | DocScrutinizer05 | but that's for xloader only |
| 18:20.19 | DocScrutinizer05 | and it's hardwired |
| 18:21.34 | DocScrutinizer05 | oops |
| 18:21.37 | DocScrutinizer05 | sys_boot[5:0]: 0x10 |
| 18:21.39 | DocScrutinizer05 | Boot order: OneNAND USB UART3 MMC1 -- |
| 18:21.43 | Pali | <PROTECTED> |
| 18:21.51 | DocScrutinizer05 | IroN900:~# omap34xx-boot-order |
| 18:21.53 | DocScrutinizer05 | sys_boot[5:0]: 0x10 |
| 18:21.54 | DocScrutinizer05 | Boot order: OneNAND USB UART3 MMC1 -- |
| 18:23.56 | Pali | <PROTECTED> |
| 18:24.11 | Pali | here are two usb commands for omap bootrom |
| 18:24.21 | Pali | usb commands exists!!!! |
| 18:25.53 | Pali | Omap Boot Messages: spruf98v.pdf (page 3444): OMAP35x Technical Reference Manual - 25.4.5 Periheral Booting |
| 18:26.08 | Pali | this is in 0xFFFF comments |
| 18:27.10 | DocScrutinizer05 | gosub @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 " |
| 18:27.45 | DocScrutinizer05 | Pali: I stand corrected |
| 18:28.09 | DocScrutinizer05 | spruf98v? W*T*F?? |
| 18:28.20 | DocScrutinizer05 | I know rev F maybe, not V |
| 18:28.42 | Pali | this is what I found and used when worked on 0xFFFF |
| 18:29.27 | Pali | and USB in bootorder is probably usb flash disk connected in usb host mode |
| 18:29.47 | Pali | not usb in peripheral mode... |
| 18:29.52 | Pali | but do not remember |
| 18:30.27 | FatPhil | [in pub] hmmm, cant' connect to any of the default repos (e.g. nokia and extras) |
| 18:30.49 | FatPhil | however, I'm doin the CSSU installation without them |
| 18:30.53 | Pali | change time back to year 2010 |
| 18:31.01 | DocScrutinizer05 | Pali: do you know which version of ROMBL this refers to? and which version N900 has? |
| 18:31.03 | Pali | otherwise nokia repo will not work |
| 18:31.18 | FatPhil | some SSL negotiation issue |
| 18:31.25 | Pali | DocScrutinizer05: do not know version |
| 18:31.43 | Pali | and I cannot opat that big pdf on n900... |
| 18:32.03 | FatPhil | Pali: can you add that to the wiki if it's not there |
| 18:32.11 | Pali | FatPhil: maybe you need to activate internet via web browser? |
| 18:33.10 | Pali | FatPhil: I'm on n900 and copy/paste lot of parts of text is hard here... |
| 18:33.15 | DocScrutinizer05 | Pali: I still think I haven't noticed those commands in SPRUF98D |
| 18:33.36 | DocScrutinizer05 | they *might* be a feature of later ROMBL versions |
| 18:33.50 | Pali | DocScrutinizer05: I tested that peripheral command and it worked and also next command worked |
| 18:33.53 | DocScrutinizer05 | or I ignored them since I thought they're useless |
| 18:34.03 | DocScrutinizer05 | ooooh :-D |
| 18:34.19 | Pali | peripheral command is used for cold flashing |
| 18:34.31 | Pali | and next to skip cold flashing |
| 18:35.01 | Pali | https://gitorious.org/0xffff/0xffff/source/master:src/cold-flash.c |
| 18:35.04 | DocScrutinizer05 | hah. awesome |
| 18:35.21 | Pali | look at cold flash source code |
| 18:35.40 | Pali | and you can see what is handled by omap bootrom and what by xloader |
| 18:36.52 | DocScrutinizer05 | /note to self: don't mess with Pali ;-) |
| 18:36.58 | FatPhil | Pali: internet's flakey, but I managed to browse to the wiki, install the repo installer, and download 50MB of CSSU, which is happily installing currently |
| 18:39.28 | Pali | do you know if it is possible to detect from asis id (sent by omap bootrom) if device is n900 or not? |
| 18:39.56 | DocScrutinizer05 | Pali: is result of omap34xx-boot-order binary correct? |
| 18:40.20 | DocScrutinizer05 | or is that somehow covered/obfuscated when system got booted up? |
| 18:40.25 | Pali | on GP device should be |
| 18:40.49 | Pali | but I think it could be correct also on HS |
| 18:41.11 | Pali | I think that obfucation does not make sense |
| 18:41.22 | Pali | still it allow booting only signed image... |
| 18:44.04 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-91-21.residential.rdsnet.ro) |
| 18:47.02 | DocScrutinizer05 | ah, maybe some memory re-mapping kicks in after some crap in HS been set |
| 18:47.09 | DocScrutinizer05 | who knows, I don't |
| 18:47.34 | DocScrutinizer05 | Boot order: OneNAND USB UART3 MMC1 -- makes no sense to me |
| 18:47.48 | *** join/#maemo-ssu Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr) |
| 18:48.17 | DocScrutinizer05 | lemme check the damn schematics |
| 18:49.11 | Pali | why? |
| 18:49.14 | Pali | its ok |
| 18:49.22 | Pali | it booting from onenand |
| 18:49.29 | DocScrutinizer05 | sys_boot4:1 6:1 5:BOOTMODE |
| 18:50.17 | Pali | usb peripheral boot for cold flash is started by special usb command before that boot order |
| 18:50.37 | DocScrutinizer05 | hmm, makes sense then |
| 18:51.25 | Pali | and usb in that boot order is probably booting from usb flash disk in host mode |
| 18:51.42 | DocScrutinizer05 | LOL, 5:BOOTMODE is determined by CHRG_IND |
| 18:51.54 | Pali | which cannot work on n900 where is no usb host mode port |
| 18:52.11 | DocScrutinizer05 | :nod: |
| 18:54.12 | kolp | Will anything break if I switch on host mode while wall-charging, without having anything else connected to the usb port? |
| 18:54.28 | DocScrutinizer05 | IOW 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 CPU |
| 18:55.03 | FatPhil | DocScrutinizer05: you understand correctly |
| 18:55.41 | FatPhil | yellow = NOLO charging, and it won't exit that till it's happy |
| 18:57.20 | Pali | where you found that? "DocScrutinizer05: LOL, 5:BOOTMODE is determined by CHRG_IND" |
| 18:58.43 | DocScrutinizer05 | schem p. 4 & 6 & |
| 18:59.31 | DocScrutinizer05 | SoC sys_boot:5 -> (BOOT_MODE) -> N1302 |
| 19:00.14 | DocScrutinizer05 | -> (CHRG_IND) -> N1140 bq24150 |
| 19:00.55 | DocScrutinizer05 | CHRG_IND also directly drives red and green (=yellow) indicator LED |
| 19:01.28 | DocScrutinizer05 | as long as BQ24150 is in emergency charge mode, CPU can't boot "normally" |
| 19:02.46 | Pali | and when bq2415x is in emergency mode? |
| 19:02.58 | Pali | when timer is not resetted in 30s? |
| 19:05.24 | DocScrutinizer05 | yes, and when battery voltage below 3.7V or sth |
| 19:05.45 | DocScrutinizer05 | and for max 30min |
| 19:07.54 | DocScrutinizer05 | FatPhil: I wouldn't call that NOLO charging, since it's an autonomous mode of BQ24150 charger chip, CPU not involved |
| 19:08.28 | DocScrutinizer05 | maybe "NOLO tolerated autonomous hw charging" |
| 19:08.58 | FatPhil | there's a bq24150 driver in it, I presume nolo sets it up, and lets it run |
| 19:09.43 | FatPhil | has anyone decompiled nolo? |
| 19:11.09 | Pali | jacekowski only some small parts |
| 19:12.05 | Pali | its funny that nolo cannot change battery when you want to enter flash mode... |
| 19:12.15 | Pali | but has charging driver... |
| 19:12.35 | Pali | so driver is either useless or not used |
| 19:12.45 | Pali | or not working |
| 19:13.03 | Pali | or need to send some special command to start it? |
| 19:18.20 | DocScrutinizer05 | ~bootloop |
| 19:18.21 | infobot | i 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. |
| 19:18.51 | DocScrutinizer05 | ~flatbatrecover |
| 19:18.51 | infobot | Remove 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)!. |
| 19:20.52 | kolp | DocScrutinizer05: in Neo900, would it be possible to export the root fs via USB when powered down? |
| 19:21.01 | kolp | Hm, prolly not because of nand or whatever |
| 19:21.21 | DocScrutinizer05 | that's a fptf question and issue |
| 19:21.35 | kolp | A software thing only? |
| 19:21.36 | DocScrutinizer05 | no hw can export anything when "powered down" |
| 19:21.44 | Pali | if you use uboot, then yes |
| 19:21.49 | kolp | Ah, well, wrong terminology then |
| 19:22.03 | Pali | uboot can support "reverse flash" |
| 19:22.42 | Pali | but uboot does not have working support for n900 onenand yet... |
| 19:22.58 | DocScrutinizer05 | Pali: are you sure N900 NOLO has anything to do with bq24150? |
| 19:23.17 | kolp | Would be useful for fixing bootloops if you could access the root fs without booting to UI |
| 19:23.22 | kolp | And a security issue... |
| 19:23.24 | Pali | I know that n900 NOLO cannot fix dead battery |
| 19:23.43 | Pali | and cause bootloops instead charging enough for flashing |
| 19:24.17 | Pali | DocScrutinizer05: this is why i wrote that nolo bq support is useless... |
| 19:24.41 | FatPhil | Pali, I may be thinking of nolo-h, not nolo-r |
| 19:25.09 | DocScrutinizer05 | Pali: I doubt there *is* *any* bq24150 support in N900 NOLO |
| 19:26.25 | DocScrutinizer05 | kolp: rescueOS can be booted from USB to RAM, and access maemo rootfs |
| 19:26.59 | DocScrutinizer05 | allegedly rescueOS even can charge a battery |
| 19:27.29 | DocScrutinizer05 | and also allegedly it can get ram-loaded even when nolo refuses to enter normal flashing mode |
| 19:27.41 | DocScrutinizer05 | I don't see that |
| 19:28.37 | DocScrutinizer05 | FatPhil: bq24150 doesn't need setup for emergency charging |
| 19:29.01 | DocScrutinizer05 | that's the whole point of that mode |
| 19:29.32 | DocScrutinizer05 | as soon as anything talks to bq24150 via i2c, emergency charging is stopped |
| 19:30.03 | DocScrutinizer05 | and will resume only on chip reset, due to reset command or i2c watchdog (32s) timeout |
| 19:30.07 | FatPhil | ~bootloop |
| 19:30.08 | infobot | bootloop 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. |
| 19:30.16 | DocScrutinizer05 | ~factinfo bootloop |
| 19:30.16 | infobot | DocScrutinizer05: there's no such factoid as bootloop |
| 19:30.38 | DocScrutinizer05 | sucker??! |
| 19:30.47 | DocScrutinizer05 | ~bootloop |
| 19:30.47 | infobot | i 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. |
| 19:30.55 | DocScrutinizer05 | ~literal bootloop |
| 19:30.55 | 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." |
| 19:31.04 | DocScrutinizer05 | ~factinfo #maemo bootloop |
| 19:31.04 | 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. |
| 19:32.47 | DocScrutinizer05 | FatPhil: 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 flash |
| 19:33.24 | DocScrutinizer05 | since NOLO threshold to allow flashing > bq24150 threshold to stop emergency charging |
| 19:34.21 | DocScrutinizer05 | iirc! |
| 19:34.51 | Pali | nolo is not signed... so maybe we can try to find hex number of that value and change it? |
| 19:35.14 | DocScrutinizer05 | yes, I suggested that several times |
| 19:35.28 | Pali | but there is another problem which I tested: |
| 19:36.04 | Pali | nolo loaded by cold flashing (it always enter to flash mode!!) has unstable usb when battery is too empty |
| 19:36.19 | Pali | which caused that I was not able to flash |
| 19:36.20 | DocScrutinizer05 | quite possible |
| 19:36.38 | Pali | because usb transfer was not possible |
| 19:36.44 | DocScrutinizer05 | :nod: |
| 19:36.55 | Pali | so hexchaning it will not help |
| 19:37.30 | Pali | we need either proper charning in nolo or increase bq treshold |
| 19:37.35 | DocScrutinizer05 | NOLO should learn my dirt-simple bq24150-charging |
| 19:37.51 | *** join/#maemo-ssu xes (~xes@unaffiliated/xes) |
| 19:38.10 | DocScrutinizer05 | 5 i2c commands to configure, one timer plus one i2c infinite loop to tickle WD |
| 19:38.33 | Pali | but omap bootrom was still able to transfer 2nd and secondary image and boot it! |
| 19:38.40 | DocScrutinizer05 | bq24150 is sane and safe |
| 19:38.51 | DocScrutinizer05 | weird |
| 19:39.02 | Pali | so if we are able to write ASM code for charning we can send 2nd and that asm code instead nolo |
| 19:39.09 | DocScrutinizer05 | maybe because ROMBL doesn't initialize RAM and stuff |
| 19:39.10 | Pali | and 2nd image can boot it |
| 19:39.23 | Pali | because nolo is not signed |
| 19:39.38 | DocScrutinizer05 | :nod: |
| 19:39.42 | Pali | but somebody must write that pure ASM code for bq charging |
| 19:39.45 | DocScrutinizer05 | sounds feasible |
| 19:39.58 | DocScrutinizer05 | that isn't hard |
| 19:40.02 | Pali | plus in this state lot of hw parts are not initialized |
| 19:40.06 | DocScrutinizer05 | i2c is a hw interface |
| 19:40.15 | Pali | and need to stop twl watchdog |
| 19:40.23 | DocScrutinizer05 | :nod: |
| 19:40.35 | Pali | DocScrutinizer05: are you able to do it? |
| 19:40.40 | DocScrutinizer05 | and possible even BB5 WD |
| 19:40.58 | DocScrutinizer05 | I'm _able_ to do that, but no time atm |
| 19:41.16 | Pali | in uboot I turned off only twl |
| 19:41.23 | Pali | and no reset anymore |
| 19:41.25 | DocScrutinizer05 | ok |
| 19:41.40 | DocScrutinizer05 | then BB5 only gets upset after it got initialized |
| 19:41.59 | DocScrutinizer05 | sounds ane |
| 19:42.02 | DocScrutinizer05 | sane even |
| 19:42.16 | Pali | and thanks to bq24150 support in qemu we can debug code :-) |
| 19:42.27 | DocScrutinizer05 | there's a reset wire from cpu to bb5, and one line the opposite direction |
| 19:42.38 | Pali | check and dump bq registers from qemu |
| 19:43.12 | DocScrutinizer05 | you already have all that in my charge draft, which ShadowJK based his charge21.sh on |
| 19:43.25 | DocScrutinizer05 | it's dirt simple |
| 19:44.03 | DocScrutinizer05 | main obstacle is talking to I2C IP lowlevel |
| 19:44.07 | Pali | but my low level hw programming skills are not good... |
| 19:44.09 | DocScrutinizer05 | on register level |
| 19:44.21 | Pali | I never wrote any i2c driver in asm |
| 19:44.28 | DocScrutinizer05 | I guess you first need to initialize it |
| 19:44.43 | DocScrutinizer05 | speed and power |
| 19:44.57 | DocScrutinizer05 | then simply read buffer, or write buffer |
| 19:45.10 | DocScrutinizer05 | rest is hw |
| 19:45.32 | DocScrutinizer05 | I never looked into ABI/API of I2C IP |
| 19:46.05 | DocScrutinizer05 | but I'm EE for knowing how it must look like |
| 19:46.16 | DocScrutinizer05 | some 2..5 registers |
| 19:46.22 | Pali | anybody who is able to do that and has time? |
| 19:46.52 | DocScrutinizer05 | btw you wouldn't need asm, use C and get the asm intermediate |
| 19:47.11 | DocScrutinizer05 | or use C straight away |
| 19:47.22 | DocScrutinizer05 | C obj code |
| 19:47.52 | DocScrutinizer05 | C is (and always been) a glorified macro assembler |
| 19:48.04 | Pali | you also need linker scripts/hacks to generate noloscnd header plus start code at specific address |
| 19:48.33 | DocScrutinizer05 | no clue about that |
| 19:48.39 | Pali | or code must be position independent |
| 19:48.45 | DocScrutinizer05 | it is |
| 19:49.15 | Pali | in asm you can add .ascii "noloscnd" |
| 19:49.17 | DocScrutinizer05 | some 50 ARM opcodes |
| 19:49.31 | DocScrutinizer05 | you can use ASM in C |
| 19:49.39 | DocScrutinizer05 | inline |
| 19:50.12 | DocScrutinizer05 | don't ask me how, last I did this been 1990 |
| 19:50.58 | DocScrutinizer05 | last I seen this must be 2 years ago |
| 19:52.17 | DocScrutinizer05 | you frequently see this stuff in highly optimized low level hw drivers |
| 19:53.17 | DocScrutinizer05 | but nowadays you almost don't need it anymore, with all that new smart stuff that C allows, like defining absolute addr or register for variables |
| 19:54.35 | DocScrutinizer05 | Pali: check SPRUF98 for I2C hw block (IP), if any questions how to handle it, ask me |
| 19:55.31 | DocScrutinizer05 | I can tell you what to do with it once you found out (with a little help from my side) _how_ to talk to I2C |
| 19:55.42 | Pali | DocScrutinizer05: I cannot look now (opening that pdf on n900 is impossible) and also Impossible) I do not have time for writing that code... |
| 19:58.30 | DocScrutinizer05 | the "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 value |
| 19:59.13 | DocScrutinizer05 | or was it chipaddr<<1&(read?0:1), then register addr |
| 20:00.23 | Pali | and for charging you need to enable some gpio |
| 20:00.40 | DocScrutinizer05 | anyway a register write are three atomic elementary writes to the i2c hw interface, a register read are two writes and one read |
| 20:00.47 | Pali | tx reset or something... |
| 20:01.05 | DocScrutinizer05 | huh? |
| 20:01.25 | Pali | some gpio, freemangordon already wrote it here... |
| 20:01.31 | Pali | look into log |
| 20:01.38 | Pali | some #define |
| 20:02.05 | DocScrutinizer05 | sorry, I didn't get it when fmg asked you about that |
| 20:02.12 | DocScrutinizer05 | and I don't get it now |
| 20:02.38 | DocScrutinizer05 | there is no GPIO I know of that needs to get set for charging |
| 20:03.15 | DocScrutinizer05 | there is some nasty foo for detecting charger |
| 20:04.17 | DocScrutinizer05 | charging is only bq24150, and that is only attached to CPU via I2C |
| 20:04.40 | DocScrutinizer05 | and it needs only I2C commands to this chip to keep it charging |
| 20:05.27 | DocScrutinizer05 | ~5 for setting up max voltage, max USB current, trickle charge, etc, and one recurring register access for tickling WD, every 15s |
| 20:05.37 | DocScrutinizer05 | that's all it needs |
| 20:05.46 | DocScrutinizer05 | ~50 ARM opcodes |
| 20:06.13 | DocScrutinizer05 | incl setup of the I2C hw interface in SoC |
| 20:06.46 | DocScrutinizer05 | more if you want to do this in a multitasking way, allowing other tasks while tickling WD |
| 20:45.39 | FatPhil | Does the bot have a way of remembering messages for people who've left the channel... |
| 20:45.48 | FatPhil | he says glaring at Pali... |
| 20:46.18 | FatPhil | oi, silly bot, tell Pali about this: http://www.spinics.net/lists/linux-omap/msg11786.html |
| 20:55.40 | FatPhil | ANyone know what http://elinux.org/N900 and https://gitorious.org/linux-n900/linux-n900 are ? |
| 21:09.24 | FatPhil | Ah, that looks like Pali's tree, and freemangordon's is a fork from it |
| 21:33.25 | *** join/#maemo-ssu nox- (noident@freebsd/developer/nox) |
| 21:44.58 | *** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 22:49.06 | *** join/#maemo-ssu amiconn (amiconn@rockbox/developer/amiconn) |
| 23:30.56 | *** join/#maemo-ssu LaoLang_cool (~LaoLang_c@218.107.16.197) |