sb0 changed the topic of #m-labs to: https://m-labs.hk :: Mattermost https://chat.m-labs.hk :: Logs http://irclog.whitequark.org/m-labs
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 276 seconds]
<mtrbot-ml> [mattermost] <sb10q> @cjbe why did you set a different tool_triple for the Cortex A9 target? you wrote code to pass "armv7-unknown-linux-gnueabihf" to LLVM while using "arm-linux-gnueabihf-xxx" for binutils
<mtrbot-ml> [mattermost] <sb10q> but LLVM seems just fine with "arm-linux-gnueabihf"
<mtrbot-ml> [mattermost] <sb10q> armv7 adds some optimizations?
<mtrbot-ml> [mattermost] <sb10q> this looks redundant with the "CPU features" list...
<mtrbot-ml> [mattermost] <sb10q> binutils is also fine with armv7-unknown-linux-gnueabihf...
<mtrbot-ml> [mattermost] <sb10q> is the discrepancy just because you copied binutils binary from somewhere else?
<sb0> whitequark: is there a difference between armv7-unknown-linux-gnueabihf and armv7-linux-gnueabihf?
zng has quit [Quit: ZNC 1.7.2 - https://znc.in]
zng has joined #m-labs
<whitequark> sb0: the first "unknown" is a "platform"
<whitequark> the only time i've seen it matter is with mingw
<whitequark> so i'm gonna say no
<sb0> ok thanks
ohama has quit [Remote host closed the connection]
<sb0> hm, rustc insists on the -unknown
<whitequark> the triple is technically made out of four parts
<whitequark> (yes, I know, sounds absurd)
<whitequark> LLVM will fill in the missing parts with basically its best guess
<whitequark> I suspect rustc wouldn't?
<whitequark> the 2nd triple is actually more like armv7--linux-gnueabihf, and the -- is the same as -unknown-
ohama has joined #m-labs
<whitequark> 2nd part of the triple*
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 276 seconds]
sb0 has quit [Quit: Leaving]
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 276 seconds]
yuriks_ has quit []
yuriks has joined #m-labs
gnufan_home has quit [Ping timeout: 246 seconds]
<_whitenotifier> [m-labs/nmigen] whitequark pushed 2 commits to master [+0/-0/±2] https://git.io/fjA4L
<_whitenotifier> [m-labs/nmigen] whitequark b4b5d9e - vendor.lattice_ecp5: revert default toolchain to Trellis.
<_whitenotifier> [m-labs/nmigen] whitequark 8de00a0 - back.verilog: bump Yosys version requirement to 0.9.
<_whitenotifier> [m-labs/nmigen] whitequark pushed 1 commit to master [+0/-0/±1] https://git.io/fjA4t
<_whitenotifier> [m-labs/nmigen] whitequark 2168ff5 - back.verilog: bump Yosys version requirement to 0.9.
<_whitenotifier> [nmigen] whitequark closed issue #55: Should nMigen check Yosys version? - https://git.io/fjkxp
<_whitenotifier> [nmigen] Success. The Travis CI build passed - https://travis-ci.org/m-labs/nmigen/builds/576743072?utm_source=github_status&utm_medium=notification
<_whitenotifier> [nmigen] Success. 80.51% (+0.15%) compared to 72cf4ca - https://codecov.io/gh/m-labs/nmigen/commit/8de00a07a89b5d6f7f2bbc9da881492c02b45683
<_whitenotifier> [nmigen] Failure. 66.66% of diff hit (target 80.36%) - https://codecov.io/gh/m-labs/nmigen/commit/8de00a07a89b5d6f7f2bbc9da881492c02b45683
gnufan_home has joined #m-labs
<_whitenotifier> [nmigen] Success. 80.36% remains the same compared to 72cf4ca - https://codecov.io/gh/m-labs/nmigen/commit/8de00a07a89b5d6f7f2bbc9da881492c02b45683
<_whitenotifier> [nmigen] Success. The Travis CI build passed - https://travis-ci.org/m-labs/nmigen/builds/576743072?utm_source=github_status&utm_medium=notification
<_whitenotifier> [nmigen] Success. The Travis CI build passed - https://travis-ci.org/m-labs/nmigen/builds/576743570?utm_source=github_status&utm_medium=notification
<_whitenotifier> [nmigen] Success. 80.51% (+0.15%) compared to 72cf4ca - https://codecov.io/gh/m-labs/nmigen/commit/2168ff512bfe04806b35c09d3b1d265a16c4ddbc
<_whitenotifier> [nmigen] Failure. 66.66% of diff hit (target 80.36%) - https://codecov.io/gh/m-labs/nmigen/commit/2168ff512bfe04806b35c09d3b1d265a16c4ddbc
<mtrbot-ml> [mattermost] <cjbe> @sb10q it was a dirty hack to get around some issues with my crappy toolchain - I was in a hurry to get a proof-of-concept working, so I did not investigate.
<_whitenotifier> [nmigen] Success. 80.36% remains the same compared to 72cf4ca - https://codecov.io/gh/m-labs/nmigen/commit/2168ff512bfe04806b35c09d3b1d265a16c4ddbc
<_whitenotifier> [nmigen] Success. The Travis CI build passed - https://travis-ci.org/m-labs/nmigen/builds/576743570?utm_source=github_status&utm_medium=notification
gnufan_home has quit [Ping timeout: 246 seconds]
gnufan_home has joined #m-labs
sb0 has joined #m-labs
<sb0> whitequark: is Glasgow able to stream samples into a computer without bugs or much fuss, at what speed, and how can I get one?
<sb0> all USB hosts appear to be affected by this sigrok/fx2 bug, just with different probablilites...
<whitequark> sb0: you can stream up to full USB2 bandwidth, i've never had any problem with the USB part of that code, and ... well, they're not mass produced yet
<whitequark> i can bring one of mine to the lab i think
<whitequark> do you want me to do it today?
<whitequark> (re USB part, if you want soft realtime response to events in python it can become a lil tricky but still doable on a fast PC)
<sb0> I just need streaming at a constant rate and low jitter, latency does not matter
<sb0> (constant rate for the samples, latency variations don't matter either)
<whitequark> sure, it does that easily
<whitequark> is 48 Msps enough?
<sb0> it's better than the shitty 6Msps I'm getting out of fx2 right now because anything higher crashes
<whitequark> if not the CDC code is affected by the bug in migen/nmigen where AsyncFIFOBuffered is translated to FFRAM
<cr1901_modern> sb0: >all USB hosts appear to be affected by this sigrok/fx2 bug, just with different probablilites.
<cr1901_modern> You mean the thing where you'll all of a sudden stop getting all 24MHz bandwidth and have to do 16 or even 12 to get reliable samples?
<sb0> really reliable is 6, but yes
<cr1901_modern> Can duplicate on Windoze too :P
<whitequark> cr1901_modern: libusb on windows works like shit in first place
<whitequark> i never got windows performance of glasgow quite to the point of the linux version
<whitequark> winusb is especially bad but libusbK isn't too great either
<cr1901_modern> switching to a different USB port gets me back to full 24MHz bandwidth (especially if not attached to my powered 2.0 hub) most of the time.
<cr1901_modern> whitequark: Anyways, tbh I don't have any working 3.0 ports on this laptop- they died long ago. But even sacrificing some channels to get more bandwidth from Glasgow on 2.0 would be a nice alternative to fx2lafw
<sb0> how did they die?
Guest47290 is now known as jayaura
<cr1901_modern> Damned if I know- some trace integrity seems to be going? The laptop is 8 years old.
<cr1901_modern> Bluetooth and fingerprint reader sometimes goes to hell and falls of the internal USB for the same reason
sb0 has quit [Quit: Leaving]
<whitequark> wtf
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 276 seconds]
mumptai has joined #m-labs
mumptai has quit [Read error: Connection reset by peer]
mumptai has joined #m-labs
lkcl has quit [Read error: Connection reset by peer]
mumptai has quit [Quit: Verlassend]
lkcl has joined #m-labs
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 272 seconds]