**** BEGIN LOGGING AT Tue May 11 02:59:56 2010 May 11 04:26:16 build #51 of gemini is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/gemini/builds/51 May 11 04:45:26 build #47 of kirkwood is complete: Failure [failed compile_4] Build details are at http://tksite.gotdns.org:8010/builders/kirkwood/builds/47 May 11 04:51:04 hello, I want a customized php package with DOM enabled. Any hint how to get this? May 11 05:42:35 build #47 of orion is complete: Failure [failed compile_4] Build details are at http://tksite.gotdns.org:8010/builders/orion/builds/47 May 11 06:45:56 build #50 of goldfish is complete: Failure [failed compile_6] Build details are at http://tksite.gotdns.org:8010/builders/goldfish/builds/50 May 11 07:21:00 build #45 of pxcab is complete: Failure [failed compile_4] Build details are at http://tksite.gotdns.org:8010/builders/pxcab/builds/45 May 11 08:01:36 build #45 of rdc is complete: Failure [failed compile_4] Build details are at http://tksite.gotdns.org:8010/builders/rdc/builds/45 May 11 09:17:53 florian * r21425 /trunk/package/kernel/modules/crypto.mk: [package] hifnHIPP also depends on PCI May 11 12:14:08 Hi, can somebody advise me on the best way to include a kernel image on my root file system? May 11 12:14:28 I want to "ship" my kernel with the root filesystem May 11 12:15:41 Can I just create a package that copies the image onto the rootfs or is the kernel image not build yet at that stage? May 11 12:17:24 Anybody some wild thoughts about this? May 11 12:17:25 thanks May 11 12:21:05 MarkV: it is not possible through a package May 11 12:21:16 MarkV: the kernel is usually stored on a different partition May 11 12:21:41 on most arches there is not even a filesystem in the kernel partition, the file is written raw to flash May 11 12:22:34 MarkV: a quick hack which might work is a symlink in files/ May 11 12:22:40 hmm May 11 12:22:48 but maybe it will only copy the link May 11 12:23:08 won't work either May 11 12:23:18 maybe on x86 May 11 12:23:24 but unlikely May 11 12:23:29 I'm using the x86 architecture. I am using a generic x86 kernel with initrd that is booted by grub. I am using this kernel to kexec() into one of multiple "slots" which contain the actual kernel and rootfs May 11 12:24:20 then ship your rootfs with the kernel image stored somewhere in boot/ or so May 11 12:25:50 I need this construction to be able to implement the required software update specs May 11 12:26:13 using multiple images which are selected by a GPIO input pin state May 11 12:27:10 (I know this is little outside the common owrt usage pattern but I just love owrt) May 11 12:28:07 the only 'hack' I can think of is to unpack the rootfs during image/build, copy the kernel into the unpacked tree and pack it again... May 11 12:28:48 MarkV: can't you simply copy it to the rootfs as a last step of the kernel build? May 11 12:28:52 but I was hoping for a more ethical solution May 11 12:29:38 I tried, but I don's seem to be able to override Kernel/Build from my target/linux/x86/*/target.mk... May 11 12:30:15 I would have to change include/kernel-build.mk or kernel-default.mk for that... Or is there a better way? May 11 12:31:35 rtz2: is that what you mean by your suggestion? May 11 12:32:29 MarkV: that's probably the easiest way May 11 12:33:00 rtz2: thanks, I'll give it a try! May 11 13:46:52 hello May 11 19:20:53 re May 11 19:21:07 rtz2, [florian] any news? May 11 19:21:13 just checking if you got it May 11 19:23:48 alesan: yep, I got it May 11 19:24:17 good May 11 19:24:21 alesan: but I didn't have time to do anything with it yet May 11 19:24:30 I guess you will need some support May 11 19:24:34 like sources drivers etc May 11 19:24:36 right May 11 19:24:44 alesan: do you already have a working linux kernel for it? May 11 19:24:54 do you have a timeframe you think you will be able to give it a look? May 11 19:25:00 rtz2, yes of course May 11 19:25:08 it's a pretty stable platfomr May 11 19:25:21 openwrt porting should be very simple May 11 19:25:34 just a metter of knowing how to port openwrt :) May 11 19:25:47 I can provide you with all details etc May 11 19:25:53 alesan: over the weekend, maybe earlier May 11 19:26:08 ok I will not be in town over the weekend, I will go climbing May 11 19:26:15 no problem May 11 19:26:18 but I can give you most of the stuff you will likely need May 11 19:26:41 alesan: could you send me the kernel patches needed and maybe a datasheet? May 11 19:27:47 alesan: and a contact e-mail, in case I have additional questions May 11 19:28:04 rtz2, datasheet :) May 11 19:28:19 I wish we had one May 11 19:28:25 I'm so ashamed May 11 19:28:33 rtz2, of course, I have your email May 11 19:28:49 I will send everything later today May 11 19:29:17 alesan: well, if you don't have one, I may have more questions :) May 11 19:29:40 well all drivers should be in place anyway May 11 19:29:50 so in theory, a datasheet is not really required May 11 19:30:02 alesan: by the way, do you plan to submit the patch for mainline inclusion? (or did you already) May 11 19:30:27 alesan: I like to play around with stuff May 11 19:32:38 rtz2, I hope so, but right now we haven't proceeded May 11 19:32:51 our kernel is 2.6.19 :( we need to update a lot of stuff May 11 19:33:03 but we are in the process to update May 11 19:34:26 alesan: I will have to port this to a newer kernel anyway May 11 19:34:43 alesan: openwrt doesn't support such an old kernel anymore May 11 19:34:43 you have to? May 11 19:34:58 what is the kernel you will be working with? May 11 19:35:20 I can take care of that actually, I mean we are in that process May 11 19:36:13 alesan: .33 or .34 most likely May 11 19:36:21 alesan: how far along are you? May 11 19:36:42 alesan: heheh now i have questions May 11 19:37:35 rtz2, well May 11 19:37:48 rtz2, let me check with my buddy here that is actually doing the thing May 11 19:38:30 the problem's also we are getting stuff from one of our vendors that is delivering a .27 right now May 11 19:38:47 just a second May 11 19:43:29 jow * r21426 /trunk/package/ppp/files/etc/hotplug.d/atm/20-atm-modem: [package] ppp: convert dos line endings in 20-atm-modem hotplug handler to unix format May 11 19:47:48 build #52 of cobalt is complete: Failure [failed shell_9] Build details are at http://tksite.gotdns.org:8010/builders/cobalt/builds/52 May 11 20:59:32 alesan: did you find out anything? May 11 21:00:26 ok sorry May 11 21:00:32 I have to meet with my buddy right now May 11 21:00:42 before I was called by the boss for something else May 11 21:00:56 I will let you know on email ok? Maybe you have to go to bed now May 11 21:00:59 alesan: no problem May 11 21:01:12 alesan: I will go eat something May 11 21:01:21 ok see you May 11 21:01:23 but May 11 21:01:25 before you go May 11 21:01:47 why, is there a dependency on the kernel version? As long as the "rootfs" can be build I do not see the dep. with kernel May 11 21:02:47 alesan: openwrt has a pretty large number of kernel patches May 11 21:02:59 alesan: and it doesn't have those for .19 anymore May 11 21:03:19 ok, but what are those patches for May 11 21:03:29 aren;t those patches board-specific? May 11 21:03:42 maybe an example will illuminate me :) May 11 21:04:00 alesan: https://dev.openwrt.org/browser/trunk/target/linux/generic-2.6/patches-2.6.34 May 11 21:04:06 that's the list May 11 21:04:17 alesan: most of them aren't needed May 11 21:04:52 alesan: but it would still be extra work to readd a .19 target to the buildsystem May 11 21:05:05 of course May 11 21:05:17 oh squashfs with lzma is not in the mainline kernel yet? what the... May 11 21:05:30 alesan: nope May 11 21:05:36 why May 11 21:05:52 alesan: it nearly made it in for .34 May 11 21:05:59 let me digg it out, one moment May 11 21:06:10 yes but it's years and years people are waiting ! May 11 21:12:13 alesan: crap, I can't find it May 11 21:12:42 alesan: basiacally, the compression lib code is a mess and linus didn't want it spreading further May 11 21:13:43 alesan: anyway, if you send me, what you have now, I can take a look at it and see how far I get May 11 21:14:01 alesan: once I know the code, updating it will be much easier May 11 21:14:06 ok May 11 21:14:10 sorry I had to change network May 11 21:14:19 ok May 11 21:14:23 ok May 11 21:14:26 did you get everything I wrote? May 11 21:14:51 alesan: crap, I can't find it May 11 21:14:59 rtz2> alesan: once I know the code, updating it will be much easier May 11 21:15:04 anything in between? May 11 21:15:43 alesan: basiacally, the compression lib code is a mess and linus didn't want it spreading further May 11 21:15:43 alesan: anyway, if you send me, what you have now, I can take a look at it and see how far I get May 11 21:54:51 so can atheros do routed client/bridging with one radio yet May 11 21:55:01 (ala brcm2.4) May 11 21:56:03 Weedy: routed yes, bridging no May 11 21:56:53 rtz2: so LAN AP with WAN STA and let openwrts firewall do it's thing May 11 21:59:06 Weedy: having both an ap and a sta interface at the same time might not work, but otherwise yes May 11 21:59:21 rtz2: well thats what i mean May 11 21:59:34 i have a routed client working now in 2.4 May 11 21:59:49 is atheros VAPs fixed in openwrt so I can do the same May 11 22:00:26 Weedy: you will have to try May 11 22:00:38 ok **** ENDING LOGGING AT Wed May 12 02:59:56 2010