IRC log for #openmoko-cdevel on 20110618

00:58.02*** join/#openmoko-cdevel jluis (~jluis@111.Red-79-151-229.dynamicIP.rima-tde.net)
00:59.02*** join/#openmoko-cdevel wolfspraul (~wolfsprau@mimi.q-ag.de)
01:44.17*** join/#openmoko-cdevel floyd2 (~floyd@p508AA2C9.dip.t-dialin.net)
02:10.17*** join/#openmoko-cdevel ferluszt (~peter@p5DD28B3F.dip0.t-ipconnect.de)
02:49.07*** join/#openmoko-cdevel NuttyBunny (~cnegrete@187.152.208.138)
04:32.16*** join/#openmoko-cdevel DocScrutinizer (~halley@openmoko/engineers/joerg)
05:46.31*** join/#openmoko-cdevel wolfspraul (~wolfsprau@mimi.q-ag.de)
06:48.22*** join/#openmoko-cdevel ThibG (~ThibG@81-64-13-28.rev.numericable.fr)
06:59.04*** join/#openmoko-cdevel GarthPS (~quassel@qrc29-1-82-245-206-103.fbx.proxad.net)
07:07.18GarthPSmoin
07:19.17Lopimoin
07:19.24*** join/#openmoko-cdevel radekp (~radek@63.120.broadband10.iol.cz)
07:22.19*** join/#openmoko-cdevel ThibG (~ThibG@81-64-13-28.rev.numericable.fr)
07:36.27*** join/#openmoko-cdevel methril (~methril@189.27.135.133.dynamic.adsl.gvt.net.br)
07:40.25*** join/#openmoko-cdevel ao2 (~ao2@2001:1418:117::1)
07:44.32*** join/#openmoko-cdevel plotr (~name@m052d.studby.ntnu.no)
08:01.04*** join/#openmoko-cdevel phh (~quassel@137.194.15.151)
08:08.33*** join/#openmoko-cdevel morphis (~morphis@p5B3E6EC5.dip.t-dialin.net)
08:20.49*** join/#openmoko-cdevel ThibG (~ThibG@81-64-13-28.rev.numericable.fr)
08:46.30*** join/#openmoko-cdevel Heinervdm (~thomas@pD9E154B1.dip.t-dialin.net)
09:16.48*** join/#openmoko-cdevel morphis (~morphis@p5489B868.dip.t-dialin.net)
09:52.36*** join/#openmoko-cdevel NIN101 (~NIN101@p5DD2998F.dip0.t-ipconnect.de)
10:13.03*** join/#openmoko-cdevel GNUtoo (~GNUtoo@host148-3-dynamic.244-95-r.retail.telecomitalia.it)
10:13.38Lopigrr I hate you baseband
10:18.48GNUtooask someone
10:29.06*** join/#openmoko-cdevel dos1 (~dos@unaffiliated/dos1)
10:38.22*** join/#openmoko-cdevel daniele_athome (~daniele@ppp-45-42.25-151.libero.it)
10:45.47LopiGNUtoo: how can I test a compile of fsogsmd?
10:48.08CIA-82freesmartphone.org: 03morphis 07aurora * r7937061e0eaf 10/aurora/systemmanager/controller.vala: aurora: handle backlight power status to deactivate touchscreen
10:59.34CIA-82freesmartphone.org: 03morphis 07aurora * r1c4709a92089 10/aurora/ (configure.ac systemmanager/Makefile.am): aurora: even add libfsosystem as dependency
11:09.02PaulFertsertsting the bot
11:09.07PaulFertsers/tst/testing/
11:09.18PaulFertser~aptsnack
11:09.47GNUtooLopi, what do you mean?
11:10.18LopiGNUtoo: ehh just running into a bunch of dependency errors whilst trying to compile
11:10.58Lopihttp://pastie.org/private/92bgb2oheyq6dufrsmaw
11:11.37LopiI understand what's wrong
11:11.43GNUtoouse bitbake
11:11.45GNUtooand autorev
11:11.56GNUtooand then
11:12.04GNUtooyou can use the devshell to compile it
11:12.12Lopiyeah, but how can I test if my plugin compiles with oe?
11:12.19LopiI mean where can I put it
11:12.23GNUtooI'll precise what I said
11:12.31GNUtoobitbake fsogsmd (with autorev set )
11:12.35GNUtooand then
11:12.44GNUtoosource ~/path/to/devshell
11:12.52GNUtoocd into your fsogsmd git dir
11:12.57GNUtooand compile there
11:13.10Lopihow do you set autorev
11:13.19GNUtooin local.conf add that:
11:13.59LopiAUTOREV="yes"
11:13.59Lopi?
11:14.04GNUtoowait a sec
11:14.27GNUtoorequire conf/distro/include/fso-autorev.inc
11:14.46GNUtooif you want you can also add that:
11:14.53GNUtoorequire conf/distro/include/shr-autorev.inc
11:15.05Lopihave them both already
11:15.18GNUtoook
11:15.40Lopidoes fsogsmd end up as a package?
11:15.50GNUtoowhich one?
11:16.00GNUtoothe one you compile with the devshell?
11:16.02GNUtoono
11:16.12GNUtoobut it creates plugins for you
11:16.14GNUtoofor instance
11:16.54leviathanGNUtoo: did the phone arrive?
11:17.00GNUtoonot yet
11:17.07leviathanwell
11:17.20leviathanI can go and track it next week
11:17.27leviathanif it doesn't arrive monday
11:17.32GNUtoofsoaudiod/src/plugins/gsmvoice_alsa_cmtspeechdata/.libs/
11:17.36leviathanI've sent it with high priority
11:17.38GNUtoonote the .libs
11:17.40GNUtoook
11:18.06GNUtoothanks
11:18.18*** join/#openmoko-cdevel GNUtoo-N900 (~root@host148-3-dynamic.244-95-r.retail.telecomitalia.it)
11:18.26Lopimm
11:18.36Lopiso if it compiles, how do I test it on my device?
11:18.49GNUtoo-N900you scp it
11:18.56GNUtoo-N900the .so
11:19.09Lopiah oaky
11:19.17GNUtoo-N900opkg files fsogsmd will tell where to scp
11:19.20Lopito /usr/lib/cornucopia/modules/fsogsm/
11:19.42GNUtoo-N900yes,something like that
11:22.30Lopihttp://pastie.org/private/sifvdbwfjtsuu5qjelvezq
11:25.12GNUtoo-N900sorry. I'll go
11:31.07GarthPSmickey|daddy: hi. can I ask you a confirmation , to see If i am stupid or what.., http://git.freesmartphone.org/?p=cornucopia.git;a=blob;f=fsodeviced/src/plugins/palmpre_quirks/powercontrol.vala;h=0e620ad40ef29637a4e7817238e6133c7c721dca;hb=HEAD line 77 is out of the previous else part ?
11:32.07GarthPSas this it will fail to bring the interface up if it actually fail to load the module right ?
11:36.25mickey|daddygarthps: morphis wrote that part, I'm not sure whether loading the interface is mandatory - it could be already loaded, so i guess we should try to bring up the interface no matter whether loading the module failed or succeede
11:36.27mickey|daddyd
11:40.34GarthPSmickey|daddy: hm yeah.. what will sirloin_wifi_mod.load() return is the modul is already loaded ?
11:42.08GarthPSthen the is_active variable handling is unsufficient as it is never tested whether it is already active or not
11:43.17GarthPSplus then is it tryied to load the interface after failing to load the module then we have a crash
11:43.35GarthPS[CRITICAL] fsodeviced : GLib <fsodevice.palmpre_quirks>: file powercontrol.c: line 267: uncaught error: Could not bring interface eth0 up: No such device (fso_framework_network_error-quark, 0)
11:44.09GarthPSorg.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
11:44.16GarthPSsorry
11:44.19GarthPSroot@palmpre2 ~ # mdbus2 -s org.freesmartphone.odeviced /org/freesmartphone/Device/PowerControl/0 org.freesmartphone.Device.PowerControl.SetPower true
11:44.19GarthPSorg.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
11:44.31GarthPSroot@palmpre2 ~ # mdbus2 -s org.freesmartphone.odeviced /org/freesmartphone/Device/PowerControl/0 org.freesmartphone.Device.PowerControl.GetPower
11:44.31GarthPSorg.freedesktop.DBus.Error.UnknownMethod: Method "GetPower" with signature "" on interface "org.freesmartphone.Device.PowerControl" doesn't exist
12:00.08GarthPSSo for now I really think th ifup thing should be in the else part
12:02.09*** join/#openmoko-cdevel fsteinel (~fsteinel@fedora/fsteinel)
12:05.06*** join/#openmoko-cdevel oln (~oln@ws43177.studby.hig.no)
12:33.15*** join/#openmoko-cdevel wolfspraul (~wolfsprau@mimi.q-ag.de)
12:39.53*** join/#openmoko-cdevel valos (~valos@mar92-6-82-227-150-198.fbx.proxad.net)
12:54.47mickey|daddyGarthPS: yep. lets bring it up to morphis next time he's here
12:58.43*** join/#openmoko-cdevel playya__ (~playya@unaffiliated/playya)
13:01.22GarthPSmickey|daddy: okey
14:01.01*** join/#openmoko-cdevel ferluszt (~peter@p5DD2961D.dip0.t-ipconnect.de)
14:38.49*** join/#openmoko-cdevel GNUtoo (~GNUtoo@host148-3-dynamic.244-95-r.retail.telecomitalia.it)
14:48.47*** join/#openmoko-cdevel jluis (~jluis@2001:5c0:1400:a::87b)
15:02.33*** join/#openmoko-cdevel fsteinel (~fsteinel@fedora/fsteinel)
15:04.02*** join/#openmoko-cdevel alexxy (~alexxy@gentoo/developer/alexxy)
15:21.15*** join/#openmoko-cdevel xrmx (~rm@151.69.107.74)
15:24.05*** join/#openmoko-cdevel alexxy (~alexxy@gentoo/developer/alexxy)
15:37.15CIA-82freesmartphone.org: 03morphis 07aurora * raf98757fecab 10/aurora/systemmanager/main.vala: aurora: don't drop priviledges in system manager for now
15:41.40*** join/#openmoko-cdevel angelox (~angelo@189-18-205-179.dsl.telesp.net.br)
16:06.14CIA-82freesmartphone.org: 03morphis 07aurora * r56f2c18efa89 10/aurora/systemmanager/controller.vala: aurora: handle backlight power update before the backlight is set
16:34.35CIA-82freesmartphone.org: 03morphis 07aurora * r13ed1762ccac 10/aurora/systemmanager/controller.vala: aurora: handle power and audio mute keys in system manager
16:37.02CIA-82freesmartphone.org: 03morphis 07aurora * r5bb5b2d8ea21 10/aurora/systemmanager/controller.vala: aurora: fix syntax error from commit before
16:53.12*** join/#openmoko-cdevel Alex[sp3dev] (~alexander@86.110.163.19)
17:00.38*** join/#openmoko-cdevel wiedi (~wiedi@smoot.w.fruky.net)
17:05.50*** join/#openmoko-cdevel angelox|n900 (~user@201-95-128-37.dsl.telesp.net.br)
17:05.54*** join/#openmoko-cdevel jluis (~jluis@2001:5c0:1400:a::77)
17:17.08*** join/#openmoko-cdevel JesusMcCloud-lt (~JesusMcCl@84.119.83.234)
17:18.26*** join/#openmoko-cdevel alexxy (~alexxy@gentoo/developer/alexxy)
17:21.21*** join/#openmoko-cdevel MadTBone (~bruce@cpe-66-65-115-115.nyc.res.rr.com)
17:30.39*** join/#openmoko-cdevel alexxy (~alexxy@gentoo/developer/alexxy)
17:46.54*** join/#openmoko-cdevel angelox|n900 (~user@189-18-107-84.dsl.telesp.net.br)
18:01.15*** join/#openmoko-cdevel GNUtoo (~GNUtoo@host148-3-dynamic.244-95-r.retail.telecomitalia.it)
18:08.31*** join/#openmoko-cdevel gena2x_ (~gena@cpe-67-250-70-77.nj.res.rr.com)
18:47.25*** join/#openmoko-cdevel max_posedon (~max_posed@178.124.160.59)
19:01.09*** join/#openmoko-cdevel _ao2 (~ao2@2001:1418:117::1)
19:07.10*** join/#openmoko-cdevel ferluszt (~peter@p5DD2961D.dip0.t-ipconnect.de)
19:29.16*** join/#openmoko-cdevel dos1 (~dos@unaffiliated/dos1)
19:57.38*** join/#openmoko-cdevel angelox|n900 (~user@201-13-208-30.dial-up.telesp.net.br)
20:12.15*** join/#openmoko-cdevel GarthPS (~quassel@qrc29-1-82-245-206-103.fbx.proxad.net)
20:14.33*** join/#openmoko-cdevel angelox (~angelo@201-13-208-30.dial-up.telesp.net.br)
20:26.22angeloxGNUtoo: Hi,i'll try install u-boot,but i'm following a tutorial on "wiki.meego.com". That's secure? it shows me how to install u-boot from the phone...
20:27.37GNUtooyes it is
20:27.41GNUtoobut it may not work
20:27.48GNUtoobasically it's as secure as flashing a kernel
20:27.56GNUtoosince uboot is flashed at the kernel place
20:28.01GNUtooit's a chainloaded bootloader
20:28.07GNUtoothe original bootloader is still there
20:28.14GNUtoowhich can be coldflashed btw
20:28.45angeloxbut why it may not work?
20:33.02Alex[sp3dev]GNUtoo: which kernel do you have on n900?
20:33.59GNUtoothe meego one
20:34.12GNUtoothe n900-adaptation one
20:34.16GNUtoowe update it often
20:34.55Alex[sp3dev]GNUtoo: when you have time, enable wl1251 debugging and make a log of successful association and pings from device to router and from pc to device
20:35.16GNUtooI've something to do with Lopi right now
20:35.21GNUtoobut I'll do it right after
20:35.24GNUtooif I don't go to bed
20:50.05DocScrutinizerthe meego kernel is *cough* erhm... not optimized for N900. There are quite some bits missing of what genuine maemo kernel had for patches on top of mainline 2.6.28 that Nokia introduced to make for a proper power economic system that really works
20:50.19GNUtoocomplain to mickey|daddy
20:50.29GNUtooI fighted a lot for keeping 2.6.28
20:52.22DocScrutinizerwell, there's nothing bad really in going for [recent], but you need to take care about such things like sensor drivers, CPUfreq governor foo, whatnot - all the stuff that's been in maemo kernel and didn't make its way upstream for one reason or the other. Simply assuming meego folks will do it right is a bit over-optimistic
20:53.15DocScrutinizerbasically my notion about meego-arm (N900) folks and their approach to kernel things: they got NFC
20:53.40GNUtoomickey|daddy's reason was devtmpfs that was lacking on 2.6.28
20:54.00DocScrutinizerthey even deliberately admit they have no clue and go mere mainstream kernel, no matter what crap is or isn't there
20:55.58DocScrutinizerprominent example: LIS302 drivers - OM/OE has a proper driver, maemo has a similar proper driver, meego is using a *JOYSTICK* driver that happens to match regex >>.*lis.*3.*02.*<< and is available upstream
20:56.18DocScrutinizerthis driver _evidently_ is fubar and bullshit
20:56.48Alex[sp3dev]why don't you port the needed stuff and mainline it? unlike other devices n900 is already well supported. you have to just do the boring integration work
20:56.56DocScrutinizersame pattern of operation applies to several other topics in meego I'd think
20:56.58GNUtooLopi, it just compiled
20:57.24LopiGNUtoo: ohh nice ^^
20:57.35DocScrutinizerAlex[sp3dev]: the problem is we can't get a proper lis302 driver upstream as there's that crap already
20:58.07GNUtoohttp://gnutoo.homelinux.org/downloads/people/Lopi/plugin.vala
20:58.08DocScrutinizergetting good driver upstream would mean to nuke the shit, and nobody is going to fight that battle
20:58.15GNUtoowget it and diff it with yours
20:58.19GNUtooI commented a part tough
20:58.24GNUtoobecause the function was not present
20:58.34Alex[sp3dev]DocScrutinizer: i see. so sitting and whining is better
20:58.36GNUtoobut it's pretty small
20:58.39GNUtooit's only a check
20:58.46DocScrutinizerAlex[sp3dev]: you're free to do that
20:58.52GNUtooI also surely messed up the identation
20:58.59GNUtooalso I didn't check pointers yet
20:59.00DocScrutinizer(whining, fighting, whatever)
20:59.14GNUtoodo you also want the binary?
20:59.40Alex[sp3dev]DocScrutinizer: sure. i just don't have n900.. but at least you can keep your own tree or integrate proper stuff to meego if mainline is a no-go
20:59.48DocScrutinizerfor SHR however I strongly suggest to keep a local branch with platform adaptions that are local
21:00.07DocScrutinizerAlex[sp3dev]: exactly my suggestion
21:00.25LopiGNUtoo: yeah give me the binary
21:00.33LopiGNUtoo: I see what you changed, very minor
21:00.42DocScrutinizermeego has a policy of "mainline ONLY" so I don't care
21:01.07GNUtoolet me try to look of the & are correct
21:01.11GNUtooand then I'll do
21:01.16DocScrutinizerAlex[sp3dev]: for SHR things are 'better' and I'm sure those smart guys here will eventually do "the right thing"
21:01.21Lopiokay sounds good ty
21:02.15GNUtooah my bad the & are correct
21:02.28DocScrutinizerembedded is always about fine tuning kernel stuff to the particular platforn, so in my book meego's "mainline only" approach never will work out
21:03.37Alex[sp3dev]DocScrutinizer: the thing is that no one likes to integrate stuff. because it is tiring and takes a lot of time. and if you take a commercial company, they'll use any opportunity to reduce development costs
21:03.54GNUtoohttp://gnutoo.homelinux.org/downloads/people/Lopi/modem_singleline.so
21:04.05GNUtoonote that it may fail at runtime
21:04.11GNUtoosince you copy-pasted lot of C
21:04.14DocScrutinizerAlex[sp3dev]: sure
21:04.17Lopiokay
21:04.18GNUtooI didn't extensively check everything
21:04.25GNUtooI just tried to compile it
21:04.27Lopiwe'll see what happens
21:04.30GNUtooso you may need gdb
21:04.31Lopiat least it's a start
21:04.46GNUtooto run it
21:04.51GNUtooadd DEBUG in fsogsmd
21:04.54GNUtooconfig
21:05.01GNUtoothen do:
21:05.05DocScrutinizerAlex[sp3dev]: otoh the lis302 joysticj driver seems got introduced to mainline by uninspired unexperienced guys that were simply lazy and unaware of what problems they create for linux at large
21:05.08GNUtookillall fsogsmd;fsogsmd
21:05.15GNUtooand make your config use singleline
21:05.24GNUtoobtw I made a porting guide on SHR wiki
21:05.32Lopioh nice
21:05.34Alex[sp3dev]DocScrutinizer: i can say the same thing about everything done by android developers
21:05.39GNUtoohttp://www.shr-project.org/trac/wiki/Device%20Porting%20Guide
21:05.44GNUtooit's a beginning
21:05.47GNUtoowe must add to it
21:06.20Lopiyeah, it's definitely needed tho
21:06.34Lopithat's the biggest problem with SHR
21:06.41Lopiour docs blow
21:06.41Alex[sp3dev]DocScrutinizer: anyhoo i had a look at the kernel source of asus transformer. they ignored pdata and decided to change gpio-keys, sdio.c and other files directly. so you're lucky with n900
21:06.43DocScrutinizerAlex[sp3dev]: for SHR it basically doesn't mater *why* upstream aka meego is broken, it just needs to take the consequences and have a branch of local patches that "fix" those things
21:07.27Alex[sp3dev]DocScrutinizer: i think we both agree that code written by hardware vendors sucks and i don't want to continue this discussion
21:08.08*** join/#openmoko-cdevel fsteinel (~fsteinel@fedora/fsteinel)
21:08.09GNUtooouch ignoring pdata????
21:08.17DocScrutinizeryou're free to stop answering to my comments directed to GNUtoo
21:08.34GNUtooread it now
21:09.10GNUtooand look at meego camera
21:09.13*** part/#openmoko-cdevel fsteinel (~fsteinel@fedora/fsteinel)
21:09.15GNUtooit's not so better
21:09.20GNUtoothe image quality...hmmm
21:09.51Alex[sp3dev]DocScrutinizer: ok, sorry for that
21:11.45GNUtooso now wl1251_sdio
21:12.02DocScrutinizerGNUtoo: I think taking 2.6.28 maemo kernel and applying all the patches on top that lift it to 2.6.3x is the correct way to go. The other option was to take a plain 2.6.3x mainline and apply Nokia's patches there, but that may suck
21:12.37GNUtoothe "only" problem is that things change at a rate that is enormous
21:12.41Alex[sp3dev]GNUtoo: yeah, just make a dmesg of n900 wifi. i think it may be huge but i really need the last part of log about events received directly during pings
21:12.47GNUtoos/enormous/very very very fast
21:12.51DocScrutinizeras you don't get the point what a particular nokia patch is meant to do, once it throws errors when applying it to 2.6.3x
21:13.53GNUtooAlex[sp3dev], n900 is wl1251_spi
21:14.16GNUtooand cleaning 2.6.28 takes a lot of time
21:14.25GNUtoo*2.6.28 patches
21:14.42DocScrutinizerGNUtoo: you're aware there's been quite some problems around wl1251 in maemo, and Nokia did some 'tricks' to make it behave?
21:14.50Alex[sp3dev]GNUtoo: i know it. i just want the logs of the events because i think tx part may be broken although i have no idea why it may work for n900 but not for our devices
21:14.55GNUtooand I have huge issues with nervousness right now......
21:15.09GNUtooDocScrutinizer, uhhh no
21:15.28GNUtooAlex[sp3dev], I'll compile for dream
21:16.03GNUtooin some minutes
21:16.11Alex[sp3dev]GNUtoo: well, if it works there, then ok. but my device is almost the same like dream so i think you can face the same problems unless you use older code
21:16.28DocScrutinizerGNUtoo: one issue I know of is the chip's eating power like mad if not associated, even when "switched off". You need to unload the driver aka kernel module
21:17.29DocScrutinizerthere have been other wicked screwed problems iirc
21:18.03Alex[sp3dev]GNUtoo: btw with the latest mainline wl1251 i can only scan with a dedicated irq. it won't work without it.
21:18.41DocScrutinizerGNUtoo: then there's been that mysterious chan6-only issue
21:19.20DocScrutinizerI never wraped my head around it
21:19.32DocScrutinizerjust saying "watch out!"
21:22.41DocScrutinizersome really smart guy RE'd and improved the driver and "published" a way better implementation that also supports injection, monitoring and whatnot, but somehow breaks some API bits a little
21:23.24DocScrutinizerhe asked for a donation of >=0ct for shipping the source, which is fine but caused lots of flames
21:23.56Alex[sp3dev]DocScrutinizer: unfortunately for me and GNUtoo on msm phones wl1251 doesn't work at all with power saving and doesn't always work on my device even without it
21:24.31DocScrutinizerAlex[sp3dev]: I can't comment on msm phones, never had a look at thiose
21:25.12Alex[sp3dev]DocScrutinizer: they're using sdio inteface, not spi. so maybe all the problems come from the way irqs are handled
21:33.58DocScrutinizerAlex[sp3dev]: quite possible. Ask wpwrak about it, he did "a master thesis" about the very topic
21:34.48DocScrutinizeron ar6000 though, but in the end it's been spi vs sdio IIRC
21:35.14Alex[sp3dev]ok, will do later. now i need to prepare for the exams. and after exams i'll need to analyze GNUtoo's dump first
21:35.21DocScrutinizerwpwrak: any comments? ^^^
21:37.40DocScrutinizerI hope msm is using hardmac? as with softmac you're running into trouble you never get behind you, on embedded
21:38.13LopiGNUtoo: I'm done with this for the day, but I made a lot of progress today
21:38.16DocScrutinizer(excuse my ignorance if wl1251 maybe has no hard- or softMAC
21:38.18DocScrutinizer)
21:40.54GNUtooDocScrutinizer, I think it's a softmac
21:41.01GNUtoobut it has some power saving features
21:41.04GNUtooand it's pretty good
21:41.07DocScrutinizerOUCH
21:41.18GNUtooit's an exception
21:41.59DocScrutinizeryou're aware what softmac is. So you know your system standby will suck on WLAN with softmac
21:42.47GNUtoook
21:42.54DocScrutinizerwaking main CPU for each random WLAN inbound pkg is for sure not helpful to get things working and saving power
21:43.12GNUtooit has PSM tough
21:43.21GNUtoobut on msm I never got it working
21:43.23DocScrutinizers/inbound pkg/random signal/
21:43.35GNUtooaltough with the android driver it works
21:43.45angeloxGNUtoo: do you know some link of a rootfs(and a kernel) to i test SHR quickly here on my N900?
21:43.50Alex[sp3dev]whatever, but the whole system with backlight, gsm and stuff takes the same amount of power as wl1251 alone without psm
21:44.14GNUtooangelox, hi, go on SHR download page, download an n900 rootfs extract it on microsd
21:44.24GNUtooangelox, did you flash uboot yet
21:44.25GNUtoo?
21:45.02angeloxi used that tutorial from meego,working uboot here already.
21:45.13GNUtoook
21:45.16GNUtoois it flashed?
21:45.32DocScrutinizerAlex[sp3dev]: yes, PSM is about suspending the RX for arbitrary durations as advised by AP, and wake it up just in time via a hw alarm clock. This probably can't be done in softmac at all
21:45.55GNUtoowl1251_sdio has psm
21:46.00GNUtooit works on the pandora
21:46.09DocScrutinizerAlex[sp3dev]: and wl1251 is known to suck power for RX
21:46.10GNUtooit also works on the ti driver
21:46.20Alex[sp3dev]GNUtoo: it even works in winmo
21:46.55angeloxGNUtoo: i really don't know,how it makes uboot work here.i don't know if it self-flashed by installing the uboot-pr13(i don't think so)
21:47.17GNUtooangelox, what do you get at boot?
21:47.22DocScrutinizeran additional problem is al lot of AP don't implement PSM correctly, so your PSM may fail despite you did everything 100% correct
21:47.36GNUtooyes
21:47.42GNUtoobut I have hostapd
21:48.13GNUtooand my laptop has that:
21:48.15GNUtoo<PROTECTED>
21:48.23DocScrutinizerhard to tackle that whole topic, without $$$k equipment to analyze OTA
21:48.34GNUtoowould an USRP help?
21:48.38angeloxGNUtoo: i get uboot menu,and i can choose for a lot of options,there's also mmc boot option...so i think that it's working
21:48.40DocScrutinizersure :-D
21:49.13GNUtoobecause I suspect that the problem is not on the wireless transmit/receive, but rather on the kenrel code and with the IRQ handling
21:49.21GNUtooangelox, ok
21:49.35DocScrutinizerGNUtoo: quite possible
21:49.45GNUtooangelox, boot maemo with it for now
21:49.50GNUtooangelox, give me some minutes
21:49.52DocScrutinizerfor softmac to work you need "realtime!"
21:50.01GNUtooI've to compile wl1251_sdio
21:50.01angeloxGNUtoo: ok,thank you.
21:50.15GNUtooI hope I don't go to bed before helping you
21:50.18GNUtoobut big warning
21:50.24GNUtoodon't stay too long in uboot
21:50.26DocScrutinizeras *all* is about timing in PSM
21:50.29GNUtooelse the battery discahrges
21:50.41GNUtooand the battery charging is an userspace program
21:50.51GNUtooso you have to be able to boot to charge it usually
21:50.55GNUtoothe details is
21:51.05GNUtoothat the bootloader has an emergency charge
21:51.12GNUtoo(not uboot but the one under it)
21:51.20GNUtooso it can charge it enough just to make you boot
21:51.28DocScrutinizernot really
21:51.36DocScrutinizerbut doesn't matter ;-)
21:51.44Alex[sp3dev]DocScrutinizer: which pretty much explains why it only works with a dedicated irq. sdio interrupts are too slow for it
21:52.05DocScrutinizerAlex[sp3dev]: yes, sounds like a story
21:52.29GNUtooDocScrutinizer, what are the real details?
21:52.34angeloxGNUtoo: hmm ok,thank you,i booted maemo by writing on uboot "run noloboot".
21:52.46DocScrutinizerAlex[sp3dev]: depending on your kernel you also got IRQ servicing latencies...
21:53.04DocScrutinizerGNUtoo: actually the chip does the emergency charging
21:53.09GNUtooah ok
21:53.17GNUtoobut the bootloader triggers it
21:53.19GNUtoo?
21:53.22DocScrutinizernope
21:53.23GNUtoolike trough i2c
21:53.25GNUtooah ok
21:53.45DocScrutinizerGNUtoo: look, if BL got loaded, the *hw* already 'booted'
21:54.18DocScrutinizerloading, BL, loading kernel. No diff for the hw
21:55.04angeloxliked his N900 and don't want to brick it :)
21:55.06DocScrutinizerbut the NOLO BL decides to immediately boot to kernel for further charging, and not allow flashing, if battery is too low
21:55.18DocScrutinizerangelox: you can't brick N900
21:55.38DocScrutinizerwell, it's at least incredibly hard to do
21:55.39GNUtooangelox, indeed you can even reflash the bootloader trough usb
21:55.42GNUtooI even did it
21:55.46*** join/#openmoko-cdevel NIN101 (~NIN101@p5DD2998F.dip0.t-ipconnect.de)
21:56.05wpwrakDocScrutinizer: sdio interrupts eating power ? in general, they shouldn't. some mmc/sd/sdio host drivers use polling instead of real interrupts, so that would eat a bit more power.
21:56.13DocScrutinizerworst thing to do is nuke CAL with all the device specific data like serial# etc
21:56.48DocScrutinizerwpwrak: softmac eating power, compared to hardmac. That's my point
21:57.26GNUtoo/dev/mtd1 then
21:57.27DocScrutinizeralso softmac is a bitch do get right, regarding strict timing of PSM
21:58.01DocScrutinizerGNUtoo: indeed. No reports on how to recover from that
21:58.16DocScrutinizermaybe it's irrelevant
21:58.19DocScrutinizermaybe not
21:58.26GNUtoomaybe reflashing a PR 1.3?
21:58.31DocScrutinizernobody tested it, for obvious reasons ;-P
21:58.51GNUtoolol
21:58.52DocScrutinizerflashing doesn't usually touch CAL
21:58.57wpwrakDocScrutinizer: you'd notice the biggest difference if you do things like wake-on-wlan. because softmac needs the cpu for that. so if the cpu isn't good at dealing with many short wakeups, then you have a problem.
21:58.58angeloxif i flashed uboot,there's somehow to recover my warranty,or i didn't lose it yet?
21:58.59GNUtooah ok
21:59.03DocScrutinizerexcept for SW version etc
21:59.17DocScrutinizerangelox: irelevant
21:59.24GNUtoowpwrak, there is a GPIO IRQ for PSM
21:59.37GNUtooMSM_GPIO_TO_INT(29) if I remember well
21:59.38DocScrutinizerangelox: you don't lose warranty by flashing kernel
22:00.13angeloxthis is good...
22:00.18DocScrutinizeryou have no warranty though on a working system with non-standard kernels :-P
22:00.41DocScrutinizerand flashing back to standard isn't covered by warranty
22:01.28DocScrutinizerso if you thoroughly screwed things, you better don't tell you messed with alterative kernels/OS ;-)
22:01.53DocScrutinizerotherwise they will charge you for restoring stock image
22:02.39DocScrutinizerthough honestly you should be capable of doing that at home, if you dare to mess with alternatives ;-)
22:02.59DocScrutinizeragain, you can't really brick N900
22:03.10GNUtooangelox, also beware with waranties, if you send it for repair you may get a N8 instead
22:03.15GNUtoo*get a N8 back
22:03.23DocScrutinizerjust recovering gets harder still, if you mess up "better"
22:03.54GNUtoocoldflashing is not hard, but it require to use flasher, which is proprietary
22:04.10DocScrutinizerflasher is all you usually need to recover from whatever "bricking" might have happpened
22:04.15GNUtoocoldflash->flashing eMMC+NAND
22:04.20GNUtooand you can recover
22:04.27DocScrutinizeryup
22:05.09DocScrutinizerCPU has a minimalistic USB bootloader that can't get nuked, so you can recover from all possible mess you might have caused
22:05.31angeloxok,i was afraid about brick it...thanks for explanation... about OS/Kernel/NAND/eMMC/Bootloader so we have no problems if "brick" it...
22:05.37GNUtooanother way to brick it is to overclock it
22:05.40GNUtoodon't overclock
22:06.19DocScrutinizerthat's not "bricking" that's deliberately cooking hw to death
22:06.40angeloxand if i brick some physical part of it? (for example,my touch stop working)
22:07.10DocScrutinizeryou have several ways to do that, not all need sw tweaks: attach 50V~ charger for example
22:08.14DocScrutinizerangelox: if your ts stops working, the you either got a crappy driver and need to flash stock OS and kernel, or you killed the hw and nobody can help -> try to get warranty repair
22:08.49DocScrutinizerflasher won't glue broken hw parts
22:09.00angeloxyes :)
22:09.11DocScrutinizerand while sw can't kill touchpanel, a nail or knife can
22:09.29DocScrutinizerplease use common sense
22:10.19GNUtoosoftware can brick it that way:
22:10.23GNUtootouchscreen not working
22:10.26GNUtoobecause of software
22:10.32GNUtooand user touching more hard
22:10.35GNUtoo*harder
22:10.37angeloxi was talking about,if i flashed my phone and it starts with a lot of logs and i brick my ts and i send to warranty..what'll they say? that isn't on warranty by changed sw?
22:10.39GNUtoowhich may damage it
22:10.43GNUtoodepending on the device
22:11.17DocScrutinizerangelox: nope
22:11.32DocScrutinizerangelox: first thing they do: reflash to known good stock OS
22:11.44DocScrutinizerangelox: then check if hw still acts up
22:12.15DocScrutinizerangelox: then if it's not evidently a OC caused CPU fry-out, they just will fix/replace
22:12.52angeloxah,ok,so i understood now,because i didn't know how they proceed to fix a phone problem
22:14.13DocScrutinizerangelox: and really, that's what you should do as well, prior to trying to go for warranty repair
22:14.47DocScrutinizerbecause if they find it's been a mere sw issue, they *might* decide to charge you for fixing your system sw
22:15.29DocScrutinizerand I'm all with them for ding so
22:15.34DocScrutinizerdoing*
22:16.12GNUtooAlex[sp3dev], now that I have my system setup
22:16.16GNUtoowhat logs do you want?
22:16.28GNUtooI can ping the router
22:17.11DocScrutinizerangelox: btw recently nokia repair sends out crappy N8 for replacement of nice maemo-based N900, as they don't have spare N900 anymore
22:17.22GNUtoo[  339.542022] wl1251: ERROR elp wakeup timeout // when I iwconfig wlan0 power on
22:17.26DocScrutinizer:-/
22:17.31Alex[sp3dev]GNUtoo: yeah, i think you can enable DEBUG_IRQ, DEBUG_MAILBOX, DEBUG_EVENT, DEBUG_TX, DEBUG_RX
22:17.41GNUtoook
22:18.32Alex[sp3dev]GNUtoo: then do it without ELP. i need the logs of it receiving events and doing tx. basically i think it fails with unaligned data and the code handling it might be inaccurate although it is 'fixed' by some patch already
22:18.45angeloxDocScrutinizer: Hmm,i see,since i have bought my N900 a day before yesterday,they should have some at there :)  (i hope,but i don't want brick it soon :D )
22:19.13Alex[sp3dev]GNUtoo: so is the compat-wireless on gitorious the one you're using?
22:19.13DocScrutinizeryour dealer may still have N900, but Nokia repair don't
22:19.15GNUtoobtw I used theses branches:
22:19.44GNUtoomaster branch of git://gitorious.org/htc-msm-2-6-32/compat-wireless.git
22:19.46angeloxDocScrutinizer: yes...
22:20.06GNUtooremotes/htc-msm/android-msm-2.6.32-rebase+needs_compat_wireless+wifi-irq of the leviathan kernel
22:21.01DocScrutinizer(nokia repair don't) which is an incredible fail, as manufacturers are supposed to keep spare parts for years after EOL of product
22:21.35angeloxas it is a great phone too
22:21.52DocScrutinizerand I really hope this has been a PEBKAC at service line of NOKIA, as otherwise the shall get sued to the ground
22:22.54*** join/#openmoko-cdevel angelox|n900 (~user@201-13-208-30.dial-up.telesp.net.br)
22:23.04GNUtooELOP == EOLP(end of life products)
22:23.09DocScrutinizeryou CAN NOT replace a linux device with a sybian based one, no matter how many more pixels the cam has
22:24.03DocScrutinizerhmm
22:24.05DocScrutinizer~elop
22:24.15DocScrutinizeramazing
22:24.30DocScrutinizer~tepco
22:24.31apt'tepco' (1 of 2): sth especially stupid or messed up; "this construction is completely tepco"; "please stop behaving tepco"
22:24.46angelox|n900dont know what do you think,but they also doesnt know that maemo is much more better than symbian one
22:25.27Alex[sp3dev]apt: ELOP is a microsoft spy and one of the most successfull corporate trolls
22:25.28aptokay, Alex[sp3dev]
22:25.45DocScrutinizerthey switched to meego, then found this is a dead end adventure...
22:25.50angeloxi think maemo 10x better than symbian for a phone/tablet device
22:26.02DocScrutinizerAlex[sp3dev]: thanks :-)
22:27.09angeloxor meego too...great OS..
22:27.40GNUtoohttp://gnutoo.homelinux.org/downloads/people/Alex%5bsp3dev%5d/association.lzma
22:27.47DocScrutinizerwell, as mentioned above, meego-arm still has not the maturity of maemo
22:28.16Alex[sp3dev]GNUtoo: thanks, downloaded.
22:28.50GNUtoolzcat it
22:28.59DocScrutinizercurses space-bar of laptop started to grate
22:29.02GNUtoobasically I had connman running
22:29.05Alex[sp3dev]GNUtoo: luckily i know what lzma is
22:29.06GNUtooso I killed it
22:29.25GNUtooyes but I just discovered lzcat
22:29.47*** join/#openmoko-cdevel valos (~valos@mar92-6-82-227-150-198.fbx.proxad.net)
22:29.54GNUtoobecause there is bzcat zcat etc...so I tought maybe there is a lzcat
22:30.09DocScrutinizer*cough*
22:30.31GNUtooso I was saying:
22:30.41GNUtooI had connmand running and I killed it
22:30.47GNUtoothen I retried to associatae
22:30.49GNUtooit worked
22:31.25Alex[sp3dev]ok, i'll reboot my pda into linux and try myself
22:31.51GNUtoo[  388.391754] wlan0: associated
22:31.54GNUtooanyway that should tell
22:32.17Alex[sp3dev]i can associate but my connection dies if i open browser or ping the device from another one
22:32.31GNUtoois the log enough?
22:34.37Alex[sp3dev]looks like yes
22:37.06DocScrutinizerAlex[sp3dev]: sounds like dhcp problems
22:37.30DocScrutinizeror re-authentication problems
22:37.42Alex[sp3dev]DocScrutinizer: no it does not. i don't use dhcp at all. but i got the log so i can compare
22:38.06DocScrutinizercheck wpa-supplicant, try open wlan
22:38.27GNUtooconnmand can block dhcp
22:38.34GNUtoobut I guess he got kernel issues
22:38.44DocScrutinizerhmm :shrug:
22:38.49Alex[sp3dev]maybe supplicant config needs to be tweaked though
22:39.17GNUtoosince I guess some stuff appeared in dmesg
22:39.28Alex[sp3dev]GNUtoo: i can upload my log if you want
22:39.35GNUtooyes good idea
22:39.37DocScrutinizerwhen wpa-supplicant purges credetials and doesn't re-authenticate, it may look like "associated, but connection stalls/drops as soon as it gets used"
22:40.09GNUtooAlex[sp3dev], I've open wifi btw
22:40.14GNUtoonot encrypted
22:40.20DocScrutinizers/purges/keeps/
22:40.22Alex[sp3dev]DocScrutinizer: very likely. if some pings are successful it is likely that supplicant is to blame
22:40.36Alex[sp3dev]GNUtoo: i have open wifi at the university and it didn't work there either
22:40.42GNUtoook
22:41.47DocScrutinizerhmmm
22:41.53Alex[sp3dev]GNUtoo: http://pastebin.com/CV9s4LTz
22:42.01*** join/#openmoko-cdevel alexxy (~alexxy@gentoo/developer/alexxy)
22:43.04DocScrutinizerhow are IP addresses associated to connection when there's no dhcp running/used?
22:43.22Alex[sp3dev]DocScrutinizer: well, actually i tried with both dhcp and manually setting address
22:44.40DocScrutinizerif your interface is missing proper address (in ifconfig list) and defalt route to AP, then your connection looks 'associated' but can't work
22:45.02GNUtoothe advantage the my compat wireless driver I put online is that one:
22:45.04GNUtooMode:Ad-Hoc
22:45.28GNUtooso tethering,batmand and friends etc... could work
22:45.58Alex[sp3dev]DocScrutinizer: please, i'm not that naive. of course i have verified it. my situation is. i start wifi. get address via dhcp or manually. ping the router from the phone - works. ping the phone from the laptop - stops working. also stops working if i open browser and try any url, even router's address
22:45.59DocScrutinizeryou're aware ad-hoc is incompatible with PSM
22:46.06GNUtooyes of course
22:46.23GNUtoobut batmand is to call only for emergency cases.....
22:46.52DocScrutinizerAlex[sp3dev]: ok, bye then
22:48.19Alex[sp3dev]GNUtoo: could you please show the options in your supplicant config?
22:48.35GNUtoonone
22:48.37GNUtooI do that
22:48.39GNUtoo*did
22:48.42GNUtooifconfig wlan0 up
22:48.45GNUtooiwconfig wlan0 router
22:48.48GNUtooudhcpc -i wlan0
22:49.16GNUtooI can make a new AP and try if you want
22:49.20GNUtoobut maybe not right now
22:49.28*** join/#openmoko-cdevel alexxy (~alexxy@gentoo/developer/alexxy)
22:49.31GNUtooI've added AP support for my bug devices
22:49.42GNUtoo(it was very easy, just rebase the patches)
22:49.52GNUtoos/the/some/
22:52.15GNUtooAlex[sp3dev], btw in which country are you?
22:52.25Alex[sp3dev]GNUtoo: in Russia
22:52.30GNUtooah ok that's far
22:52.40GNUtoobecause I've two htcdreams
22:52.43Alex[sp3dev]yeah, most likely i won't be able to use your AP
22:53.20GNUtooit was rather for sending you an htcdream to help you, and you would fix the wifi on it while beeing at it
22:53.40Alex[sp3dev]that's a bribe
22:53.50GNUtoosomething like that
22:54.05GNUtoobut I guess customs are problematic there
22:54.51Alex[sp3dev]well i guess if i fix wifi here it will work on dream. and i also wonder why ADSP doesn't respond when running from nand.. honestly don't want to disassemble the whole winmo sound driver
22:55.15GNUtooah?
22:55.29GNUtooMaybe wrong nand partitioning(blind guess)
22:55.33Alex[sp3dev]GNUtoo: with LK bootloader we can now boot from nand on kovsky but sound won't work
22:55.42GNUtoook
22:55.47GNUtoois there LK for htcdream?
22:55.53Alex[sp3dev]on rhodium [acl] even made a full nand rom and it works but they have different AMSS
22:55.57GNUtoosince LK has sources that interesses me
22:56.11Alex[sp3dev]GNUtoo: you can port but i don't think you need it, you have recovery and native bootloader
22:56.13GNUtooah ok...sigh with different AMSSes
22:56.36GNUtooyes, but I guess soldering for the jtag is hard on that device
22:56.44GNUtooso I won't port it
22:56.54Alex[sp3dev]why would you need jtag? jtag is cheating
22:57.09GNUtoolikes jtag, serial etc....
22:57.23Alex[sp3dev]we just chain load it. we make a wrapper around LK that makes it look like wince image and is accepted by windows bootloader
22:57.23GNUtoohas some nervousness problems and having the right tools is so great
22:57.32GNUtooah ok
22:58.13GNUtootought of replacing totally fastboot with a free bootloader but:
22:58.16GNUtoo*that's risky
22:58.28GNUtoo*no one did it yet and I've no time to work on it
22:58.42GNUtoo* no way to get jtag easily
22:58.58Alex[sp3dev]well. it was done once for ipaq 4700 but it was done by paid developers with jtag who had documentation from hp. ahum
22:59.09GNUtoook
23:05.14angeloxGNUtoo: it's possible run shr using bootmenu-n900 on n900 instead uboot?
23:06.27GNUtooangelox, I guess you need to flash shr's uboot
23:06.42GNUtooah sorry
23:06.45GNUtooI misunderstood
23:06.48GNUtooI read too fast
23:06.52GNUtoonot currently
23:06.57GNUtoolong time ago it was possible
23:07.06GNUtoowe have two dual-boot solutions:
23:07.11GNUtoo* SHR's uboot
23:07.28GNUtooI guess that one is broken currently(wrong /dev/mmcblk)
23:07.43GNUtooif you find the right uboot for it it'll work
23:07.46GNUtoomrmoku|italy, is not there
23:07.53GNUtoohe knew that stuff
23:07.59GNUtooalong with JaMa
23:08.07GNUtooboth are away for a long period
23:08.09Alex[sp3dev]GNUtoo: ok. i'm fairly sure wpa_supplicant is buggy now. and my power routine needs to be changed - does not survive and ifconfig down/up. although if i enable psm, writes and reads to/from elp are ok. if i ping from the laptop, i get events and i can scan for networks
23:08.32GNUtooelse I can give you something for kexecboot
23:08.52GNUtoook, wow
23:09.09GNUtoowhere is your source for read/write elp?
23:09.11Alex[sp3dev]GNUtoo: does that look ok http://pastebin.com/A4tHzbCy?
23:09.21angeloxGNUtoo: 'couse i wouldn't like ever time i boot the phone i need see uboot...
23:09.23angeloxs/couse/cause/
23:09.42GNUtooAlex[sp3dev], at first sight that looks ok
23:09.58GNUtooangelox, then there is kexecboot
23:10.02GNUtooit can dual boot
23:10.05GNUtoobut it add one minute
23:10.09GNUtooto the boot time
23:10.17GNUtoobasically you select SHR on the menu
23:10.22GNUtoothe screen becomes black
23:10.30GNUtooduring one minute
23:10.35GNUtooand finally X start
23:10.39angeloxeven to boot maemo?
23:10.45GNUtoono
23:10.51GNUtoomaemo is faster to boot
23:10.52Alex[sp3dev]GNUtoo: there we go https://gitorious.org/~ast/linux-on-qualcomm-s-msm/alex-linux-xperia/commit/61a60bba9cdb48fef326d713b2a94c988c23a568
23:10.58GNUtoobut you need the power kenrel
23:11.05GNUtooelse you can't dual-boot it
23:11.10GNUtooI've documented it here:
23:11.28GNUtoohttp://www.shr-project.org/trac/wiki/Devices/NokiaN900/Booting
23:11.50Alex[sp3dev]GNUtoo: i stole that from 2.6.39 and hacked (added || card->sdio_funcs == 1) condition). that got me rid of -83 errors with CCCR_INTx
23:12.09GNUtoook nice
23:12.23Alex[sp3dev]GNUtoo: iirc that was your only problem, right?
23:12.33angeloxGNUtoo: great,easy installation...let me try it
23:13.16angeloxbut..when i boot the phone after installed it,it'll show me something or go direct to maemo?
23:13.48GNUtooAlex[sp3dev], yes
23:14.03GNUtooangelox, it gives a menu
23:14.08GNUtooa pretty menu
23:14.15GNUtoobut it add 1 minute to SHR boot time
23:14.23GNUtooand it require you to follow a guide
23:14.31GNUtoofor preparing maemo for beeing kexec-booted
23:15.04Alex[sp3dev]GNUtoo: and this one https://gitorious.org/~ast/linux-on-qualcomm-s-msm/alex-linux-xperia/commit/e3634792a8d4dc1a6ece286f35c0ca4b94edf146
23:15.09Alex[sp3dev]to actually enable that code
23:15.33angeloxso only the shr-project.org/trac/wiki/Devices/NokiaN900/Booting how-to doesn't work only to boot maemo atm?
23:16.40DocScrutinizerGNUtoo: kexecboot, is that like kexec? and if yes, how comes everybody says kexec doesn't work on maemo?
23:16.54GNUtooDocScrutinizer, it doesn't work with the normal kernel
23:17.00GNUtooit works with the power kernel
23:17.01DocScrutinizer:nod:
23:17.27DocScrutinizerangelox: what's wrong with uboot?
23:17.28GNUtooso it forces people to use the power kernel
23:18.08DocScrutinizerangelox: I think uboot is a clean nice solution, and adds only like max 5s to boot time
23:18.27angeloxDocScrutinizer: i need ever when i'll boot maemo type "run noloboot" on it
23:18.47DocScrutinizerthat's a definitely broken uboot config then
23:19.10Alex[sp3dev]GNUtoo: sorry for asking again but what kernel are you using?
23:19.16DocScrutinizermy uboot here boots maemo automatically after timeout of the ~3s to catch any keypress
23:20.16angeloxmy one too,but i got some *memory i guess* problems,since the gui goes crazy when i press 'power' button when i leave it boot maemo automatically
23:20.28DocScrutinizerthe particularly fubar thing with uBoot n900 flavour is the missing env storage and edit methods
23:21.21GNUtooAlex[sp3dev], leviathan-incommig
23:21.24GNUtoofrom htc-msm
23:21.31GNUtooI gave the branch not so long ago
23:21.47DocScrutinizerhmm, can't comment on that, as my setip here is PK-uboot with a massively tweaked PR1.2 based system
23:22.08angeloxthere's some uboot cfg file to i read it?
23:22.12DocScrutinizernever had any such problems though with it
23:22.14GNUtooDocScrutinizer, there is the possibility to do some boot.cfg
23:22.28DocScrutinizerindeed?
23:22.30DocScrutinizernice
23:22.37angeloxnever used u-boot since today
23:22.42GNUtoonot sure if it works well tough
23:22.51GNUtooyou may have to run a command for that
23:23.16DocScrutinizerI doubt any cmd will help, as uboot lives in kernel NAND partition
23:23.27*** join/#openmoko-cdevel jeepingben (~jeepingbe@h69-131-52-12.swisme.dsl.dynamic.tds.net)
23:23.29DocScrutinizereither it accesses this file directly, or never cares
23:24.32DocScrutinizerI thought the parameters from any such config file get compiled into uBoot
23:24.41Alex[sp3dev]GNUtoo: i take it you never disable wifi power at all?
23:25.11GNUtooAlex[sp3dev], ?
23:25.22DocScrutinizerwhich would be hard to establish anyway (disable wifi power)
23:25.38Alex[sp3dev]GNUtoo: with msm-wifi looks like you can only disable it by rmmod msm_wifi
23:25.48GNUtooyes
23:25.59GNUtoowe should use runtime-pm API
23:26.01Alex[sp3dev]then it is the reason of my problems
23:26.05GNUtoobut I've an old kernel
23:26.10GNUtoowhat problems?
23:26.10Alex[sp3dev]i've put power code into mmc vdd switch
23:26.24GNUtoook
23:26.29GNUtooI've issues too with elp
23:27.39Alex[sp3dev]i wonder what the proper way to do it all is. looks like a circular dependency. we need to have the code in mmc vdd to make the card recognize but we don't need it there if we don't want it to die after ifconfig down
23:27.58GNUtooah I had that too
23:28.14GNUtoormmod msm_wifi froze the phone
23:28.26Alex[sp3dev]well. i hate modules
23:28.40Alex[sp3dev]i just want to control power via ifconfig or rfkill without hacks
23:28.56GNUtoothen learn about the runtime PM API
23:29.07Alex[sp3dev]i will
23:30.27GNUtoo[  248.182495] wl1251: ERROR elp wakeup timeout
23:30.33GNUtooI added your 2 patches
23:30.36Alex[sp3dev]that's not ok
23:30.57Alex[sp3dev]i have another little change but don't think it is relevant at all
23:31.30GNUtoo[  324.482360] wl1251: ERROR sdio read failed (-110)
23:31.46Alex[sp3dev]strange
23:32.19GNUtooI'll remove runtime PM
23:34.50*** join/#openmoko-cdevel angelox|n900 (~user@201-13-208-30.dial-up.telesp.net.br)
23:38.39Alex[sp3dev]GNUtoo: ok, see you later. will fix wifi after the exams
23:38.45GNUtoook
23:38.47*** part/#openmoko-cdevel Alex[sp3dev] (~alexander@86.110.163.19)
23:38.47GNUtoothanks
23:41.15angelox|laptopdevice not booting.... bad
23:42.00GNUtoobut it boots maemo
23:42.07angelox|laptop<PROTECTED>
23:42.17angelox|laptopjust reboot the device....
23:42.27GNUtoowhat did you do?
23:42.37angelox|laptopnothing,just restarted the phone...
23:42.51angelox|laptopremoved the battery and put it again worked...why this is happening??
23:42.55GNUtooyou forgot to do noloboot
23:43.06angelox|laptopi did,got the same
23:43.14GNUtooretry then
23:43.20GNUtooit worked some minutes ago
23:43.41angelox|laptopworking maemo now,should i reboot to check if it is running fine?
23:43.56GNUtoo?
23:44.08angelox|laptopi mean,about uboot,i think it's with some problem
23:44.16GNUtooyes it has some issues
23:44.20GNUtooat least for booting SHR
23:45.11angelox|laptophmm,i think i'll remove u-boot and only install it when i really need use it...
23:45.42GNUtooyes
23:45.46GNUtoolet's see that later
23:46.33angelox|laptopyes,let me enjoy my new linux device before hack it :)
23:47.15*** part/#openmoko-cdevel jeepingben (~jeepingbe@h69-131-52-12.swisme.dsl.dynamic.tds.net)
23:49.10GNUtoook

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