01:07 <kristianpaul> huge

01:12 <kristianpaul> _Operator is a bit crazy, guess python fault here

01:14 <kristianpaul> ah, yes cluttered same as with _Assign, but it have method, very easy to read

01:15 <kristianpaul> of course _Operator should not be used, i see why ;)

01:22 <kristianpaul> "breaking down a Migen system into multiple sub-systems, possibly using different clock domains."

01:22 <kristianpaul> *g*

03:57 <cladamw> ( M1rc3 yield ) 85 sets until now.

05:51 <xiangfu> about the /ssd mode. after rebase rtems-yaffs2.git to last upstream. now it's 0777 again.

05:51 <xiangfu> oh. I have send the rtems-yaffs2.git 20 patches to yaffs2 upstream.

07:02 <xiangfu> this patch fix the ftpd root problem. http://www.rtems.org/pipermail/rtems-devel/2011-December/000087.html

07:04 <GitHub115> [flickernoise] xiangfu pushed 1 new commit to master: http://git.io/cUHP_g

07:04 <GitHub115> [flickernoise/master] assign FTPD_ROOT to /ssd/ - Xiangfu Liu

07:05 <xiangfu> after fix the ftpd_root. now only 'nautilus' give me some errors. filezilla works fine now.

08:33 <cladamw> xiangfu, have you met that mouse works well on both usb port in GUI but got 'RX timeout error' in 'boot.crc.be5b0e7.bin' ?

08:34 <xiangfu> cladamw, oh. then the 'RX timeout error' should be also under GUI. have to check the serial output when boot to GUI?

08:34 <cladamw> xiangfu, and VID & PID are all detected well.

08:34 <xiangfu> cladamw, this is a regression on new USB software core.

08:34 <xiangfu> cladamw, yes. all works fine only give RX timeout error.

08:35 <cladamw> there's no show 'RX timeout error' serial output when boot to GUI.

08:36 <cladamw> xiangfu, hmm.... so I'd have to use GUI to double confirm the test results now. :0

08:37 <xiangfu> cladamw, wait. maybe because the recently commit in milkymist.git? I will build a boot.crc.bin now. by using the milkymist.git 1.1 tag

08:40 <xiangfu> cladamw, try again with this boot.crc: http://downloads.qi-hardware.com/people/xiangfu/tmp/boot.crc.be5b0e7.bin

08:40 <cladamw> xiangfu, before you compile a new one. could you check that 2011-11-29 version with 'boot.crc.be5b0e7.bin' to see if the same as mine?

08:40 <xiangfu> cladamw, see if there still RX timeout error.

08:40 <cladamw> xiangfu, okay.

08:41 <xiangfu> cladamw, run the 'md5sum boot.crc.be4b0e7.bin' in your local.

08:41 <xiangfu> I will upload the md5sum to server

08:45 <cladamw> xiangfu, where's the folder md5sum supposed to be in my local folder?

08:49 <xiangfu> cladamw, the boot.crc....bin md5 have add to : http://milkymist.org/updates/current/for-rc3/md5sums

08:49 <cladamw> xiangfu, great ! there's no 'RX timeout error' msg in the new 'boot.crc.be5b0e7.bin'.

08:50 <xiangfu> cladamw, ok. then there is some regression in recently commit. :)

08:50 <xiangfu> cladamw, will replace new one in server

08:51 <cladamw> xiangfu, but wait a moment. let me test all items to see if else. :-)

08:51 <xiangfu> yes

09:00 <cladamw> xiangfu, seems good but only 0045 and midi.

09:01 <xiangfu> old 'boot.crc...bin' don't have midi error?

09:01 <cladamw> the phy id 0045, we knew it already. and the midi test result will show up 'PASS' at first round/time, if you retest midi 'i' item, then it will show 'failes', check it out if you are the same as mine. :-)

09:02 <cladamw> use this: http://downloads.qi-hardware.com/people/xiangfu/tmp/boot.crc.be5b0e7.bin

09:03 <cladamw> maybe I didn't notice well when i used previous bin. but you can check to retest 'i' for midi then if show failed. :-)

09:14 <xiangfu> cladamw, sorry one moment.

09:18 <cladamw> xiangfu, yes, i can surely confirm that 'retest' midi by selecting 'i' will always show 'failed' now. :-)

09:55 <cladamw> ( M1rc3 yield ) 86 sets until now.

10:06 <wpwrak> the RX timeout is a regression in the USB firmware. i'll fix it, just didn't have time to look into it.

10:07 <wpwrak> flickernoise doesn't report thnigs like "RX timeout" but they still happen. you just don't see them :)

10:08 <wpwrak> also, "RX timeout" means that one transfer failed. not that the whole communication broke down. USB will just retry.

10:10 <cladamw> wpwrak, ha ... thanks !

10:11 <wpwrak> so if your mouse works, there's nothing to worry about. and if it doesn't work, try another one ;-)

10:13 <cladamw> oah ~yes. since I was testing a new rc3 board, just found. :) Thanks told me this. ;-)

10:41 <lekernel> 86/90? that's pretty cool

10:42 <cladamw> lekernel, these days I'm still fixing remaining boards. :-)

10:43 <lekernel> what are the most common problems?

10:45 <cladamw> victims( clean ) after several times of reworks and unqualified usb transceiver.

10:48 <wpwrak> almost 96% yield. not bad at all. i think we started with something like 50% :)

10:49 <lekernel> it was less than that, thanks to the counterfeit buffers

10:49 <lekernel> maybe 20% or something

10:51 <wpwrak> ah yes, the very early beginnings :) adam found those quickly, though