<mtrbot-ml>
[mattermost] <sb10q> why is the CSR bus different from the current one in misoc, except for the addition of the read enable (or strobe) signal?
lkcl has quit [Ping timeout: 250 seconds]
_whitelogger has joined #m-labs
<whitequark>
sb: I explained why it can't be used for wishbone in general: because there is no guarantee that dat_o will be undriven when !(stb&cyc) according to wishbone spec
<whitequark>
so you can use it for a misoc wishbone subset, but not wishbone in general
<whitequark>
for CSR, you could probably use it if you really wanted, but it doesn't make the code more compact or easier to understand
<_whitenotifier>
[nmigen] whitequark commented on issue #257: Unexpected behaviour of `Record.connect()` - https://git.io/Je0er
<mtrbot-ml>
[mattermost] <sb10q> ah yes, it can't be used for multiple wishbone targets. but for point-to-point links it is fine
<mtrbot-ml>
[mattermost] <sb10q> there's no misoc wishbone subset, misoc only uses Record.connect() on point-to-point wishbone
<mtrbot-ml>
[mattermost] <sb10q> basically .connect() is intended for point-to-point links in general, with the special case of OR-multiplexing if you do specify multiple targets
<mtrbot-ml>
[mattermost] <sb10q> but that does require a protocol that uses OR-multiplexing
<mtrbot-ml>
[mattermost] <sb10q> oh and .connect() is useful for streams as well
<mtrbot-ml>
[mattermost] <sb10q> which are all point-to-point
<_whitenotifier>
[nmigen] jordens commented on issue #257: Unexpected behaviour of `Record.connect()` - https://git.io/Je0fr
<_whitenotifier>
[nmigen] whitequark commented on issue #257: Unexpected behaviour of `Record.connect()` - https://git.io/Je0fK
X-Scale has quit [Ping timeout: 276 seconds]
Getorix has joined #m-labs
Getorix has quit [Ping timeout: 240 seconds]
X-Scale has joined #m-labs
mtrbot-ml has quit [Remote host closed the connection]
mtrbot-ml has joined #m-labs
<_whitenotifier>
[nmigen] akukulanski commented on issue #257: Unexpected behaviour of `Record.connect()` - https://git.io/Je0Yl
Stormwind_mobile has joined #m-labs
Stormwind_mobile has quit [Client Quit]
<_whitenotifier>
[nmigen] sbourdeauducq commented on issue #257: Unexpected behaviour of `Record.connect()` - https://git.io/Je0YE
Stormwind_mobile has joined #m-labs
harryho has quit [Remote host closed the connection]
harryho has joined #m-labs
harryho has quit [Remote host closed the connection]
harryho has joined #m-labs
Stormwind_mobile has quit [Read error: Connection reset by peer]
Stormwind_mobile has joined #m-labs
Stormwind_mobile has quit [Ping timeout: 245 seconds]
Stormwind_mobile has joined #m-labs
lolsborn has quit [Ping timeout: 240 seconds]
bradbqc has joined #m-labs
<bradbqc>
sb10q: I've tried creating the interface externally and running with sandbox disabled and still get the same error. Is it possible that the MAC address resolution isn't the problem?
<bradbqc>
"the same error" is the license not found error, just to be clear
Stormwind_mobile has quit [Ping timeout: 240 seconds]
Stormwind_mobile has joined #m-labs
Stormwind_mobile has quit [Ping timeout: 276 seconds]
Stormwind_mobile has joined #m-labs
mumptai has joined #m-labs
mumptai has quit [Client Quit]
bradbqc has quit [Remote host closed the connection]
Stormwind_mobile has quit [Read error: Connection reset by peer]
Stormwind_mobile has joined #m-labs
Stormwind_mobile has quit [Ping timeout: 250 seconds]
Stormwind_mobile has joined #m-labs
Stormwind_mobile has quit [Ping timeout: 246 seconds]
Stormwind_mobile has joined #m-labs
Stormwind_mobile has quit [Read error: Connection reset by peer]
Stormwind_mobile has joined #m-labs
Stormwind_mobile has quit [Read error: Connection reset by peer]
Stormwind_mobile has joined #m-labs
Stormwind_mobile has quit [Ping timeout: 240 seconds]