**** BEGIN LOGGING AT Tue Jul 02 02:59:58 2013 Jul 02 04:55:52 build #238 of mcs814x is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/mcs814x/builds/238 Jul 02 06:15:05 build #242 of adm5120 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/adm5120/builds/242 Jul 02 07:20:02 KanjiMonster: I have made a minimal merge to the lantiq-flash, for the iteration over the resources, but I get error: can't request region for resource [mem 0x10000000-0x107fffff] - this is for the second resource Jul 02 07:38:35 KanjiMonster: Also taken the memory allocation part (first part in the loop), Now the flash detection is OK, I have been able to concatenate the MTD devices ;) Jul 02 07:42:06 I still get the error: SQUASHFS error: unable to read id index table Jul 02 07:42:14 then a list of all 6 partitions Jul 02 07:42:28 No filesystem could mount root, tried: squashfs Jul 02 09:29:10 The_Lizard: the filesystem error is expected if you boot a non-ramdisk kernel and never flash any rootfs. Also please put your changes into pastebin or so to be able to review them - without the code it's hard to tell where the issue is Jul 02 09:36:25 blogic r37126 trunk/target/linux/lantiq/patches-3.9/0007-NET-MIPS-lantiq-adds-xrx200-net.patch * lantiq: xrx200_net compile fix Jul 02 09:36:45 blogic r37127 trunk/package/system/ubox/Makefile * ubox: add e2fsck support Jul 02 09:37:04 tripolar: ^ Jul 02 09:37:49 <_trine> http://dpaste.com/1280387/ trunk didnt compile Jul 02 09:38:29 latest trunk ? Jul 02 09:38:34 <_trine> yes Jul 02 09:38:39 [florian]: ^ Jul 02 09:44:45 KanjiMonster: http://pastebin.com/efMQL3dc Jul 02 09:47:20 The_Lizard: now you dts ;) Jul 02 09:47:25 *your Jul 02 09:48:36 http://pastebin.com/dQxGgra1 Jul 02 09:48:41 is the dts Jul 02 09:52:48 looks okay - can you please paste the bootlog, too? Jul 02 09:53:20 hmmm Jul 02 09:54:29 the driver wont handle multiple reg entries i think Jul 02 09:56:21 blogic: thanks - just saw the commit in ubox on nbd.name Jul 02 09:56:52 thanks for the patch Jul 02 09:57:18 my plan is to merge block and mountd into 1 app Jul 02 09:57:18 blogic: but i found a security flow on openwrt - when a user manges to hack any program even when its a noboy user the user is able to call ubus and bring down the interface Jul 02 09:57:30 <[florian]> _trine: did you enable initramfs in your config? Jul 02 09:57:37 a user check or only root can run ubus would be more secure Jul 02 09:57:48 blogic: thanks for the commit :) Jul 02 09:57:58 tripolar: acl will come soon Jul 02 09:58:10 okay Jul 02 09:58:51 also i want to look into a backend for mounting external filesystems Jul 02 09:58:58 like nfs, smb ... Jul 02 09:59:20 you mean something like a nfs root? Jul 02 09:59:23 via a script Jul 02 09:59:24 yeah Jul 02 09:59:36 yeah would be nice Jul 02 09:59:56 but every target needs an running network when doing this Jul 02 10:00:02 at preinit Jul 02 10:00:23 best would be even with the firewall startd... Jul 02 10:00:44 tripolar: minor nitpick to your patches: the version info belongs in the [PATCH] tag; so it should be [PATCH V3] foo, not [PATCH] foo V3 ;) Jul 02 10:00:51 (for next time) Jul 02 10:00:54 luka r37128 trunk/include/kernel-defaults.mk * include: fix path for kernel-generated cpio removal Jul 02 10:02:04 KanjiMonster: okay Jul 02 10:02:22 blogic: https://github.com/ffainelli/openwrt/tree/nfs Jul 02 10:03:50 KanjiMonster block would be more generic and wouldn't need a new kernel Jul 02 10:04:07 could be configured through fstab Jul 02 10:05:07 well, block allows you to just mount a nfs independent of it being / Jul 02 10:05:59 <_trine> [florian], I didnt change anything from last nights build which built ok Jul 02 10:07:48 <_trine> [florian], I think the last build which I compiled was about 7pm BST yesterday Jul 02 10:08:00 <_trine> and that was ok Jul 02 10:08:58 <[florian]> _trine: please answer my question, do you have initramfs enabled in your .config? Jul 02 10:10:22 <_trine> no Jul 02 10:12:31 <_trine> # CONFIG_TARGET_ROOTFS_INITRAMFS is not set Jul 02 10:12:31 <_trine> CONFIG_EXTERNAL_CPIO="" Jul 02 10:13:18 <[florian]> _trine: please send me your .config file Jul 02 10:14:29 <_trine> http://pastebin.com/dr0eGdtc Jul 02 10:15:06 <[florian]> thanks Jul 02 10:34:54 KanjiMonster: sorry for the delay Jul 02 10:34:54 http://pastebin.com/09aCZeUc Jul 02 10:35:07 Had some mechanics connecting new internet connection ;) Jul 02 10:40:15 The_Lizard: looks like your code is working Jul 02 10:40:25 Cool, what is the next step then? Jul 02 10:40:43 the rootfs looks really huge though Jul 02 10:41:00 it actually is, it should be 12 MB or something Jul 02 10:41:18 oh no, even more, Jul 02 10:41:21 no I meant the autocreated partition Jul 02 10:41:45 this is a ~4.5 MiB squashfs acording to the bootlog Jul 02 10:42:32 the 270000 - 460000? Jul 02 10:42:43 ah wait, I can't calculate Jul 02 10:42:50 -ENOCOFFEE Jul 02 10:42:52 yeah Jul 02 10:42:58 forgot to substract the 270000 Jul 02 10:43:02 *coughs* Jul 02 10:43:48 The_Lizard: anyway, you are still booting a non-ramdisk image, that's why its trying to mount the rootfs from the flash Jul 02 10:44:24 I know, but I have no idea which image I would have to run that contains the squashfs image... Jul 02 10:44:38 I have only 4 binaries starting with uImage Jul 02 10:44:50 1 normal, 3 containing -jfs2-xxk Jul 02 10:44:52 The_Lizard: did you enable initramfs in menuconfig? Jul 02 10:45:08 florian r37129 trunk/target/linux/ar71xx/image/Makefile * ar71xx: only invoke Initramfs building when enabled Jul 02 10:45:15 <[florian]> _trine: ^^ should fix your issue Jul 02 10:46:16 where should it be listed? under target images? Jul 02 10:46:35 yes Jul 02 10:46:39 first option Jul 02 10:46:55 it is listed as ramdisk, and yes, it is enabled Jul 02 10:47:08 luka r37130 trunk/package/kernel/gpio-button-hotplug/src/gpio-button-hotplug.c * gpio-button-hotplug: add support for EV_SW Jul 02 10:47:09 luka r37131 trunk/target/linux/ar71xx/files/arch/mips/ath79/mach-wzr-hp-ag300h.c * ar71xx: Buffalo WZR-HP-AG300H (600DHP) change button type Jul 02 10:47:52 then it should generate a initramfs image. But I currently don't have a lantiq tree, so maybe blogic or [florian] chan check if it's supposed to be correctly built ;) Jul 02 10:48:33 I do have vmlinux-initramfs files in my built tree... Jul 02 10:49:21 KanjiMonster: initramfs is not working on lantiq last time i checked, i didnt have time to fix it last night... Jul 02 10:49:30 * luka will look at that later Jul 02 10:49:39 oh, okay Jul 02 10:50:07 <[florian]> even if it did before, it did not properly specify which image was an initramfs and which one was not Jul 02 10:51:14 <[florian]> so in any case it will not to handle initramfs building properly now Jul 02 10:51:22 I could write the root.squashfs file to my nor flash... Jul 02 10:54:53 Currently i'm using the uImage with jffs2-256k, is that ok? Jul 02 10:55:22 I see that both 128 and 256 are equal (in size and contents) Jul 02 10:55:45 <_trine> [florian], I will give it a try Jul 02 10:55:49 <_trine> thanks Jul 02 10:58:36 The_Lizard: the 128/256 has to match the erase block size of the flash you want to write it to - also use squashfs not, jffs2 Jul 02 11:02:16 Ok, I have removed the jffs2 option from the menuconfig, So i only have the normal uImage left Jul 02 11:02:25 is the dtb file required for something? Jul 02 11:04:16 KanjiMonster: I have written the root.squashfs file to my flash @ 0x270000, but I get the same error in the bootlog Jul 02 11:04:51 the dtb is embedded in the kernel, so no Jul 02 11:04:51 <_trine> [florian], it compiles ok now thanks Jul 02 11:05:02 <[florian]> _trine: you are welcome Jul 02 11:13:04 The_Lizard: hm, no idea then. except wait for the ramdisk images to get fixed (or fix them yourself ;) Jul 02 11:13:48 I'd love to, but I really don't have a clue now ;) Jul 02 11:14:27 I will start by updating the wiki for my device for now... so that there is a proper flash layout there ;) Jul 02 11:15:52 nbd r37132 trunk/include/target.mk * build: remove hotplug2 from DEFAULT_PACKAGES Jul 02 11:39:51 KanjiMonster: I have updated the flash layout, I'm uncertain about the mini_fo and overlay parts, but the rest should be OK Jul 02 11:40:01 http://wiki.openwrt.org/toh/arcadyan/vgv7519 Jul 02 11:42:15 The_Lizard: How you changed the bootloader? Could you access the brn-boot administrator mode? Jul 02 11:42:39 No, too bad I couldn't, I have flashed it over with JTAG Jul 02 11:43:08 Hooking up to the serial with 115200/8N1 enables you to access the bootloader. You have to enter three spaces immediately after powerup after which you have to enter some secret password (seems to be 16 characters, but of course I have no idea what it would be… The SHA-1 hash for the password is: 42f25cd06c3e1d7096b35cbd3c3813c23adaf03a Jul 02 11:43:39 It is pretty screwed, as there is a pretty descent protection in place... Jul 02 11:44:24 :( At least you have the router running openwrt. Congratulation! Jul 02 11:44:26 I have managed to hack out the protection, so I could access the loader's menu, but it won't let you overwrite the bootloader Jul 02 11:44:43 Not entirely ;) Jul 02 11:44:57 Currently messing around getting the storage fixed ;) Jul 02 11:45:31 Also I don't have a clue what wireless stuff is in there, so lot's of stuff to do... Jul 02 11:45:52 but you have done a very good advance Jul 02 11:46:46 Yes, thanks to Daniel Schwierzeck, for help with OpenOCD and u-boot, and KanjiMonster, blogic and others for the OpenWRT parts Jul 02 11:47:03 Daniel will post up the patches to his github I guess... Jul 02 11:47:23 As the board has a pretty rare dual nor flash setup... Jul 02 11:48:49 and not to forget, a colleague of mine, who helped me a lot with disassembling the stupid bootloader ;) Jul 02 11:49:16 dual nor flash setup? yes, it's a problem... Jul 02 11:50:02 it is supposed to work for me now Jul 02 11:51:05 then, congratulations for all the people that helped you with the router. Amazing job. Jul 02 11:52:04 So the next thing to do seems to be to fix ramdisk images... Jul 02 11:54:18 step by step, but amazing job Jul 02 11:55:09 luka: do you have any idea when you have time to take a look at it, or point me in the right direction? Jul 02 11:57:14 Pteridium: Would you like to have openWRT on the same router? Jul 02 11:57:45 [florian]: excuse me, is the rtl819x sdk a good start point to port the rtl8672? seems that rtl8198 share the same lexra core Jul 02 11:59:08 The_Lizard: no, the livebox 2.1, but maybe more skilled persons should do it. Jul 02 11:59:28 It seems to be almost the same board right? Jul 02 11:59:41 <[florian]> Pteridium: no idea what's in the latest realtek sdsk these days Jul 02 12:00:05 someone added to the VGV7519 wiki: There seem to be ARV7519RW (aka Livebox 2.1) and ARV7519KW (aka KPN Experia Box v8). Jul 02 12:00:08 The_Lizard: more or less the same board Jul 02 12:00:27 Do you have JTAG access? Jul 02 12:01:31 i haven't the livebox, so i don't know the important stuff Jul 02 12:02:41 if someone is very interested then he will find how to make it works with owrt Jul 02 12:04:10 I guess it is not for the average to add support to a board * and I include myself to the average ppl * Jul 02 12:04:26 I'm an embedded software engineer, but I wouldn't have made it alone... Jul 02 12:04:35 [florian]: here is the sdk. http://sourceforge.net/projects/rtl819x/ GCC 4.1 and kernel 2.6.30 Jul 02 12:05:38 The_Lizard: i'm a simple electronics technician, so i am below the average Jul 02 12:07:01 still need to learn a lot of things about embedded systems, linux and openwrt Jul 02 12:07:32 step by step... Jul 02 12:07:48 <[florian]> Pteridium: porting proper Linux kernel to realtek chips is really really painful Jul 02 12:07:54 <[florian]> as they use these lexra clones Jul 02 12:08:31 <[florian]> maybe not the latest realtek SoCs though Jul 02 12:09:12 [florian]: then i need a huge amount of luck. A lot of thanks for the help Jul 02 12:09:28 <[florian]> Pteridium: luck won't help much here ;) Jul 02 12:09:38 <[florian]> Pteridium: but if you do it step by step you should be able to make it work Jul 02 12:09:52 <[florian]> Pteridium: the toolchain is also a bit of an hassle here Jul 02 12:10:00 <[florian]> since it must not emit the patented instructions Jul 02 12:10:25 <[florian]> Pteridium: this is the "most up to date" that I have for rtl865x: http://alphacore.org/~florian/openwrt/rtl865x-2.6.23-svn-13090.diff Jul 02 12:10:52 <[florian]> which you can probably use the toolchain patches and forward port them Jul 02 12:10:57 <[florian]> as well as the kernel memcpy stuff Jul 02 12:11:10 yes, i've read info about the lexra cores. Jul 02 12:11:50 memcpy seems to be core dependent. am i right? Jul 02 12:12:33 <[florian]> it can, when there are specific SoC/CPU optimizations that make it worth Jul 02 12:12:47 <[florian]> but in the lexra case it is modified because you need to avoir unaligned accesses Jul 02 12:13:12 <[florian]> *avoid unaligned accesses Jul 02 12:13:22 yes, that 4 instructions are the basic problem Jul 02 12:13:42 as you said, step by step Jul 02 12:13:55 <[florian]> first getting a recent toolchain to build their sdk could be a good point Jul 02 12:14:07 <[florian]> then you can start over porting their kernel sources to a more recent 3.10 or something like that Jul 02 12:14:15 <[florian]> and once done, start cleaning up, refactoring Jul 02 12:15:24 i think would be better start with backfire, and once ported move forward Jul 02 12:15:36 i think that's a bad idea Jul 02 12:15:50 <[florian]> I would start with trunk right away Jul 02 12:16:11 btw. in case you need any lexra core docs, i just remembered that they appeared on wikileaks: https://wikileaks.org/wiki/Lexra_CPU_core_documentation Jul 02 12:16:26 <[florian]> nbd: oh, sweet! Jul 02 12:17:16 sadly i don't have enough skills. If i have success with backfire i will be very happy Jul 02 12:18:15 <[florian]> if you are porting to a new hardware, just use what's more up to date Jul 02 12:19:44 yes, the best is to use the more up to date, but my knowledge of this stuff is very very limited Jul 02 12:20:05 more info about lexra Jul 02 12:20:39 http://jonahprobell.com/lexra.html Jul 02 12:20:57 i go to lunch, thanks for your help Jul 02 13:10:36 luka: I can't make sense of the makefiles as the lantiq stuff differs from all the others... I really have no clue what to do to add the initramfs... Jul 02 13:30:56 <[florian]> The_Lizard: ok, let me help you out there Jul 02 13:31:24 <[florian]> The_Lizard: to start with you could use vmlinux-initramfs instead of vmlinux throughout the makefile Jul 02 13:32:54 I might have started to understand a bit... Jul 02 13:34:06 <[florian]> The_Lizard: basically what you need to to is modify each make macro taking vmlinux into taking it vmlinux-initramfs (possibly as a parameter) Jul 02 13:34:17 <[florian]> and ensure that templates using this also pass -initramfs for instance Jul 02 13:35:12 I started to think that way ;) Jul 02 13:35:34 <[florian]> I reckon this is not very straight forward Jul 02 13:35:41 In /target/linux/lantiq/image/Makefile Jul 02 13:35:41 <[florian]> lack of named arguments in GNU make makes it even worse Jul 02 13:35:45 <[florian]> correct Jul 02 13:36:02 I have added a few lines: just below define Image/BuildKernel Jul 02 13:36:41 I added a "," just before the last ), and below I added a ifneq($(CONFIG_TARGET_ROOTFS_INITRAMFS),) Jul 02 13:36:56 with a $(call Image/BuildKernel/Profile/$(PROFILE),-initramfs) Jul 02 13:37:24 so that another call to makeKernel is made, with the -initramfs parameter Jul 02 13:37:38 <[florian]> ok, sounds good Jul 02 13:38:39 But I guess the Image/BuildKernel/Template is not correct yet, as it doesnt add the second parameter to the filename it is copied to... Jul 02 13:38:56 (it does something to check if there is a 2nd argument in the first line I guess... Jul 02 13:40:05 ah, MkImageLzma doesnt pass the second argument Jul 02 13:42:49 * pray * Jul 02 13:45:41 [florian]: Which directory is the output directory? is it /bin or the /build_dir/target-mips....../linux-lantiq-xway Jul 02 13:47:39 <[florian]> bin is the final output directory Jul 02 13:47:45 <[florian]> and the latter is the intermediate output directory Jul 02 13:50:02 so the intermediate dir is the $(KDIR) in the makefiles? Jul 02 13:50:11 <[florian]> right Jul 02 13:52:11 I have an additonal initramfs file, but is just slightly different from the original, is that ok? Jul 02 13:52:33 <[florian]> what do you mean by slightly different? Jul 02 13:53:05 <[florian]> it should be slightly bigger at least Jul 02 13:54:10 I guess the original lzma image has to be made as well ;) Jul 02 13:54:26 it just has a different header Jul 02 13:57:13 I did have a vmlinux-initramfs (and an .elf) file, these have to be compressed to the vmlinux-Board Jul 02 13:57:32 so I have to make sure the initramfs one is made there as well... Jul 02 13:59:06 <[florian]> vmlinux-initramfs is an objcopied elf to binary file Jul 02 13:59:25 <[florian]> vmlinux-initramfs.elf is the real ELF file Jul 02 14:01:06 is there a preference in naming order to which the files should be called? Jul 02 14:01:37 in KDIR i have vmlinux, vmlinux-initramfs and vmlinux-VGV7519NOR Jul 02 14:01:45 what should be the combination of them? Jul 02 14:02:52 <[florian]> you should suffix or make it clear when your kernel/image is initramfs Jul 02 14:02:56 <[florian]> that's the only thing Jul 02 14:23:08 [florian]: I'm having issues with a construction in Image/BuildKernel/Template Jul 02 14:23:41 the $(if $(2),$(2) machtype=$(1),) is bugging me Jul 02 14:28:40 the machtype construction seems to be passedm while i wouldn't expect it Jul 02 14:30:41 And the weird thing is that $(2) isn't used from PatchKernelLzma Jul 02 14:34:01 The_Lizard: the machtype thingy is from pre device tree conversion Jul 02 14:34:15 So it can be eliminated? Jul 02 14:34:47 probably Jul 02 14:34:55 if there's nothing using it Jul 02 15:21:41 Weird, it required a clean to make the thing work... Jul 02 15:22:51 So now I have an initramfs uImage, lets try it out ;) Jul 02 15:29:22 KanjiMonster, [florian], luka: does procd: - init complete - say anything to you ;) Jul 02 15:30:36 You can check out the bootlog on the wiki: http://wiki.openwrt.org/toh/arcadyan/vgv7519#openwrt.bootlog Jul 02 15:31:58 <[florian]> The_Lizard: nice, congrats Jul 02 15:34:32 really thanks to you all... Jul 02 15:35:00 Now up to the next steps... I guess configuring the device... Jul 02 15:50:52 I see a network link on 3 ports (not on the 2 internal PHY's) Jul 02 15:51:31 I am unable to access the device through telnet or ssh Jul 02 15:51:45 while I have entered a password in the serial console Jul 02 15:54:03 KanjiMonster: According to this bootlog, the dual nor construction doesn't work anymore... Jul 02 15:55:18 The_Lizard: maybe you accidentially deleted your changes? did you make your changes in build_dir and cleaned the kernel somewhen inbetween perhaps? Jul 02 15:55:32 oops, yes I did... Jul 02 15:55:50 luckily, all my changes are in pastebin... Jul 02 15:56:08 Where should I place my changes? Jul 02 15:56:51 make it a patch Jul 02 15:58:55 The_Lizard: since lantiq_flash is unmodified in lantiq for current kernels, you can just clone a vanilla linux git and base your patch on that Jul 02 16:05:42 What are the next useful steps? Jul 02 16:07:19 probably make a backup of the flash if you didn't do yet, make pci/wifi work, try to flash squashfs image Jul 02 16:21:32 I already have a complete flash backup, because I want to be able to reverse back to the original firmware when it is not going to work. Jul 02 16:22:28 Apparently I have to do some more things, the external ethernet PHY's work, but the internal don't do yet, but they get their firmware according to the log Jul 02 16:38:49 blogic: The ethernet PHY firmware (the a2x versions) differ from what Daniel Schwierzech has placed in his u-boot lantiq tree Jul 02 17:09:08 ok Jul 02 17:09:16 there are 2 Jul 02 18:19:55 nbd: thanks to blogic and you the arv4518pw and ath5k in AA work perfect. Great job! Jul 02 19:03:07 build #325 of brcm63xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/325 Jul 02 19:08:19 i have a series of devices i made patches for (all the same chip and oem). what type of patch do you prefer upstream? per device or all-in-one? Jul 02 19:09:56 <[florian]> something which is as atomic as possible, so probably per device Jul 02 19:10:04 <[florian]> and if it is upstreamable, send patches upstream too Jul 02 19:10:43 well it's mostly owrt related. the rest is rt2x00 which i tend to proxy through blogic :D Jul 02 19:11:12 <[florian]> oh ok, well yeah that probably works Jul 02 19:12:18 rt2x00 tends to proxy through juhosg ;) Jul 02 19:13:34 didn't know that :D Jul 02 19:44:10 build #321 of at91 is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/321 Jul 02 21:29:20 tripolar r37133 packages/mail/fetchmail/Makefile * [packages] update fetchmail to v6.3.26 Jul 02 21:36:48 build #225 of mpc52xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/mpc52xx/builds/225 Jul 02 21:45:42 build #300 of ramips is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/300 Jul 02 21:49:19 build #279 of rb532 is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/279 Jul 02 21:52:53 build #279 of ppc44x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/279 Jul 02 21:58:19 build #299 of lantiq is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/299 Jul 02 21:59:53 hi Jul 02 22:00:25 when i update a program does it have to work out of the box? i mean dovecot - it's not really possible to provide a default config Jul 02 22:06:55 tripolar: it does not need to have default config Jul 02 22:07:23 maybe i should just package the default config so users can dowload it if needed Jul 02 22:07:31 its ~166kb Jul 02 22:09:09 i'd say users who are going to use dovecot on owrt will know how to configure it Jul 02 22:09:31 so dont bother with the config optimizations Jul 02 22:10:25 just put minimal config file if possible Jul 02 22:10:38 there is no real minimal Jul 02 22:10:44 all needs manual config Jul 02 22:10:57 for example a passdw file is needed Jul 02 22:11:01 at best a new user Jul 02 22:11:09 .... Jul 02 22:11:46 hmm any short hint on how i can access the value of a gpio button when it is handled by gpio-keys-polled? Jul 02 22:12:02 if you want ssl you have to create keys Jul 02 22:15:19 tripolar: i'd leave that to the user Jul 02 22:15:45 i'd put entire config into the package Jul 02 22:17:50 best idea i will do this Jul 02 23:09:53 luka r37134 trunk/target/linux/imx6/config-3.10 * imx6: make kernel_oldconfig Jul 02 23:09:55 luka r37135 trunk/package/ boot/uboot-envtools/Makefile boot/uboot-envtools/patches/115-writing-environment-for-mtd-devices.patch boot/uboot-envtools/patches/110-add-support-for-MTD_ABSENT.patch * [package] uboot-envtools: upgrade to 2013.07-rc1 Jul 02 23:09:56 luka r37136 trunk/package/ boot/uboot-envtools/Makefile boot/uboot-envtools/files/imx6 * [package] uboot-envtools: add support for imx6 target Jul 02 23:14:12 luka r37137 packages/utils/uboot-envtools-mmc/ (7 files in 2 dirs) * [packages] uboot-envtools-mmc: remove package Jul 02 23:15:05 tripolar r37138 packages/net/ git/Makefile git/patches/100-convert_builtin.patch * [packages]: update git to v1.8.3.2 Jul 02 23:24:33 tripolar r37139 packages/sound/cmus/Makefile * [packages] cmus update to v2.5.0 Jul 02 23:58:06 luka r37140 packages/utils/pciutils/ patches/103-relative-path-ids.patch patches/101-no-strip.patch Makefile * [packages] pciutils: update to version 3.2.0 **** BEGIN LOGGING AT Wed Jul 03 01:02:05 2013 Jul 03 01:13:46 luka r37141 trunk/package/utils/usbutils/Makefile * [package] usbutils: upgrade to version 007 Jul 03 01:14:43 build #311 of orion is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/311 Jul 03 01:42:12 build #265 of sibyte is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/265 Jul 03 01:51:05 tripolar r37142 packages/mail/dovecot/ Makefile files/dovecot.init patches/001-configure_in.patch patches/002-example_conf.patch * [packages]dovecot update to v2.2.4 Jul 03 01:52:51 build #315 of brcm47xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/315 Jul 03 01:55:28 build #267 of xburst is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/267 **** ENDING LOGGING AT Wed Jul 03 02:59:57 2013