mithro has quit [Read error: Connection reset by peer]
alanvgreen has quit [Read error: Connection reset by peer]
guan has quit [Read error: Connection reset by peer]
mithro has joined #nmigen
alanvgreen has joined #nmigen
guan has joined #nmigen
Degi_ has joined #nmigen
Degi has quit [Ping timeout: 258 seconds]
Degi_ is now known as Degi
benreynwar_ has joined #nmigen
alanvgreen has quit [Ping timeout: 252 seconds]
mithro has quit [Ping timeout: 258 seconds]
Qyriad has quit [Ping timeout: 258 seconds]
benreynwar_ is now known as benreynwar
benreynwar has quit [Ping timeout: 258 seconds]
Qyriad has joined #nmigen
zedtwitz has quit [Ping timeout: 258 seconds]
alanvgreen has joined #nmigen
mithro has joined #nmigen
zedtwitz has joined #nmigen
zedtwitz has quit [Ping timeout: 245 seconds]
bvernoux has joined #nmigen
gekh has quit [Quit: Goodbye!]
gekh has joined #nmigen
<FL4SHK>
How do I access an FPGA pin marked as `inout`?
<FL4SHK>
It's mainly the data pin of a memory chip that I need to access.
<FL4SHK>
*data pins
<FL4SHK>
I'm building an SDRAM controller.
<vup>
you can make it `dir='io'`, then when you request it you ge a record with three signals: `.i` (the io buffer input), `.o` (the io buffer output) and `.oe` (the io buffer output enable)
<FL4SHK>
It's already `dir="io"` in this case, as I get the pins from nmigen_boards
<FL4SHK>
That sounds good.
<FL4SHK>
Cool.
<FL4SHK>
test
<FL4SHK>
Really? No activity here?
<FL4SHK>
I see.
<vup>
what kind of activity are you looking for? :)
<FL4SHK>
Good point!
bvernoux has quit [Read error: Connection reset by peer]