**** BEGIN LOGGING AT Sun Oct 03 02:59:57 2010 Oct 03 07:58:39 freesmartphone.org: 03morphis 07utilities * r560d39984e37 10/palmpre/tsmd/src/tsmd.c: Oct 03 07:58:39 freesmartphone.org: palmpre: tsmd: report even pressure of touchscreen events Oct 03 07:58:39 freesmartphone.org: Signed-off-by: Simon Busch Oct 03 08:21:44 freesmartphone.org: 03morphis 07msmcomm * r35b6868136f9 10/ (6 files in 2 dirs): msmcommd: introduce PhonebookBookType enumeration for dbus api Oct 03 08:21:44 freesmartphone.org: 03morphis 07msmcomm * r8ee7982000a9 10/msmcommd/ (4 files in 2 dirs): Oct 03 08:21:44 freesmartphone.org: msmcommd: use lowlevel control when config recommends it Oct 03 08:21:44 freesmartphone.org: Signed-off-by: Simon Busch Oct 03 08:46:11 freesmartphone.org: 03morphis 07utilities * r20de92c01ea7 10/palmpre/tsmd/src/tsmd.h: palmpre: tsmd: set max value of pressure to 2^8 Oct 03 09:01:59 freesmartphone.org: 03morphis 07utilities * r0a3fb1c64a04 10/palmpre/tsmd/src/tsmd.c: Oct 03 09:01:59 freesmartphone.org: palmpre: tsmd: if pressure == 0 then report a BTN_TOUCH event Oct 03 09:01:59 freesmartphone.org: Signed-off-by: Simon Busch Oct 03 09:08:42 freesmartphone.org: 03morphis 07utilities * r695d7324a064 10/palmpre/tsmd/src/tsmd.c: Oct 03 09:08:43 freesmartphone.org: palmpre: tsmd: if pressure == 0 then report a BTN_TOUCH event Oct 03 09:08:43 freesmartphone.org: Signed-off-by: Simon Busch Oct 03 09:15:31 freesmartphone.org: 03morphis 07utilities * r400ea671d44d 10/palmpre/tsmd/src/tsmd.c: Oct 03 09:15:32 freesmartphone.org: palmpre: tsmd: report correct BTN_TOUCH events Oct 03 09:15:32 freesmartphone.org: Signed-off-by: Simon Busch Oct 03 09:46:33 morning Oct 03 09:49:42 JaMa|Off, please bump mokowm and mokosuite2 to latest :) Oct 03 09:50:04 mrmoku: ping Oct 03 09:54:59 daniele_athome: pong Oct 03 09:55:09 mrmoku, hi there :) Oct 03 09:55:14 hey Oct 03 09:55:23 how's going? Oct 03 09:57:59 daniele_athome: struggling with n900 Oct 03 09:58:16 :) Oct 03 09:59:08 mrmoku, i've made some nice improvements and fixes to the suite, can you bump mokowm and mokosuite2? Oct 03 09:59:16 as well as libfreesmartphone-glib Oct 03 10:00:32 daniele_athome: if you tell me the revs Oct 03 10:00:38 sure Oct 03 10:00:57 mokosuite2 37bea7f4e6a0ed48189a15ca0fbd04ef8a7c487d Oct 03 10:01:06 mokowm 902e90843a03f865404ebb43cd236402b4c6e776 Oct 03 10:01:20 libfreesmartphone-glib 133dc094f98e772e89949b4e35002ab5c1f2d7e2 Oct 03 10:01:34 mrmoku, i think libfreesmartphone-glib is already at that rev Oct 03 10:01:47 libfreesmartphone-glib1 - 0.2+gitr3+133dc094f98e772e89949b4e35002ab5c1f2d7e2-r0.5 - freesmartphone.org API GLib wrapper (auto-generated) Oct 03 10:01:52 yes confirmed :) Oct 03 10:02:12 ok Oct 03 10:02:19 thanks! Oct 03 10:06:56 done Oct 03 10:08:14 mrmoku, already started build? Oct 03 10:08:20 daniele_athome: no Oct 03 10:08:26 mrmoku, good, don't :) Oct 03 10:08:43 daniele_athome: and I won't either ;) Oct 03 10:08:47 damn just found a segv Oct 03 10:08:47 :S Oct 03 10:08:56 ok Oct 03 10:09:28 you should start to find them before bumping the rev ;) Oct 03 10:10:15 mrmoku, i'm sorry just found now Oct 03 10:10:16 :( Oct 03 10:10:22 seems efl related Oct 03 10:10:24 just a sec Oct 03 10:11:19 mrmoku, i thought so :( Oct 03 10:12:30 mrmoku: http://pastebin.com/2Xc9VUV3 Oct 03 10:13:15 libelementary-ver-pre-svn-07.so.0 Oct 03 10:13:18 that is old stuff, no? Oct 03 10:13:44 mrmoku, i'm trying on my notebook Oct 03 10:13:51 anyway the bug is the same Oct 03 10:14:29 i'll try to update to latest efl, but mine it's not very old Oct 03 10:14:52 * daniele_athome is upgrading to rev 52995 Oct 03 11:16:50 moin Oct 03 11:18:21 hi JaMa Oct 03 11:51:00 mrmoku, JaMa: new mokosuite2 rev e70e928216eea9d07c28327634ea49c87bc0c92f Oct 03 11:51:05 worked around elm bug :( Oct 03 11:51:49 hi JaMa Oct 03 11:51:59 oops wrong channel Oct 03 11:52:06 I should talk to you in #oe Oct 03 11:54:02 freesmartphone.org: 03morphis 07utilities * r798c26a7022d 10/palmpre/tsmd/src/tsmd.c: Oct 03 11:54:02 freesmartphone.org: palmpre: tsmd: report BTN_TOUCH correctly and even report ABS_PRESSURE Oct 03 11:54:02 freesmartphone.org: Signed-off-by: Simon Busch Oct 03 11:59:24 daniele_athome: ok, is it really safe to bump and build or should I wait a bit more? Oct 03 12:00:39 JaMa, it's ok for me... i guess it depends on elm now... Oct 03 12:01:05 except for that bug, i tested it for 2 days in my daily phone use Oct 03 12:11:25 hi leviathan Oct 03 12:11:37 you bought an usb cable? Oct 03 12:12:22 I've again forgotten it... -.- Oct 03 12:12:25 too much to do Oct 03 12:12:30 I'll do it on monday... Oct 03 12:12:34 certainly Oct 03 12:12:35 ... Oct 03 12:12:36 ok Oct 03 12:12:48 leviathan, you've got a german dream? Oct 03 12:12:53 I mean htc dream Oct 03 12:12:53 yes Oct 03 12:12:56 ok Oct 03 12:12:59 swiss german Oct 03 12:13:00 with german keyboard Oct 03 12:13:00 :-) Oct 03 12:13:03 ah ok Oct 03 12:13:08 how's the keyboard? Oct 03 12:13:43 I've fully mapped the keyboard of the dream mickeyl sent me Oct 03 12:13:50 it's a german keyboard Oct 03 12:15:08 not in oe yet but in shr git repo for xkeyboard-config Oct 03 12:15:14 htcdream branch Oct 03 12:16:02 hi, i just ran opkg upgrade on SHR-U, but unfortunately, I missed some of the collected errors. is there any way to reproduce them? Oct 03 13:21:45 mrmoku: how do you think, should AmbientLight be implemented as resource, like Proximity? Oct 03 13:24:19 dos1: did not look at how the proximity thing works Oct 03 13:24:43 emitting signals on light change Oct 03 13:24:45 mrmoku: it signals ProximityChanged only, when Proximity resource is requested Oct 03 13:24:53 yeah Oct 03 13:24:55 sounds sane Oct 03 13:25:07 how do accels work? Oct 03 13:25:29 though light readings changes much more frequent Oct 03 13:27:02 so maybe we should poll it only every n seconds? Oct 03 13:27:37 take a look at what mickey did for the accels Oct 03 13:27:44 in the end it's similiar Oct 03 13:28:00 i think that's what maemo and symbian does on various devices, as it takes about 5 seconds for them to adjust backlight Oct 03 13:28:09 heh, yes :) Oct 03 13:28:32 which does not mean it's the most elegant way ;) Oct 03 13:37:38 mrmoku: but i think it's the best Oct 03 13:38:10 there is only "lux" sysfs node, which changes really quickly Oct 03 13:38:42 and ambient light sensor, unlike accels, is rather meant to be enabled all the time Oct 03 13:39:08 so handling every change would just waste cpu Oct 03 13:40:07 freesmartphone.org: 03seba.dos1 07cornucopia * r885f3d67d940 10/fsodeviced/src/plugins/accelerometer_lis302/plugin.vala: accelerometer_lis302: fix to work with new kernels Oct 03 13:40:58 freesmartphone.org: 03seba.dos1 07cornucopia * r3d3e1f618b07 10/fsodeviced/src/plugins/accelerometer_lis302/plugin.vala: accelerometer_lis302: fix to work with new kernels Oct 03 13:45:51 dos1: fix the typos in there too :-) Oct 03 13:46:35 where? Oct 03 13:46:37 internal const int KXSD9_DEFAULT_SAMPLERATE = 250; Oct 03 13:46:49 in the lis plugin is unaesthetic :P Oct 03 13:47:05 yup, already changed that Oct 03 13:47:13 logger.warning( "Kxsd9 configuration sysfs not available at %s. Accelerometer will not work properly.".printf( sysfsnode ) ); Oct 03 13:47:16 even worse Oct 03 13:47:28 :) Oct 03 13:47:31 already changed every kxsd9 to lis302 ;) Oct 03 13:47:37 good :) Oct 03 13:48:10 dos1: what is your take on which kernel to take? Oct 03 13:48:16 what about accels on n900? Oct 03 13:48:27 they're lis too I think Oct 03 13:48:36 there is lis302 too, but maemo kernel does not export it as input device Oct 03 13:49:20 The N900 has builtin STMicroelectronics LIS302DL accelerometers. Oct 03 13:49:21 yeah Oct 03 13:49:22 mrmoku: you mean Maemo vs. Meego patches? Oct 03 13:49:40 yup, either 2.6.28 with maemo patches Oct 03 13:49:47 or 2.6.35 + meego patches Oct 03 13:50:44 mrmoku: I have patch for GNU screen to work again without that kernel patch revert :) Oct 03 13:51:00 * JaMa can build in his env again :) Oct 03 13:51:14 JaMa: fortunatelly I don't use screen with your chroot :) Oct 03 13:51:37 ah lucky :) Oct 03 13:51:55 JaMa: your opinion too please... which kernel shall we take for n900 Oct 03 13:51:56 btw everything using ttyname(int fd) could be broken with 2.6.36 Oct 03 13:52:59 mrmoku: i would like to have newer kernel, but i saw you and GNUtoo|laptop complained about some missing parts in it Oct 03 13:53:08 well for "first version" I would like to use 2.6.28 to keep it as compatible with maemo as possile (from kernel pov) Oct 03 13:53:22 and 2.6.28 already works and is usable Oct 03 13:53:32 also, JaMa++ Oct 03 13:53:49 * mrmoku would prefer the new kernel too :P Oct 03 13:54:04 meego kernel can be build in shr-kms with some switch-for-kernel script again :) Oct 03 13:54:04 but I'm having problems... don't get g_ether to work reliably Oct 03 13:54:31 and maemo kernel has important stuff for powersaving (DVFS) which is missing in the meego kernel Oct 03 13:54:44 and I don't know how fast the meego kernel will evolve Oct 03 13:54:48 for my taste too slow :P Oct 03 13:55:04 GNUtoo|laptop: ^^^^ Oct 03 13:55:29 GNUtoo|laptop: so... let's go old kernel for the beginning Oct 03 13:55:34 ahh... there was one nasty problem Oct 03 13:55:42 it does not boot without USB attached :P Oct 03 13:55:45 we have to solve that one then Oct 03 13:57:04 ok, what does mickey|away think about it? Oct 03 13:57:20 no idea Oct 03 13:57:45 guess he wants the fastest way too Oct 03 14:06:05 hmm Oct 03 14:06:26 "The new ambient light brightness." Oct 03 14:06:46 i think we should define, if that's percentage or lux or some other unit... Oct 03 14:11:42 radekp: Hi, do you still have gta01 from pavel? Do you plan to use 2.6.34 on it? Oct 03 14:14:15 freesmartphone.org: 03seba.dos1 07specs * rf0e1ff218cbb 10/ (2 files in 2 dirs): org.freesmartphone.Device.Proximity: define units in description Oct 03 14:14:17 freesmartphone.org: 03seba.dos1 07specs * r6380a5ee1ced 10/ (4 files in 4 dirs): Merge branch 'master' of git.freesmartphone.org:specs Oct 03 14:14:26 JaMa: hi, yes i have, but no plan for 2.6.34 right now Oct 03 14:14:49 ah ok Oct 03 14:15:38 JaMa: is there any branch of 2.6.34 for GTA01? To me it looks like the GTA01 support was removed Oct 03 14:15:56 dos1: good question Oct 03 14:16:53 radekp: no there isn't, last gta01 branch was 2.6.31, but IIRC only 2 patches from there need to be ported to 2.6.34 Oct 03 14:17:16 radekp: better to skip 2.6.32 porting as .34 has different arch/mach- layout :) Oct 03 14:20:32 JaMa: i was hoping someone will work on GTA01 after i port it to qtmoko but no developer was interested and i saw only very few users Oct 03 14:20:44 radekp: same with shr :/ Oct 03 14:20:49 JaMa: i wonder if there is any GTA01 user at all Oct 03 14:20:59 radekp: one is on #openmoko right now :) Oct 03 14:21:31 radekp: we have nonworking shr-u images for gta01 since we switched userspace to 2.6.32 paths etc.. Oct 03 14:22:45 JaMa: hmm GTA01 is quite nice HW - nearly same as GTA02 but it has just 64 MB of internal flash, so it's quite hard to fit there Oct 03 14:22:46 radekp: but as you, I would like to see some advanced user who cares about gta01 and send patches for it Oct 03 15:31:19 DocScrutinizer51: any hint how to debug nolo? Oct 03 15:31:33 muhahaha LOL Oct 03 15:31:37 :P Oct 03 15:31:40 * mrmoku feared that Oct 03 15:31:58 live with it or sell N900 Oct 03 15:32:07 the maemo kernel we build ourselves does not boot without usb attached Oct 03 15:32:19 meh, weird Oct 03 15:32:22 and there is not even debug output on the framebuffer Oct 03 15:32:47 sure, as there IS no framebuffer during NOLO really Oct 03 15:32:48 it feels like the kernel does not even get loaded Oct 03 15:33:01 yeah, wanted to say that the kernel does not even get started Oct 03 15:33:15 probably you got some kernel cmdline shit like console=USB ? Oct 03 15:33:30 possibly? Oct 03 15:33:35 no, moment Oct 03 15:34:00 CMDLINE_nokia900_shr = "snd-soc-rx51.hp_lim=42 snd-soc-tlv320aic3x.hp_dac_lim=6 console=tty1 root=/dev/mmcblk1p2 rootwait panic=20 debug" Oct 03 15:35:02 DocScrutinizer51: I could try without console=tty1 if you think that might be it Oct 03 15:35:07 console=tty1 ? erm, maybe that doesn't pan out without real console attached to the debug testpoints under batery? Oct 03 15:35:28 ok, then I will try without that Oct 03 15:35:38 because in the end we build a stock maemo kernel Oct 03 15:35:41 also I guess that's not the real cmdline NOLO is using Oct 03 15:35:45 so one of the few differences might be cmdline Oct 03 15:35:58 yes Oct 03 15:36:09 at least for root=... I'm sure it has effect :) Oct 03 15:36:34 * mrmoku rebuilds without console=tty1 Oct 03 15:36:46 aiui there's a fake cmdline built into kernel, and a real set of bootoptions (one of which is cmdline) that NOLO is using Oct 03 15:37:39 root@nokia900 ~ # cat /proc/cmdline Oct 03 15:37:39 snd-soc-rx51.hp_lim=42 snd-soc-tlv320aic3x.hp_dac_lim=6 console=tty1 root=/dev/mmcblk1p2 rootwait panic=20 debug Oct 03 15:38:04 either NOLO chockes on a kernel with 'wrong' fake cmdline, or your kernel gets stuck really really early on console output Oct 03 15:39:07 but then why would it work with usb attached? Oct 03 15:39:10 but honestly talking out of my ass here Oct 03 15:39:18 nfc Oct 03 15:39:46 btw. GNUtoo|laptop did a patch to get some bq27x00 info via sysfs Oct 03 15:40:01 mrmoku, forget that patch Oct 03 15:40:03 which means we have to adjust the charging script Oct 03 15:40:12 mrmoku, use the new charging script Oct 03 15:40:22 GNUtoo|laptop: at least it makes fso2 read the correct bat capacity Oct 03 15:40:29 ah ok Oct 03 15:40:37 maemo does some weird shit with act_dead boot runlevel changes, and also on testing R&D mode Oct 03 15:41:12 would it (in theory) be possible to replace nolo with something different? Oct 03 15:41:45 nope, probably not, as first level (ROM) bootloader afaik checks NOLO for signature Oct 03 15:41:54 ok :/ Oct 03 15:42:09 jacekowski knows more about it Oct 03 15:42:10 GNUtoo|laptop: where is that new one? Oct 03 15:43:01 but you shoukd be able to get NOLO to chainload whatever uBoot / grub /whatever you like Oct 03 15:43:07 mrmoku, new one? Oct 03 15:43:28 17:39 < GNUtoo|laptop> mrmoku, use the new charging script Oct 03 15:43:31 as NOLO isn't checking any signature or anything Oct 03 15:43:39 mrmoku, the one there is at your address Oct 03 15:43:56 http://build.shr-project.org/tests/mrmoku/n900/ Oct 03 15:44:01 well, that one does not work due to your bq27x00 thing sitting on i2c Oct 03 15:44:14 or wasn't that your problem? Oct 03 15:44:20 to be precise boot sequence is 0:ROM -> 1:nxldr -> 2:NOLO ->3:arbitrary binary, usually kernel Oct 03 15:44:20 that's what I was saying, do we really need power_supply class Oct 03 15:44:24 but you told that yes Oct 03 15:44:27 so... Oct 03 15:44:39 mrmoku, do like DocScrutinizer said long time ago: Oct 03 15:44:42 DocScrutinizer51: btw. do you know what cabc_mode for the acx565akm is? Oct 03 15:44:54 merge the one we have for n900 and the one for openmoko Oct 03 15:45:18 I have the openmoko one, the 2.6.28 bq27x00 and you patch open in gvim :-) Oct 03 15:45:28 just need to get a clue about what to do with it :P Oct 03 15:45:32 curious-adaptive-background-contrast-mode? for LCD? (semi kidding) Oct 03 15:45:44 hehe Oct 03 15:45:55 root@nokia900 /sys/devices/platform/omap2_mcspi.1/spi1.2/backlight/acx565akm # cat cabc_available_modes Oct 03 15:45:58 off ui still-image moving-image Oct 03 15:46:03 mrmoku, basically you need to get rid of the openmoko interface and use the i2c interface instead Oct 03 15:46:09 in the openmoko driver Oct 03 15:46:28 it's modulating backlight according to content of screen Oct 03 15:46:30 maybe some sort of compression Oct 03 15:46:33 something like that Oct 03 15:46:43 ah ok so I'm worng about compression Oct 03 15:46:59 but we need a patch against bq27xx00... so I need to bring the platform stuff from the openmoko one to the other one Oct 03 15:47:22 and that one has code for bq272000 too Oct 03 15:47:37 DocScrutinizer51: ok, ic Oct 03 15:50:36 dos1: does wifi work for you ? Oct 03 15:51:51 mrmoku: wifi at all, or wifi with fsodeviced module? Oct 03 15:52:09 (i'm not using selfbuilt kernel yet) Oct 03 15:52:27 mrmoku, don't forget the firmware on n900 Oct 03 15:52:36 and the nvs Oct 03 15:52:38 dos1: wifi with iliwi and fsodeviced, yes Oct 03 15:52:42 firmware I have Oct 03 15:52:44 (need to get a clue about what to do with it) ?? may I help? Oct 03 15:52:45 what is nvs? Oct 03 15:52:46 ok Oct 03 15:52:48 and it doesn't work Oct 03 15:52:50 calibration Oct 03 15:52:56 should be in /lib/firmware Oct 03 15:53:44 mrmoku: i haven't tested ifconfig module on n900 yet, only on my laptop, but it should be the same Oct 03 15:53:55 DocScrutinizer51: probably, but first I want to test the kernel without console=tty1 Oct 03 15:54:11 dos1: it works fine... iliwi scans and finds network Oct 03 15:54:14 and wifi worked to me some time ago when i tried it, but with plain wpa_supplicant Oct 03 15:54:15 just connecting does not work Oct 03 15:54:22 haven't tried iliwi at all Oct 03 15:54:25 ok Oct 03 15:54:27 (even with FR :P) Oct 03 15:54:34 * mrmoku notes to trie wpa_supplicant directly Oct 03 15:54:39 s/ie/y/ Oct 03 15:55:11 I noticed you had extensive chats about booting on #meego-arm. Weren't those helpful? Oct 03 15:57:25 not really Oct 03 15:57:39 no help for 2.6.28 maemo kernel Oct 03 15:57:58 and with the meego kernel it boots fine even without usb attached Oct 03 15:58:19 (which probably means omitting console=tty1 won't help :/) Oct 03 15:59:25 yeah, did not help Oct 03 15:59:44 mrmoku: maybe that's something related to g_ether being builit-in? Oct 03 16:03:29 it's not built in Oct 03 16:03:35 or is it? Oct 03 16:03:56 no, isn't Oct 03 16:04:10 GNUtoo|laptop: do you know where to find the kernel config maemo is using? Oct 03 16:04:18 mrmoku, that's simple Oct 03 16:04:27 it comes with a debian directory Oct 03 16:04:35 look in there if it uses the one from Oct 03 16:04:41 arch/arm/config/rx51* Oct 03 16:04:57 ahh, ok... within the patch we apply then? Oct 03 16:05:50 debian is the debian rules Oct 03 16:05:56 it's like an oe recipe Oct 03 16:06:04 and yes apply all our patches before Oct 03 16:06:06 DEFCONFIG := rx51_defconfig Oct 03 16:06:13 in debian/rules Oct 03 16:06:56 ok Oct 03 16:07:02 so should be like what I said Oct 03 16:10:23 GNUtoo|laptop: yeah, and there's not that many differences Oct 03 16:10:32 hmmm Oct 03 16:10:36 you get no wifi? Oct 03 16:10:40 with 2.6.28? Oct 03 16:11:14 I can scan and find networks Oct 03 16:11:21 but not connect Oct 03 16:11:22 but connection does not work (with iliwi) Oct 03 16:11:30 hmm, could you blinkenlight somwhere next to first 100 opcodes of your kernel, to know if it gets loaded at all Oct 03 16:11:36 are you sure you don't have to press a button on your router Oct 03 16:11:40 or something like that Oct 03 16:11:47 yep, sure Oct 03 16:11:56 works fine with maemo, my laptop and the FR Oct 03 16:12:11 mrmoku, what iwconfig says? Oct 03 16:12:13 wlan0? Oct 03 16:12:14 wlan1 Oct 03 16:12:15 ? Oct 03 16:12:17 wlan99 Oct 03 16:12:18 ? Oct 03 16:12:19 my neighbour has a mac... which offers his wireless unencrypted ;) Oct 03 16:12:22 could try that one Oct 03 16:12:35 GNUtoo|laptop: I added an udev rule to make it wlan0 always Oct 03 16:12:40 I use "wlan" Oct 03 16:12:43 ah ok Oct 03 16:12:58 hmmm should I try? Oct 03 16:13:02 mrmoku: keep in mind that with SHR you have random MAC address for WiFi on N900 Oct 03 16:13:03 mrmoku: hmm, could you blinkenlight somwhere next to first 100 opcodes of your kernel, to know if it gets loaded at all? Oct 03 16:13:07 it changes every boot Oct 03 16:13:37 yuk Oct 03 16:14:02 consider to get cal? Oct 03 16:14:26 it's like ubootenv partition on FR Oct 03 16:14:43 I'm quite sure it has MAC and shit Oct 03 16:15:01 DocScrutinizer: how do I do blinkenlightening ? Oct 03 16:15:11 good question Oct 03 16:15:25 could you wag some GPIO? Oct 03 16:15:41 isn't printk better? Oct 03 16:15:49 we don't see that Oct 03 16:15:58 yeah sure, printk to metaspace Oct 03 16:15:59 if kernel fails before initializing the framebuffer Oct 03 16:16:08 ??? Oct 03 16:16:14 JTAG? Oct 03 16:16:17 I thought we were talking about a wifi problem Oct 03 16:16:31 lindi-: you got a JTAG jig? Oct 03 16:16:33 we're talking about the 2.6.28 non-booting thing then? Oct 03 16:16:38 GNUtoo|laptop: DocScrutinizer is talking about the 'boot without usb' problem Oct 03 16:16:47 ok sorry Oct 03 16:16:47 yep Oct 03 16:16:57 DocScrutinizer: no idea, I thought openmoko debug board had some jtag stuff Oct 03 16:17:04 there is a way Oct 03 16:17:06 kexec Oct 03 16:17:11 with that if we get it right Oct 03 16:17:13 we can have dmes Oct 03 16:17:14 g Oct 03 16:17:18 *dmesg Oct 03 16:17:28 else serial Oct 03 16:17:37 but I bet no-one wants to risk a 600E device Oct 03 16:17:41 alas kexec seems doesn't even work on proper maemo kernel, nor meego yet Oct 03 16:17:50 really? Oct 03 16:17:56 ah so this was SHR on n900? Oct 03 16:17:56 then we patch it? Oct 03 16:18:02 lindi-: yup Oct 03 16:18:10 there are patch floating arround Oct 03 16:18:18 DocScrutinizer: console=ttyMTD,log console=tty0 is what the maemo kernel has in it's cmdline Oct 03 16:18:28 maybe my ramconsole patch could help there too? Oct 03 16:18:36 mrmoku: sounds ane Oct 03 16:18:52 sane even Oct 03 16:19:29 * mrmoku tries if it boots with charger connected instead of laptop :P Oct 03 16:19:30 iirc second console= is optional in that kernel will ignore errors on opening it Oct 03 16:19:50 charger should work too Oct 03 16:20:26 * GNUtoo|laptop fetches his n900 Oct 03 16:21:56 GNUtoo|laptop: maybe building bq27x00 not as module? Oct 03 16:21:57 I suspect some weird NOLO pecularity which is messing up things wrt flashing/USB detection etc Oct 03 16:22:23 maybe don't build it at all Oct 03 16:22:27 maybe that's the problem Oct 03 16:22:29 inded Oct 03 16:22:36 charger works too Oct 03 16:22:41 will try without it now Oct 03 16:22:42 I've finally succeeded in building SHR images. I wanted to try to run them in qemu. qemu apparently only supports the GTA-01. But, SHR's root file system is 82Mb. Isn't this too large for a GTA-01? Oct 03 16:22:45 remove bq27 Oct 03 16:22:50 and power supply class Oct 03 16:22:52 very good idea Oct 03 16:23:02 mrmoku: if you could find a way to inject a GPIO4711 = 1, I'd probably be able to find the proper GPIO for you Oct 03 16:23:15 I remember trying it and it still not booting tough Oct 03 16:23:46 btw: https://bugs.maemo.org/show_bug.cgi?id=3745#c12 Oct 03 16:24:57 DocScrutinizer: to make it blink? Oct 03 16:25:02 yup Oct 03 16:25:08 or anything Oct 03 16:25:13 vibrate whatever Oct 03 16:26:16 DocScrutinizer: ok, if leaving out power supply does not work I will try :) Oct 03 16:26:22 I guess you can't talk to I2C that early? Oct 03 16:27:24 (though mere bitbanging I2C shouldn't be hard either, just c&p some 50 lines of code I guess) Oct 03 16:32:08 mrmoku: McSPI2_SIMO Y2 GPT9_PWM directly drives custom IR LED. OK visibility with plain eye is suboptimal, but then every cam usually seeing that IR, and the interface is pretty basic Oct 03 16:32:52 lemme check if I can find something better Oct 03 16:34:50 ok Oct 03 16:35:07 strange it powers off Oct 03 16:35:11 and doesn't reboot Oct 03 16:35:15 I'll check with cable Oct 03 16:36:28 rootfs not found Oct 03 16:36:29 ok Oct 03 16:36:44 I forgott CMDLINE Oct 03 16:37:06 :) Oct 03 16:37:24 * mrmoku dinner first Oct 03 16:38:19 mrmoku: hmm, everything else is quite a bit more involved, from sw pov. next best thing is you could *try* what's happening when you set H26 GPIO_88 DSS_DATA18 to high, and wag CAM_STROBE D25. *Might* trigger flashlight Oct 03 16:39:38 mrmoku: when you're done with all this booting, then don't forget to include fcam drivers with our kernel ;) Oct 03 16:39:54 don't worrky about LEDs, they _should_ switch off automatically after 0.5s iirc Oct 03 16:41:03 but don't forget to kick out fcam gui app, as it does bs to the indicator sysfs nodes :-P Oct 03 16:41:26 nah I guess you wan't include maemo GUI apps to SHR, will you? Oct 03 16:41:37 won't* Oct 03 16:42:17 (above 2 lines are a reply to dos1 's comment, unrelated to booting) Oct 03 16:42:38 DocScrutinizer: no, i don't think so ;) Oct 03 16:43:10 wm.h Oct 03 16:43:16 sorry Oct 03 17:08:06 mrmoku: SLEEP_IND (GPIO_162 W21 McBSP1_CLKX ) may enable keyboard backlight flickering via NSLEEP1 and SYS_CLKREQ Oct 03 17:08:25 DocScrutinizer: ok, did not work :/ Oct 03 17:08:31 (NOLO does that on R&D afaik) Oct 03 17:08:40 DocScrutinizer: now try that Oct 03 17:09:30 SYS_CLKREQ AF25 SYS_CLKREQ Oct 03 17:09:55 NSLEEP1 AF22 SYS_OFF_MODE Oct 03 17:10:14 no idea if those really are GPIO though Oct 03 17:10:28 heh, first I have to find the place to stuff that in :P Oct 03 17:10:39 :-) Oct 03 17:13:42 init/main.c sound like a good place :P Oct 03 17:15:15 :nod: AIUI you can load the kernel via flasher, no? So you have a way to actually test if it's really showing some sign of life, i.e. flashing up some LED Oct 03 17:22:19 yup Oct 03 17:29:03 DocScrutinizer: maybe qi has some code I could use? Oct 03 17:30:12 DocScrutinizer: something like this: http://gitorious.org/0xlab-bootloader/qi-bootloader/blobs/master/src/blink_led.c Oct 03 17:32:09 or better http://gitorious.org/0xlab-bootloader/qi-bootloader/blobs/master/src/drivers/i2c-bitbang.c Oct 03 17:34:00 blink_led.c has maybe 2 lines of code actually useful Oct 03 17:35:22 yeah Oct 03 17:35:39 the name is more interesting thean the content :P Oct 03 17:42:52 hi folks, how's n900 progressing? Oct 03 17:45:26 mickeyl: we're trying to decide which kernel to use Oct 03 17:45:33 well... somehow we decided already :) Oct 03 17:45:39 a) maemo 2.6.28 Oct 03 17:45:43 b) meego 2.6.35 Oct 03 17:45:51 but meego is missing too much things Oct 03 17:46:06 <[Rui]> mickeyl: hurra! you're back! had a nice vacation? :) Oct 03 17:46:19 so GNUtoo|laptop and JaMa|AFK (and somehhow dos1 and me too) would like to go with the old maemo kernel Oct 03 17:46:20 <[Rui]> mickeyl: req n.1: please fix gprs segv :) Oct 03 17:46:33 <[Rui]> seems nobody else found out how to solve it Oct 03 17:47:01 <[Rui]> mickeyl: Serdar also wants to speak with you WRT making a presentation on FSO and OpenMoko for FOSDEM Oct 03 17:47:15 mrmoku: ok, sounds like a) then Oct 03 17:47:33 [Rui]: yes, pretty much. GPRS sigsegv... just on FR or everywhere? Oct 03 17:47:42 [Rui]: ok, will check with serdar Oct 03 17:47:53 <[Rui]> mickeyl: I don't know, let me find the bug # Oct 03 17:48:06 mickeyl: hey! Oct 03 17:48:11 mickeyl: dos1 added proximity and wlan to fsodeviced Oct 03 17:48:20 2.6.28 comes without rfkill for wlan Oct 03 17:48:32 <[Rui]> gprs segv: http://trac.freesmartphone.org/ticket/587 Oct 03 17:48:36 hi dos1 Oct 03 17:48:37 mickeyl: i have a question. in which units should i report ambient light values? Oct 03 17:48:40 mrmoku: wow, cool Oct 03 17:49:10 we can build a nice image for you to start hacking on the modem ;) Oct 03 17:49:13 dos1: i'm afraid on most devices we will not get units, but just min and max Oct 03 17:49:17 mrmoku: excellent ;) Oct 03 17:49:23 dos1: so i'd tend to percentage Oct 03 17:49:31 mickeyl: on n900 there is lux value Oct 03 17:50:21 dos1: cool, but i'm afraid pretty rare Oct 03 17:51:08 we can have a seperate method for Lux, if we really need that kind of precision Oct 03 17:51:15 mickeyl: so what should i do then? assume some max value? (but then how to define that max value?) Oct 03 17:51:47 can you check the maximum the sensor driver will emit? Oct 03 17:51:49 then use that as max Oct 03 17:54:09 ok, i'll check Oct 03 17:55:15 (though that's tricky, as on different devices the same value returned by FSO will mean different things :x ) Oct 03 17:55:31 ? Oct 03 17:55:55 that's an argument for normalizing (i.e. using percentages) and not against, isn't it? Oct 03 17:56:19 mickeyl: yup, but only with sane max values :) Oct 03 17:56:21 -assuming- that most light sensors pretty much cover the same area Oct 03 17:56:22 ;) Oct 03 17:56:28 true Oct 03 17:56:58 next week i'll slowly dive back into work. will update our vala et. al., and then look into the SIGSEGV Oct 03 17:57:03 need to run some errands now Oct 03 17:57:04 cya Oct 03 18:00:08 too bad I missed mickeyl Oct 03 18:00:16 I was eating Oct 03 18:01:14 <[Rui]> mickey|bbl: cya (gaaah... my monthly 5€/75MB gprs already half wasted) :) Oct 03 18:24:33 how can there be any sane max for ambient light values? Oct 03 18:24:53 mrmoku, we should package ofono and the pulse daemon then Oct 03 18:24:54 not to talk about even percentage Oct 03 18:25:23 dos1, on my bug device I've lux Oct 03 18:25:58 DocScrutinizer: thar's what i wondered too Oct 03 18:25:59 DocScrutinizer, any idea for boot? kexec did reboot Oct 03 18:26:03 s/r's/t's/ Oct 03 18:26:05 dos1 meant: DocScrutinizer: that's what i wondered too Oct 03 18:26:07 maybe I should ask in #meego-arm Oct 03 18:26:23 dos1: there's simply no better unit than lux Oct 03 18:26:43 GNUtoo|laptop: why ofono? Oct 03 18:26:44 there's actually no other faintly sane unit than lux Oct 03 18:27:03 mrmoku, because I bet it's necessary for working on the modem Oct 03 18:27:12 and I bet that we could use that Oct 03 18:27:28 maybe with hmmm elektranox(sorry doc) library Oct 03 18:27:29 ? Oct 03 18:27:35 well, I think that is mickey's take Oct 03 18:27:37 or find a way to use ofono Oct 03 18:27:44 mrmoku, ok but you told that: Oct 03 18:27:58 we can build a nice image for you to start hacking on the modem ;) Oct 03 18:28:18 yeah, and I meant an image that boots and has working ssh Oct 03 18:28:26 so he can hack on fsogsmd and try it Oct 03 18:28:30 ah ok Oct 03 18:28:41 not only an image Oct 03 18:28:44 but an oe tree Oct 03 18:28:46 yup Oct 03 18:28:48 where he can build the image Oct 03 18:28:56 we have to start cherry-picking stuff Oct 03 18:29:15 honestly, assuming any arbitrary max of ALS sensor as a 100% is exactly the contrary to a normalization, as every sensor will have another dynamic range Oct 03 18:30:11 so 100% for ambient brightness is even worse than raw hex values Oct 03 18:30:57 GNUtoo|laptop: sorry, absolutely short on ideas about your question regarding boot Oct 03 18:31:05 ok Oct 03 18:31:13 DocScrutinizer, no one ever tried serial? Oct 03 18:31:32 I just know kexec has some issues with OMAP, possibly related to the security architecture Oct 03 18:31:54 ah ok Oct 03 18:32:20 GNUtoo|laptop: jacekowsky did serial console via TP under battery (read only afaik) Oct 03 18:32:29 got logs from NOLO :-) Oct 03 18:33:00 ok Oct 03 18:33:16 were can I find him or the doc he wrote Oct 03 18:33:22 s/doc/docs Oct 03 18:33:26 you need a jig to press pogopins to the TPs, and a level-shifter to convert LV-rs232 to usual +-12V Oct 03 18:33:38 mompls Oct 03 18:34:49 http://cpkb.org/wiki/Nokia_N900_pinout Oct 03 18:35:06 does it have the required voltage to drive a max3232cpe Oct 03 18:36:32 also most important Oct 03 18:36:36 I don't want to solder Oct 03 18:36:43 how do I connect to the testpads Oct 03 18:36:48 ? Oct 03 18:37:22 http://wiki.maemo.org/N900_Hardware_Hacking#Debug_ports Oct 03 18:37:42 GNUtoo|laptop: do you rrad what I post here? Oct 03 18:37:54 [2010-10-03 20:32:16] you need a jig to press pogopins to the TPs, and a level-shifter to convert LV-rs232 to usual +-12V Oct 03 18:38:32 yes of course I read Oct 03 18:38:42 just that I expressed myself badly Oct 03 18:38:51 *I don't want to solder on the testpads Oct 03 18:39:12 *I bet some tape won't work Oct 03 18:39:17 so I wonder Oct 03 18:39:36 http://wiki.maemo.org/N900_Hardware_Hacking/serial_dump Oct 03 18:39:38 what's the way of fisically connecting a piece of cable to a testpad, I don't mean the pinout Oct 03 18:40:28 http://www.fonefunshop.co.uk/Unlocking/servicecableuniversal1.htm Oct 03 18:41:43 in't there a way with some platsitc and some round soldered thin Oct 03 18:41:50 s/thin/tin Oct 03 18:43:00 nope Oct 03 18:43:34 hmmm Oct 03 18:43:43 moreover if I hack something Oct 03 18:43:48 tin is about as bad as it gets, when it's about forming proper touch contacts Oct 03 18:43:57 the pieces could fall into the phone Oct 03 18:44:36 what about an array of pin? Oct 03 18:45:15 those type of contacts always include some spring loaded gold plated thing, usually referred to as pogopins Oct 03 18:45:19 or similar Oct 03 18:46:05 cya, got some RL Oct 03 20:33:26 mrmoku, I've an idea Oct 03 20:33:29 disable CMDLINE Oct 03 20:33:40 that part is bootloader specific etc... Oct 03 20:58:14 hmmm Oct 03 20:58:19 DocScrutinizer, what's that: * Fixes: NB#129918 - kernel/initrd not compatible with latest FIASCOs Oct 03 20:59:04 no idea, NB# is Nokia (internal) Bugtracker Oct 03 20:59:09 ah ok Oct 03 21:00:12 you *might* find something by google, as sometimes they reference to NB# in public changelogs and bugs.maemo.org Oct 03 21:00:22 ok Oct 03 21:00:59 maybe I should try kernel power? **** ENDING LOGGING AT Mon Oct 04 02:59:57 2010