**** BEGIN LOGGING AT Sun Jan 25 02:59:59 2015 **** BEGIN LOGGING AT Sun Jan 25 03:37:33 2015 Jan 25 04:07:33 swScaler: Compile-time maximum width is 2048 change VOF/VOFW and recompile Jan 25 04:07:36 :( Jan 25 04:08:41 * Maxdamantus is seeing if he can encode from FCam to ffv1 using ffmpeg. Jan 25 04:13:47 Mm, seems to be doing about 1 fps, basically max CPU, I think 850 MHz Jan 25 04:20:00 n900s were never known to be the most speedy cpus... Jan 25 04:22:12 I'm surprised it actually manages 1 fps. Jan 25 04:22:26 by encode from FCam, I mean 2592*1968 frames. Jan 25 04:22:42 (ffv1 is a lossless video format) Jan 25 04:24:58 So essentially compressed 826 MiB of raw UYVY images to 44 MiB. Jan 25 04:25:10 though the images are mostly black in this case :\ Jan 25 04:25:31 can the emmc even write 44MB/sec? Jan 25 04:25:40 It's not 44 MiB/sec Jan 25 04:25:57 That's 44 MiB for 108 frames. Jan 25 04:26:09 which should be about 108 seconds. Jan 25 04:27:09 that makes more sense, a lot slower... Jan 25 04:27:28 Well, the raw data will be about 16 MiB per frame Jan 25 04:27:31 normally when talking about video it's all bitrates Jan 25 04:27:36 which the eMMC probably won't handle. Jan 25 04:27:49 I'm still writing that raw data, 16 MiB/s Jan 25 04:27:52 it's just compressed. Jan 25 04:28:20 16MiB/s is likely doable for the N900's eMMC Jan 25 04:28:35 yes Jan 25 04:28:43 but through the MMC controller it has? Jan 25 04:28:50 I think I topped it out at around 24MiB/s? The OneNAND is way faster at 50-80MiB/s (depending on condition) though Jan 25 04:28:55 44MB/sec is too high Jan 25 04:29:49 Ah, I can read it at 20 MiB/s, at least. Jan 25 04:30:11 I guess writing through a filesystem is just slower. Jan 25 04:31:06 what's the fastest anyone has gotten through the microsd slot? Jan 25 04:31:40 I got 11MiB/s sequential write and 16MiB/s sequential read Jan 25 04:31:42 and actually, it's not 16 MiB/s raw, only 7.6 MiB/s Jan 25 04:32:18 if you get a good enough microSD it should be comparable to the eMMC, they're both connected to the same controller iirc Jan 25 04:32:33 not sure if either/both use parallel mode or not Jan 25 04:33:02 on a side note, >mfw my Note 4's eMMC is faster than my desktop SSD Jan 25 04:33:13 Yeah, I think the bottleneck is usually the controller, not the MMC. Jan 25 04:33:58 * Maxdamantus wants to try making an SD card ring some time. Jan 25 04:34:11 can't seem to find any documentation of anyone actually trying it though. Jan 25 04:34:16 Maxdamantus: >SPI chaining Jan 25 04:34:22 The only evidence I can see of it existinrg is in the SD specification. Jan 25 04:34:55 that's gonna be... fun. Jan 25 04:35:30 Would be pretty cool to be able to buy four 256 GB SD cards and put them in a mugen case. Jan 25 04:35:35 1 TB phone. Jan 25 04:36:05 is SPI breadboardable though? last time I tried a SD hack for my router, there was too much noise on the wires. had to spin a board for it. Jan 25 04:54:41 regarding the NAND being way faster than the MMC, how sensible would it be to use that for swap? Jan 25 04:56:10 * Maxdamantus is basically just using that as a modifiable initramfs. Jan 25 05:20:52 Heh, noticed it said the device was using more CPU than the charger is providing when I ran my thing. Jan 25 05:21:00 er, more power* Jan 25 05:22:26 Maybe it'd be a better idea to just lzop the raw stream. Jan 25 05:46:09 Hm .. futex(0x3aac0, FUTEX_WAIT, 0, NULL^C Jan 25 05:46:22 wonder why that happens while it's meant to be locked. Jan 25 05:46:24 (in fcam) Jan 25 06:07:16 Maybe I need to disable sleep. Jan 25 06:08:01 not actual sleep, but some sort of powersaving mode. Jan 25 06:36:57 Maxdamantus: nand is small Jan 25 06:58:47 kerio: it's still almost as large as the RAM. Jan 25 06:59:04 you want it to be a fuckton bigger Jan 25 06:59:08 so it doesn't get fragmented Jan 25 06:59:24 Also, turns out my battery calibration was wrong. Jan 25 06:59:38 I think. Jan 25 06:59:57 seemed to jump from ~40% to 5%, then die. Jan 25 07:32:29 8/1486 mAh Jan 25 08:49:14 https://drive.google.com/file/d/0B2Ob19L8oYDMcHZnMEI4MWdXb3c/view Jan 25 08:49:25 Need tape .. and to remember to change focus. Jan 25 08:49:40 and probably different exposure or something. Jan 25 08:50:02 (that video is cropped and downscaled) Jan 25 09:56:59 DocScrutinizer: infobot joined! Jan 25 10:53:54 ~seen FatPhil Jan 25 10:53:56 fatphil <~pcarmody@87-119-188-75.tll.elisa.ee> was last seen on IRC in channel #maemo, 59d 19h 33m 24s ago, saying: 'I know I'll get in trouble for asking, but what kernel are you running?'. Jan 25 10:54:00 ~seen FatPhil_ Jan 25 10:54:00 fatphil_ <~pcarmody@87-119-183-129.tll.elisa.ee> was last seen on IRC in channel #maemo-ssu, 493d 14h 5m 45s ago, saying: 'yup, those are the US americans'. Jan 25 11:11:35 Pali: we'd better write an email Jan 25 11:12:10 ok, will you write it? Jan 25 11:12:34 I will, but not now Jan 25 11:13:05 ok Jan 25 11:42:17 anybody using yappari? Jan 25 11:42:23 seems it doesn't workanymore Jan 25 11:43:06 honestly_: check the new thread on TMO Jan 25 11:43:35 TMO? Jan 25 11:43:42 ~tmo Jan 25 11:43:43 methinks tmo is http://en.wikipedia.org/wiki/TMO, or http://talk.maemo.org, or http://de.wikipedia.org/wiki/Terrestrial_Trunked_Radio#TMO. It's *not* T-MO (see ~T-MO) or trolls, morons, oxen. Jan 25 11:44:04 ah. Jan 25 11:45:14 what thread? Jan 25 11:45:36 oh nevermind Jan 25 11:45:39 found it Jan 25 11:47:08 so tl;dr there is a new version but it's not in the normal repo yet? Jan 25 11:47:56 Hm. So does anyone know why fcam (the library) would lag/freeze when the screen turns off? Jan 25 11:48:36 when not connected to USB. Jan 25 11:48:46 obviously something to do with powersaving .. but what exactly? Jan 25 11:48:47 honestly_: it's probably in -devel Jan 25 11:49:05 Maxdamantus: what do you mean by "lag" ? Jan 25 11:52:09 bencoh: well, I don't want to enable -devel and pull in lots of other stuff Jan 25 11:52:27 it might take a few shots, then the process using the library hangs on a futex. Jan 25 11:52:44 honestly_: personally I do apt-pinning Jan 25 11:52:44 and this in the kernel messages: [15704.067108] sbl overflow 00400000 Jan 25 11:53:21 Maxdamantus: taking shots when screen is off using fcam ? Jan 25 11:53:27 bencoh: yes. Jan 25 11:53:29 how do you actually take shots ? Jan 25 11:53:41 (fcam API, or fcamera app ?) Jan 25 11:53:42 fcam is a library and some kernel modules. Jan 25 11:53:45 API. Jan 25 11:53:49 oh, okay :) Jan 25 11:54:06 bencoh: yeah I might try that if I'm not sleep-deprived at some point in the near future Jan 25 12:00:00 Pali: how to attach gdb to qemu? Jan 25 12:00:33 append -S -s to qemu command line Jan 25 12:00:42 ok Jan 25 12:00:45 and in gdb run: target remote localhost:1234 Jan 25 12:00:51 ok Jan 25 12:00:57 you need gdb with armel target compiled Jan 25 12:01:09 BTW I am trying to build qemu with traces enabled, for some reason I see nothing :( Jan 25 12:25:24 Pali: ping Jan 25 12:25:36 freemangordon: pong Jan 25 12:26:00 Pali: in /proc/iomem, there is "02000000-0201ffff : omap2-onenand" Jan 25 12:26:23 what is omap2-onenand? Jan 25 12:28:56 memory range: start=0x02000000 size=0x01000000 is 16MB gpmc for smc91c96 ethernet Jan 25 12:29:12 available only in qemu and development boards Jan 25 12:29:30 range start=0x01000000 size=0x01000000 is 16MB for onenand Jan 25 12:29:35 hmm, this is what I see on the device itself Jan 25 12:29:58 Nokia-N900:/dev# cat /proc/iomem Jan 25 12:29:58 00000000-00000000 : omapflash.0 Jan 25 12:29:58 01000000-0100000f : smc91x Jan 25 12:29:58 02000000-0201ffff : omap2-onenand Jan 25 12:32:12 above info is from n900 DT comments Jan 25 12:32:25 but in u-boot is #define ONENAND_MAP 0x20000000 /* OneNand addr */ Jan 25 12:32:45 so maybe comments in n900 DT linux file are incorrect Jan 25 12:34:30 hm... in qemu 3.19 kernel I see: 04000000-0401ffff : omap2-onenand Jan 25 12:34:37 kernel can remap it?? Jan 25 12:35:09 I can normally mount ubifs in that kernel from rootfs nand Jan 25 12:35:18 so nand is 100% working Jan 25 12:36:42 freemangordon: if kernel say it is onenand it would be onenand... Jan 25 12:37:33 maybe omap iommu can do some magic... Jan 25 12:37:56 Pali: well, ok. Any idea how to dump the bootrom? Jan 25 12:38:10 you can try via /dev/mem Jan 25 12:38:29 open it, mmap needed areay to userspace Jan 25 12:38:32 and try to read it Jan 25 12:38:45 sure, but how? "dd if=/dev/mem of=/home/user/MyDocs/flash bs=4096 count=1" gives me "badd address" Jan 25 12:38:57 oh, mmap Jan 25 12:39:09 or try to use devmem2 Jan 25 12:39:19 (or how is that program called) Jan 25 12:39:32 hmm, iirc I have it somewhere Jan 25 12:41:33 https://github.com/XVilka/htools/blob/master/dump/dump_bootrom.c Jan 25 12:46:23 http://www.droid-developers.org/wiki/Application_Processor_Boot_ROM#Secure_part_of_Application_Processor_Boot_ROM Jan 25 12:47:02 http://www.droid-developers.org/wiki/Booting_chain Jan 25 12:47:04 yeah, nice Jan 25 12:47:20 anyway, I'll try to compile that module Jan 25 12:49:17 in that module are interesting data Jan 25 12:49:21 ROM CODE starts at 0x00014000 Jan 25 12:49:55 yeah Jan 25 12:49:57 if (is_sram_locked) { ... if (omap_type() == OMAP2_DEVICE_TYPE_SEC) rom_boot_size = 0x7000 Jan 25 12:50:40 Nokia-N900:~# ./devmem2 0x00014000 Jan 25 12:50:40 /dev/mem opened. Jan 25 12:50:40 Memory mapped at address 0x4001f000. Jan 25 12:50:40 Value at address 0x14000 (0x4001f000): 0xEA00022E Jan 25 12:50:50 seems I don;t need kernel module Jan 25 12:52:08 ok, module built, lets see :) Jan 25 14:11:29 Pali: bootrom dumped, seems like standart OMAP boot rom, version 14.57 Jan 25 14:11:44 freemangordon: ok Jan 25 14:11:53 and what is at that address called by nolo?? Jan 25 14:12:18 not part of it :D Jan 25 14:12:30 so it is secure part... Jan 25 14:12:37 yeah, maybe Jan 25 14:12:42 can you access that address via devmem2? Jan 25 14:15:22 no, "bus error" Jan 25 14:22:46 freemangordon: this is interesting: http://www.droid-developers.org/wiki/Mbmloader#How_to_know_in_advance_whether_a_given_mbmloader_can_work_on_the_Milestone Jan 25 14:23:23 I bet mbmloader has same header as our xloader (header strucutre where is stored certificate and other data) Jan 25 14:26:18 already checked, the structure is different (we have "NOLO" and "RX-51" things) Jan 25 14:27:00 oh, wait Jan 25 14:27:05 this is different Jan 25 14:30:17 check also http://www.droid-developers.org/wiki/ISW Jan 25 14:32:36 Pali: maybe we should simply brute-force the private key and end this saga :D Jan 25 14:32:55 1024 RSA shouldn't be impossible for distributed brute force Jan 25 14:33:09 can you extract public key? Jan 25 14:33:20 maybe it could be weak :-) Jan 25 14:33:43 the public key is in xloader afaik Jan 25 14:34:53 and it would be different for different hw revision... Jan 25 14:35:19 I doubt Jan 25 14:35:40 we can try to check that sha1 checksum from ASIC id from different hw revisions... Jan 25 14:35:45 as AFAIK this new xloader can be flashed on 2204 for example Jan 25 14:36:02 why then there are different versions of xloader for different hw revisions? Jan 25 14:36:22 NFC, honestly, maybe the HW have special needs Jan 25 14:36:34 but it makes no sense to have different keys Jan 25 14:36:43 see: http://pastebin.com/WYPnsttB Jan 25 14:37:08 2204 has same xloader as 2101 Jan 25 14:37:17 yep Jan 25 14:37:27 but 2301 different Jan 25 14:37:34 but... Jan 25 14:37:44 int the very beginning of xloader is the HW revision Jan 25 14:38:07 need to compare ASIC ID from more n900s... Jan 25 14:38:23 Pali: the easiest way - cat xloader | xxd -ps Jan 25 14:38:29 then diff/meld Jan 25 14:39:48 HW rev is on offset 484 Jan 25 14:41:07 yes, there is hw rev Jan 25 14:41:56 that changes the hash Jan 25 14:42:27 BTW it seems we really have the same ROMBL as droid Jan 25 14:43:10 droid has also hw revision at offset 484? Jan 25 14:43:25 anyway hw revision is also in xloader-qemu.bin Jan 25 14:43:29 not xloader, but ROMBL Jan 25 14:43:52 ROM bootloader that is, the one that is at address 0x14000 Jan 25 14:44:54 ok Jan 25 14:45:41 Pali: http://www.droid-developers.org/wiki/File:Omap_3430_bootrom.idb.gz Jan 25 14:45:55 even the revision at the end is the same Jan 25 14:46:58 not that it helps much, as those unknown foncs are not in rombl Jan 25 14:47:03 *funcs Jan 25 15:00:34 <_jester_> Hello World Jan 25 15:02:06 <_jester_> quick question, nokia n900, flashed, cssu thumb installed. clock/alarms are not working, I get an error libgq-gconf.so.0 is missing Jan 25 15:03:19 where is that error? Jan 25 15:03:24 <_jester_> oh and apt-get install libgq-gconf0 returns, no installation candidate Jan 25 15:03:50 <_jester_> from the gui, it basically never starts, to debug i tried running 'worldclock' from the console Jan 25 15:04:51 hmm, weird Jan 25 15:05:00 ii libgq-gconf0 0.2-5+0m5 a Qt wrapper for GConf Jan 25 15:05:14 <_jester_> oh sorry, apt-get actually returns "libgq-gconf0 is already the newest version Jan 25 15:05:37 <_jester_> actually i think with the new updates, a few old apps are kinda getting broken Jan 25 15:05:44 how did you install cssu-thumb? Jan 25 15:06:18 <_jester_> flashed the n900, clicked on the cssu-thumb link on the maemo.org site Jan 25 15:06:29 <_jester_> installation went smoothly Jan 25 15:06:53 <_jester_> oh and enabled the extra testing repo Jan 25 15:07:59 could you try "ldd /usr/bin/worldclock | grep conf" from the terminal Jan 25 15:08:31 <_jester_> yup Jan 25 15:08:36 <_jester_> give me a minute Jan 25 15:08:53 also, try to start worldclock from terminal Jan 25 15:09:25 <_jester_> i did, thats how i got the error message about the libgq-gconf.so.0 missing Jan 25 15:09:56 did you install anything else but cssu-thumb? like bash or whatnot? Jan 25 15:10:15 <_jester_> i installed a lot of apps Jan 25 15:10:21 :) Jan 25 15:10:53 <_jester_> you think one of the apps messed up the library ? Jan 25 15:11:17 for some reason a library that is in /usr/lib/ can;t be found Jan 25 15:11:23 I guess so Jan 25 15:12:00 <_jester_> cause an "apt-get install --reinstall libgq-gconf0" doesnt work Jan 25 15:12:42 <_jester_> it says its not possible and the package cannot be downloaded, so im assuming its part of the core, as it should be Jan 25 15:12:47 could you try "LD_LIBRARY_PATH=/usr/lib worldclock"? Jan 25 15:12:55 _jester_: enable your okia repos Jan 25 15:12:59 *nokia Jan 25 15:13:05 in HAM Jan 25 15:13:10 <_jester_> ah, youre right, i have those disabled Jan 25 15:13:35 *DO NOT* disable those Jan 25 15:13:49 <_jester_> yes sir ! Jan 25 15:13:52 :) Jan 25 15:14:55 <_jester_> and after enabling them, i should try and reinstall the library ? Jan 25 15:15:11 first try the LD_LIBRARY_PATH trick Jan 25 15:16:47 <_jester_> nopes, i still get the error for the missing libraries Jan 25 15:17:31 try to apt-get install --reinstall Jan 25 15:17:59 though that shouldn;t be needed for a library in /usr/lib Jan 25 15:18:05 unless your flash is broken Jan 25 15:18:19 <_jester_> nopes, just reinstalled it and everything works now Jan 25 15:18:25 weird Jan 25 15:18:33 <_jester_> freemangordon, youre a superstar dude Jan 25 15:18:40 oh, come on Jan 25 15:18:41 :) Jan 25 15:19:02 _jester_: anything in dmesg log? Jan 25 15:19:08 anithing weird that is Jan 25 15:19:13 *anything Jan 25 15:19:49 <_jester_> well you essentially saved me a reflash Jan 25 15:19:49 <_jester_> cause this was annoying the hell out of me Jan 25 15:20:26 yeah, I can imagine Jan 25 15:20:39 <_jester_> nopes, just the usual slider open, wlan0: authenticated messages Jan 25 15:21:29 hmm, weird Jan 25 15:21:40 anyway, good that it works now Jan 25 15:22:08 <_jester_> yea man, thanks a lot ... this is much appreciated Jan 25 15:44:10 vakkov: actually I am not REing NOLO, but xloader. Or rather trying to find what xloader does to enable the AES HW module Jan 25 15:51:14 freemangordon: i see; if someone knows where in NOLO is the hardcoded value (size) of the ram, please do ping me. Jan 25 16:00:29 vakkov: why do you think the RAM size is hardcoded? Jan 25 16:02:22 there is an issue with yappari Jan 25 16:02:30 http://talk.maemo.org/showthread.php?s=f1b8b1b6f0b130fd878d5c7dbaa9232e&p=1458065#post1458065 Jan 25 16:02:48 also a irc channel #yappari Jan 25 16:03:34 as far as i understood Pali i t is hardocded in NOLO and nolo passes it to the kernel via an ATAG. the mainline kernel has it hardcoded though and ignores the atag. but older ones need the atag. freemangordon: Jan 25 16:04:08 freemangordon: ram size is in DT Jan 25 16:04:17 also in board rx51 file Jan 25 16:04:17 zammy: see the other yappari thread Jan 25 16:04:27 (the new one) Jan 25 16:04:28 and also in uboot rx51 include config Jan 25 16:04:35 link me thanks Jan 25 16:04:38 and also nolo pass it in atags Jan 25 16:04:56 zammy: http://talk.maemo.org/showthread.php?t=94465 Jan 25 16:05:08 isn't it possible to just make u-boot change the atag, Pali Jan 25 16:05:26 yes, it is possible Jan 25 16:05:38 uboot does not reuse memory atag from nolo Jan 25 16:05:45 but it read it from uboot rx51 include file Jan 25 16:06:24 but the old kernels do use the atag? so it needs to be changed somehow for them? Jan 25 16:11:21 vakkov: yes Jan 25 16:11:51 vakkov: you have n900 with 512 MB of RAM? Jan 25 16:12:04 vakkov: you can change uboot config Jan 25 16:12:14 and you do not need to modify atags Jan 25 16:12:20 uboot generate them Jan 25 16:12:49 freemangordon: no, they are all stock for now. the plan is to upgrade to 1 gig using the n9 ram+nand chip Jan 25 16:13:05 the nand in n9 and n900 is pin-compatible Jan 25 16:25:27 bencoh what about repository from now to beyond Jan 25 16:26:06 I use the wetransfer link to install yappari 2.0.2 and it' all fine but... repository and future updates? Jan 25 16:26:30 zammy: I'm not ceene, I dont know :) Jan 25 16:26:41 alright Jan 25 16:26:41 he probably didnt have time to push it to -devel Jan 25 16:27:17 "Cepiperez has uploaded changes to the code and a binary here, but latest .deb version is already available for download and is already on the autobuilder, so upgrading should be easily done via HAM in a few hours." Jan 25 16:27:27 if I get it right, it is still not ready to be released in the repos Jan 25 16:27:37 ok Jan 25 16:28:03 * freemangordon does not use it, so doesn't really know Jan 25 16:28:20 * bencoh doesnt either :) Jan 25 16:28:28 but it's not in maemo.org/packages Jan 25 16:28:56 freemangordon: btw, any idea regarding my question on microb (chan next door) ? Jan 25 16:28:57 fuck we are all whatsapp/yappari drugged Jan 25 16:29:09 I meant I don't use yappari/whatsapp at all :) Jan 25 16:32:23 ok anyway thanks to all Jan 25 16:32:59 bencoh: could you repeat your question? was it about kernels 3.x? Jan 25 16:33:30 23:35 < bencoh> bleh, now cc1plus segfaults ... http://pastebin.notk.org/pastebin.php?show=m4336cf71 :/ Jan 25 16:33:33 23:36 < bencoh> freemangordon: which version/tree did you build ? Jan 25 16:33:36 :-) Jan 25 16:33:43 (I got past the js "unable to dump" error) Jan 25 16:33:49 the one on cssu gitorious Jan 25 16:34:03 git://gitorious.org/community-ssu/microb-engine.git ? Jan 25 16:34:06 yep Jan 25 16:34:13 hmm ... then I dont understand Jan 25 16:34:33 you didnt get the cc1plus segfault ? Jan 25 16:34:37 if you build in thumb target, you need to use the thumb-testing branch Jan 25 16:34:48 I build for vanilla Jan 25 16:35:00 then master branch it is Jan 25 16:35:09 no, never seen gcc segfaulting Jan 25 16:35:11 actually for cssu-t, so I reverted the libpng/zlib patches Jan 25 16:35:23 reverted? Jan 25 16:35:28 on a local branch :) Jan 25 16:35:32 libpng and zlib are in cssu-t Jan 25 16:35:39 erm, in cssu-s, mybad Jan 25 16:35:43 oh Jan 25 16:36:07 anyway, gcc should not segfault Jan 25 16:36:34 what linux is that? Jan 25 16:36:39 VM? Jan 25 16:36:43 yeah Jan 25 16:36:59 give it plenty of RAM, like 4GB+swap Jan 25 16:37:04 qemu-kvm on a i686/core2duo Jan 25 16:37:15 I'll try with some swap Jan 25 16:37:27 and ... yeah, more ram as well Jan 25 16:37:49 you'll wait a week, mind you(if it hits the swap) Jan 25 16:37:55 haha Jan 25 16:37:57 true Jan 25 16:38:12 you'd better use SDK vmware image Jan 25 16:38:25 or setup SB in your host linux Jan 25 16:38:48 hmmm, no I dont really want to try SB on a grsec host :) Jan 25 16:39:27 I admit trying to build old mozilla stuff isn't sane behavior, but I'm not *that* crazy :) Jan 25 16:40:06 let's try and give it moar ram Jan 25 16:40:50 qemu: at most 2047 MB RAM can be simulated Jan 25 16:40:51 lol Jan 25 16:44:15 :) Jan 25 16:45:30 you'd better get VMWare SDK image and install LPAE kernel Jan 25 16:47:30 oh btw, did you have to export ARM_FORCE_PLATFORM=v7l ? Jan 25 16:49:57 used mem including buffers/caches never goes higher than 400M (for a total of 2047M) when building it, and it still fails :/ Jan 25 16:50:03 I doubt it's a ram issue Jan 25 16:50:22 never seen that export before Jan 25 16:50:36 you try to cross-compile? Jan 25 16:50:46 dpkg-buildpackage from sb Jan 25 16:50:59 something is broken in your SB install Jan 25 16:51:09 just grab SDK image Jan 25 16:51:32 ~sb Jan 25 16:51:32 extra, extra, read all about it, scratchbox is a cross-compiling system that uses binfmt_misc, rpc calls, and an nfs mount to make a cross-build appear to be 100% native, and is found at http://www.scratchbox.org/, hosted by maemo now. Also at http://maemo.merlin1991.at/files/SB Jan 25 16:51:56 yep, that's it Jan 25 16:52:12 merlin's one Jan 25 16:53:10 freemangordon: at which point did you have to add a symlink for 3.2->2.6 ? Jan 25 16:53:42 after it complained for missing build script Jan 25 16:53:53 but this is not needed in SDK image Jan 25 16:54:05 the thing is ... it didnt complain (yet) here Jan 25 16:54:16 which kernel? Jan 25 16:54:19 3.2 Jan 25 16:54:30 dunno Jan 25 16:54:35 give it some time :) Jan 25 16:54:39 haha Jan 25 16:54:42 it will, most probably Jan 25 16:54:58 yeah I guess you're right about that Jan 25 17:04:28 hi Jan 25 17:04:42 i just realized that the autobuilder for yappari had failed Jan 25 17:04:50 i'm just uploading it again Jan 25 17:04:55 sorry :/ Jan 25 17:09:07 freemangordon: invoking cc1plus manually works .... Jan 25 17:10:34 bencoh: shouldn't be like that Jan 25 17:11:40 yeah I guess so ... Jan 25 17:12:37 * freemangordon gtg Jan 25 17:12:43 bbl, night guys Jan 25 17:12:48 cya, and thx :) Jan 25 22:52:56 Hehe, can now type all printable ASCII characters in u-boot. **** ENDING LOGGING AT Mon Jan 26 02:59:59 2015