sb0 changed the topic of #m-labs to: ARTIQ, Migen, MiSoC, Mixxeo & other M-Labs projects :: fka #milkymist :: Logs http://irclog.whitequark.org/m-labs
<GitHub190>
[smoltcp] dlrobertson commented on pull request #59 723226c: Added tests for the added logic. https://git.io/vdM6J
<GitHub69>
[smoltcp] dlrobertson commented on pull request #59 723226c: Added documentation about the added logic and updated documentation about the default value. https://git.io/vdM6U
Gurty has joined #m-labs
<sb0>
are 19-inch subrack card guides standard, or do the expensive schroff card guides only work with expensive schroff enclosures?
<GitHub55>
nu-servo/master 213e57c Robert Jordens: kasli
<_florent_>
rjo: thanks, that's fine for now, i'm able to build design, build firmware, load it
<_florent_>
rjo: for now it seems ddr3 is not working correctly when serwb is integrated (i think sb0 already saw that)
<_florent_>
rjo: i found a workaround for that (to be able to continue serwb tests, artiq integration): reduce ddr64 to 32 bits...
<_florent_>
rjo: i'll look at the ddr issue later
<rjo>
_florent_: ack.
<_florent_>
rjo: i'm going to look at serwb and then clocking, i'll ask if i need help, thanks
<_florent_>
rjo: ethernet still need to be investigated right?
acathla has quit [Quit: Coyote finally caught me]
rjo- has joined #m-labs
<rjo->
_florent_: yes. I don't know how much sb0 has looked into it.
acathla has joined #m-labs
acathla has quit [Changing host]
acathla has joined #m-labs
rjo- has quit [Quit: AtomicIRC: The nuclear option.]
<GitHub44>
[smoltcp] whitequark commented on pull request #59 723226c: Same as above. https://git.io/vdDGm
<GitHub178>
[smoltcp] whitequark commented on pull request #59 723226c: TTL value of 0 is clearly user error so you should panic rather than silently ignore. https://git.io/vdDGO
<GitHub160>
[smoltcp] whitequark commented on pull request #59 723226c: Let's leave this out, `set_payload_len` is special here. https://git.io/vdDGY
<GitHub92>
[smoltcp] dlrobertson commented on issue #59: Good catches. Updated. https://git.io/vdDZT
<_florent_>
rjo/sb0: i got serwb working with artiq targets (rtm_identifier was read correctly by rust runtime), initialization is sometime failing, i'll investigate that (and also see if vivado constraints are correct).
rohitksingh has joined #m-labs
<whitequark>
sb0: ping
<whitequark>
I'm observing something very strange
<whitequark>
is rtio::get_counter not atomic?
<whitequark>
I'm computing counter differences and I get a few results on the order of 0xfc880c5fd8
<whitequark>
which, actually, make very little sense even if the counter halves aren't read at the right time, hm
<sb0>
rjo, you don't understand how this works. it would be "hours traveling to Shenzhen and scouring markets with a translator". a lot of chinese electronic/mechanical stuff isn't crappy at all, but it is undocumented and they expect face-to-face meetings.
<whitequark>
how can it possibly be atomic?
<whitequark>
it's a 64-bit value
<whitequark>
oh I see
<whitequark>
nevermind
<sb0>
and in this case I was looking at a Rittal case, not a chinese one, and it also suffers from the same lack of docs.
<sb0>
whitequark, what do you mean by atomic?
<sb0>
_florent_, there was some intermittent vivado breakage with ddr3. I don't know how frequent is it nor what the impact of serwb exactly is.
<sb0>
_florent_, yes Ethernet still needs fixing
<mithro>
FYI - We found an issue with tftp booting in the bios today
<mithro>
Will send patch upstream soon
<sb0>
Rittal is 1/3 the price of Schroff, which is still expensive by chinese standards, but yes I want to avoid the hours of annoyance you mention
<whitequark>
sb0: ok I figured out why perf counter data was completely worthless
<whitequark>
because the implementation is just broken