IRC log for #maemo on 20160326

00:00.12*** join/#maemo HRH_H_Crab (~crab@kowloontong.dim-sum.org)
00:04.36*** join/#maemo HRH_H_Crab (~crab@kowloontong.dim-sum.org)
00:24.43fishbulbI'd like to report a bug on that flashitall script
00:24.48fishbulbin that it doesn't work
00:27.04fishbulball calls, all texts, all contacts, all calendar appointments, and I don't know what else yet, are all still there
00:28.12DocScrutinizer05you need to enter 'YES'
00:28.20fishbulbI did
00:28.33DocScrutinizer05obviously not
00:28.49DocScrutinizer05the script is tested
00:28.58DocScrutinizer05afaik
00:29.11DocScrutinizer05well, I tested it before I published it
00:29.14fishbulbI'll try it again
00:29.20fishbulbhas anyone else tested it?
00:29.40DocScrutinizer05I'm pretty sure several people used it already
00:30.17fishbulbI'll do it again
00:33.00*** join/#maemo alien2003 (~alien@230.97.121.77.pool.smart.vn.ua)
00:33.27DocScrutinizer05see http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir_flash-it-all.sh.LOG
00:34.18alien2003Hi. Can you help me with U-Boot pls? After I select the kernel it says "Unsupported filesystem"... I tried to fsck and to switch between FAT32 and ext3 filesystem... On FAT it even doesn't show my kernels
00:40.49DocScrutinizer05fishbulb: you also can use flash-it-all.sh to flash your backupmenu image. however you need move the image to the my-private-workdir and do a   'md5sum flashable_rootfs_v0.56-1-20101109.img >>md5sums.txt'   first
00:41.29DocScrutinizer05after that call 'sudo ./flash-it-all.sh flashable_rootfs_v0.56-1-20101109.img'
00:45.51fishbulbInvalid FIASCO file header
00:45.51fishbulbsorry, flashing flashable_rootfs_v0.56-1-20101109.img (NOLO, rootfs, modem-fw) failed with errorcode 0
00:46.17DocScrutinizer05then the file is not correct
00:46.40fishbulbI got it off the backupmenu post
00:46.56DocScrutinizer05I never used that flashable_rootfs_v0.56-1-20101109.img
00:47.06fishbulbwell it's fucked
00:47.31DocScrutinizer05seems so. Did you check that you downloaded it without errors?`
00:47.51fishbulbyes
00:48.56DocScrutinizer05alien2003: wait for Pali
00:51.55DocScrutinizer05I noticed a tiny error in flasher file, it shouldn't say "failed with errorcode 0"
00:52.11DocScrutinizer05irrelevant for that issue here
00:52.30fishbulba tiny error?
00:52.35DocScrutinizer05yes
00:53.09DocScrutinizer05it should read "failed with errorcode 5" or whatever
00:53.18fishbulbok, it didn't
00:53.44DocScrutinizer05yes, I see. That's why I say "I noticed a tiny irrelevant error"
00:54.25*** join/#maemo krnlyng (~liar@77.116.25.35.wireless.dyn.drei.com)
00:55.54fishbulbyeah, the process still didn't work
00:56.27fishbulbI flashed it a second time and it did erase the stuff though
00:56.34DocScrutinizer05sure
00:56.41fishbulbthe first time it said it was doing that and it didn't
00:56.50DocScrutinizer05o.O
00:57.22fishbulbwhere are the repos?
00:57.30DocScrutinizer05~repos
00:57.30infoboti guess repos is "deb http://maemo.muarf.org/apt-mirror/mirror/downloads.maemo.nokia.com/fremantle/ssu/apps/ ./ ;; deb http://maemo.muarf.org/apt-mirror/mirror/downloads.maemo.nokia.com/fremantle/ssu/mr0/ ./", or see http://wiki.maemo.org/Repository#List_of_Maemo_repositories
00:58.33DocScrutinizer05~jrrepos
00:58.34infobotjrrepos is, like, http://maemo.cloud-7.de/maemo5/et_al/HAM-catalogs/
00:58.50DocScrutinizer05one-click-install
01:00.13fishbulbI put that in the browser?
01:07.37DocScrutinizer05yes
01:07.47DocScrutinizer05on N900
01:08.22DocScrutinizer05actually http://maemo.cloud-7.de/maemo5/et_al/HAM-catalogs/recommended.install
01:08.50fishbulbif I install all the repos will it spaz out
01:09.34DocScrutinizer05yes
01:09.53DocScrutinizer05you only need http://maemo.cloud-7.de/maemo5/et_al/HAM-catalogs/recommended.install
01:10.28fishbulbdon't you need devel for backup menu, cssu and power kernel
01:10.46DocScrutinizer05that's unrelated
01:11.09DocScrutinizer05well, use http://maemo.cloud-7.de/maemo5/et_al/HAM-catalogs/muarf_devel_tools.install
01:12.26DocScrutinizer05INSTEAD OF recommended
01:12.50fishbulbok well luckily you said that last
01:13.35DocScrutinizer05worst case you need to delete catalogs in ham which are duplicate
01:14.00fishbulbI don't know which ones are
01:14.25DocScrutinizer05you'll see by their names
01:15.43fishbulbthere doesn't seem to be extras or extras-devel
01:16.05DocScrutinizer05extras is on by default
01:16.21DocScrutinizer05extras-devel is in http://maemo.cloud-7.de/maemo5/et_al/HAM-catalogs/muarf_devel_tools.install
01:17.25DocScrutinizer05[extras-devel]
01:17.26DocScrutinizer05name = Maemo Extras-DEVEL catalogue (read WARNING!)
01:17.28DocScrutinizer05uri = http://repository.maemo.org/extras-devel
01:17.29DocScrutinizer05dist = fremantle
01:17.31DocScrutinizer05components = free non-free
01:17.48fishbulbthat still works?
01:17.56DocScrutinizer05sure, why not?
01:22.41fishbulbthe linenoise ones are 404
01:24.38fishbulbok I can't seem to find cssu or anything else
01:24.47fishbulbmaybe those repos are no good
01:25.05fishbulbthey might have a tiny error making them unusable
01:27.06fishbulbI have to try later, cheers
01:33.27*** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian)
01:47.52*** join/#maemo louis__ (~louisdk@static-5-103-130-65.seas-nve.net)
02:34.36*** join/#maemo eMHa__ (~mh@p579DB536.dip0.t-ipconnect.de)
02:41.07*** join/#maemo vakkov (~vakkov@s3n104.brunel.ac.uk)
03:33.11*** join/#maemo peetah (~peetah@cha92-9-82-236-202-86.fbx.proxad.net)
04:01.46*** join/#maemo lxp1 (~lxp@unaffiliated/lxp)
04:20.34*** join/#maemo vahe (~funtoo@130.193.124.135)
04:21.08*** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg)
05:04.21*** join/#maemo vahe (~funtoo@130.193.124.135)
06:53.28*** join/#maemo LauRoman (~LauRoman@5-14-7-240.residential.rdsnet.ro)
07:01.58*** join/#maemo futpib (~futpib@176.214.25.234)
07:21.04*** join/#maemo juiceme (~juice@cerebro.liukuma.net)
07:59.42*** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au)
08:37.29*** join/#maemo juiceme (~juice@cerebro.liukuma.net)
08:48.25*** join/#maemo sig (~sig@kekkonen.niksula.hut.fi)
08:48.41*** join/#maemo mickname (~mickname@low6.kyla.fi)
08:48.48*** join/#maemo xorly (~xorly@ip-86-49-15-121.net.upcbroadband.cz)
08:55.31*** join/#maemo juiceme_ (~juice@cerebro.liukuma.net)
08:56.07*** join/#maemo sig (~sig@130.233.41.50)
09:01.25*** join/#maemo sig (~sig@130.233.41.50)
09:02.13*** join/#maemo mickname (~mickname@low6.kyla.fi)
09:07.16*** join/#maemo sig (~sig@130.233.41.50)
09:07.19*** join/#maemo ceene (~ceene@collins.gmr.ssr.upm.es)
09:11.49*** join/#maemo ceene (~ceene@collins.gmr.ssr.upm.es)
09:12.16*** join/#maemo sig (~sig@130.233.41.50)
09:14.23*** join/#maemo mickname (~mickname@low6.kyla.fi)
09:18.54*** join/#maemo juiceme (~juice@cerebro.liukuma.net)
09:18.54*** join/#maemo ceene (~ceene@collins.gmr.ssr.upm.es)
09:22.44*** join/#maemo sig (~sig@kekkonen.niksula.hut.fi)
09:24.16*** join/#maemo juiceme_ (~juice@185.34.0.166)
09:38.59jonwilhi
09:39.33freemangordonjonwil: hi! how's lego train going?
09:39.41jonwilMy LEGO stuff is going great
09:39.59freemangordon:)
09:41.20jonwilNext thing I need to build is a couple more sideshow games then I need to add people to my golf course and sideshow games
09:42.58jonwilI have quite a few vehicles already
09:44.23jonwilI have a police car, a taxi, a van for my SWAT team, a petrol tanker, a Ute, 4 different buses and 3 lamborghinis
09:44.56jonwilI still need to build a prisoner transport and a police helicopter
09:45.16jonwilplus a bunch of 2-wheel vehicles for my police (motorbikes and bicycles)
09:47.26jonwilmy petrol station looks great, I even built a custom signboard for it (with actual petrol prices taken from a local petrol station on the day I was making the sign)
09:47.36*** join/#maemo mickname (~mickname@low6.kyla.fi)
09:47.36*** join/#maemo sig (~sig@kekkonen.niksula.hut.fi)
09:47.36*** join/#maemo ceene (~ceene@collins.gmr.ssr.upm.es)
09:47.41*** join/#maemo juiceme_ (~juice@cerebro.liukuma.net)
09:47.50jonwilIn other news, it was my birthday on Thursday :)
09:48.04jonwilGoing out to a nice steakhouse for dinner to celebrate tomorrow :)
09:52.56*** join/#maemo juiceme (~juice@cerebro.liukuma.net)
09:54.16*** join/#maemo sig (~sig@130.233.41.50)
09:54.59*** join/#maemo ceene (~ceene@collins.gmr.ssr.upm.es)
09:55.38*** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
09:57.22*** join/#maemo Pali (~pali@Maemo/community/contributor/Pali)
10:01.24freemangordonPali: summan anna said they will send some patches related to IVA2, I am waiting to see what will be send and will decide what to do next after that
10:01.43Paliok
10:02.06freemangordonPali: in the meanwhile did you see that gadget oops I sent on the ML?
10:02.23Palinow looking at it
10:02.31freemangordonok
10:03.02*** join/#maemo juiceme_ (~juice@185.34.0.166)
10:03.02*** join/#maemo mickname (~mickname@82.130.32.110)
10:03.02*** join/#maemo sig (~sig@130.233.41.50)
10:05.08PaliI see just your twl patches
10:05.11Palinot gadget oops
10:05.31*** join/#maemo fuz_ (nobody@vau75-10-88-164-23-88.fbx.proxad.net)
10:09.51*** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
10:11.38*** join/#maemo juiceme_ (~juice@cerebro.liukuma.net)
10:11.38*** join/#maemo ceene (~ceene@138.4.36.7)
10:11.38*** join/#maemo sig (~sig@130.233.41.50)
10:12.23*** join/#maemo mickname (~mickname@low6.kyla.fi)
10:17.15freemangordonPali: "Re: USB gadgets with configfs hang reboot"
10:18.30PaliI'm not using configfs
10:19.03freemangordonPali: the same bug prevents reboot on n900
10:19.10freemangordonreboot and poweroff
10:19.29Palihm...
10:19.37Palionenand corruption
10:20.03freemangordonPali: if g_nokia is not used, the device reboots just fine, with it it hangs
10:20.43*** join/#maemo mickname (~mickname@low6.kyla.fi)
10:20.47*** join/#maemo juiceme_ (~juice@cerebro.liukuma.net)
10:20.58freemangordonPali: do you have "ARM: OMAP2+: Fix onenand initialization to avoid filesystem corruption" ?
10:21.14PaliI think yes
10:21.20Paliin linux-n900 tree
10:21.40Paliyes, there is
10:22.19freemangordonwell, your onenand seem to be corrupted before that patch
10:26.37*** join/#maemo pagurus (~user@pD950CCCC.dip0.t-ipconnect.de)
10:31.44*** join/#maemo ceene (~ceene@138.4.36.7)
10:31.45*** join/#maemo sig (~sig@130.233.41.50)
10:31.45*** join/#maemo mickname (~mickname@low6.kyla.fi)
10:34.25freemangordonPali: no much options but a reflash :(
10:37.15*** join/#maemo mickname (~mickname@low6.kyla.fi)
10:37.15*** join/#maemo sig (~sig@130.233.41.50)
10:37.15*** join/#maemo ceene (~ceene@138.4.36.7)
10:37.15*** join/#maemo juiceme_ (~juice@cerebro.liukuma.net)
10:38.57*** join/#maemo sig (~sig@kekkonen.niksula.hut.fi)
10:43.54*** join/#maemo sig (~sig@kekkonen.niksula.hut.fi)
10:48.39*** join/#maemo ceene (~ceene@collins.gmr.ssr.upm.es)
10:48.54*** join/#maemo sig (~sig@kekkonen.niksula.hut.fi)
10:54.01*** join/#maemo sig (~sig@kekkonen.niksula.hut.fi)
10:58.07*** join/#maemo mickname (~mickname@low6.kyla.fi)
11:05.31*** join/#maemo ceene (~ceene@collins.gmr.ssr.upm.es)
11:14.54*** join/#maemo juiceme (~juice@cerebro.liukuma.net)
11:14.55*** join/#maemo mickname (~mickname@82.130.32.110)
11:15.04*** join/#maemo ceene (~ceene@collins.gmr.ssr.upm.es)
11:19.19*** join/#maemo ceene (~ceene@collins.gmr.ssr.upm.es)
11:20.24*** join/#maemo sig (~sig@kekkonen.niksula.hut.fi)
11:22.14*** join/#maemo mickname (~mickname@82.130.32.110)
11:24.31*** join/#maemo ceene (~ceene@collins.gmr.ssr.upm.es)
11:25.55*** join/#maemo vahe (~funtoo@130.193.124.135)
11:26.11*** join/#maemo juiceme_ (~juice@cerebro.liukuma.net)
11:29.48*** join/#maemo louis__ (~louisdk@static-5-103-130-65.seas-nve.net)
12:22.23*** join/#maemo louis__ (~louisdk@static-5-103-130-65.seas-nve.net)
12:27.56*** join/#maemo krnlyng (~liar@77.116.25.35.wireless.dyn.drei.com)
12:56.05*** join/#maemo vectis3 (~user@79-64-232-175.host.pobb.as13285.net)
12:57.08*** join/#maemo M4rtinK (~M4rtinK@77.48.149.46)
13:09.57*** join/#maemo Kabouik (~quassel@65.76.93.92.rev.sfr.net)
13:15.27*** join/#maemo futpib_ (~futpib@86.57.255.91)
13:16.07*** join/#maemo mickname (~mickname@low6.kyla.fi)
13:22.00*** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil)
13:23.53*** join/#maemo futpib_ (~futpib@176.214.25.234)
14:39.56*** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
14:40.10*** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
14:41.55*** join/#maemo zGrr (~GrR@user-109-243-36-204.play-internet.pl)
14:57.56*** join/#maemo Elleo (~Elleo@mikeasoft.com)
14:57.56*** join/#maemo Elleo (~Elleo@libre.fm/hacker/elleo)
15:00.07*** join/#maemo mickname (~mickname@low6.kyla.fi)
15:28.10*** join/#maemo zGrr (~GrR@178235245220.warszawa.vectranet.pl)
15:42.08*** join/#maemo chfoo (~chris@UNVLON5554W-LP130-03-1242507786.dsl.bell.ca)
16:07.25*** join/#maemo vakkov (~vakkov@s3n104.brunel.ac.uk)
17:20.01DocScrutinizer05Pali: I dunno how many hours it took, but finally http://projects.goldelico.com/p/gta04-kernel/source/tree/master/ loaded and rendered
17:20.20Palipassword protected
17:20.47DocScrutinizer05yeah, you need to register first, lightweight process
17:21.46*** join/#maemo sunshavi (~user@190.235.18.236)
17:25.58DocScrutinizer05anyway I *really* wonder ehat the heck this server is doing, takes literally hours to generate and send content
17:26.30DocScrutinizer05projects.goldelico.com/p/gta04-kernel/source/tree/gta04-next-upstream-twl4030-madc/ is not a tad faster
17:27.02DocScrutinizer05neither is projects.goldelico.com/p/gta04-kernel/source/tree/master/GTA04
17:27.58DocScrutinizer05the wonders of webgit?
17:40.11DocScrutinizer05still loading - weird enough it gets no server timeout
17:41.42DocScrutinizer05Pali: you said there's a generic MADS interface in /sys/?
17:41.50DocScrutinizer05MADC actually
17:42.15*** join/#maemo vakkov (~vakkov@ic-s221n133.brunel.ac.uk)
17:42.34DocScrutinizer05or in /dev/ ?
17:43.25DocScrutinizer05if yes, you could check bupbat voltage in MADCIN9
17:44.22DocScrutinizer05if charging is actually enabled, it should be significantly >0 even when bupbat broken
17:54.58*** join/#maemo futpib (~futpib@37.113.245.193)
18:00.29*** join/#maemo futpib_ (~futpib@176.212.183.213)
18:06.23KotCzarnykeep in mind it might have been disabled for some reason
18:12.47PaliDocScrutinizer05: maemo kernel has /dev/madc* device and you can ask for value for any adcin channel
18:13.17Paliin upstream kernel is madc hwmon device (/sys/class/hwmon) but doing some conversion and does not return "raw" value
18:43.49*** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
18:43.55*** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
18:45.48DocScrutinizer05Pali: (ask for value) how?
18:46.31DocScrutinizer05IroN900:/dev# echo 9 >twl4030-adc
18:46.32DocScrutinizer05bash: echo: write error: Invalid argument
18:46.40DocScrutinizer05IroN900:/dev# cat twl4030-adc
18:46.41DocScrutinizer05cat: twl4030-adc: Invalid argument
18:48.54DocScrutinizer05some nasty ioctl?
18:51.29DocScrutinizer05WOW, bot URLs loaded
18:51.33DocScrutinizer05both*
18:53.02Paliyes, ioct
18:53.04Pali*ioctl
18:53.37PaliDocScrutinizer05: see: https://github.com/community-ssu/getbootstate/blob/master/bsi-read.c
18:53.51DocScrutinizer05ta
18:53.58Palithis will read channel 4 (line 54: "par.channel = 4;")
18:54.11Paliand also channel 12 (line 63)
18:54.41Palioutput is in "par.result"
18:56.24DocScrutinizer05yes, I see. I wish I had a working scratchbox env to make a simple knockoff that does "par.channel = argv[1]"
18:56.52DocScrutinizer05err
18:57.15DocScrutinizer05"par.channel = str2i(argv[1])"
19:00.57DocScrutinizer05strtol?
19:02.26*** join/#maemo ceene (~ceene@138.4.36.7)
19:04.02*** join/#maemo mickname (~mickname@82.130.32.110)
19:05.17DocScrutinizer05strtol(argv[1], 0, 0)
19:09.10DocScrutinizer05of course I could try binary patching the original executable, but... meh!
19:11.40PaliDocScrutinizer05: argc == 2 && (channel = strtol(argv[1], &endptr, 10), *endptr == 0) && channel >= 0 && channel <= 10
19:11.58DocScrutinizer05<=14?
19:12.06Paliyou need to check if argv is really number
19:12.11Palimaybe 14, do not know
19:12.19DocScrutinizer05don't bother, it simply will segfault ;-)
19:12.56Paliit will not segfault, strtol will return 0
19:13.05DocScrutinizer05even better, yes
19:13.31DocScrutinizer05it will segfault when argv[1] doesn't exist I guess
19:14.04Paliargv[1] should always exists :-) argv is terminated by NULL
19:14.20Paliand when argv[0] exists, then argv[1] must be NULL
19:14.30Palibut strtol does not check for NULL...
19:15.19DocScrutinizer05that's no problem, it returns 0 then
19:15.41DocScrutinizer05anyway this is completely fine behavior for my purpose
19:15.57DocScrutinizer05you get what you asked for
19:16.21DocScrutinizer05maemo-madc 555  --> segfault
19:16.26DocScrutinizer05100% ok
19:21.42DocScrutinizer05Pali: btw maybe argv[1] is a string at some address with argv[1][0] = NULL, but maybe argv[1] itself is NULL, I.E. the address pointer points to 0x0000
19:22.12DocScrutinizer05I'm not that much into c programming anymore
19:22.38kerioDocScrutinizer05: one of the two things is impossible
19:22.45DocScrutinizer05man strtol doesn't tell what happens when &nptr == 0
19:22.49kerioare we talking about argv as in the second argument to main()?
19:22.55DocScrutinizer05yes
19:23.05kerioargv[1][0] can't be equal to NULL
19:23.08keriowithout some pretty creative casting
19:23.15DocScrutinizer05why?
19:23.16Paliit can be 0
19:23.22DocScrutinizer05echo ""
19:23.22kerioit can be 0 yes
19:23.29Palitypeof argv[1][0] is char
19:23.32kerioif argv is a char**, argv[1][0] is char
19:23.32Palinot char*
19:23.37DocScrutinizer05sure, sorry
19:24.35DocScrutinizer05GOD c makes me dizzy
19:25.25keriook actually
19:25.47kerioi'm not at all sure that a comparison between a char and a void* should return a warning
19:25.57keriothe thing is, though
19:26.11DocScrutinizer05argv is a list of address pointers to strings, and that list is stored in memory, starting at the address value of argv. No?
19:26.24kerioif argv[1][0] is anything but 0, i don't think it makes sense to consider it in a pointer context
19:26.56keriobut NULL is quite literally just something that's a null pointer in pointer context
19:27.02DocScrutinizer05kerio: yes, a string is null-terminated
19:27.06kerio`#define NULL 0` is a thing
19:27.17DocScrutinizer05means it has 0x00 as termination char
19:27.29kerioeven though it typically is something like ((void *)0)
19:27.35DocScrutinizer05yes
19:28.19DocScrutinizer05s/list/array/
19:28.33kerioDocScrutinizer05: yes, argv is a pointer to a NULL-terminated array of pointers to C strings
19:28.36PaliNULL is (void *)0
19:28.47kerioPali: you're assuming that the c standard makes sense
19:28.49kerio:>
19:29.34DocScrutinizer05oooh, the array is open and NULL terminated? so if no argv[1] exists, accessing argv[1] reads form address 0x00000000 ---> segfault
19:29.56kerioDocScrutinizer05: argv[1] always exists
19:30.05DocScrutinizer05how so?
19:30.25keriounless you're in a freestanding environment, posix requires argv[0] to be the program name
19:30.33DocScrutinizer05yes
19:30.41keriowhich means that argv always has at least one string
19:30.47DocScrutinizer05yes
19:30.58kerioso argv[1] is always a constructible and dereferentiable pointer
19:31.04kerioer
19:31.07kerio&argv[1]
19:31.08DocScrutinizer05huh?
19:31.13kerioso argv[1] exists
19:31.26DocScrutinizer05yes, it points to 0x00000000
19:31.36kerioDocScrutinizer05: don't say stuff like that
19:31.44Palikerio: C11 says that: The macros are NULL which expands to an implementation-defined null pointer constant
19:31.46kerioyou can't know the bit-by-bit of a null pointer
19:31.48Palisection 7.19
19:31.59keriobut yes, it could be NULL
19:32.25kerioPali: yes, but 0 is a valid null pointer constant
19:32.26DocScrutinizer05reading from a NULL pointer is a segfault by definitionem, no?
19:32.31kerioreading from a null pointer, yes
19:32.38kerioi said that argv[1] exists
19:32.44Palipointer type is e.g. void*
19:32.46kerionot that *argv[1] exists
19:32.49kerioPali: lmao
19:32.50DocScrutinizer05so what?
19:32.54Luke-Jrcouldn't the virtual memory at address 0 be allocated?
19:32.59DocScrutinizer05the array is open and NULL terminated? so if no argv[1] exists, accessing argv[1] reads form address 0x00000000 ---> segfault
19:33.07Luke-JrIIRC it used to be allowed to mmap at NULL
19:33.11kerioLuke-Jr: compiler don't care, compiler don't give a fuck
19:33.22kerioor rather
19:33.25kerioC standard don't give a fuck
19:33.35DocScrutinizer05Luke-Jr: try cat /proc/kmem
19:33.41kerioif you have implementation-defined tricks to actually read from something with a physical or logical address of 0, that's your problem
19:33.47PaliDocScrutinizer05: yes, dereferncing argv[1] (if is NULL) cause segfault
19:33.56DocScrutinizer05what I say
19:33.56Luke-Jrkerio: doesn't the C spec allow the compiler to do literally anything in such circumstances?
19:34.07Palibut you can write: if (argv[1]) ... and this will not segfault
19:34.14kerioLuke-Jr: dereferencing a null pointer is undefined behaviour, yes
19:34.20DocScrutinizer05hmm, prolly
19:34.37keriobut like i tried to say to DocScrutinizer05, null pointer mustn't be all-bits-zero
19:34.44kerioall-bits-zero is a null pointer
19:34.58keriobut talking about the bits of pointers is kinda weird anyway
19:35.04DocScrutinizer05I don't care if it's all zeroes or your birthday or full of gremlins
19:35.04keriothey're not guaranteed to be inspectionable like that
19:36.20DocScrutinizer05I don't inspect them, I pondered what happens when you feed NULL pointer for &nptr to strtol()
19:37.12kerioIf endptr is not NULL, strtol() stores the address of the first invalid character in *endptr.
19:37.27DocScrutinizer05that's why I hate c. You can't write half a line of code without getting into arguments about what it really does
19:37.38keriowhy are you even passing argv[1] to strtol
19:37.54DocScrutinizer05HUHH?
19:38.09Luke-Jrit's not possible to feed into &nptr
19:38.12DocScrutinizer05what else would you pass to it?
19:38.20kerionot as the end pointer
19:38.21Luke-Jrnptr is in a register, it has no address
19:38.30DocScrutinizer05who says ENDpointer???
19:38.32keriohold on what's nptr
19:38.36keriooh, str
19:38.37Luke-Jrkerio: the first arg
19:38.44Palilooks like when nptr is NULL, then behaviour is undefined
19:38.52PaliC11 does not say anything about it
19:39.00kerioye if it's not specified then it's definetely UB
19:39.01Pali(section 7.22.1.4)
19:39.03DocScrutinizer05have fun discussing c, guys
19:39.07DocScrutinizer05I'm afk
19:39.14Luke-Jrif you specify NULL for nptr, you get baby kittens
19:39.19kerio:3
19:40.14Palifrom your CD-rom drive jump cat and eat your usb mouse :-)
19:40.51DocScrutinizer055 bucks on segfault
19:41.25Luke-JrDocScrutinizer05: segfault is not guaranteed
19:41.27DocScrutinizer05which is totally fine with me for this particular purpose
19:41.50Paliit is not defined what happen...
19:41.53DocScrutinizer05Luke-Jr: if it was, I had risked a 1000
19:43.00PaliDocScrutinizer05: do you know if backup battery is charning on n900?
19:43.19DocScrutinizer05no, that's why I would like to read out MADC9
19:43.22Paliyou send that screen where is written that in some condition charning is turned off...
19:43.44Palishould I provide some armel binary which will read madc9?
19:43.44DocScrutinizer05...and that kernel needs to turn it on, yes
19:43.54PaliI have arm cross compilers
19:43.55DocScrutinizer05yes, pretty please
19:44.17DocScrutinizer05that's how this mad discussion started ;-)
19:45.03DocScrutinizer05I'd even prefer a binary that allows argv[1] to tell the channel
19:45.18DocScrutinizer05without any fancy tests
19:46.24DocScrutinizer05and if you really wanna go fancy, allow argv[2] for numebr of average samples
19:51.13DocScrutinizer05if argv2 isn't present, should default to 1
19:51.41DocScrutinizer05if argv1 isn't present, I'm happy with any (non defined) behavior
19:52.15Paliprogram ready :-) going to check if on my n900
19:52.56DocScrutinizer05if you want to do excessive tests, spit out usage on argv1 missing and check argv1 for range 0<=argv<256
19:53.31DocScrutinizer05:-)
19:53.53kerioalso add --version and --help like GNU says
19:54.02DocScrutinizer05bwahaha
19:54.15keriodid you know that /bin/true from GNU coreutils can return nonzero?
19:54.16DocScrutinizer05and interactive mode ;-P
19:54.40DocScrutinizer05kerio: prolly when invoked with incorrect parameters?
19:54.49keriono, true is supposed to ignore parameters
19:55.02keriousing it as a throwaway command in makefiles and stuff like that is a common unix idiom
19:55.04DocScrutinizer05then how could it return non-true?
19:55.14keriobecause they actually parse the commands and react to --version
19:55.20kerioand --version needs to allocate some memory
19:55.22keriowhich can fail
19:55.29DocScrutinizer05hahahaha
19:55.33kerioor something like that
19:55.39DocScrutinizer05rotfl
19:55.54keriooh wait, even easier
19:55.59kerio--help and --version output things
19:56.05DocScrutinizer05ohmy
19:56.16keriowhich means that you'll get an error if stdout is closed or full
19:56.26kerio/bin/true --version >/dev/full
19:56.57DocScrutinizer05bash is sane ;-)   true --help ==> NO help
19:57.04kerioyeah that's the builtin
19:57.13kerio"This version of true is implemented as a C program, and is thus more secure and faster than a shell script implementation, and may safely be used as a dummy shell for the purpose of disabling accounts."
19:57.20kerioL
19:57.20kerioM
19:57.22kerioAYY
19:57.23kerioO
19:57.44Palihttps://atrey.karlin.mff.cuni.cz/~pali/files/madc.tar.gz
19:57.45DocScrutinizer05/bin/true --help|wc -l
19:57.46DocScrutinizer0518
19:57.48Palihave fun!
19:57.55DocScrutinizer05\o/
19:57.59DocScrutinizer05many rhanks!
19:58.32kerio"Note also the claim that there is no warranty, which in this case presumably means that if the program actually does something, you can't sue them."
19:58.38keriofrom http://trillian.mit.edu/~jc/humor/ATT_Copyright_true.html
19:58.41Palisource + armel binary (for linux kernel 2.6.8+)
20:00.48PaliDocScrutinizer05: please check if backup battery is charging and if not, try to write some patch or something to enable it...
20:01.03DocScrutinizer05sure thing :-)
20:01.41keriofreebsd doesn't even have a /bin/true
20:01.42DocScrutinizer05I prolly won't write a patch (my c foo is way too weak) but I'll check what such patch needs to do and when
20:01.52kerioapparently you don't need it to boot, so it's in /usr/bin instead
20:02.13DocScrutinizer05LOL
20:02.54keriohttps://svnweb.freebsd.org/base/head/usr.bin/true/true.c?view=markup
20:02.57keriobigass copyrights
20:03.01kerioand then just a return 0, like it should be
20:05.52DocScrutinizer05IroN900:/dev# madc 9
20:05.54DocScrutinizer05Channel 9: 709
20:06.51kerioDocScrutinizer05: hold on why didn't you use python for this
20:06.53DocScrutinizer05http://maemo.cloud-7.de/maemo5/usr/local/sbin/madc
20:07.16DocScrutinizer05because my python actually sucks more than my c
20:08.34ecc3g/usr/bin/true
20:08.42DocScrutinizer05any other volunteers for madc 9 ?
20:09.12ecc3gwhy is it in /usr/bin...
20:09.18keriowhy not
20:09.28PaliChannel 9: 706
20:09.42DocScrutinizer05so it seems it's charging
20:10.14DocScrutinizer05otherwise your value should differ significantly from mine
20:10.16ecc3ggranted one would hope nobody would be writing boot scripts that depend on true/false but they may well be.
20:10.31kerioecc3g: yeah but
20:10.33kerioif they're scripts
20:10.40keriothen true and false are going to be the builtins
20:10.54DocScrutinizer05unless braindamaged shell
20:11.02ecc3gthat's true for bash.  but the original bourne shell, no
20:11.06ecc3gor rather, false
20:12.17DocScrutinizer05well, bsd may have quite different definitions for what we at linux call FHS
20:12.23PaliDocScrutinizer05: is there way to check capacity of that backup battery?
20:12.49DocScrutinizer05errr, yes. check how long it takes after battery removal until RTC loses time
20:13.03keriowe should totally rebase fremantle onto freebsd
20:13.05DocScrutinizer05or probe voltage with a meter
20:13.07kerioso we can use zfs
20:13.23kerioand have negative ram at boot time
20:14.12DocScrutinizer05Pali: another way would be to completely deplete battery (several days without main battery, with good bupbat even several months) and then check how fast it charges
20:16.10DocScrutinizer05Pali: charging of bupbat also is CC/CV controlled and not instantly, so from speed of voltage rise at / after bootup from 'no main battery' you can tell the capacity
20:17.38DocScrutinizer05even when bupbat not completely empty, the delta-volt/time will be the higher the less total capacity the bupbat has
20:19.56DocScrutinizer05please see http://www.ti.com/lit/an/swca025/swca025.pdf - it's only a humbe 8 pages of very good info
20:24.35*** join/#maemo louis__ (~louisdk@static-5-103-130-65.seas-nve.net)
20:30.27DocScrutinizer05anyway for more specific investigation of the whole issue, we need to readout and possibly even set the BB_CFG resgister in TWL4030
20:34.33DocScrutinizer05http://wstaw.org/m/2016/03/26/plasma-desktopHq2219.png  http://www.ti.com/product/tps65950?qgpn=tps65950
20:34.54Palihttps://www.mail-archive.com/linux-omap@vger.kernel.org/msg45338.html
20:35.34Palihttp://lists.infradead.org/pipermail/linux-arm-kernel/2015-March/327115.html
20:37.09Palialso look at this log: https://support.logicpd.com/Portals/0/Users/049/05/305/20150427 - Ethernet over USBOTG as Host.log.txt
20:37.18Paliuboot print this line: "Enable battery backup charger (BB_CFG = 0x1c)"
20:39.22DocScrutinizer05:-D
20:39.52Paligoing to investigate if upstream kernel set bb_cfg register or not
20:39.54DocScrutinizer05let's see what that means in detail
20:40.17PaliDocScrutinizer05: can you via i2c-get read bb_cfg register?
20:40.27Paliand check if charger is enabled or not?
20:40.51DocScrutinizer05NFC, prolly I could if I knew which address it is
20:41.27DocScrutinizer05unless some nasty module has the I2C bus exclusively opened
20:41.57Paliuse --force
20:41.59DocScrutinizer05seems I need to check the OMAP3530 TRM to find out about registers in TWL4030
20:44.35Palihttp://lxr.free-electrons.com/source/drivers/power/twl4030_charger.c?v=3.14#L238
20:46.51DocScrutinizer05aaah SWCU050G
20:47.24DocScrutinizer05or your sourcecode, yes
20:51.36DocScrutinizer05anyway you'll '*love*' that: swcu050g.pdf on page 89 has RTC registers **for secure mode** and for **unsecure mode**
20:53.57Palilooks like conversion formula for madc channel 9 (backup battery voltage is): (raw * BK_VOLT_STEP_SIZE) / BK_VOLT_PSR_R;
20:54.03Pali#define BK_VOLT_STEP_SIZE441
20:54.09Pali#define BK_VOLT_PSR_R100
20:54.18Palifile twl4030_bci_battery.c in nokia kernl
20:54.32Palithat one provides http://projects.goldelico.com/p/gta04-kernel/page/Power/
20:55.21Palibut because it is hardwired into twl4030_bci_battery.c driver (for twl4030 charger), bk_battery part cannot be used alone
20:55.53*** join/#maemo fuz_ (nobody@vau75-10-88-164-23-88.fbx.proxad.net)
20:58.53DocScrutinizer05http://wstaw.org/m/2016/03/26/plasma-desktopyJ2219.png
21:00.56Palihttps://github.com/pali/linux-n900/blob/v2.6.28-nokia/drivers/power/twl4030_bci_battery.c
21:01.05Palisearch for twl4030backupbatt_voltage_setup
21:01.20DocScrutinizer05PSR is PreScalerResistor or sth like that
21:01.41Paliit set BBCHEN bit in BB_CFG register
21:02.00PaliDocScrutinizer05: if BBCHEN bit is not set, then charging is disabled?
21:02.10DocScrutinizer05err yes, aiui
21:02.27Paliare you able to read that bit from userspace?
21:02.49DocScrutinizer05if I can find out which I2C register that is, then yes
21:03.08Paliok, I will try to find it from kernel sources
21:04.30DocScrutinizer05Address Offset  0x12-0x12 in 0x17 byte increments
21:04.31DocScrutinizer05Physical Address  0x0000 006D-0x0000 006D
21:05.05DocScrutinizer05http://wstaw.org/m/2016/03/26/plasma-desktopyJ2219.png
21:09.55DocScrutinizer05http://wstaw.org/m/2016/03/26/plasma-desktopKY2219.png
21:11.55*** join/#maemo troulouliou_div2 (~troulouli@unaffiliated/troulouliou-div2/x-0271439)
21:12.47DocScrutinizer05http://wstaw.org/m/2016/03/26/plasma-desktopar2219.png
21:13.17Palii2c bus: 0; i2c address: 0x4b (TWL_MODULE_PM_RECEIVER); register: 0x12 (BB_CFG); value 0x10 (BBCHEN)
21:13.54Palithis is calling kernel driver twl4030_bci_battery.c (if I decoded it correctly)
21:14.13DocScrutinizer05makes sense
21:15.47DocScrutinizer05BBCHEN is bit4 in BB_CFG
21:18.06Paliso call? $ sudo i2cget -f -y 1 0x4b 0x12 b
21:18.36DocScrutinizer05if 0x14 from uboot is correct, it sets BBCHEN= 1, BBSEL= 0 1 = 3.0V, BBISEL = 0 0 = 25µA
21:18.51DocScrutinizer05yes, that should work
21:19.06Paliit is safe to call it?
21:19.12DocScrutinizer05prolly yes
21:19.15Paliare you going to call that command? :-)
21:19.22DocScrutinizer05yes, will do
21:19.44DocScrutinizer05IroN900:/dev# i2cget -f -y 1 0x4b 0x12 b
21:19.46DocScrutinizer050x00
21:19.52DocScrutinizer05:-(
21:19.53Palihm...
21:20.13DocScrutinizer05secure mode?
21:20.19Pali$ sudo i2cget -f -y 1 0x4b 0x12 b
21:20.20Pali0x00
21:20.40Palido you mean omap HS mode?
21:21.29Paliif HS mode stop your command, you would see SIGBUS signal
21:21.40Paliand pagefault message in dmesg
21:21.44DocScrutinizer05no, seems twl4030 has some write protection, however registers should be readable any case
21:22.11Palimaybe it is correct output, just charging is disabled
21:22.16DocScrutinizer05yes
21:22.25Palii2cset and enable it :-)
21:22.44Palibut which value for bbsel and bbisel?
21:23.16Palitwl4030_bci_battery.c in twl4030backupbatt_voltage_setup() set 0x10
21:23.21DocScrutinizer05are you sure about I2Cbus 1?
21:23.33Paliyes, 100%
21:23.39DocScrutinizer05already tried i2cset ;-)
21:23.50Palilook at /sys/bus/i2c/drivers/twl4030/
21:23.55PaliI have there 1-0048
21:24.00Paliwhich means bus 1
21:24.13Palialso look at /sys/bus/i2c/devices/
21:24.25Palithey are in format "busnum-address"
21:24.30DocScrutinizer05IroN900:/dev# i2cset -f -y 1 0x4b 0x12 0x10 b
21:24.31DocScrutinizer05IroN900:/dev# i2cget -f -y 1 0x4b 0x12 b
21:24.33DocScrutinizer050x10
21:25.00Palimaybe your backup battery starts working? o?
21:25.29DocScrutinizer05no idea
21:25.32Paliso 0x10 is 2.5V and 25uA
21:25.45DocScrutinizer05IroN900:/dev# madc 9
21:25.47DocScrutinizer05Channel 9: 708
21:25.52DocScrutinizer05yes
21:27.07Paligoing to recheck if address/register is correct
21:27.10DocScrutinizer05IroN900:/dev# i2cset -f -y 1 0x4b 0x12 0x1b b
21:27.12DocScrutinizer05IroN900:/dev# i2cget -f -y 1 0x4b 0x12 b
21:27.13DocScrutinizer050x1b
21:27.15DocScrutinizer05IroN900:/dev# madc 9
21:27.16DocScrutinizer05Channel 9: 710
21:28.51Palido you know how long can work rtc in your n900 without main battery?
21:28.52DocScrutinizer05.oO(???)
21:29.07DocScrutinizer05no, not realy tested yet, not long
21:29.38Palitry to let it enabled for a longer time
21:30.06Palimy rtc loose time in few minutes without backup battery
21:30.21PaliI can do this test to see if it increase time...
21:30.53Paliif charging of backup battery was totally disabled it is really stupid from nokia...
21:32.04DocScrutinizer05http://paste.opensuse.org/80296157
21:32.38DocScrutinizer05--> no visible effect
21:32.57*** join/#maemo shentey (~shentey@p4FF0E1FB.dip0.t-ipconnect.de)
21:35.20*** join/#maemo ceene (~ceene@collins.gmr.ssr.upm.es)
21:36.48DocScrutinizer05http://paste.opensuse.org/37478659
21:37.19WizzupPali: my rtc dies pretty much instantly
21:37.26Wizzupswapping battery is enough to reset the clock
21:37.34Wizzupmaybe I need more context.
21:37.40PaliWizzup: are you going to try it? :D
21:37.41Wizzupreads up
21:38.37DocScrutinizer05Wizzup: http://maemo.cloud-7.de/maemo5/usr/local/sbin/madc
21:39.20PaliDocScrutinizer05: if it is truth that backup battery was never charged, and n900 just totally discharged it... it is possible to charge such "fully discharged battery"?
21:39.33Palido you know what type of battery is it?
21:39.54Palior discharging that battery makes it permanent damage and dead?
21:40.09DocScrutinizer05it's most probably a LiMn
21:40.41DocScrutinizer05it should be immune against deep discharge, somewhat
21:41.34DocScrutinizer05but those cells are notorious for blowing chunks after max 12 to 18 months, seen exactly same with Freerunner
21:42.40DocScrutinizer05however that the voltage as seen by madc 9 doesn't change _at all_ no matter what voltage I set and if BBCHEN = 1 or 0....   verrrrry suspicious
21:43.07DocScrutinizer05battemp is ADCIN4, right?
21:43.27Palino
21:43.33PaliADCIN0 is temperature
21:43.43PaliADCIN4 is BSI
21:44.06DocScrutinizer05right
21:44.08*** join/#maemo ceene (~ceene@collins.gmr.ssr.upm.es)
21:44.35DocScrutinizer05what's your madc 0, madc 4 ?
21:44.56DocScrutinizer05Channel 0: 62   Channel 4: 469
21:45.04*** join/#maemo florian (~fuchs@Maemo/community/contributor/florian)
21:45.06Palichannel0=55 channel4=465
21:45.18Palicurrently charging my n900 via wallcharger
21:45.24DocScrutinizer05your room temperature a tad to the low side?
21:45.43DocScrutinizer05aaah wait, it's inverted, right?
21:45.49Paliyes
21:45.58Palisomewhere I have formula
21:45.59DocScrutinizer05so yes, makes perfect sense
21:46.15DocScrutinizer05nevermind formula
21:46.23PaliTEMP = (1/(t1 + 1/298) - 273.15)
21:46.23PaliWhere t1 = (1/B) * ln((RAW_ADC_U * 2.5)/(R * I * 255))
21:46.33PaliR = 100, B = 3380, I = 0.00671
21:47.09Paliso right it is inverted
21:47.36DocScrutinizer05http://paste.opensuse.org/37195031
21:48.23DocScrutinizer05afk
21:48.52DocScrutinizer05holler if you can think of another way to nuke my device via cmdline ;-)
21:51.30PaliI let charging enabled... will see what happen...
21:51.56DocScrutinizer05zilch will happen, I've set it to 1mA and notching changed
21:52.31DocScrutinizer05anyway, I'll set it to 3V 1mA again
21:53.08DocScrutinizer05meh, I set it to 3V3 1mA
21:55.14DocScrutinizer05recheck if 0x4b 0x12 is actually the right address
21:55.20DocScrutinizer05please
21:55.28Palialready did it
21:55.51DocScrutinizer05compare to some register with well known content
21:56.00Palithat uboot doing this: val |= 0x10; twl4030_i2c_write_u8(TWL4030_CHIP_PM_RECEIVER, val, TWL4030_PM_RECEIVER_BB_CFG)
21:56.26Pali#define TWL4030_CHIP_PM_RECEIVER                      0x4b
21:56.56Pali#define TWL4030_PM_RECEIVER_BB_CFG                    0x6D
21:57.15Palihmmm BB_CFG is 0x6D why?
21:57.52Palilinux kernel define BB_CFG as 0x12
21:58.13Palihere is that uboot patch: http://repository.timesys.com/buildsources/u/u-boot/u-boot-2011.06/u-boot-2011.06-omap3logic-BSP-2.2-0-01-201210241030.patch
21:58.17Palisearch for function twl4030_enable_bb_charging
21:59.59Palistatic inline int twl4030_i2c_write_u8(u8 chip_no, u8 val, u8 reg) { return i2c_write(chip_no, reg, 1, &val, 1); }
22:00.22Palii2c_write(uchar chip, uint addr, int alen, uchar *buffer, int len);
22:00.46PaliDocScrutinizer05: uboot uses 0x6D and BB_CFG
22:00.54Palis/and/as/
22:03.20*** join/#maemo vectis3 (~user@79-64-237-207.host.pobb.as13285.net)
22:06.38Pali$ sudo i2cget -f -y 1 0x4b 0x6d b
22:06.38Pali0x1b
22:10.09Pali0x1b would mean 3.1V/1mA
22:11.33DocScrutinizer05yes
22:13.20DocScrutinizer05http://paste.opensuse.org/6040681
22:17.08DocScrutinizer05I wonder what the heck means      Physical Address  0x0000 006D-0x0000 006D
22:19.11DocScrutinizer05IroN900:/dev# i2cget -f -y 1 0x4b 0x6d b
22:19.13DocScrutinizer050x1b
22:20.59DocScrutinizer05oooh, you already said that
22:24.45*** join/#maemo vectis3 (~user@79-64-236-43.host.pobb.as13285.net)
22:24.55DocScrutinizer05WOW!
22:24.58DocScrutinizer05IroN900:/dev# i2cset -f -y 1 0x4b 0x6d 0x1f b; i2cget -f -y 1 0x4b 0x6d b; madc 9
22:24.59DocScrutinizer050x1f
22:25.01DocScrutinizer05Channel 9: 735
22:25.02DocScrutinizer05IroN900:/dev# madc 9
22:25.04DocScrutinizer05Channel 9: 735
22:25.38DocScrutinizer05IroN900:/dev# i2cset -f -y 1 0x4b 0x6d 0x1b b; i2cget -f -y 1 0x4b 0x6d b; madc 9
22:25.39DocScrutinizer050x1b
22:25.41DocScrutinizer05Channel 9: 709
22:26.23DocScrutinizer05I guess it's time for a hard reset
22:26.44DocScrutinizer05messed around with too many random registers of twl4030
22:28.04DocScrutinizer05can't even find what's "physical address 0x12"
22:28.29DocScrutinizer05to make matters worse I also messed with 0x6b by typo
22:29.43DocScrutinizer05IroN900:/dev# i2cset -f -y 1 0x4b 0x6d 0x00 b; i2cget -f -y 1 0x4b 0x6d b; madc 9
22:29.45DocScrutinizer050x00
22:29.46DocScrutinizer05Channel 9: 0
22:29.50DocScrutinizer05my bupbat is a dummy
22:30.43DocScrutinizer05ooh wait, the ADC only works when BBCHEN
22:30.45DocScrutinizer05iirc
22:35.04DocScrutinizer05http://paste.opensuse.org/64107729
22:39.00*** join/#maemo TS3 (~skrydll@92.84.141.245)
23:04.07Paliso charging of backup battery is enabled by default
23:06.32DocScrutinizer05looks like
23:06.42DocScrutinizer051c
23:06.50DocScrutinizer05err 1b
23:07.17DocScrutinizer05wait... I forgot
23:07.30DocScrutinizer051b, right
23:07.52DocScrutinizer05and madc 9 clearly follows with zilch delay on my device
23:08.08DocScrutinizer05which means zilch buffering from bupbat?

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.