**** BEGIN LOGGING AT Sat Jun 18 02:59:56 2011 Jun 18 07:08:55 moin Jun 18 07:20:54 moin Jun 18 10:15:16 grr I hate you baseband Jun 18 10:20:26 ask someone Jun 18 10:47:25 GNUtoo: how can I test a compile of fsogsmd? Jun 18 10:49:46 freesmartphone.org: 03morphis 07aurora * r7937061e0eaf 10/aurora/systemmanager/controller.vala: aurora: handle backlight power status to deactivate touchscreen Jun 18 11:01:13 freesmartphone.org: 03morphis 07aurora * r1c4709a92089 10/aurora/ (configure.ac systemmanager/Makefile.am): aurora: even add libfsosystem as dependency Jun 18 11:10:40 tsting the bot Jun 18 11:10:45 s/tst/testing/ Jun 18 11:10:46 PaulFertser meant: testinging the bot Jun 18 11:10:56 ~aptsnack Jun 18 11:11:25 Lopi, what do you mean? Jun 18 11:11:57 GNUtoo: ehh just running into a bunch of dependency errors whilst trying to compile Jun 18 11:12:37 http://pastie.org/private/92bgb2oheyq6dufrsmaw Jun 18 11:13:16 I understand what's wrong Jun 18 11:13:21 use bitbake Jun 18 11:13:23 and autorev Jun 18 11:13:34 and then Jun 18 11:13:42 you can use the devshell to compile it Jun 18 11:13:50 yeah, but how can I test if my plugin compiles with oe? Jun 18 11:13:58 I mean where can I put it Jun 18 11:14:02 I'll precise what I said Jun 18 11:14:10 bitbake fsogsmd (with autorev set ) Jun 18 11:14:14 and then Jun 18 11:14:22 source ~/path/to/devshell Jun 18 11:14:31 cd into your fsogsmd git dir Jun 18 11:14:36 and compile there Jun 18 11:14:49 how do you set autorev Jun 18 11:14:57 in local.conf add that: Jun 18 11:15:37 AUTOREV="yes" Jun 18 11:15:38 ? Jun 18 11:15:43 wait a sec Jun 18 11:16:05 require conf/distro/include/fso-autorev.inc Jun 18 11:16:24 if you want you can also add that: Jun 18 11:16:31 require conf/distro/include/shr-autorev.inc Jun 18 11:16:44 have them both already Jun 18 11:16:57 ok Jun 18 11:17:18 does fsogsmd end up as a package? Jun 18 11:17:28 which one? Jun 18 11:17:39 the one you compile with the devshell? Jun 18 11:17:40 no Jun 18 11:17:51 but it creates plugins for you Jun 18 11:17:53 for instance Jun 18 11:18:32 GNUtoo: did the phone arrive? Jun 18 11:18:39 not yet Jun 18 11:18:46 well Jun 18 11:18:58 I can go and track it next week Jun 18 11:19:06 if it doesn't arrive monday Jun 18 11:19:10 fsoaudiod/src/plugins/gsmvoice_alsa_cmtspeechdata/.libs/ Jun 18 11:19:15 I've sent it with high priority Jun 18 11:19:17 note the .libs Jun 18 11:19:18 ok Jun 18 11:19:44 thanks Jun 18 11:20:04 mm Jun 18 11:20:14 so if it compiles, how do I test it on my device? Jun 18 11:20:28 you scp it Jun 18 11:20:34 the .so Jun 18 11:20:47 ah oaky Jun 18 11:20:55 opkg files fsogsmd will tell where to scp Jun 18 11:20:59 to /usr/lib/cornucopia/modules/fsogsm/ Jun 18 11:21:20 yes,something like that Jun 18 11:24:09 http://pastie.org/private/sifvdbwfjtsuu5qjelvezq Jun 18 11:26:50 sorry. I'll go Jun 18 11:32:46 mickey|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 ? Jun 18 11:33:46 as this it will fail to bring the interface up if it actually fail to load the module right ? Jun 18 11:38:04 garthps: 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 Jun 18 11:38:05 d Jun 18 11:42:13 mickey|daddy: hm yeah.. what will sirloin_wifi_mod.load() return is the modul is already loaded ? Jun 18 11:43:47 then the is_active variable handling is unsufficient as it is never tested whether it is already active or not Jun 18 11:44:56 plus then is it tryied to load the interface after failing to load the module then we have a crash Jun 18 11:45:13 [CRITICAL] fsodeviced : GLib : file powercontrol.c: line 267: uncaught error: Could not bring interface eth0 up: No such device (fso_framework_network_error-quark, 0) Jun 18 11:45:47 org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) Jun 18 11:45:55 sorry Jun 18 11:45:57 root@palmpre2 ~ # mdbus2 -s org.freesmartphone.odeviced /org/freesmartphone/Device/PowerControl/0 org.freesmartphone.Device.PowerControl.SetPower true Jun 18 11:45:57 org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) Jun 18 11:46:09 root@palmpre2 ~ # mdbus2 -s org.freesmartphone.odeviced /org/freesmartphone/Device/PowerControl/0 org.freesmartphone.Device.PowerControl.GetPower Jun 18 11:46:09 org.freedesktop.DBus.Error.UnknownMethod: Method "GetPower" with signature "" on interface "org.freesmartphone.Device.PowerControl" doesn't exist Jun 18 12:01:46 So for now I really think th ifup thing should be in the else part Jun 18 12:56:26 GarthPS: yep. lets bring it up to morphis next time he's here Jun 18 13:03:01 mickey|daddy: okey Jun 18 15:38:55 freesmartphone.org: 03morphis 07aurora * raf98757fecab 10/aurora/systemmanager/main.vala: aurora: don't drop priviledges in system manager for now Jun 18 16:07:54 freesmartphone.org: 03morphis 07aurora * r56f2c18efa89 10/aurora/systemmanager/controller.vala: aurora: handle backlight power update before the backlight is set Jun 18 16:36:16 freesmartphone.org: 03morphis 07aurora * r13ed1762ccac 10/aurora/systemmanager/controller.vala: aurora: handle power and audio mute keys in system manager Jun 18 16:38:42 freesmartphone.org: 03morphis 07aurora * r5bb5b2d8ea21 10/aurora/systemmanager/controller.vala: aurora: fix syntax error from commit before Jun 18 20:28:04 GNUtoo: 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... Jun 18 20:29:18 yes it is Jun 18 20:29:22 but it may not work Jun 18 20:29:30 basically it's as secure as flashing a kernel Jun 18 20:29:37 since uboot is flashed at the kernel place Jun 18 20:29:42 it's a chainloaded bootloader Jun 18 20:29:49 the original bootloader is still there Jun 18 20:29:55 which can be coldflashed btw Jun 18 20:30:26 but why it may not work? Jun 18 20:34:44 GNUtoo: which kernel do you have on n900? Jun 18 20:35:41 the meego one Jun 18 20:35:53 the n900-adaptation one Jun 18 20:35:58 we update it often Jun 18 20:36:36 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 Jun 18 20:36:57 I've something to do with Lopi right now Jun 18 20:37:02 but I'll do it right after Jun 18 20:37:05 if I don't go to bed Jun 18 20:51:46 the 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 Jun 18 20:52:00 complain to mickey|daddy Jun 18 20:52:10 I fighted a lot for keeping 2.6.28 Jun 18 20:54:04 well, 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 Jun 18 20:54:57 basically my notion about meego-arm (N900) folks and their approach to kernel things: they got NFC Jun 18 20:55:22 mickey|daddy's reason was devtmpfs that was lacking on 2.6.28 Jun 18 20:55:42 they even deliberately admit they have no clue and go mere mainstream kernel, no matter what crap is or isn't there Jun 18 20:57:39 prominent 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 Jun 18 20:57:59 this driver _evidently_ is fubar and bullshit Jun 18 20:58:29 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 Jun 18 20:58:37 same pattern of operation applies to several other topics in meego I'd think Jun 18 20:58:40 Lopi, it just compiled Jun 18 20:59:05 GNUtoo: ohh nice ^^ Jun 18 20:59:16 Alex[sp3dev]: the problem is we can't get a proper lis302 driver upstream as there's that crap already Jun 18 20:59:48 http://gnutoo.homelinux.org/downloads/people/Lopi/plugin.vala Jun 18 20:59:50 getting good driver upstream would mean to nuke the shit, and nobody is going to fight that battle Jun 18 20:59:56 wget it and diff it with yours Jun 18 21:00:01 I commented a part tough Jun 18 21:00:06 because the function was not present Jun 18 21:00:16 DocScrutinizer: i see. so sitting and whining is better Jun 18 21:00:17 but it's pretty small Jun 18 21:00:20 it's only a check Jun 18 21:00:28 Alex[sp3dev]: you're free to do that Jun 18 21:00:34 I also surely messed up the identation Jun 18 21:00:40 also I didn't check pointers yet Jun 18 21:00:42 (whining, fighting, whatever) Jun 18 21:00:56 do you also want the binary? Jun 18 21:01:21 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 Jun 18 21:01:29 for SHR however I strongly suggest to keep a local branch with platform adaptions that are local Jun 18 21:01:49 Alex[sp3dev]: exactly my suggestion Jun 18 21:02:07 GNUtoo: yeah give me the binary Jun 18 21:02:14 GNUtoo: I see what you changed, very minor Jun 18 21:02:24 meego has a policy of "mainline ONLY" so I don't care Jun 18 21:02:49 let me try to look of the & are correct Jun 18 21:02:52 and then I'll do Jun 18 21:02:57 Alex[sp3dev]: for SHR things are 'better' and I'm sure those smart guys here will eventually do "the right thing" Jun 18 21:03:03 okay sounds good ty Jun 18 21:03:57 ah my bad the & are correct Jun 18 21:04:09 embedded is always about fine tuning kernel stuff to the particular platforn, so in my book meego's "mainline only" approach never will work out Jun 18 21:05:18 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 Jun 18 21:05:36 http://gnutoo.homelinux.org/downloads/people/Lopi/modem_singleline.so Jun 18 21:05:46 note that it may fail at runtime Jun 18 21:05:53 since you copy-pasted lot of C Jun 18 21:05:55 Alex[sp3dev]: sure Jun 18 21:05:59 okay Jun 18 21:06:00 I didn't extensively check everything Jun 18 21:06:06 I just tried to compile it Jun 18 21:06:09 we'll see what happens Jun 18 21:06:12 so you may need gdb Jun 18 21:06:12 at least it's a start Jun 18 21:06:28 to run it Jun 18 21:06:33 add DEBUG in fsogsmd Jun 18 21:06:35 config Jun 18 21:06:43 then do: Jun 18 21:06:47 Alex[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 Jun 18 21:06:50 killall fsogsmd;fsogsmd Jun 18 21:06:57 and make your config use singleline Jun 18 21:07:06 btw I made a porting guide on SHR wiki Jun 18 21:07:14 oh nice Jun 18 21:07:15 DocScrutinizer: i can say the same thing about everything done by android developers Jun 18 21:07:21 http://www.shr-project.org/trac/wiki/Device%20Porting%20Guide Jun 18 21:07:25 it's a beginning Jun 18 21:07:29 we must add to it Jun 18 21:08:02 yeah, it's definitely needed tho Jun 18 21:08:16 that's the biggest problem with SHR Jun 18 21:08:22 our docs blow Jun 18 21:08:22 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 Jun 18 21:08:25 Alex[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 Jun 18 21:09:09 DocScrutinizer: i think we both agree that code written by hardware vendors sucks and i don't want to continue this discussion Jun 18 21:09:50 ouch ignoring pdata???? Jun 18 21:09:59 you're free to stop answering to my comments directed to GNUtoo Jun 18 21:10:16 * GNUtoo read it now Jun 18 21:10:51 and look at meego camera Jun 18 21:10:56 it's not so better Jun 18 21:11:01 the image quality...hmmm Jun 18 21:11:32 DocScrutinizer: ok, sorry for that Jun 18 21:13:27 so now wl1251_sdio Jun 18 21:13:44 GNUtoo: 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 Jun 18 21:14:18 the "only" problem is that things change at a rate that is enormous Jun 18 21:14:22 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 Jun 18 21:14:29 s/enormous/very very very fast Jun 18 21:14:32 as 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 Jun 18 21:15:35 Alex[sp3dev], n900 is wl1251_spi Jun 18 21:15:57 and cleaning 2.6.28 takes a lot of time Jun 18 21:16:06 *2.6.28 patches Jun 18 21:16:24 GNUtoo: you're aware there's been quite some problems around wl1251 in maemo, and Nokia did some 'tricks' to make it behave? Jun 18 21:16:31 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 Jun 18 21:16:37 and I have huge issues with nervousness right now...... Jun 18 21:16:51 DocScrutinizer, uhhh no Jun 18 21:17:09 Alex[sp3dev], I'll compile for dream Jun 18 21:17:45 in some minutes Jun 18 21:17:53 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 Jun 18 21:18:09 GNUtoo: 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 Jun 18 21:19:10 there have been other wicked screwed problems iirc Jun 18 21:19:44 GNUtoo: btw with the latest mainline wl1251 i can only scan with a dedicated irq. it won't work without it. Jun 18 21:20:23 GNUtoo: then there's been that mysterious chan6-only issue Jun 18 21:21:02 I never wraped my head around it Jun 18 21:21:13 just saying "watch out!" Jun 18 21:24:23 some 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 Jun 18 21:25:05 he asked for a donation of >=0ct for shipping the source, which is fine but caused lots of flames Jun 18 21:25:38 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 Jun 18 21:26:12 Alex[sp3dev]: I can't comment on msm phones, never had a look at thiose Jun 18 21:26:54 DocScrutinizer: they're using sdio inteface, not spi. so maybe all the problems come from the way irqs are handled Jun 18 21:35:40 Alex[sp3dev]: quite possible. Ask wpwrak about it, he did "a master thesis" about the very topic Jun 18 21:36:29 on ar6000 though, but in the end it's been spi vs sdio IIRC Jun 18 21:36:55 ok, will do later. now i need to prepare for the exams. and after exams i'll need to analyze GNUtoo's dump first Jun 18 21:37:03 wpwrak: any comments? ^^^ Jun 18 21:39:22 I hope msm is using hardmac? as with softmac you're running into trouble you never get behind you, on embedded Jun 18 21:39:54 GNUtoo: I'm done with this for the day, but I made a lot of progress today Jun 18 21:39:57 (excuse my ignorance if wl1251 maybe has no hard- or softMAC Jun 18 21:40:00 ) Jun 18 21:42:36 DocScrutinizer, I think it's a softmac Jun 18 21:42:42 but it has some power saving features Jun 18 21:42:46 and it's pretty good Jun 18 21:42:48 OUCH Jun 18 21:43:00 it's an exception Jun 18 21:43:41 you're aware what softmac is. So you know your system standby will suck on WLAN with softmac Jun 18 21:44:29 ok Jun 18 21:44:36 waking main CPU for each random WLAN inbound pkg is for sure not helpful to get things working and saving power Jun 18 21:44:54 it has PSM tough Jun 18 21:45:03 but on msm I never got it working Jun 18 21:45:05 s/inbound pkg/random signal/ Jun 18 21:45:05 DocScrutinizer meant: waking main CPU for each random WLAN random signal is for sure not helpful to get things working and saving power Jun 18 21:45:16 altough with the android driver it works Jun 18 21:45:27 GNUtoo: do you know some link of a rootfs(and a kernel) to i test SHR quickly here on my N900? Jun 18 21:45:32 whatever, but the whole system with backlight, gsm and stuff takes the same amount of power as wl1251 alone without psm Jun 18 21:45:55 angelox, hi, go on SHR download page, download an n900 rootfs extract it on microsd Jun 18 21:46:05 angelox, did you flash uboot yet Jun 18 21:46:06 ? Jun 18 21:46:43 i used that tutorial from meego,working uboot here already. Jun 18 21:46:55 ok Jun 18 21:46:57 is it flashed? Jun 18 21:47:14 Alex[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 Jun 18 21:47:37 wl1251_sdio has psm Jun 18 21:47:41 it works on the pandora Jun 18 21:47:50 Alex[sp3dev]: and wl1251 is known to suck power for RX Jun 18 21:47:51 it also works on the ti driver Jun 18 21:48:01 GNUtoo: it even works in winmo Jun 18 21:48:37 GNUtoo: 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) Jun 18 21:48:59 angelox, what do you get at boot? Jun 18 21:49:03 an additional problem is al lot of AP don't implement PSM correctly, so your PSM may fail despite you did everything 100% correct Jun 18 21:49:18 yes Jun 18 21:49:24 but I have hostapd Jun 18 21:49:55 and my laptop has that: Jun 18 21:49:57 Power Management:on Jun 18 21:50:05 hard to tackle that whole topic, without $$$k equipment to analyze OTA Jun 18 21:50:16 would an USRP help? Jun 18 21:50:20 GNUtoo: 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 Jun 18 21:50:21 sure :-D Jun 18 21:50:55 because I suspect that the problem is not on the wireless transmit/receive, but rather on the kenrel code and with the IRQ handling Jun 18 21:51:03 angelox, ok Jun 18 21:51:17 GNUtoo: quite possible Jun 18 21:51:26 angelox, boot maemo with it for now Jun 18 21:51:32 angelox, give me some minutes Jun 18 21:51:34 for softmac to work you need "realtime!" Jun 18 21:51:42 I've to compile wl1251_sdio Jun 18 21:51:42 GNUtoo: ok,thank you. Jun 18 21:51:56 I hope I don't go to bed before helping you Jun 18 21:52:00 but big warning Jun 18 21:52:05 don't stay too long in uboot Jun 18 21:52:08 as *all* is about timing in PSM Jun 18 21:52:10 else the battery discahrges Jun 18 21:52:22 and the battery charging is an userspace program Jun 18 21:52:32 so you have to be able to boot to charge it usually Jun 18 21:52:37 the details is Jun 18 21:52:47 that the bootloader has an emergency charge Jun 18 21:52:53 (not uboot but the one under it) Jun 18 21:53:02 so it can charge it enough just to make you boot Jun 18 21:53:10 not really Jun 18 21:53:18 but doesn't matter ;-) Jun 18 21:53:25 DocScrutinizer: which pretty much explains why it only works with a dedicated irq. sdio interrupts are too slow for it Jun 18 21:53:47 Alex[sp3dev]: yes, sounds like a story Jun 18 21:54:11 DocScrutinizer, what are the real details? Jun 18 21:54:15 GNUtoo: hmm ok,thank you,i booted maemo by writing on uboot "run noloboot". Jun 18 21:54:27 Alex[sp3dev]: depending on your kernel you also got IRQ servicing latencies... Jun 18 21:54:45 GNUtoo: actually the chip does the emergency charging Jun 18 21:54:50 ah ok Jun 18 21:54:59 but the bootloader triggers it Jun 18 21:55:00 ? Jun 18 21:55:04 nope Jun 18 21:55:05 like trough i2c Jun 18 21:55:07 ah ok Jun 18 21:55:27 GNUtoo: look, if BL got loaded, the *hw* already 'booted' Jun 18 21:56:00 loading, BL, loading kernel. No diff for the hw Jun 18 21:56:45 * angelox liked his N900 and don't want to brick it :) Jun 18 21:56:47 but the NOLO BL decides to immediately boot to kernel for further charging, and not allow flashing, if battery is too low Jun 18 21:56:59 angelox: you can't brick N900 Jun 18 21:57:20 well, it's at least incredibly hard to do Jun 18 21:57:21 angelox, indeed you can even reflash the bootloader trough usb Jun 18 21:57:24 I even did it Jun 18 21:57:47 DocScrutinizer: 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. Jun 18 21:57:55 worst thing to do is nuke CAL with all the device specific data like serial# etc Jun 18 21:58:30 wpwrak: softmac eating power, compared to hardmac. That's my point Jun 18 21:59:07 /dev/mtd1 then Jun 18 21:59:09 also softmac is a bitch do get right, regarding strict timing of PSM Jun 18 21:59:42 GNUtoo: indeed. No reports on how to recover from that Jun 18 21:59:58 maybe it's irrelevant Jun 18 22:00:01 maybe not Jun 18 22:00:08 maybe reflashing a PR 1.3? Jun 18 22:00:13 nobody tested it, for obvious reasons ;-P Jun 18 22:00:33 lol Jun 18 22:00:34 flashing doesn't usually touch CAL Jun 18 22:00:38 DocScrutinizer: 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. Jun 18 22:00:40 if i flashed uboot,there's somehow to recover my warranty,or i didn't lose it yet? Jun 18 22:00:40 ah ok Jun 18 22:00:44 except for SW version etc Jun 18 22:00:59 angelox: irelevant Jun 18 22:01:05 wpwrak, there is a GPIO IRQ for PSM Jun 18 22:01:18 MSM_GPIO_TO_INT(29) if I remember well Jun 18 22:01:20 angelox: you don't lose warranty by flashing kernel Jun 18 22:01:55 this is good... Jun 18 22:01:59 you have no warranty though on a working system with non-standard kernels :-P Jun 18 22:02:23 and flashing back to standard isn't covered by warranty Jun 18 22:03:09 so if you thoroughly screwed things, you better don't tell you messed with alterative kernels/OS ;-) Jun 18 22:03:34 otherwise they will charge you for restoring stock image Jun 18 22:04:21 though honestly you should be capable of doing that at home, if you dare to mess with alternatives ;-) Jun 18 22:04:41 again, you can't really brick N900 Jun 18 22:04:51 angelox, also beware with waranties, if you send it for repair you may get a N8 instead Jun 18 22:04:57 *get a N8 back Jun 18 22:05:04 just recovering gets harder still, if you mess up "better" Jun 18 22:05:36 coldflashing is not hard, but it require to use flasher, which is proprietary Jun 18 22:05:52 flasher is all you usually need to recover from whatever "bricking" might have happpened Jun 18 22:05:57 coldflash->flashing eMMC+NAND Jun 18 22:06:01 and you can recover Jun 18 22:06:08 yup Jun 18 22:06:51 CPU has a minimalistic USB bootloader that can't get nuked, so you can recover from all possible mess you might have caused Jun 18 22:07:13 ok,i was afraid about brick it...thanks for explanation... about OS/Kernel/NAND/eMMC/Bootloader so we have no problems if "brick" it... Jun 18 22:07:19 another way to brick it is to overclock it Jun 18 22:07:22 don't overclock Jun 18 22:08:01 that's not "bricking" that's deliberately cooking hw to death Jun 18 22:08:22 and if i brick some physical part of it? (for example,my touch stop working) Jun 18 22:08:52 you have several ways to do that, not all need sw tweaks: attach 50V~ charger for example Jun 18 22:09:56 angelox: 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 Jun 18 22:10:31 flasher won't glue broken hw parts Jun 18 22:10:41 yes :) Jun 18 22:10:53 and while sw can't kill touchpanel, a nail or knife can Jun 18 22:11:11 please use common sense Jun 18 22:12:00 software can brick it that way: Jun 18 22:12:05 touchscreen not working Jun 18 22:12:08 because of software Jun 18 22:12:14 and user touching more hard Jun 18 22:12:17 *harder Jun 18 22:12:19 i 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? Jun 18 22:12:21 which may damage it Jun 18 22:12:25 depending on the device Jun 18 22:12:59 angelox: nope Jun 18 22:13:13 angelox: first thing they do: reflash to known good stock OS Jun 18 22:13:25 angelox: then check if hw still acts up Jun 18 22:13:56 angelox: then if it's not evidently a OC caused CPU fry-out, they just will fix/replace Jun 18 22:14:34 ah,ok,so i understood now,because i didn't know how they proceed to fix a phone problem Jun 18 22:15:54 angelox: and really, that's what you should do as well, prior to trying to go for warranty repair Jun 18 22:16:29 because if they find it's been a mere sw issue, they *might* decide to charge you for fixing your system sw Jun 18 22:17:11 and I'm all with them for ding so Jun 18 22:17:16 doing* Jun 18 22:17:53 Alex[sp3dev], now that I have my system setup Jun 18 22:17:58 what logs do you want? Jun 18 22:18:10 I can ping the router Jun 18 22:18:53 angelox: btw recently nokia repair sends out crappy N8 for replacement of nice maemo-based N900, as they don't have spare N900 anymore Jun 18 22:19:04 [ 339.542022] wl1251: ERROR elp wakeup timeout // when I iwconfig wlan0 power on Jun 18 22:19:08 :-/ Jun 18 22:19:13 GNUtoo: yeah, i think you can enable DEBUG_IRQ, DEBUG_MAILBOX, DEBUG_EVENT, DEBUG_TX, DEBUG_RX Jun 18 22:19:23 ok Jun 18 22:20:14 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 Jun 18 22:20:27 DocScrutinizer: 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 ) Jun 18 22:20:55 GNUtoo: so is the compat-wireless on gitorious the one you're using? Jun 18 22:20:55 your dealer may still have N900, but Nokia repair don't Jun 18 22:20:57 btw I used theses branches: Jun 18 22:21:26 master branch of git://gitorious.org/htc-msm-2-6-32/compat-wireless.git Jun 18 22:21:28 DocScrutinizer: yes... Jun 18 22:21:48 remotes/htc-msm/android-msm-2.6.32-rebase+needs_compat_wireless+wifi-irq of the leviathan kernel Jun 18 22:22:43 (nokia repair don't) which is an incredible fail, as manufacturers are supposed to keep spare parts for years after EOL of product Jun 18 22:23:17 as it is a great phone too Jun 18 22:23:34 and I really hope this has been a PEBKAC at service line of NOKIA, as otherwise the shall get sued to the ground Jun 18 22:24:46 ELOP == EOLP(end of life products) Jun 18 22:24:51 you CAN NOT replace a linux device with a sybian based one, no matter how many more pixels the cam has Jun 18 22:25:45 hmm Jun 18 22:25:47 ~elop Jun 18 22:25:57 amazing Jun 18 22:26:12 ~tepco Jun 18 22:26:13 'tepco' (1 of 2): sth especially stupid or messed up; "this construction is completely tepco"; "please stop behaving tepco" Jun 18 22:26:28 dont know what do you think,but they also doesnt know that maemo is much more better than symbian one Jun 18 22:27:09 apt: ELOP is a microsoft spy and one of the most successfull corporate trolls Jun 18 22:27:10 okay, Alex[sp3dev] Jun 18 22:27:27 they switched to meego, then found this is a dead end adventure... Jun 18 22:27:32 i think maemo 10x better than symbian for a phone/tablet device Jun 18 22:27:44 Alex[sp3dev]: thanks :-) Jun 18 22:28:51 or meego too...great OS.. Jun 18 22:29:22 http://gnutoo.homelinux.org/downloads/people/Alex%5bsp3dev%5d/association.lzma Jun 18 22:29:29 well, as mentioned above, meego-arm still has not the maturity of maemo Jun 18 22:29:58 GNUtoo: thanks, downloaded. Jun 18 22:30:31 lzcat it Jun 18 22:30:41 * DocScrutinizer curses space-bar of laptop started to grate Jun 18 22:30:44 basically I had connman running Jun 18 22:30:47 GNUtoo: luckily i know what lzma is Jun 18 22:30:48 so I killed it Jun 18 22:31:07 yes but I just discovered lzcat Jun 18 22:31:36 because there is bzcat zcat etc...so I tought maybe there is a lzcat Jun 18 22:31:51 *cough* Jun 18 22:32:13 so I was saying: Jun 18 22:32:23 I had connmand running and I killed it Jun 18 22:32:29 then I retried to associatae Jun 18 22:32:31