IRC log for #maemo on 20150124

00:00.55*** join/#maemo ruskie (ruskie@sourcemage/mage/ruskie)
00:14.59*** join/#maemo githogori (~githogori@98.234.68.64)
00:30.04*** join/#maemo ssvb (~ssvb@85-76-74-251-nat.elisa-mobile.fi)
00:38.03*** join/#maemo fmunozs (~frod@pdpc/supporter/active/fmunozs)
00:42.38*** join/#maemo FR-PC (~honoo-pc@110.159.109.26)
01:06.11*** join/#maemo DrCode (~DrCode@gateway/tor-sasl/drcode)
01:22.24*** join/#maemo githogori (~githogori@98.234.68.64)
01:38.00*** join/#maemo Kabouik_ (~quassel@10.165.69.86.rev.sfr.net)
01:54.16*** join/#maemo robbiethe1st (~robbiethe@50.107.30.118)
02:05.18*** join/#maemo gregoa (~gregoa@colleen.colgarra.priv.at)
02:28.34*** join/#maemo bef0rd (~bef0rd@unaffiliated/beford)
02:57.02Maxdamantuswonders how to take a proper photo without the camera-ui.
02:57.42MaxdamantusThis is a bit silly: http://wiki.maemo.org/Phone_control#Shoot_photo_after_10_seconds
02:58.10Maxdamantusit just reads it as a video source, upscaling the first frame.
03:25.35Maxdamantusugh, wtf
03:25.43Maxdamantusno wonder the default camera application is so laggy.
03:26.10Maxdamantusit reads images and other application resources when you take a picture?
03:55.29robbiethe1stHow does fcam do it?
04:02.03*** join/#maemo lxp (~lxp@unaffiliated/lxp)
04:06.15uhhimheredoes maemo5 run on n800?
04:20.04*** join/#maemo pdz (~paul@c-73-202-198-20.hsd1.ca.comcast.net)
04:47.39*** join/#maemo protem (~protem@unaffiliated/protem)
04:57.08*** join/#maemo Venusaur (~wdwrwf@wikipedia/Antonio-Lopez)
05:02.24*** join/#maemo RedW (~redw@89-73-179-171.dynamic.chello.pl)
05:18.04*** join/#maemo FlameReaper-PC (~honoo-pc@115.132.66.21)
05:25.43*** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil)
05:26.54*** join/#maemo at1as (~at1as@kurios.r4780y.com)
05:56.29*** join/#maemo Vajb (~Vajb@85-76-101-2-nat.elisa-mobile.fi)
06:05.16*** join/#maemo b1101 (~b@fsf/member/b1101)
06:07.56*** join/#maemo futpib (~futpib@176.104.193.185)
06:14.30*** join/#maemo LauRoman|Alt (~LauRoman@5-14-137-193.residential.rdsnet.ro)
06:21.44*** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil)
06:34.56*** join/#maemo b_ (~b@fsf/member/b1101)
07:07.45*** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil)
07:23.32*** join/#maemo mavhc (~mavhc@cpc12-basf8-2-0-cust10.12-3.cable.virginm.net)
07:26.37*** join/#maemo _rd (~rd@p4FD1EC23.dip0.t-ipconnect.de)
07:29.11*** join/#maemo VDVsx (~VDVsx@192.194.199.34)
07:46.48*** join/#maemo eMHa__ (~mh@HSI-KBW-46-223-128-114.hsi.kabel-badenwuerttemberg.de)
08:02.15*** join/#maemo auenf (David@171.72.233.220.static.exetel.com.au)
08:14.15*** join/#maemo _rd (~rd@p4FD1EC23.dip0.t-ipconnect.de)
08:38.57Sicelo~packages
08:39.16Sicelo~maemo-pgks
08:39.20Sicelomeh
08:43.24*** join/#maemo Pali (~pali@Maemo/community/contributor/Pali)
09:03.50Maxdamantuswonders how the camera-ui decides to produce the "Memory Full" error.
09:04.00Maxdamantuswonders if it has to do with ke-recv.
09:26.27*** join/#maemo sq-one (~sq-one@HSI-KBW-5-56-238-129.hsi17.kabel-badenwuerttemberg.de)
09:32.28*** join/#maemo geaaru (~geaaru@host217-224-dynamic.6-79-r.retail.telecomitalia.it)
09:50.33*** join/#maemo Haudegen (~quassel@85.124.51.57)
09:56.13keriomaemo is full of stupid shit
09:56.14*** join/#maemo eMHa__ (~mh@5.158.128.91)
09:56.22keriobecause user interface simplification
09:57.01*** join/#maemo florian (~fuchs@Maemo/community/contributor/florian)
10:05.28MaxdamantusIndeed.
10:06.21MaxdamantusUI simplification vs. modularity
10:06.51MaxdamantusI'd go with modularity, but phone producers probably don't usually care about me.
10:10.37*** join/#maemo florian (~fuchs@Maemo/community/contributor/florian)
10:15.18*** join/#maemo FReaper-PC (~honoo-pc@115.132.66.21)
10:22.21MaxdamantusYay. Got it to stop trying to mount /dev/mmcblk0p1 without recompiling ke-recv, and the camera still works.
10:22.54MaxdamantusWill use it as a boot partition instead.
10:26.29*** join/#maemo sq-one (~sq-one@HSI-KBW-5-56-238-129.hsi17.kabel-badenwuerttemberg.de)
10:27.35Maxdamantuswonders if anyone's tried GRUB on u-boot on the N900.
10:28.22keriowhy bother?
10:28.25keriouboot is pretty good
10:28.37kerioisn't ke-recv just some shell scripts
10:28.42MaxdamantusIt seems tedious to configure.
10:28.49MaxdamantusNo. It's a program written in C.
10:28.57Maxdamantusbut it comes with some shell scripts.
10:29.06kerioalso what i'd like is to be able to open the back panel without forcibly cutting off the uSD
10:29.14MaxdamantusDone.
10:29.20keriopls giff solution
10:29.28Maxdamantushttp://talk.maemo.org/showthread.php?t=94463
10:29.53Maxdamantushacky solution, but it seems better than no solution.
10:30.05MaxdamantusI think I'm meant to be using kernel-power, rather than the cssu1 thing.
10:32.16Maxdamantusbetter for me anyway, as I don't have much interest in swapping SD cards.
10:32.39keriowhy even bother with the "if"
10:32.43keriojust to keep the patch small?
10:33.22MaxdamantusWhat would you do? Comment it out? Delete the line?
10:33.31keriodelete it
10:33.43keriothe source is not the place for removed code
10:33.48keriothat's the VCS' job
10:33.50MaxdamantusThen it's not obvious what the original code was.
10:34.07keriowho gives a shit
10:34.12MaxdamantusExactly.
10:34.14kerioit's right there in the history
10:34.27kerioyou're one of *those* aren't you
10:34.31MaxdamantusMy text editor doesn't show the history.
10:35.00kerioyou comment huge blocks of code and put "// maybe we'll need this later"
10:35.21*** join/#maemo geaaru (~geaaru@host217-224-dynamic.6-79-r.retail.telecomitalia.it)
10:35.26Maxdamantuswould rather use a /* */ comment
10:35.34*** join/#maemo LauRoman|Alt (~LauRoman@5-14-137-193.residential.rdsnet.ro)
10:35.36kerio/* */ doesn't work with nested comments
10:35.37Maxdamantusbut that requires insertions in two places.
10:35.45kerioyou should use #if 0/#endif
10:35.47kerioand even then
10:36.11keriothe source code isn't meant for storing old text
10:36.31keriothat's the VCS' responsibility
10:36.54Maxdamantusbut it's not really old.
10:37.08MaxdamantusSince the rest of the code that uses that mechanism is still there.
10:37.18MaxdamantusThat code essentially becomes dead too.
10:37.35kerioyou can remove that too i guess
10:37.38kerioif it's not in the API
10:37.41MaxdamantusThat's difficult.
10:38.29keriowhat's gpio_is_valid?
10:38.33kerioi don't have the source handy
10:39.15MaxdamantusIt's part of the current mainline tree.
10:39.26Maxdamantusdoesn't want to switch branches atm
10:42.29*** join/#maemo _rd (~rd@p4FD1EC23.dip0.t-ipconnect.de)
10:46.23*** join/#maemo Haudegen (~quassel@85.124.51.57)
10:55.29*** join/#maemo auenf (David@171.72.233.220.static.exetel.com.au)
10:57.12*** join/#maemo auenf (David@171.72.233.220.static.exetel.com.au)
11:10.53kerioyeah but
11:10.56keriocan we just make the gpio invalid
11:10.58keriosomehow
11:15.07*** join/#maemo eMHa__ (~mh@HSI-KBW-46-223-128-114.hsi.kabel-badenwuerttemberg.de)
11:21.24MaxdamantusIt's not particular to the mmc driver.
11:22.10Maxdamantusbut yes, you could probably just modify the gpio_is_valid function and say no when given the identifier for the cover.
11:22.30Maxdamantusthat might have negative effects on the OS.
11:23.18MaxdamantusIt wouldn't indicate that the cover is closed. It would say the GPIO indicating whether or not it's closed no longer exists.
11:38.06*** join/#maemo arcean (~arcean@aael34.neoplus.adsl.tpnet.pl)
11:39.06*** join/#maemo VDVsx (~VDVsx@dsl-hkibrasgw1-58c019-114.dhcp.inet.fi)
11:56.21*** join/#maemo aloril (~aloril@dsl-tkubrasgw2-54f81c-109.dhcp.inet.fi)
12:03.30*** join/#maemo auenf (David@220.233.72.171)
12:09.50*** join/#maemo vakkov (~vakkov@s3n104.brunel.ac.uk)
12:13.27*** join/#maemo mattaustin (mattaustin@gateway/shell/blinkenshell.org/x-swhbagbsqxzpbluf)
12:15.01*** join/#maemo kraft (kraft@gateway/shell/blinkenshell.org/x-fubkfilhqenidwaj)
12:15.27ShadowJK(this is why I don't publish patches)
12:26.49*** join/#maemo M4rtinK (~M4rtinK@mail.melf.eu)
12:31.58*** join/#maemo hurrian (~hurrian@unaffiliated/rikanee)
12:32.13*** join/#maemo vakkov (~vakkov@134.83.207.11)
12:46.01*** join/#maemo Natch (~Natch@h-155-122.a444.priv.bahnhof.se)
12:46.52*** join/#maemo frals (~frals@h-246-101.a328.priv.bahnhof.se)
12:46.52*** join/#maemo frals (~frals@Maemo/community/contributor/frals)
12:51.59*** join/#maemo peetah (~peetah@cha92-9-82-236-202-86.fbx.proxad.net)
13:18.09*** join/#maemo _rd (~rd@p4FD1EC23.dip0.t-ipconnect.de)
13:19.55*** join/#maemo GNUtoo-irssi (~GNUtoo@mek33-3-82-230-169-239.fbx.proxad.net)
13:20.03GNUtoo-irssihi,
13:20.32GNUtoo-irssimy n900 battery is empty and I can't start the n900 at all, so I've succedded to boot it trough an external battery:
13:20.48GNUtoo-irssiI keep the nokia battery in and trough wires I also connect an external battery
13:20.54GNUtoo-irssiand I monitor voltage trough a DMM
13:21.23GNUtoo-irssinow if I remove the external battery power source it shuts down
13:21.43GNUtoo-irssiI guess the proprietary charger daemon/script doesn't like the external battery
13:21.48GNUtoo-irssiIf I put the charger
13:21.50*** join/#maemo wotan147 (~max@2a02:8071:2ec9:bf00:b00e:92a4:49b2:8027)
13:21.50GNUtoo-irssiit keep beeing on
13:21.55GNUtoo-irssibut it won't charge either
13:22.02GNUtoo-irssiso I wonder what the best strategy is
13:22.20GNUtoo-irssiI've at my disposal (beside the hardware that I just mentioned):
13:22.38GNUtoo-irssia) a setup to compile mainline kenrel, I've a black screen when I launch it
13:22.46GNUtoo-irssib) a setup to compile uboot
13:22.53GNUtoo-irssic) an SHR image but no setup to compile it
13:23.02GNUtoo-irssi(my toolchain is an arm-none-*)
13:23.43GNUtoo-irssiI see nothing on lsusb
13:24.14GNUtoo-irssiI mean: I see nothing on usb once the kernel is "booted" but 0xFFFF does work with nolo
13:24.24*** join/#maemo pdz (~paul@c-73-202-198-20.hsd1.ca.comcast.net)
13:24.53GNUtoo-irssiahh ok the kernel panics
13:25.02GNUtoo-irssihmmm
13:25.08GNUtoo-irssimaybe bad microsd partition
13:25.20ShadowJKSounds to me like the battery is dead?
13:25.27GNUtoo-irssinot totally dead
13:25.29GNUtoo-irssiit's not 0v
13:25.37GNUtoo-irssiI want to jumpstart it
13:25.49GNUtoo-irssilet me explain a bit more background
13:26.03GNUtoo-irssiless than one week ago I used this very same battery to jumpstart another phone
13:26.16GNUtoo-irssiand I didn't charge it after
13:26.28*** join/#maemo ssvb (~ssvb@85-76-74-251-nat.elisa-mobile.fi)
13:26.29GNUtoo-irssiand now I'm ending up trying to jumpstart this n900 battery...
13:27.01GNUtoo-irssifirst the jumpstart was to save my C155 battery (an osmocombb compatible featurephone)
13:27.10GNUtoo-irssiand the n900 battery isn't flat at all
13:27.21GNUtoo-irssiSince the mainline kenrel now has charging and so on
13:27.32GNUtoo-irssiwould it charge the battery during a kernel panic?
13:27.45GNUtoo-irssior while waiting for a rootfs
13:27.51ShadowJKwhat's the voltage of the batteries involved?
13:28.15GNUtoo-irssihere the total voltage is 3.58 with a nexus s battery and the n900 battery
13:28.19GNUtoo-irssithey're both in parallel
13:28.28GNUtoo-irssithe + is connected to both batteries's +
13:28.30ShadowJKthat's in the low end
13:28.31GNUtoo-irssiand same for the GND
13:28.37GNUtoo-irssi?
13:28.44GNUtoo-irssiwhat do you mean by that's in the low end?
13:28.47GNUtoo-irssiah ok
13:28.55GNUtoo-irssi3.7v required I guess
13:29.55ShadowJKclose to shutdown.
13:29.56ShadowJKIf the nokia batery is very old and worn, it might drop too low once the other battery is disconnected
13:29.58GNUtoo-irssithat's when connected to the n900
13:29.59GNUtoo-irssiok
13:29.59ShadowJKas for charging, you'll see for yourself if voltage rises or not
13:30.05GNUtoo-irssiit does
13:30.07GNUtoo-irssiok
13:30.14GNUtoo-irssi0.93v
13:30.18ShadowJKif that's 3.58 while charging at full rate, the battery is extremely empty
13:30.27GNUtoo-irssithat's what it drops too
13:30.28GNUtoo-irssiok
13:30.32GNUtoo-irssiyes
13:30.39ShadowJKbattery/batteries
13:30.56GNUtoo-irssilet me boot under maemo
13:31.19GNUtoo-irssiI connected the charger
13:31.24GNUtoo-irssiand I'll let it bot
13:32.12GNUtoo-irssiwhat happens if nolo charges the battery?
13:32.22GNUtoo-irssiis there some light emmited?
13:32.33ShadowJKIf the two are very far apart in voltage when you parallell them, there could be large amount of current flowing between them, which could trigger the battery's protection circuit, effectively disabling one of them
13:32.50GNUtoo-irssiyes
13:32.56GNUtoo-irssinow I've a light under nolo
13:33.23GNUtoo-irssiand the voltage is at 3.50v
13:33.28GNUtoo-irssiso I'll keep it there
13:33.29GNUtoo-irssiright?
13:33.44GNUtoo-irssiorange light
13:34.00GNUtoo-irssithe voltage is at 3.50v with the charger and only the nokia battery
13:35.10GNUtoo-irssibeside the DMM I didn't succeed at knowing if the internal battery is connected
13:36.22*** join/#maemo Kabouik (~quassel@10.165.69.86.rev.sfr.net)
13:36.37*** join/#maemo _rd (~rd@p4FD1EC23.dip0.t-ipconnect.de)
13:37.46GNUtoo-irssi(I've prevented it to boot from nolo)
13:38.23ShadowJK.93 is too low, in the sense that the protrction circuit kicks in at 2.8 or so
13:38.38GNUtoo-irssiShadowJK: ok
13:39.04GNUtoo-irssinow the led is orange in nolo with only nokia battery and charger
13:39.14ShadowJKand that li-ion batteries get severely worn for every day at 2.8V already, let alone lower voltages
13:39.40GNUtoo-irssisince the wiki is down I've no idea of what it means (the orange led)
13:39.59ShadowJKrecharging li-ion that's dropped to .9V could be dangerous, so dont leave it unattended (ever)
13:40.05GNUtoo-irssiok
13:40.07GNUtoo-irssiI did once
13:40.12GNUtoo-irssiit didn't charge at all
13:40.13GNUtoo-irssiok
13:40.19GNUtoo-irssiI left it in maemo
13:40.23GNUtoo-irssiwith the battery and the charger
13:40.34GNUtoo-irssinow it's in nolo
13:40.43GNUtoo-irssiI keep monitoriing but still 3.50/3.51
13:40.53GNUtoo-irssiI guess I need linux, and an initramfs
13:41.09GNUtoo-irssiI didn't succeed to boot something else than maemo
13:41.24ShadowJKI'm not sure what mainline does, if it needs software to turn on charging or not
13:41.32GNUtoo-irssiok
13:41.36GNUtoo-irssielse there is SHR
13:41.42GNUtoo-irssibut I didn't succeed either
13:41.47MaxdamantusMainline works for me.
13:41.49GNUtoo-irssiit bet it didn't find mmc
13:41.49GNUtoo-irssiok
13:41.56GNUtoo-irssiMaxdamantus: how do you boot it?
13:42.04GNUtoo-irssicombined kernel+uboot?
13:42.14MaxdamantusI can give you a kernel you should be able to use to load the shell from ubifs, if you want.
13:42.15GNUtoo-irssiif so how to produce that, the python script that did it is done
13:42.17Maxdamantus(no modules needed)
13:42.19MaxdamantusYes, uboot.
13:42.22GNUtoo-irssiI have that
13:42.26GNUtoo-irssiI have mainline too
13:42.31GNUtoo-irssibut I need to make them boot
13:42.39MaxdamantusOh, wait, my kernels have Dvorak hardcoded.
13:42.41GNUtoo-irssiI have that working:
13:42.50GNUtoo-irssinolo->kernel->nothing on display
13:43.07GNUtoo-irssinolo->uboot->2.6.37 on mmc
13:43.11GNUtoo-irssiand doesn't find rootfs
13:43.14GNUtoo-irssiso I need:
13:43.17keriodoes mainline have Pali's modules for bq24150?
13:43.20GNUtoo-irssinolo->uboot->mainline->
13:43.24GNUtoo-irssiI know how to compile mainline
13:43.29GNUtoo-irssiI did it in fact
13:43.31GNUtoo-irssiI lack:
13:43.41GNUtoo-irssi1) the script to assemble the mainline+uboot image
13:43.42Palikerio: yes: http://elinux.org/N900
13:43.48GNUtoo-irssi2) good cmdline args
13:43.57GNUtoo-irssiI have that currently:
13:44.16GNUtoo-irssiCONFIG_CMDLINE="omapfb.vram=0:2M,1:2M,2:2M snd-soc-rx51.hp_lim=42 snd-soc-tlv320aic3x.hp_dac_lim=6 root=/dev/mmcblk1p1 rw console=tty0 panic=1"
13:44.17MaxdamantusI copied the cmdline from 2.6.28.10
13:44.23GNUtoo-irssiwith CONFIG_CMDLINE_FORCE=y
13:44.27GNUtoo-irssiand I boot with DT
13:44.34GNUtoo-irssiso I've the combined zImage
13:44.44keriocan't you get emergency charging from just nolo or uboot?
13:44.47Maxdamantusare you sure the mmc device is right?
13:44.50GNUtoo-irssiany idea on what keystroke to make the bootloader boot maemo?
13:44.57GNUtoo-irssiMaxdamantus: of course not
13:45.00PaliGNUtoo-irssi: 1) script is part of u-boot-tools extras package (/usr/bin/u-boot-gen-combined)
13:45.06keriolol
13:45.07GNUtoo-irssiok thanks a lot!!!!
13:45.09MaxdamantusI've noticed with 3.14–3.18, mmcblk0 is SD
13:45.16kerioGNUtoo-irssi: any reason why you're not booting rescueOS?
13:45.20GNUtoo-irssiI've tried both mmcblk0 and mmcblk1
13:45.30GNUtoo-irssikerio: yes, I've not ever eared of it
13:45.32keriommcblk0 is SD if there's a SD
13:45.34GNUtoo-irssiok
13:45.37kerio~rescueos
13:45.37infoboti guess rescueos is http://n900.quitesimple.org/rescueOS/
13:45.39GNUtoo-irssiok
13:45.41PaliGNUtoo-irssi: you can use my linux-n900.git branch which contains patches which are not in mainline
13:45.46kerioloadable via usb
13:45.56kerioflasher-3.5 -k 2.6.37 -n initrd.img -l -b"rootdelay root=/dev/ram0"
13:45.56Palihttps://gitorious.org/linux-n900/linux-n900
13:47.01PaliMaxdamantus: mmc0 device is always uSD card, but mapping mmc0 to mmcblk0 or mmcblkd1 is not race free
13:47.42Palifor that reason there is udev rule in maemo which maps eMMC (mmc1) to mmcblk0 and uSD (mmc0) to mmcblk1
13:47.43GNUtoo-irssinice
13:47.46GNUtoo-irssithanks a lot
13:47.49MaxdamantusAh.
13:47.53GNUtoo-irssilet me try it
13:48.08GNUtoo-irssibtw I use 0xFFFF and the new features are so nice
13:48.14GNUtoo-irssithanks a lot for them
13:48.22GNUtoo-irssithere is even coldflashing now
13:49.38PaliGNUtoo-irssi: on linux-n900 there is branch v3.19-rc5-n900
13:49.42Paliwhich I updated *now*
13:49.59GNUtoo-irssiok
13:50.00Palibut I (auto)tested it only in qemu
13:50.04GNUtoo-irssiI was on 3.18
13:50.09GNUtoo-irssi3.18.*
13:50.25Paliit boots to busybox shell
13:52.28Maxdamantushas had problems with 3.18, relative to 3.14
13:52.42Maxdamantuslooks like ones people are aware of though.
13:54.35Maxdamantus(USB not working, doesn't seem to shut down properly—screen goes blank and have to just take out the battery)
13:55.13Paliin my git repo is some hack patch which could fix usb problems
13:56.52MaxdamantusI think it happened in your repo too.
13:56.59Maxdamantussomething about musb core not ready. Dunno.
13:57.00*** join/#maemo _rd (~rd@p4FD1EC23.dip0.t-ipconnect.de)
13:57.59Maxdamantus(n900 repo, 3.18-rc6)
14:02.04GNUtoo-irssiok, networking problem, since the n900 is 192.168.2.15
14:02.07GNUtoo-irssiI'll fix that later
14:02.49GNUtoo-irssiI found that: ./rescueOS/charge21.bash
14:03.37GNUtoo-irssi
14:03.39Maxdamantusif that's over usb, ifconfig usb0 10.0.0.123
14:03.48Maxdamantus(the networking problem)
14:03.48GNUtoo-irssiyes
14:05.00GNUtoo-irssidone anyway
14:05.02Maxdamantus(or 10.123 for short)
14:05.27GNUtoo-irssiyes, here's what I have:
14:06.12GNUtoo-irssiStatus: 0x10 Mode: CHARGING Full: 0 Wall: 0 Voltage: 3668 NAC: 0 level: 0 % Rate: 0 System: -950 Ch: 950
14:06.17GNUtoo-irssiNAC means?
14:06.29GNUtoo-irssiI guess NAC != NAK
14:06.31Maxdamantusnominal available charge
14:06.34GNUtoo-irssiok
14:06.40GNUtoo-irssiI'll check sysfs
14:07.12GNUtoo-irssistatus discharging
14:07.14GNUtoo-irssihmmm
14:07.26GNUtoo-irssipresent 1
14:07.32GNUtoo-irssiI'll look if I can get an ID
14:08.11GNUtoo-irssiStatus: 0x10 Mode: CHARGING Full: 0 Wall: 0 Voltage: 4118 NAC: 0 level: 0 % Rate: 0 System: -625 Ch: 625
14:08.15GNUtoo-irssimaybe it still charges?
14:08.25GNUtoo-irssibeside wat the battery gauge driver says
14:09.31*** join/#maemo bef0rd (~bef0rd@unaffiliated/beford)
14:10.13GNUtoo-irssilet me look
14:10.17GNUtoo-irssiI forgott the other battery on
14:12.20*** join/#maemo kerio (kerio@acehack.de)
14:18.26GNUtoo-irssiwhere's the . on the keyboard?
14:21.56*** join/#maemo xes (~xes@unaffiliated/xes)
14:28.37ShadowJKcharge script probably interacts badly if there's kernel charging modules
14:29.19ShadowJKor kernel battery gauge module
14:29.52ShadowJKmiddle row third last key, my guess
14:31.19ShadowJKit's weird that it shows somewhat credible voltage, but everything else is 0
14:32.03ShadowJK... and where the hell did 625 come from D:
14:33.12ShadowJKOh, I see
14:39.20GNUtoo-irssiShadowJK: ok
14:39.28GNUtoo-irssihmmm
14:39.30GNUtoo-irssiI boot
14:39.39GNUtoo-irssioops
14:39.52GNUtoo-irssiis there a way to setup the rescueOS to boot directly from flash
14:40.05GNUtoo-irssi(with reguard to kernel parameters)
14:40.47GNUtoo-irssibtw, I booted trough dual-batteries
14:41.01GNUtoo-irssienabled charging
14:41.10GNUtoo-irssiswitched to charger cable after enabling wifi
14:41.16GNUtoo-irssithen stopped charging
14:41.21GNUtoo-irssiit powered off
14:41.35GNUtoo-irssiI didn't restart charging fast enough to keep it on
14:42.55GNUtoo-irssiI'll tr again
15:01.24GNUtoo-irssihmmm
15:01.43GNUtoo-irssiI guess the bootargs are in nolo, right?
15:04.46*** join/#maemo RiD (~RiD@bl22-17-202.dsl.telepac.pt)
15:15.32GNUtoo-irssiis it problematic if the charger script stays in 0x10?
15:15.46GNUtoo-irssiif I remember well 0x10 is usb charging trough a computer
15:16.17*** join/#maemo wizbit (~wizbit@unaffiliated/wizbit)
15:16.56GNUtoo-irssican I try to force 0x90?
15:16.59GNUtoo-irssilike by i2cset?
15:17.03keriowhat for
15:17.07ShadowJKi would have said other way around
15:17.10GNUtoo-irssiok
15:17.18GNUtoo-irssiright, safer
15:17.29kerioafaik the charge21.bash script in rescueOS assumes you're using a wallcharger
15:17.40GNUtoo-irssiok
15:17.48GNUtoo-irssiI don't remember well the status values
15:17.52GNUtoo-irssiit's been years...
15:18.23GNUtoo-irssiStatus: 0x10 Mode: CHARGING Full: 0 Wall: 0 Voltage: 4172 NAC: 0 level: 0 % Rate: 0 System: -213 Ch: 213
15:18.34GNUtoo-irssithe DMM says 4.17/4.18
15:18.46GNUtoo-irssiand the screen says something about stfu
15:18.53GNUtoo-irssiI've not yet looked at stfu
15:18.57ShadowJKrate 0 is weird.
15:18.58GNUtoo-irssibeside the fact that it disables the message
15:19.00GNUtoo-irssiok
15:19.25GNUtoo-irssiright now after booting it trough a second battery, it now has only the charger and the internal battery
15:19.32GNUtoo-irssiand it's available trough wifi
15:19.33ShadowJKIf there's battery gauge kernel module loaded, the script wouldn't be able to get that data
15:19.36GNUtoo-irssi(the shell)(
15:19.38GNUtoo-irssi)
15:20.03ShadowJKwhat's voltage with one batt? with two battery?
15:20.38GNUtoo-irssione batt: the ones that I just gave (4.16/4.17/1.18)
15:21.19Maxdamantus03:39:47 < GNUtoo-irssi> is there a way to setup the rescueOS to boot directly from flash
15:21.43GNUtoo-irssiMaxdamantus: should I recompile the kenrel or should I instead boot trough uboot?
15:21.44Maxdamantususing mkimage from u-boot-tools, yes.
15:21.46GNUtoo-irssiok
15:21.50GNUtoo-irssiuboot then
15:21.53MaxdamantusDon't need to recompile the kernel.
15:22.03GNUtoo-irssiwell the fastest boot way would be better
15:22.08GNUtoo-irssibut that can work too
15:22.33Maxdamantusif your uboot menu has something like "run emmcboot" in it, that looks for boot.scr on ext2 partitions on the eMMC.
15:22.47GNUtoo-irssiyes
15:24.06MaxdamantusTo make the uboot kernel image: mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -n rescueOS -d 2.6.37 rescue.u
15:24.15GNUtoo-irssiyes
15:25.10Maxdamantusand the commands to boot it, I think: ext2load mmc 1:2 $loadaddr /rescue.u; setenv bootargs 'init=..'; bootm
15:25.15GNUtoo-irssiit also often disconnect wifi-wise
15:25.49GNUtoo-irssiI could also modify the initramfs to have some more automatic boot
15:25.54GNUtoo-irssilike connect to wifi
15:26.12MaxdamantusYou write those commands into a file, say, foo, then: mkimage -A arm -O linux -T script -C none -n boot -d foo boot.scr
15:26.21Maxdamantuswonders why it has to be so tedious.
15:26.57Maxdamantus(the 1:2 above is assuming the ext partition with /resue.u is the second one)
15:27.04Maxdamantus/rescue.u*
15:27.26GNUtoo-irssicompressed rom fs is CRAMFS?
15:27.53MaxdamantusI think "compressed rom fs" refers to something other than cramfs.
15:27.57Maxdamantusbut will be conceptually similar.
15:28.19GNUtoo-irssitype cramfs
15:28.20GNUtoo-irssiindeed
15:28.20MaxdamantusYeah, cromfs, not cramfs.
15:28.24GNUtoo-irssiok
15:28.29GNUtoo-irssiit says cramfs
15:28.31GNUtoo-irssistrange
15:28.40GNUtoo-irssiif I do mkcramfs and so on, would it work?
15:29.14MaxdamantusDoes the kernel have cramfs built-in?
15:29.15GNUtoo-irssito be more precise:
15:29.29GNUtoo-irssi.../initramfs/rescueOS-1.1.img on .../initramfs/tmp type cramfs (ro,relatime)
15:29.33GNUtoo-irssithat's what mount shows
15:29.47GNUtoo-irssiCONFIG_CRAMFS=y
15:29.48GNUtoo-irssiyes
15:29.55MaxdamantusYeah, that should work then.
15:30.00GNUtoo-irssianyway I'm recompiling it, souds more simple than uboot
15:30.08GNUtoo-irssibecause uboot is yet one more interaction/hop
15:30.42MaxdamantusWhat does recompiling it achieve?
15:30.59MaxdamantusOh, you mean recreating the cramfs?
15:33.01GNUtoo-irssiyes
15:33.08GNUtoo-irssiand hardcoding the CMDLINE
15:33.21GNUtoo-irssiI'm doing both
15:33.36GNUtoo-irssifor the compilation I've just to wait it to finish
15:33.49GNUtoo-irssiI'll see if it didn't finish in time for uboot
15:35.20GNUtoo-irssihmmm
15:35.21GNUtoo-irssiautostart_script=`grep -q autostart /proc/cmdline && cat /proc/cmdline | sed -e 's/.*autostart=\(.*\)/\1/'`
15:36.17GNUtoo-irssiso I could just put some commands in the cmdline?
15:40.03GNUtoo-irssiand it's cramfs
15:40.11GNUtoo-irssithe images looks the same under file
15:51.04GNUtoo-irssiok my cramfs work
15:51.06GNUtoo-irssibut not my kernel
15:51.10GNUtoo-irssilet me relook
15:51.30*** join/#maemo Vajb (~Vajb@85-76-23-183-nat.elisa-mobile.fi)
15:53.03GNUtoo-irssianyway, while a cramfs is read only, it's way easier than a classic initramfs to repack
15:53.23GNUtoo-irssiclassic initramfs is gunzip + cpio -idv < ./the_image + cpio somestuff
15:54.08Maxdamantusfind . | cpio -o -H newc | gzip -9 >foo.gz
15:54.12MaxdamantusI think.
15:54.16GNUtoo-irssiyes
15:54.21GNUtoo-irssibut I often have issues
15:54.24GNUtoo-irssieven if I do newc
15:54.37GNUtoo-irssilike I never remember how it works when including it inside the kernel
15:54.43GNUtoo-irssibut that's another story
15:55.18MaxdamantusI'm not sure you're going to be able to include the cramfs in your kernel.
15:55.24Maxdamantusif you're intending to flash the kernel.
15:55.27GNUtoo-irssinow I have:
15:55.27GNUtoo-irssiStatus: 0x10 Mode: CHARGING Full: 0 Wall: 0 Voltage: 4172 NAC: 0 level: 0 % Rate: 0 System: -213 Ch: 213
15:55.31GNUtoo-irssiyes
15:55.42GNUtoo-irssiI was talking about the usual way of doing repack
15:55.52GNUtoo-irssiand I was praising the easyness of this way
15:55.57MaxdamantusI think it has to be less than somewhere around 4 MiB.
15:58.18GNUtoo-irssiok
16:05.08MaxdamantusPali: is your bootmenu thing able to be reused?
16:05.24Palireused for what?
16:05.50Maxdamantuseg, from the default menu, loading a script using the eMMC entry that does something like: bootmenu_0=foo=bar; bootmenu
16:06.10MaxdamantusThat would at least not clear the other entries, I'd imagine.
16:06.28*** join/#maemo GNUtoo-irssi (~GNUtoo@mek33-3-82-230-169-239.fbx.proxad.net)
16:06.30GNUtoo-irssisorry, some router issues
16:06.41GNUtoo-irssianyway I'll use uboot
16:06.56GNUtoo-irssithe compiled kernel didn't boot...
16:07.21PaliMaxdamantus: if you overwrite uboot env then it should work
16:07.48Palijust run command bootmenu again
16:08.05Maxdamantusuboot env?
16:08.23Palibootmenu_X is uboot env
16:08.32MaxdamantusOh, right, each one.
16:08.48MaxdamantusHm.
16:09.05Maxdamantuswonders why he didn't put an underscore in his uboot keyboard layout.
16:10.31GNUtoo-irssiwonder where the dot is in the rescueOS
16:11.35MaxdamantusOh. I probably do have an underscore, in the usual position.
16:13.07GNUtoo-irssibtw, I didn't find /usr/bin/u-boot-gen-combined
16:13.12GNUtoo-irssiis that a package of maemo?
16:13.18GNUtoo-irssiI looked in uboot source
16:13.25GNUtoo-irssi(upstream uboot)
16:13.54Paliit is only in maemo extras u-boot-tools package
16:14.19Paliit is shell script (busybox enabled :-))
16:14.57MaxdamantusAhah. I've been doing it completely wrong.
16:15.39GNUtoo-irssiok
16:15.51GNUtoo-irssibusybox shell is fine
16:15.55MaxdamantusMk, that does work.
16:16.00GNUtoo-irssiI've busybox on the rescueOS anyway
16:16.14GNUtoo-irssiwhere are the CSSU repos so I can download it?
16:16.23Pali~packages
16:16.23GNUtoo-irssiwiki is down, so I'm a bit out of documentation
16:16.25GNUtoo-irssiok
16:16.26GNUtoo-irssithanks
16:16.29Pali~pkg
16:16.29infobothmm... pkg is http://maemo.org/packages/
16:18.58GNUtoo-irssithanks
16:24.02*** join/#maemo sq-one (~sq-one@HSI-KBW-5-56-238-129.hsi17.kabel-badenwuerttemberg.de)
16:40.04*** join/#maemo _rd (~rd@p4FD1EC23.dip0.t-ipconnect.de)
17:08.21*** join/#maemo vakkov (~vakkov@s3n106.brunel.ac.uk)
17:12.58GNUtoo-irssibtw, just out of curiosity, was there some research to run uboot earlier than after nolo
17:13.01GNUtoo-irssilike to replace nolo
17:13.14GNUtoo-irssiI guess that no one tried to replace the xloader since it's signed
17:13.23GNUtoo-irssibut since there is coldflashing in 0xFFFF
17:13.37GNUtoo-irssimaybe some people started working on that?
17:16.32PaliI tried to do in qemu, but there were 2 problems
17:16.51Pali1) uboot is too big OR size for secondary nolo is too small
17:16.57GNUtoo-irssiah right
17:17.02Pali2) it does not worked
17:17.08GNUtoo-irssiok
17:17.20Paliuboot spl was unable to initialize something and so hangs
17:17.27GNUtoo-irssibtw since you work on the kernel, any hints on how to get some outputs on it
17:17.37GNUtoo-irssithe mainline has no output
17:17.50GNUtoo-irssidisplay: nothing
17:17.53Palisee cmdline which is in -n900 branch
17:17.55GNUtoo-irssiok
17:18.01Palitty options
17:18.15Palithey redirect output to both screen and serial console
17:18.22GNUtoo-irssiv3.18 or v3.19
17:18.23GNUtoo-irssiok
17:18.33GNUtoo-irssiI've on 3.18
17:18.41GNUtoo-irssiI'll look
17:19.07Paliconsole=tty0 console=ttyO2
17:19.13Pali(in this order)
17:20.03GNUtoo-irssithanks
17:20.06GNUtoo-irssiyes
17:23.40freemangordonPali: I am still unable to figure out what *exactly* that new xloader does compared to stock. I see 2 more functions on addresses starting at 0x20xxxx are called, along with 2 more SMC calls
17:23.58freemangordonbut I can't find the code behind those functions :(
17:24.56freemangordonPali: do you have any idea if xloader is linear? i.e. is it possible that different parts are put on different addresses?
17:25.44PaliI guess it is linear
17:25.51GNUtoo-irssican we coldflash different xloaders than nokia's signed ones?
17:26.08freemangordonGNUtoo-irssi: coldflash? why coldflash?
17:26.22GNUtoo-irssiwell, flash
17:26.31Paliwe can store to nand what we want
17:26.39GNUtoo-irssiyes, but will it boot then
17:26.46freemangordonPali: do you know if flasher (or 0xFFFF) wraps the xloader.bin with some additional data?
17:26.49Palidifferent question is if omap bootrom it accept for booting
17:26.52GNUtoo-irssiin other words is there some way arround the secure mode
17:27.05GNUtoo-irssiyes, was there some research in that area?
17:27.26GNUtoo-irssithe Android motorolas phones also had omap
17:27.46Palifreemangordon: all images for flashing are sent together with fiasco header to NOLO via usb
17:27.59GNUtoo-irssiand there was some key to sign the bootloaders that was part of some lg source code dump
17:28.05Palibut xloader and secondary images are stored without it
17:28.19*** join/#maemo _rd (~rd@p4FD1EC23.dip0.t-ipconnect.de)
17:28.22GNUtoo-irssiso I was wondering if people figuredout how to make the bootrom run a replacement for nokia's xloader
17:28.26freemangordonPali: I am asking, because qemu (for example) searches for some sections (those with RAM/GPMC/etc) parameters which are missing in xloader.bin
17:28.30Paliraw dump from /dev/mtd0 is same as orignal image (after deleting padding)
17:28.43freemangordonhmm, weird
17:29.04PaliGNUtoo-irssi: replace omap hw chip
17:29.05freemangordonPali: see https://gitorious.org/qemu-maemo/qemu-n900/source/d631b7aa43cdea46187c2aff896ddd99f371c759:hw/omap3_boot.c#L246-248
17:29.07PaliGNUtoo-irssi: not possible
17:29.12GNUtoo-irssiok
17:29.24freemangordonand those must be present according to TRM
17:29.33freemangordonbut they are missing in xloader
17:30.29Palithose strings must be in xloader image??
17:30.44freemangordonyep, see 26.4.8.1 in TRM
17:31.16freemangordonbut they are missing
17:31.24Paliit is missing also in xloader-qemu.bin
17:31.28Paliand xloader-qemu.bin is booted by qemu
17:31.32freemangordonyes
17:31.44freemangordonI know, already checked and REed
17:31.59freemangordonwe miss something there
17:32.25freemangordonBTW ever tried qemu with xloader for the device?
17:32.44Paliyes, years ago and qemu crashed
17:32.49freemangordon:)
17:32.57Palibut can try it again :-)
17:33.19freemangordonI guess it doesn't like SCM calls and writes to co-processors
17:33.27freemangordonSMC that is
17:33.48Paliin qemu source code is written that smc instrucntions are noop in ROM vector
17:34.00Palimaybe it is bug in qemu and implemented incorrectly
17:34.13freemangordonyeah, but if you try to write to non-emulated CP it bails out iirc
17:34.19Palior someting change that ROM code (xloader? nolo? kernel?)
17:35.16freemangordonMaybe I should try to dump bootrom and see what happens there
17:36.26Paliqemu-xloader with 2101 seconary booted kernel in qemu
17:36.50freemangordonPali: BTW what I am trying to achieve is to enable AES, not simply detect if it is enabled  :)
17:37.16freemangordonsecondary == NOLO ?
17:37.18Pali2101 xloader with qemu seconary cause qemu crash
17:37.21freemangordonfrom the device?
17:37.24Paliyes seconary == NOLO
17:37.31Palifrom FIASCO image
17:37.35freemangordonok
17:37.41Palicrash: (qemu) qemu: fatal: Trying to execute code outside RAM or ROM at 0x000025a4
17:37.45freemangordonat what stage is the crash?
17:38.02Paliprobably xloader
17:38.09freemangordonyeah, most probably
17:38.11Palibecause it did not print anything to serial console
17:38.21freemangordonthere is some ROM code qemu is missing
17:38.35freemangordonwait, xloader has some strings in it
17:38.41Palicurrent state of non zero registers: R00=40014044 R01=000025a4 R13=4020fcb0 R15=000025a4 PSR=400001df -Z-- A sys32
17:39.16PaliPC is R15?
17:39.17freemangordonR13 is in xloader
17:39.31freemangordonnot sure
17:39.35freemangordon(R15)
17:39.43*** join/#maemo sq-one (~sq-one@HSI-KBW-5-56-238-129.hsi17.kabel-badenwuerttemberg.de)
17:39.57freemangordonlemme check
17:40.09Paliyes, R15 is PC register
17:40.18freemangordon:nod:
17:40.27freemangordonand R14 should be LR?
17:40.41Paliso secure xloader is really calling something at 0x2xxx
17:40.58Paliyes, R14 LR
17:41.05freemangordonand it is zero?
17:41.10freemangordonR13 is SP
17:41.14Paliyes
17:41.19PaliR14 is zero
17:41.20freemangordonthe fuck?
17:41.33PaliI can connect gdb and see more
17:42.05freemangordonok, so SP in xloader (xloader sets SP to start at the end of the image iirc) means that it is really xloader crashing
17:42.38Paliit started execution at 0x40014000
17:42.39freemangordonPali: you'd better dump the memory from 0x000000 to 0x20FFFF
17:42.44freemangordonthis is bootrom
17:42.54freemangordon(0x4.....)
17:43.35freemangordonxloader is loaded at 0x40208000
17:43.48freemangordonxloader-qemu at 0x40200000
17:43.57freemangordon(those come from the header)
17:45.23Palihttp://pastebin.com/7xSfdYF8
17:45.29freemangordonPali: first function is at address 0x208F05, the second on 0x208DFD
17:45.46GNUtoo-irssiPali: what is your last known booting branch (gitorious)?
17:46.07PaliGNUtoo-irssi: in qemu is working also 3.19
17:46.14Palion my n900 is working 3.12
17:46.27Pali(do not remember if new branched working with maemo)
17:46.27GNUtoo-irssiok
17:46.48freemangordonPali: maybe xloader detects this is GP device and doesn't behave the same as on the real HS HW
17:47.12Palifreemangordon: see step by step log
17:47.26Palijust few instructions are done before crash
17:47.45freemangordonyep, saw it, maybe qemu can't parse xloader header
17:48.09Paliyes, maybe this is reason
17:48.27Palithere is block of public key and certificate...
17:48.47freemangordonanyway, gtg, will continue on that tomorrow
17:48.49freemangordonbye
17:49.48GNUtoo-irssiPali: you use dtb in your branches?
17:51.27GNUtoo-irssiguesses so but just wants to check
17:53.21*** join/#maemo aaaaaa_ (~aaaaaa@collins.gmr.ssr.upm.es)
17:53.34PaliGNUtoo-irssi: DT is used only in new
17:53.38Pali3.19 is DT
17:53.46*** join/#maemo incrys (~incrys@adsl-ull-42-42.42-151.net24.it)
17:53.47Pali3.12 is not DT for sure
17:54.04GNUtoo-irssiok
17:56.25*** join/#maemo hhhh (bc304bef@gateway/web/freenode/ip.188.48.75.239)
17:58.23*** join/#maemo geaaru (~geaaru@host217-224-dynamic.6-79-r.retail.telecomitalia.it)
18:08.47bencohwooh, gnutoo is back on the n900 ? :)
18:10.02*** join/#maemo GNUtoo-irssi (~GNUtoo@mek33-3-82-230-169-239.fbx.proxad.net)
18:11.42*** join/#maemo sparetire_ (~sparetire@unaffiliated/sparetire)
18:18.34*** join/#maemo obsed (~obesd@unaffiliated/obesd)
18:19.27*** join/#maemo _rd (~rd@p4FD1EC23.dip0.t-ipconnect.de)
18:26.04*** join/#maemo Haudegen (~quassel@85.124.51.57)
18:29.53*** join/#maemo pdz (~paul@c-73-202-198-20.hsd1.ca.comcast.net)
18:37.42*** join/#maemo blotter (~janus@95.90.242.35)
18:57.00GNUtoo-irssiok, I now have: Linux rescueos 3.19.0-rc5+ #14 PREEMPT Sat Jan 24 19:51:56 CET 2015 armv7l GNU/Linux
18:57.13GNUtoo-irssiI must wait to see if the mainline drivers charge?
18:57.20GNUtoo-irssithe sysfs says charging
19:06.34*** join/#maemo maybeWTF (~cl@p5B163776.dip0.t-ipconnect.de)
19:22.04GNUtoo-irssi<PROTECTED>
19:22.21GNUtoo-irssi- ti,weak-battery-voltage: The chip will use slow precharge if battery voltage is below this value.
19:22.28*** join/#maemo nox- (noident@freebsd/developer/nox)
19:22.28GNUtoo-irssisorry for the first wrong line
19:22.32GNUtoo-irssiI've also shortened the second
19:22.39GNUtoo-irssiso I guess it will charge very slowly
19:23.29*** join/#maemo maybeHere (~cl@p5B163776.dip0.t-ipconnect.de)
19:23.50GNUtoo-irssiI'll eat and shut down the charge during that
19:24.14bencohwhy shut it down ?
19:25.07GNUtoo-irssisafety reasons
19:26.43*** join/#maemo _rd (~rd@p4FD1EC23.dip0.t-ipconnect.de)
19:29.32PaliGNUtoo-irssi: kernel driver should autodetect wallcharger and automatically charge battery
19:30.24Paliwithout any userspace support
19:38.08ShadowJKi still think the bl-5j he's using is broken
19:42.32*** join/#maemo obsed (~obesd@unaffiliated/obesd)
19:43.39*** join/#maemo vakkov (~vakkov@s3n106.brunel.ac.uk)
19:54.51GNUtoo-irssiok
19:54.58GNUtoo-irssiyes, that's what I did
19:55.05GNUtoo-irssiI disabled the charger script
20:00.05*** join/#maemo obsed (~obesd@unaffiliated/obesd)
20:09.48*** join/#maemo b1101 (~b@fsf/member/b1101)
20:50.58*** join/#maemo babytoes (~chris@c-68-82-59-230.hsd1.pa.comcast.net)
20:51.59wizbitwhat is the 2nd most open user friendly phone apart from the n900?
20:52.31keriogta04
20:53.45bencohn9 isnt too bad as well
20:56.48GNUtoo-irssigta04, indeed
20:56.59GNUtoo-irssithen there is also the lg optimus black in the works
20:57.21GNUtoo-irssicheck code.paulk.fr: he is porting uboot to it
21:32.46*** join/#maemo githogori_ (~githogori@c-76-126-237-233.hsd1.ca.comcast.net)
22:16.43*** join/#maemo Haudegen (~quassel@85.124.51.57)
22:42.38*** join/#maemo heroux (~heroux@gateway/shell/insomnia247/x-vdthhalkhczjltyi)
22:51.40*** join/#maemo vakkov (~vakkov@134.83.207.11)
22:54.01*** join/#maemo Majmun (~Gost@109-93-152-20.dynamic.isp.telekom.rs)
22:56.13*** part/#maemo Majmun (~Gost@109-93-152-20.dynamic.isp.telekom.rs)
22:58.14*** join/#maemo hurrian (~hurrian@unaffiliated/rikanee)
23:04.15*** join/#maemo githogori (~githogori@98.207.182.139)
23:05.51*** join/#maemo githogori_ (~githogori@c-98-234-224-38.hsd1.ca.comcast.net)
23:10.50Maxdamantuswonders what he's doing wrong trying to boot a 2.6.28.10-{cssu1,power53} kernel from uboot, without attachboot.
23:11.34Maxdamantustrying something like: ext2load mmc 1:1 0x82000000 /k/zImage-2.6.28.10-cssu1.u; bootm 0x82000000
23:11.42Maxdamantuswhich works for a 3.14 mainline.
23:17.11*** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr)
23:17.18*** join/#maemo r00t|home (~r00t@port-92-196-14-156.dynamic.qsc.de)
23:28.11MaxdamantusAhah, finally.
23:28.31Maxdamantuswonders if it was the lack of setup_omap_atag.
23:36.23*** join/#maemo Guest18889 (~mario@unaffiliated/mario)
23:44.54*** join/#maemo hurrian (~hurrian@unaffiliated/rikanee)

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