**** BEGIN LOGGING AT Fri May 13 02:59:58 2011
May 13 05:47:53 <builder_> build #33 of brcm47xx is complete: Exception [exception interrupted]  Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/33
May 13 05:47:53 <builder_> build #32 of atheros is complete: Exception [exception interrupted]  Build details are at http://buildbot.openwrt.org:8010/builders/atheros/builds/32
May 13 05:47:55 <builder_> build #32 of cobalt is complete: Exception [exception interrupted]  Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/32
May 13 05:47:57 <builder_> build #31 of orion is complete: Exception [exception interrupted]  Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/31
May 13 06:09:03 <CIA-89> cshore * r26879 /trunk/target/linux/x86/ (Makefile generic/profiles/Alix.mk image/Config.in): (log message trimmed)
May 13 06:09:03 <CIA-89> This patch provides an image suitable for the alix2*, alix3, and alix6 headless (non-VGA equipped) SBC's.
May 13 06:09:03 <CIA-89> Note that the Alix6 uses GPIO 27 to disable wireless transmit (W_DIS#), whereas on all other versions this is used to actuate the speaker.
May 13 06:09:03 <CIA-89> GPIO 1 : SIM select (Alix6)
May 13 06:09:03 <CIA-89> GPIO 6 : LED1
May 13 06:09:03 <CIA-89> GPIO 25 : LED2
May 13 06:09:04 <CIA-89> GPIO 27 : LED3 or RFKILL (Alix6)
May 13 06:11:10 <CIA-89> cshore * r26880 /trunk/target/linux/x86/alix2/ (. config-default target.mk): (log message trimmed)
May 13 06:11:10 <CIA-89> Add missed files from previous commit: This patch provides an image suitable for the alix2*, alix3, and alix6 headless (non-VGA equipped) SBC's.
May 13 06:11:10 <CIA-89> Note that the Alix6 uses GPIO 27 to disable wireless transmit (W_DIS#), whereas on all other versions this is used to actuate the speaker.
May 13 06:11:10 <CIA-89> GPIO 1 : SIM select (Alix6)
May 13 06:11:11 <CIA-89> GPIO 6 : LED1
May 13 06:11:11 <CIA-89> GPIO 25 : LED2
May 13 06:11:11 <CIA-89> GPIO 27 : LED3 or RFKILL (Alix6)
May 13 06:34:01 <CIA-89> jow * r26881 /packages/net/openvpn/ (Makefile files/openvpn.init): [packages] openvpn: stop instances even if they are disabled (#9404)
May 13 07:25:31 <CIA-89> cshore * r26882 /trunk/target/linux/x86/generic/profiles/Alix.mk: [x86] Removed Alix.mk profile which was accidently left as an empty file applying the patch during r26879 and r26880.
May 13 07:26:24 <builder_> build #31 of pxcab is complete: Failure [failed compile_3]  Build details are at http://buildbot.openwrt.org:8010/builders/pxcab/builds/31
May 13 07:41:29 <builder_> build #25 of au1000 is complete: Exception [exception compile_3 shell_13 compile_12]  Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/25
May 13 07:41:30 <builder_> build #30 of ppc40x is complete: Exception [exception interrupted]  Build details are at http://buildbot.openwrt.org:8010/builders/ppc40x/builds/30
May 13 07:41:32 <builder_> build #30 of rb532 is complete: Exception [exception interrupted]  Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/30
May 13 07:41:34 <builder_> build #29 of ppc44x is complete: Exception [exception interrupted]  Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/29
May 13 08:18:40 <builder_> build #35 of brcm63xx is complete: Exception [exception shell compile_3 shell_13 compile_12]  Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/35
May 13 08:18:40 <builder_> build #21 of gemini is complete: Exception [exception interrupted]  Build details are at http://buildbot.openwrt.org:8010/builders/gemini/builds/21
May 13 08:18:42 <builder_> build #21 of rdc is complete: Exception [exception interrupted]  Build details are at http://buildbot.openwrt.org:8010/builders/rdc/builds/21
May 13 08:18:44 <builder_> build #29 of uml is complete: Exception [exception interrupted]  Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/29
May 13 09:12:51 <lauri> Good mornin guys
May 13 09:13:14 <lauri> I'd like to get some patches merged upstream :)
May 13 09:13:19 <lauri> https://lists.openwrt.org/pipermail/openwrt-devel/2011-May/010892.html
May 13 09:13:30 <lauri> https://lists.openwrt.org/pipermail/openwrt-devel/2011-May/010904.html
May 13 09:23:13 <blogic> lauri: let me have a look
May 13 09:24:18 <blogic> lauri: tmp/.config-package.in:8830:warning: 'select' used by config symbol 'PACKAGE_cmus' refer to undefined symbol 'PACKAGE_libiconv-full'
May 13 09:24:21 <blogic> ?!
May 13 09:25:03 <jow_laptop> blogic: how recent is your feed?
May 13 09:25:22 <jow_laptop> blogic: and your buildroot?
May 13 09:25:47 <blogic> trunk is recent
May 13 09:25:53 <blogic> packages folder apparently is outdated ;)
May 13 09:26:14 <blogic> cmus seems to be in there already
May 13 09:26:58 <jow_laptop> indeed
May 13 09:27:13 <blogic> ;)
May 13 09:27:19 <jow_laptop> oh that was even me
May 13 09:27:27 <blogic> shall i close it in oatchwork for the commiter ?
May 13 09:27:33 <jow_laptop> must have done that when going through patchwork
May 13 09:27:36 <jow_laptop> yes
May 13 09:27:44 <blogic> ;)
May 13 09:27:46 <blogic> closed
May 13 09:27:51 <blogic> lauri cmus is already in trunk
May 13 09:28:03 * blogic will do all the small patches that add udhcpc and dnsmasq options today
May 13 09:30:20 <lauri> blogic: cmus != mocp
May 13 09:31:41 <blogic> ?
May 13 09:31:53 <blogic> that patch you posted added a folder that was already there
May 13 09:32:23 <blogic> ok, wrong link ;)
May 13 09:33:11 <blogic> lauri: those patches are not in patchwork
May 13 09:33:24 <lauri> blogic: uhm?
May 13 09:33:52 <blogic> http://patchwork.midlink.org/project/openwrt/list/
May 13 09:35:34 <lauri> blogic: Interestingly this is the first time I hear about this website :D
May 13 09:35:39 <blogic> hehe
May 13 09:35:43 <blogic> well its the old link
May 13 09:35:56 <lauri> I just attached patches to e-mails
May 13 09:35:59 <jow_laptop> it automatically scrapes patches from the list
May 13 09:36:01 <blogic> patchwork.openwrt.org
May 13 09:36:20 <lauri> appearently Gmail screws up my e-mails
May 13 09:36:21 <blogic> jow_laptop:  does patchwork require inline ?
May 13 09:36:22 <jow_laptop> if your patches do not appear there, something was wrng with the mails
May 13 09:36:26 <blogic> yes
May 13 09:36:50 <lauri> jow_laptop: mailinglist should extract *.patch attachments right?
May 13 09:36:58 <lauri> and send them to patchwork?
May 13 09:37:16 <jow_laptop> it should, yes
May 13 09:37:36 <jow_laptop> from a parsers pov, inline patches and attached patches are little difference
May 13 09:37:59 <jow_laptop> however maybe your attachments got base64 encoded or something
May 13 09:38:02 <lauri> so I could just copy-paste the patch into my e-mail and it should be detected?
May 13 09:38:38 <jow_laptop> yes but then you have to take care of not screwing up whitespace (tab, space) and line breaks
May 13 09:40:22 <lauri> arrrgh @ gmail
May 13 09:41:21 <lauri> does it detect let's say diff.gz?
May 13 09:41:27 <jow_laptop> no
May 13 09:41:33 <jow_laptop> I doubt that
May 13 09:41:43 <lauri> what could I try?
May 13 09:42:25 <jow_laptop> I don't know
May 13 09:42:29 <jow_laptop> I don't use google
May 13 09:42:33 <jow_laptop> -mail
May 13 09:44:52 <blogic> ask google ?
May 13 09:45:00 <blogic> i am sure that gmail will let you post patches
May 13 09:45:20 <blogic> or send the patch via git
May 13 09:46:56 <lauri> via git?
May 13 09:47:26 <blogic> http://www.kernel.org/pub/software/scm/git/docs/git-send-email.html
May 13 09:49:25 <lauri> I'm gonna try with a local e-mail client first
May 13 09:59:34 <lauri> blogic: http://patchwork.openwrt.org/patch/986/ I got lucky
May 13 10:02:11 <blogic> yes
May 13 10:02:18 <blogic> just answered your mail
May 13 10:03:00 <blogic> lauri: elt me do that in a bit
May 13 10:03:08 <blogic> justr strated something else
May 13 10:04:54 <lauri> no problem
May 13 10:06:20 <lauri> Arrgh patchwork handles only one patch at once?
May 13 10:17:59 <blogic> lauri: just keep resending till you worked it out
May 13 10:18:08 <blogic> we can always drop stuff from patchwork
May 13 10:21:37 <lauri> okay I got them submitted tools & targets separately though
May 13 10:22:03 <[florian]> lauri: submitting patches guide suggset you send multiple emails with one patch per email
May 13 10:23:28 <lauri> now it's a bit too  late for RFTM :D
May 13 10:29:07 <lauri> I admit that I should've read that
May 13 10:35:14 <lauri> blogic: http://patchwork.openwrt.org/patch/987/ http://patchwork.openwrt.org/patch/988/
May 13 10:35:26 <lauri> or anyone else for that matter :)
May 13 10:39:02 <CIA-89> hcg * r26883 /trunk/target/linux/omap35xx/image/Makefile: [omap35xx] Squash uids
May 13 10:58:02 <KanjiMonster> lauri: use a mail client for sending from google; e.g. git send-email works for me fine ;)
May 13 11:52:13 <CIA-89> hcg * r26884 /trunk/target/linux/omap35xx/gumstix/ (defconfig.es profiles/002-es.mk): [omap35xx]: Add new defconfig and profile for es variant
May 13 11:54:37 <^Willie^> hmm hope that i get my profilic pl2303 cable working this afthernoon :S
May 13 11:55:01 <CIA-89> hcg * r26885 /trunk/scripts/remote-gdb: Correct libc path
May 13 11:55:47 <^Willie^> no pinouts of those siemens c55 cables i have here.. and the rusian doc's are based on a diffrent type..
May 13 11:57:45 <blogic> ^Willie^:
May 13 11:57:47 <blogic> ^Willie^: http://public.perdmann.de/blog/siemens_datenkabel.gif ?
May 13 11:58:09 <^Willie^> ehh. moment looking right now
May 13 11:59:02 <^Willie^> ahh but i got just the bare pcb here ;)
May 13 11:59:20 <blogic> ok
May 13 12:00:05 <^Willie^> i got this one including vreg and switch http://bird40.at.tut.by/PL-2303-plata.jpg
May 13 12:00:43 <^Willie^> afther digging the data sheets looks like the switch is used for selecting 3/3.3/5v operation based on target vcc or internal 3.3v
May 13 12:05:22 <^Willie^> also must have some 3232's somewhere around anyway. but those cables are easyer to use ;)
May 13 12:06:04 <blogic> ok
May 13 12:06:06 <blogic> there are 4 pads
May 13 12:06:13 <blogic> 1234 on the horizontal on the top
May 13 12:06:18 <blogic> do you know which i mean ?
May 13 12:06:52 <^Willie^> on this image right side inner row is market as pad 1 till 4 indeed
May 13 12:07:16 <blogic> yes
May 13 12:07:19 <blogic> 1 is VCC
May 13 12:07:25 <^Willie^> my plan was grab the multi meter and start lookich wich pin is connected to pin 1 and wich to pin5 on the 2303 chip..
May 13 12:07:45 <^Willie^> pin 1 must be tx and 5 rx
May 13 12:08:23 <blogic> 2/5 are rx/tx i guess
May 13 12:08:35 <blogic> is this a default subd pinout maybe ?
May 13 12:08:54 <^Willie^> hmm 1 is the vcc pin used for auto detect target vcc indeed if the switch is installed and set right indeed.
May 13 12:09:05 <^Willie^> hmm i guessed this can be default sub-d pinout yes.
May 13 12:09:27 <^Willie^> do not trust on that guess so will test first ..
May 13 12:10:01 <blogic> hehe
May 13 12:10:12 <blogic> 1 would say 1 is vcc and 9 gnd looking at the pcb
May 13 12:10:22 <blogic> the others all directly connect the the prolific
May 13 12:10:26 <^Willie^> hmm do have the chips datacheet including pinouts.. quick fix will be testing with the fluke..
May 13 12:10:33 <blogic> so grap the prolofic datasheet and check what pin is which
May 13 12:10:40 <^Willie^> 1 tx 5 rx.
May 13 12:11:07 <^Willie^> looks like pin 3 and one of those between 5 and 8..
May 13 12:11:12 <blogic> google for "pl-2303 filetype:pdf"
May 13 12:13:03 <^Willie^> ahh almosth the same datasheet as i have but then the right version.
May 13 12:13:42 <^Willie^> blogic: hmm btw have you ever heared any reports about inverted signals from these 2303's ?
May 13 12:13:55 <blogic> nope
May 13 12:14:01 <blogic> i normally use a ftdi ;)
May 13 12:14:05 <^Willie^> datasheet info looks like regulair rs232 with ttl support
May 13 12:14:13 <blogic> they are more stable for me
May 13 12:14:19 <^Willie^> hmm ftdi is not so easy to find.. only those conrad cords.
May 13 12:14:31 <^Willie^> or the bare chip for 7 eur..
May 13 12:15:01 <^Willie^> but is indeed mutch more feature rich .. pl2303 can't be used for jtag programming.
May 13 12:15:33 <blogic> http://www.ic-board.de/product_info.php?info=p29_USB-A-UART-Bridge.html
May 13 12:15:37 <blogic> i use that one
May 13 12:16:18 <blogic> or
May 13 12:16:29 <^Willie^> looks ready to use
May 13 12:16:35 <blogic> that is cp2102
May 13 12:16:52 <blogic> the ftdi one i use is a clone of the moko debug board
May 13 12:17:08 <blogic> and that has the ftdi 2232 with jtag + serial
May 13 12:18:21 <^Willie^> hmm for jtag i do have a lpt hc244 board.. and somewhere a max3232 prototype but nowdays usb 232 cords are mosthly easyer then regulair serial port
May 13 12:18:35 <^Willie^> at least if those cables are prepared for the job
May 13 12:18:50 <blogic> yep
May 13 12:18:58 <blogic> the ftdi jtag solution works well
May 13 12:19:04 <blogic> if you have a good board ;)
May 13 12:19:49 <^Willie^> hmm never tested that solution still not have a ftdi based dongle here.. have seen a few that *posible* can be used as jtag dongle over the subd bus.. but i don't expect them to work indeed
May 13 12:20:12 <^Willie^> those ready to use usb -> subd 9pin 232 cords/cables
May 13 12:21:28 <blogic> http://www.amontec.com/jtagkey-tiny.shtml
May 13 12:21:31 <blogic> works very well
May 13 12:22:06 <^Willie^> ahh price is also mutch better then wat i have seen before :)
May 13 12:23:13 <^Willie^> but for my ubicom platform i don't need jtag anyway.
May 13 12:23:23 <^Willie^> tftp and webif work well.
May 13 12:24:00 <^Willie^> iirc some screen shots will be nice as better explanation how i manage that.
May 13 15:54:09 <builder_> build #34 of s3c24xx is complete: Failure [failed compile_10]  Build details are at http://buildbot.openwrt.org:8010/builders/s3c24xx/builds/34
May 13 17:54:38 <builder_> build #31 of lantiq is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/31
May 13 18:28:17 <CIA-89> blogic * r26886 /packages/multimedia/mocp/ (. Makefile): [packages] mocp: adds Music On Console player
May 13 19:04:48 <CIA-89> mhei * r26887 /packages/lang/php5/Makefile: [packages] php5: add gettext module
May 13 20:49:24 <swalker> blogic: shouldn't have mocp landed in the sound dir rather than multimedia?
May 13 20:50:10 <xMff> I think we should merge sound into multimedia
May 13 21:44:11 <builder_> build #23 of etrax is complete: Failure [failed compile_3]  Build details are at http://buildbot.openwrt.org:8010/builders/etrax/builds/23
May 13 22:23:43 <builder_> build #22 of ep93xx is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/22
May 13 22:37:27 <builder_> build #21 of mpc52xx is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/mpc52xx/builds/21
May 14 00:30:52 <CIA-89> jow * r26888 /branches/backfire/toolchain/uClibc/ (3 files in 3 dirs): [backfire] uclibc: backport strverscmp(), versionsort() and versionsort64() from uClibc git, required by at least alsa-lib
**** ENDING LOGGING AT Sat May 14 02:59:58 2011