2011-08-11 01:42 <qi-bot> [commit] Ayla: Read config file(s) present on both system and user-specific directories. (master) http://qi-hw.com/p/gmenu2x/3d3e0fa
2011-08-11 01:42 <qi-bot> [commit] Ayla: Set card root to /media by default for the Dingux port. (master) http://qi-hw.com/p/gmenu2x/4fd4b23
2011-08-11 02:06 <aw> rc3: regards to power-cycling of rendering failure, I am going to use 'replug the dc adapter male plug' not to switch power cord to see if secrets behind. ;-)
2011-08-11 02:07 <xiangfu> aw, :)
2011-08-11 02:07 <aw> rc3: just have that a little times of feeling on this without firm data, but worthy to see if difference existed.
2011-08-11 02:08 <aw> regards to great email from Werner about Full speed on usb host, I'll try that after my this round( get all vga/midi/usb done firstly). ;-)
2011-08-11 03:07 <rjeffries> image processing pr0n http://diydrones.com/profiles/blogs/new-image-sensor-chips-for-robotics-and-embedded-vision
2011-08-11 03:19 <aw> the method of input of power-cycling is dependent to rendering fail since just got @7th on 0x6b, before this board, I tested successfully 0x56, 0x5e.
2011-08-11 03:21 <aw> sorry that corrected last sentences is 'independent'
2011-08-11 04:01 <rjeffries> .
2011-08-11 04:38 <rjeffries> quote: "
2011-08-11 04:38 <rjeffries> A smartphone might involve as many as 250,000 (largely questionable) patent claims,"
2011-08-11 04:38 <rjeffries> http://googleblog.blogspot.com/2011/08/when-patents-attack-android.html
2011-08-11 04:49 <larsc> so what do we learn from this? never try to build and distribute a smartphone
2011-08-11 04:50 <rjeffries> larsc i don't know the number of potential patents is mind-boggling
2011-08-11 04:53 <kristianpaul> larsc: not sell it with android i would think :)
2011-08-11 04:54 <larsc> kristianpaul: so you think those patents only apply to android?
2011-08-11 04:56 <kristianpaul> larsc: sure not, but i dont started the patent troll 
2011-08-11 05:00 <kristianpaul> i'm new on this field, but i'm sure is not the first time apple/microft  acude to litigation when they feels their IP spectrum is not enought to control a "market" 
2011-08-11 05:02 <kristianpaul> also if we want to ignore other not so know lawsuits related to smartphone (not that i know of, but i guess there are)
2011-08-11 05:03 <kristianpaul> so if we as a copyleft dont call that atention that lot well.. there is some safety
2011-08-11 05:04 <kristianpaul> like promoting milkmist is a gpu that can beat nvidia.. and such..
2011-08-11 05:04 <kristianpaul> imho
2011-08-11 05:08 <kristianpaul> fighting against wpa2/wifi and hostapd and posible ath5k driver issues :S ?
2011-08-11 05:08 <kristianpaul> arghh
2011-08-11 06:51 <aw> 0x66 test histories: 1. usb – A without reply, replaced a new U16 then pass(with CRC check) 2. tested CRC failed after replaced u7/u19/u20. 3. reflashed again successfully, http://downloads.qi-hardware.com/hardware/milkymist_one/production/rc3/test_results/66-reflash-results-1 4. tested successfully
2011-08-11 06:53 <aw> first time I got an CRC failure. :-) see test logs: http://downloads.qi-hardware.com/hardware/milkymist_one/production/rc3/test_results/66-results
2011-08-11 06:54 <aw> interesting on 0x66. ;-)
2011-08-11 06:56 <aw> the image CRC has failed in 'Checking : flickernoise.fbi(rescue)(CRC)CRC failed (expected aa12a56a, got 92968609)'
2011-08-11 07:48 <wpwrak> aw: (0x66) did you reflash after replacing u7/u19/u20 ? or was that the same flash content that worked before (and then failed) ?
2011-08-11 08:16 <aw> wpwrak, after replacing u7/u19/u20, i tested then got CRC failed. so I then reflashed it again and show without CRC err.
2011-08-11 08:21 <aw> wpwrak, before replacing u7/u19/u20, I still used test image with CRC checking, and no err; at that time I tested a new U16 usb transceiver.
2011-08-11 08:24 <aw> wpwrak, good now I just got 0x64 with CRC err. at 'Checking : standby.fpgCRC failed (expected c58e8905, got ac858cbf)'
2011-08-11 08:24 <wolfspraul> aw: hey :-) how is the testing going?
2011-08-11 08:25 <aw> new condition on CRC err I met on 0x66, you can see the logs
2011-08-11 08:26 <aw> now I just got 0x64 with standby CRC failed....;-)
2011-08-11 08:27 <aw> http://downloads.qi-hardware.com/hardware/milkymist_one/production/rc3/test_results/64-results
2011-08-11 08:28 <aw> this log was done by last first round by shorter cable
2011-08-11 08:28 <wolfspraul> did you upload the latest testing results?
2011-08-11 08:29 <wolfspraul> I am most interested in one category of boards: those that performed rendering fine, but then after X power cycles, stopped rendering
2011-08-11 08:29 <wolfspraul> do we have such cases?
2011-08-11 08:29 <aw> now I was going to test it after replacing u/7u/19/u20, then got CRC err with new test image
2011-08-11 08:29 <aw> wolfspraul, not yet updated this 0x64 test log
2011-08-11 08:32 <aw> updated 0x64: http://downloads.qi-hardware.com/hardware/milkymist_one/production/rc3/test_results/64-results
2011-08-11 08:32 <aw> now going to reflash it again.
2011-08-11 08:33 <wolfspraul> aw: 31 boards 'available' now
2011-08-11 08:33 <wolfspraul> hmm
2011-08-11 08:33 <wolfspraul> I mean cases like 0x6B
2011-08-11 08:34 <aw> I've not finished 2nd round tests about vga/midi/usb reworks, the 'available' qty should be a little more later.
2011-08-11 08:35 <wolfspraul> ok
2011-08-11 08:35 <wolfspraul> but I think there are boards that first rendered, and then stop reconfiguring
2011-08-11 08:35 <aw> for me, no idea to care cases about 0x6B while 2nd round tests. sorry..i just recorded first
2011-08-11 08:35 <wolfspraul> makes sense
2011-08-11 08:35 <wolfspraul> yes, finish the complete round first
2011-08-11 08:35 <wolfspraul> then we look at the numbers
2011-08-11 09:01 <wpwrak> aw: when you get a CRC error, do you always reflash ? or did you try a few times to see if the board will pass the CRC check without reflashing ?
2011-08-11 09:03 <aw> wpwrak, yes, now I just reflash it, not try few times to see if the board will pass.
2011-08-11 09:04 <aw> later if i found it again. i can try to do a few times to see if pass. ;-)
2011-08-11 09:04 <wpwrak> aw: yes, the next time you hit a CRC error, it would be good to try a few times. if the CRC error goes away (or changes), then it's a problem of the flash itself
2011-08-11 09:05 <wpwrak> aw: if the CRC error stays, then it's flash corruption
2011-08-11 09:08 <aw> wpwrak, seems understood from your analysis on either 'flash corruption' or 'flash itself', good. thanks. i missed a good chance to know a firm hard data we can get. :(
2011-08-11 09:09 <wpwrak> aw: it seems that the CRC error happens often enough that you'll have plenty more opportunities :)
2011-08-11 09:11 <aw> wpwrak, hope I meet it again, good also bad. ;-)
2011-08-11 09:12 <wolfspraul> looking at the results overall right now I think things are starting to look much better
2011-08-11 09:12 <wolfspraul> especially after Adam continues to fix the vga/midi/usb cases that are probably all fixable easily
2011-08-11 09:12 <wpwrak> wolfspraul: let's not praise the day before the CRC error :)
2011-08-11 09:13 <wolfspraul> then we are down to flash and render/reconfig issues, which may all end up with the same root cause
2011-08-11 09:13 <wolfspraul> oh there will be flash & render/reconfig issues, and they have to be resolved
2011-08-11 09:13 <wolfspraul> there are way too many boards now that start falling into non-reconfigurable mode after 2, 5, 9 etc. times rendering, which is totally unacceptable
2011-08-11 09:14 <wolfspraul> but Adam is right, first finish _all_ reworks around usb/midi/vga, then look at the data
2011-08-11 09:14 <wolfspraul> aw: did I understand your plan correctly?
2011-08-11 09:15 <wpwrak> i'd just oportunistically try to reproduce a CRC error when one occurs. beats finishing everything else and then having to spend days trying to reproduce the error, which will then of course hide
2011-08-11 09:16 <aw> wolfspraul, you did.
2011-08-11 09:19 <wolfspraul> aw: when you do the render cycle testing, how do you do the power cycling? do you just unplug the DC jack from the running system?
2011-08-11 09:19 <wolfspraul> or do you shutdown m1 with the menu in the gui?
2011-08-11 09:21 <aw> wolfspraul, before today, i always switched my power cord to disconnect the 110V AC, I doubted through this way this morning, so I unplugged the DC male jack instead, but still got 6B rendering failure.
2011-08-11 09:22 <wolfspraul> but in both cases we suddently withdraw current
2011-08-11 09:22 <wolfspraul> suddenly
2011-08-11 09:22 <xiangfu> DocScrutinizer2, I got the little usb grab device recording the video now.
2011-08-11 09:22 <xiangfu> wpwrak, ^
2011-08-11 09:23 <wolfspraul> should not be much difference from the board's perspective
2011-08-11 09:23 <xiangfu> the output  file format have "HIDVD" and "MPEG4" "DVD" "VCD" .... I have finish with "HIDVD" and "MPEG4"
2011-08-11 09:23 <wolfspraul> I am wondering whether the problem with boards going to unreconfigurable state also exists if you do the shutdown in the gui first, and only once it's powered down you unplug the cable...
2011-08-11 09:23 <aw> wolfspraul, i now don't think those two ways are related to rendering failure issue though. ;-)
2011-08-11 09:24 <wpwrak> disconnecting mains would cause a slow voltage drop. pulling DC is faster. dunno what "shutdown" does
2011-08-11 09:25 <wolfspraul> aw: ok, don't let my comment confuse you
2011-08-11 09:25 <wolfspraul> I was jsut thinking
2011-08-11 09:25 <aw> wpwrak, agreed you, so I just tried to use disconnecting dc jack this morning. but still got rendering err. though. ;-)
2011-08-11 09:25 <wolfspraul> maybe the corruption (if it is one) also happens because of how we shutdown, not because of how it starts
2011-08-11 09:26 <aw> wolfspraul, yes..sorry that guys I have to finish them firstly then chat if i found new different err or CRC again. :)
2011-08-11 09:26 <wpwrak> "no rendering" means that it reconfigures but doesn't boot into flickernoise ? or does it boot and then somehow fail later ?
2011-08-11 09:26 <wolfspraul> yes, finish everything first, including all usb/midi/vga fixes
2011-08-11 09:27 <aw> wpwrak, means 'can't reconfiguration from power-cycle' which is bad.
2011-08-11 09:27 <wolfspraul> I think they are all the same, one root cause
2011-08-11 09:27 <aw> even surely can't be boot up.
2011-08-11 09:27 <wolfspraul> which is good
2011-08-11 09:28 <wolfspraul> but needs to be fixed before we start selling :-)
2011-08-11 09:28 <aw> i go to test..
2011-08-11 09:28 <wpwrak> ah, so you're not even near rendering yet, but reconfiguration
2011-08-11 09:28 <wpwrak> wolfspraul: yes, sounds all like flash trouble
2011-08-11 09:29 <xiangfu> aw, hi  if can not boot up. if the reboot working
2011-08-11 09:29 <xiangfu> aw, like press the three buttons at same time?
2011-08-11 09:30 <xiangfu> aw, middle one is for powerup, press all three buttons is for reboot. I always use 'reboot' I found is faster and better then just 'power-up'
2011-08-11 09:30 <wpwrak> http://en.qi-hardware.com/wiki/Milkymist_One_Power_On_Off_Sequence#cite_note-5   (the link to the NOR data sheet) doesn't work :-(
2011-08-11 09:30 <aw> xiangfu, no need do this I think....which is un-normal though. ;-)
2011-08-11 09:31 <wpwrak> good that i found the data sheet before and have the URL in my IRC log ;-)
2011-08-11 09:31 <xiangfu> aw, hmm..  maybe help for debug :)
2011-08-11 09:31 <xiangfu> aw, yes it's un-normal.
2011-08-11 09:35 <wpwrak> hmm. the NOR's Vcc(min) = 2.7 V. U24's -Vdet(min) is 2.577 V. so at least theoretically, the board could be at a voltage where the NOR is outside its range and the reset hasn't kicked in yet
2011-08-11 09:35 <wpwrak> a similar condition may exist for the FPGA
2011-08-11 09:36 <wpwrak> maybe U24 should use a higher threshold. e.g., nominally 3 V (corresponds to 2.94-3.06 V)
2011-08-11 09:39 <wpwrak> wolfspraul: btw, why do we have all the M1 hw discussions on #qi-hardware now ? trying not to disturb lekernel ? :)
2011-08-11 09:40 <wolfspraul> not on purpose, sure they can be on #milkymist as well
2011-08-11 09:42 <xiangfu> aw, I am try to [power cycle] --> [rending 30 seconds] --> [power cycle] in my m1. see if there is problem on my m1.
2011-08-11 09:45 <aw> xiangfu, yours is rc2 without reset ic and diode h/w patches which is rc3 we have now. ;-)
2011-08-11 09:55 <xiangfu> in that wiki page: Fig. 15 <-- when you press middle and right at same time it will boot to that screen.
2011-08-11 09:55 <xiangfu> this page: http://en.qi-hardware.com/wiki/Milkymist_One_Power_On_Off_Sequence#Results
2011-08-11 10:07 <xiangfu> aw, I can reproduce your bug: -0000a80 0000 26cc 0000 0000 0000 0000 440c 6000
2011-08-11 10:07 <xiangfu> +0000a80 1000 26cc 0000 0000 0000 0000 440c 6000
2011-08-11 10:07 <xiangfu> I tried 7 times then it can not boot up. then I use jtag read the standby back.
2011-08-11 10:07 <xiangfu> diff with origin one. I got one diff:
2011-08-11 10:07 <xiangfu> -0000a80 0000 26cc 0000 0000 0000 0000 440c 6000
2011-08-11 10:07 <xiangfu> +0000a80 1000 26cc 0000 0000 0000 0000 440c 6000
2011-08-11 10:08 <xiangfu> the 0xa80, it should be '1' but now in my m1 it's '0'
2011-08-11 10:09 <xiangfu> now I reflash standby, test again.
2011-08-11 10:15 <aw> xiangfu, when you said 'can not boot up', please see LED 2 and LED3, are they dimly lit or fully off? we described a 'can't reconfigure' status is that LED 2(d2) and LED 3(d3) are dimly lit. if they are all fully off after powered-cycle, fpga finished reconfiguration.
2011-08-11 10:15 <xiangfu> aw, fully off here.
2011-08-11 10:17 <aw> xiangfu, different from mine rc3 here. but good that you found bug in rc2 you there.
2011-08-11 10:21 <xiangfu> aw, now I am try again. already three times.
2011-08-11 10:43 <xiangfu> aw, ok. I can not reproduce again. now I have tried 20 times.
2011-08-11 10:50 <xiangfu>  Fig. 15, hold left and middle then press right will goto that screen. it's a test screen wait input from serial console
2011-08-11 11:04 <qi-bot> [commit] Werner Almesberger: schhist/README: fixed typo (by Holger Freyther) (master) http://qi-hw.com/p/eda-tools/487e0e6
2011-08-11 12:15 <bartbes> so this 'new' mediatomb, does it play back from upnp too?
2011-08-11 13:09 <bartbes> is there a reason guile is at version 1.8.x, instead of 2.0.x?
2011-08-11 13:20 <xiangfu> bartbes, no. just no one upgrade the makefile and test
2011-08-11 13:20 <bartbes> which is why I'm redownloading the sdk and stuff
2011-08-11 13:21 <bartbes> here's hoping libffi has already been ported
2011-08-11 13:21 <bartbes> (I checked, it does run on MIPS)
2011-08-11 13:23 <bartbes> xiangfu: also, do you know who have access to the repo management, I kind of forgot my login details
2011-08-11 13:23 <xiangfu> bartbes, (libffi) just checked:Search results in feed 'packages':
2011-08-11 13:23 <xiangfu> libffi                   Foreign Function Interface (FFI) library
2011-08-11 13:23 <xiangfu> libffi-sable             Foreign Function Interface library (for sablevm)
2011-08-11 13:23 <bartbes> or well, it is not accepting the password in my password manager
2011-08-11 13:23 <bartbes> ah, cool, thanks
2011-08-11 13:23 <xiangfu> bartbes, what is your name?
2011-08-11 13:23 <bartbes> real name or account name?
2011-08-11 13:24 <xiangfu> account name.
2011-08-11 13:24 <bartbes> bartbes, afaik
2011-08-11 13:24 <xiangfu> ok. I will try to reset your password on projects.qi-hardware.com
2011-08-11 13:25 <bartbes> thanks
2011-08-11 13:25 <bartbes> (again)
2011-08-11 14:00 <bartbes> any interest in a minimal config around
2011-08-11 14:00 <bartbes> (I disabled everything)
2011-08-11 14:01 <wolfspraul> definitely
2011-08-11 14:01 <wolfspraul> there is one btw, we can compare with yours
2011-08-11 14:02 <wolfspraul> there should be a config.minimal somewhere
2011-08-11 14:05 <bartbes> it's just there to provide me with an sdk for the time being, next I will enable guile, build it and start working on updating it
2011-08-11 14:06 <bartbes> here's hoping I can get guile 2.0.2 on
2011-08-11 14:06 <wolfspraul> yes, that's great!
2011-08-11 14:06 <bartbes> ffi ftw
2011-08-11 14:07 <bartbes> I heard libffi is already on there, so it can't be too hard
2011-08-11 14:07 <bartbes> but I can't count on it being easy :P
2011-08-11 14:11 <bartbes> wolfspraul: so why is that old 'btr' script not in the image?
2011-08-11 14:11 <bartbes> (the battery checking one)
2011-08-11 14:11 <wolfspraul> no reason
2011-08-11 14:12 <wolfspraul> which package was it in before? if it fell through the cracks, we need to add it back
2011-08-11 14:12 <bartbes> that's one hell of a reason
2011-08-11 14:12 <bartbes> it never was in one, it was on the wiki
2011-08-11 14:12 <wolfspraul> oh you mean it should have been packaged
2011-08-11 14:12 <wolfspraul> nobody got to it yet
2011-08-11 14:48 <wpwrak> DocScrutinizer2: how do you like the N9 global release plan ? seems like a random pick of countries ;-)
2011-08-11 14:49 <kodein> I thought the MO was to fail hard enough at launching it that they can pull it off the shelves at the earliest possible convenience.
2011-08-11 14:51 <wpwrak> yes, it does look a bit as if this was part of their plan ;-)
2011-08-11 15:04 <kristianpaul> N9 is on my country, but too expensive 350usd for a  25usd internet plan
2011-08-11 15:21 <kristianpaul> stay with his oldfashioned phone
2011-08-11 15:32 <kodein> I have a newfashioned phone that isn't too old, so I won't get the N9 either.
2011-08-11 15:32 <kodein> I might've considered it if it isn't an orphaned project even before launch :/
2011-08-11 20:46 <bartbes> how are the patch files created again?
2011-08-11 20:46 <bartbes> I can't remember what the diff arguments were..
2011-08-11 20:51 <bartbes> hmm, -ruN looks sane
2011-08-11 20:53 <bartbes> except it doesn't work
2011-08-11 20:59 <bartbes> pokes wolfspraul 
2011-08-11 21:01 <Dubbles> hey
2011-08-11 21:04 <Dubbles> anyone here?
2011-08-11 21:04 <bartbes> yes
2011-08-11 21:05 <Dubbles> can you help me with this laptop
2011-08-11 21:05 <Dubbles> http://wiki.teamliquid.net/starcraft2/Terran_Strategy
2011-08-11 21:05 <Dubbles> woops
2011-08-11 21:05 <Dubbles> http://www.newegg.com/Product/Product.aspx?Item=N82E16834152279
2011-08-11 21:06 <bartbes> wrong channel
2011-08-11 21:08 <Dubbles> what is the right channel lol
2011-08-11 21:08 <bartbes> one that is about general channel, but of which I don't know its name or location on the internet, perhaps.
2011-08-11 21:13 <kristianpaul> Dubbles: /j #hardware
2011-08-11 21:13 <bartbes> ooh, someone arrives
2011-08-11 21:13 <bartbes> kristianpaul: you don't happen to be able to answer my question, do you?
2011-08-11 21:16 <kristianpaul> bit busy right now, i'll check backlog as i get to home :)
2011-08-11 21:27 <wpwrak> bartbes: in what way does does  diff -ruN  fail to do what you expect of it ?
2011-08-11 21:28 <bartbes> in this way: can't find file to patch at input line 3
2011-08-11 21:28 <bartbes> it fails to apply with the toolchain ;)
2011-08-11 21:28 <bartbes> but when I used patch -p0 < patch it works
2011-08-11 21:28 <bartbes> *worked
2011-08-11 21:32 <wpwrak> hmm, maybe the "toolchain" (=?) assumes -p1 or such ?
2011-08-11 21:33 <bartbes> I just need to know how I can export compatible diffs
2011-08-11 21:33 <bartbes> I tried the diff --git mentioned in the diff I am replacing
2011-08-11 21:33 <bartbes> but.. it does not appear to be a feature of my diff
2011-08-11 21:33 <bartbes> (and it's no git repo)
2011-08-11 21:37 <wpwrak> seems to be mainly a question of what you consumer expects. so that's where you should look for the answer. i.e., the patch command, if there's one
2011-08-11 21:37 <bartbes> in the openwrt toolchain?
2011-08-11 21:38 <bartbes> last I checked my suicide wish wasn't that bad
2011-08-11 21:38 <bartbes> :P
2011-08-11 21:39 <wpwrak> nice .. how do you do bold ?
2011-08-11 21:47 <bartbes> ^B
2011-08-11 21:47 <bartbes> on my client, anyway
2011-08-11 21:48 <wpwrak> hmm, i must say that i'm duly impressed with what Microchip have done with their USB PIGs. they seem to be about the only low-cost USB devices on the market that can handle low voltages (~2 V), e.g., for mixed USB and battery operation. oddly enough, even companies that have MCUs with very decent low-voltage performance, like Atmel, don't manage to combine that with USB (i.e., their USB devices want 2.7 V or even more)
2011-08-11 21:48 <wpwrak> test bold normal
2011-08-11 21:49 <wpwrak> kewl :) thanks !
2011-08-11 21:50 <steve|m> 12,14nice
2011-08-11 21:53 <wpwrak> what was that ? :)
2011-08-11 21:53 <steve|m> http://irssi.org/documentation/formats :)
2011-08-11 21:54 <steve|m> "MIRC" colors
2011-08-11 21:56 <wpwrak> ah, xchat only gets ^B through. ^- and ^V do other things
2011-08-11 21:58 <steve|m> does ^_ or ^7 work?
2011-08-11 22:01 <wpwrak> not with xchat
2011-08-11 22:02 <wpwrak> they do nothing. ^_ produces the right code in an xterm, so it's not a keyboard/etc. problem
2011-08-11 22:02 <bartbes> steve|m: there's underline and stuff when you right click on the input box
2011-08-11 22:02 <bartbes> see
2011-08-11 22:03 <bartbes> %UI am told this works too?%U
2011-08-11 22:03 <bartbes> not really
2011-08-11 22:03 <bartbes> :P
2011-08-11 22:03 <bartbes> you probably have to set them somewhere
2011-08-11 22:03 <steve|m> bartbes: I'm using irssi, so there's no right-click whatsoever :)
2011-08-11 22:04 <bartbes> oh right, in irssi it's just ^7 yeah
2011-08-11 22:04 <bartbes> it was meant for wpwrak, of course ;)
2011-08-11 22:05 <wpwrak> bartbes: eeey, 12coolness ! thanks !
2011-08-11 22:05 <bartbes> :)
2011-08-11 22:06 <bartbes> so either of you know about the diff format the toolchain wants?
2011-08-11 22:07 <wpwrak> bartbes: i think you need to set a trap for kyak :)
2011-08-11 22:07 <bartbes> I expect xiangfu to know as well
2011-08-11 22:07 <bartbes> since he made the previous patch
2011-08-11 22:08 <bartbes> even better
2011-08-11 22:08 <bartbes> I made one before..
2011-08-11 22:09 <wpwrak> ah yes, xiangfu may show up even sooner
2011-08-11 22:09 <wpwrak> ;-)
2011-08-11 22:11 <bartbes> oh
2011-08-11 22:11 <bartbes> I did it
2011-08-11 22:11 <bartbes> wow
2011-08-11 22:11 <bartbes> miracles came true
2011-08-11 22:11 <bartbes> so it's not the format it choked on
2011-08-11 22:11 <bartbes> but the filename
2011-08-11 22:11 <bartbes> of course..
2011-08-11 22:12 <wpwrak> it must be something after all :)
2011-08-11 22:13 <bartbes> oh... boy
2011-08-11 22:13 <bartbes> ehm, libunistring
2011-08-11 22:14 <bartbes> let me guess, unported?
2011-08-11 22:25 <bartbes> it takes hours to compile too (natively)
2011-08-11 22:25 <bartbes> fun fun fun
2011-08-11 22:25 <wpwrak> C++ ? :)
2011-08-11 22:25 <bartbes> like the friday it's just become
2011-08-11 22:25 <bartbes> a unicode library, that basically says it, doesn't it?
2011-08-11 22:29 <LunaVorax_win> Evening everyone
2011-08-11 22:29 <wpwrak> luddites like me shun unicode and C++, so yes, what would be an indication. (luddite(C++) == luddite(unicode)) ergo (unicode => C++)
2011-08-11 22:30 <bartbes> no, it's c code
2011-08-11 22:31 <mth> bartbes: maybe -p0 is the problem, for example buildroot assumes patches are made for -p1
2011-08-11 22:32 <bartbes> mth: yeah, that was the problem
2011-08-11 22:32 <bartbes> oh.. no..
2011-08-11 22:32 <bartbes> not another libiconv problem!
2011-08-11 22:32 <bartbes> how do I select the full iconv again?
2011-08-11 22:32 <bartbes> tries libiconv-full
2011-08-11 22:33 <bartbes> seems to be working
2011-08-11 22:33 <bartbes> more compiling, yaaay
2011-08-11 22:34 <LunaVorax_win> wpwrak: which software does QI use to make schematics ?
2011-08-11 22:34 <bartbes> I have a feeling I needed to do something extra with libiconv-full..
2011-08-11 22:35 <wpwrak> LunaVorax_win: we try to converge on kicad. i use kicad. m1 still used altium.
2011-08-11 22:35 <LunaVorax_win> Ok, thanks :)
2011-08-11 22:36 <LunaVorax_win> wpwrak: Altium via wine ?
2011-08-11 22:40 <wpwrak> LunaVorax_win: no idea. i just read the PDF ;-)
2011-08-11 22:40 <LunaVorax_win> ok :)
2011-08-11 23:21 <bartbes> interesting post here.. not: http://mkl-note.blogspot.com/2011/03/uclibc-0931-testsuite-error.html