**** BEGIN LOGGING AT Tue Jul 12 02:59:57 2011
Jul 12 03:29:29 <CIA-89> nbd * r27596 /trunk/package/mac80211/patches/550-ath9k_mmic_verify.patch: ath9k: fix mic frame handling for bigger packets
Jul 12 03:30:54 <CIA-89> nbd * r27597 /branches/backfire/package/mac80211/patches/550-ath9k_mmic_verify.patch: ath9k: fix mic frame handling for bigger packets (backport of r27596)
Jul 12 08:00:04 <CIA-89> loswillios * r27598 /packages/libs/lzo/Makefile: [packages] lzo: update to 2.05
Jul 12 09:03:54 <loswillios> jow_laptop: I think the mtd-utils split has some problems: satisfy_dependencies_for: Cannot satisfy the following dependencies for mtd-utils-flash_eraseall: mtd-utils *
Jul 12 09:04:02 <loswillios> jow_laptop: but there is no mtd-utils anymore
Jul 12 09:46:57 <loswillios> nbd: seems uClibc-0.9.32 is out
Jul 12 10:13:52 <luka12345|wiik> can anybody tell me how to effectively manage kernel patches
Jul 12 10:14:22 <luka12345|wiik> i have been using quilt and that is ok with me; http://wiki.openwrt.org/doc/devel/patches
Jul 12 10:15:19 <luka12345|wiik> but some patches seem to be managed with git, like this one https://dev.openwrt.org/browser/trunk/target/linux/lantiq/patches-2.6.39/601-mach-gigasx76x.patch?format=txt
Jul 12 10:16:10 <luka12345|wiik> and when i use quilt to patch this patch I end with something like this: https://lists.openwrt.org/pipermail/openwrt-devel/2011-July/011586.html
Jul 12 10:17:47 <luka12345|wiik> i would like that I do not end up changing 'headers' of original patch
Jul 12 10:18:38 <luka12345|wiik> is there a way to preserve ---a/... and +++b/... git like diff output with quilt?
Jul 12 10:21:03 <luka12345|wiik> can anyone share a better way to manage kernel patches?
Jul 12 10:35:21 <sekon_> luka12345|wiik: http://manpages.ubuntu.com/manpages/natty/man7/guilt.7.html
Jul 12 11:11:11 <KanjiMonster> luka12345|wiik: do a target/linux/refresh; this will make it "git-like" (with a/... ... b/..)
Jul 12 11:15:51 <jow_laptop> loswillios: mirko did that, and afair I already told him that
Jul 12 11:16:32 <luka12345|wiik> KanjiMonster: thx
Jul 12 11:16:45 <loswillios> ah, ok
Jul 12 11:17:07 <luka12345|wiik> ill try it, i used to do 'quilt diff > path/to/file'
Jul 12 11:17:48 <KanjiMonster> luka12345|wiik: I mean after you put the patch in target/linux/.../patches-<>/
Jul 12 11:18:35 <KanjiMonster> then do a {clean,refresh}, this also takes care of any fuzz when applying the patch (e.g. because you did it against a vanilla kernel)
Jul 12 11:21:22 <luka12345|wiik> KanjiMonster: thx, i'll try it when i get home
Jul 12 11:21:38 <luka12345|wiik> i guess that this can be done for all packages as well
Jul 12 11:21:44 <KanjiMonster> right
Jul 12 11:22:04 <luka12345|wiik> is this prefered way how patches should look like
Jul 12 11:22:11 <KanjiMonster> well, not all packages. any package already having a "patches" directory will fail, e.g. mac80211 ;)
Jul 12 11:23:36 <luka12345|wiik> i guess that has something to do with '-p0' and '-p1' flags in patch command, right?
Jul 12 11:25:17 <KanjiMonster> if the extracted sources contain a "patches" directory it fails, since quilt wants a "patches" directory too, so it overwrites the target's one - might still work if no patch touches the patches, but I'm not 100% sure
Jul 12 11:26:51 <luka12345|wiik> KanjiMonster: thanks for helping :)
Jul 12 11:27:15 <KanjiMonster> luka12345|wiik: yw :)
Jul 12 12:11:52 <loswillios> seems like patchwork doesn't honour the Message-ID for V2 patches
Jul 12 13:38:58 <CIA-89> kaloz * r27599 /trunk/toolchain/gcc/patches/linaro/840-armv4_pass_fix-v4bx_to_ld.patch:
Jul 12 13:38:58 <CIA-89> [toolchain]: In R27118, TARGET_FIX_V4BX_SPEC got lost in the linker parameters.
Jul 12 13:38:58 <CIA-89> Add it back.
Jul 12 13:38:58 <CIA-89> Signed-off-by: Jochen Friedrich <jochen@scram.de>
Jul 12 13:48:55 <CIA-89> kaloz * r27600 /trunk/target/linux/ (8 files in 2 dirs): [generic]: upgrade to 3.0-rc7
Jul 12 17:32:42 <CIA-89> blogic * r27601 /packages/multimedia/minidlna/Makefile:
Jul 12 17:32:42 <CIA-89> Version Bump Minidlna 1.0.20
Jul 12 17:32:42 <CIA-89> Primary changes are adding support for streaming to more hardware.
Jul 12 17:32:42 <CIA-89> Signed-off-by: Ian Leonard <antonlacon@gmail.com>
Jul 12 17:35:16 <Chocky> mooo
Jul 12 17:35:25 * Chocky wiggles blogic for no particular reason
Jul 12 17:35:39 * blogic wobbles
Jul 12 17:37:51 <Chocky> I'm sure I had questions
Jul 12 17:37:57 <Chocky> oh yes.
Jul 12 17:38:00 <Chocky> will later.
Jul 12 20:45:33 <danitool> I can boot the system with the kernel elf image but not with the vmlinux binary
Jul 12 20:45:40 <danitool> what does it mean?
Jul 12 20:53:30 <Chocky> it means your bootloader accepts ELF images
Jul 12 21:03:55 <danitool> yes it always accepted it
Jul 12 21:04:39 <danitool> but also the vmlinux ...
Jul 12 21:05:09 <Chocky> ...
Jul 12 21:05:30 <Chocky> given the almost zero details you've supplied, would you like me to wildly speculate?
Jul 12 21:06:19 <Chocky> you forgot to sacrifice that goat
Jul 12 21:06:33 <danitool> well when the board loads the vmlinux it returns zero details :P
Jul 12 21:06:45 <Chocky> bread board?
Jul 12 21:06:55 <danitool> bcm63xx
Jul 12 21:07:05 <Chocky> http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
Jul 12 21:10:35 <danitool> it's a florian's fault :)
Jul 12 21:10:45 <Chocky> no doubt
Jul 13 01:10:02 <RealOpty> hey
Jul 13 01:11:09 <Chocky> hay
Jul 13 01:11:10 <RealOpty>  target/linux/XXXX/config*
Jul 13 01:13:51 <RealOpty> what processes the file?
Jul 13 01:14:26 <RealOpty> specifically for x86
Jul 13 01:14:37 <RealOpty> trying to add 3.0 support
Jul 13 01:52:54 <RealOpty> cshore, hey
Jul 13 01:53:14 <Chocky> I am not cshore, and won't ever be
Jul 13 01:55:27 <RealOpty> ...
Jul 13 01:56:32 <Chocky> ...
**** ENDING LOGGING AT Wed Jul 13 02:59:56 2011