whitequark[cis] changed the topic of #glasgow to: https://glasgow-embedded.org · digital interface explorer · https://www.crowdsupply.com/1bitsquared/glasgow · code https://github.com/GlasgowEmbedded/glasgow · logs https://libera.catirclogs.org/glasgow · matrix #glasgow-interface-explorer:matrix.org · discord https://1bitsquared.com/pages/chat
balrog has quit [Quit: Bye]
GNUmoon has quit [Ping timeout: 264 seconds]
GNUmoon has joined #glasgow
balrog has joined #glasgow
meklort has joined #glasgow
<_whitenotifier-2> [glasgow] github-merge-queue[bot] created branch gh-readonly-queue/main/pr-805-34e4bd252f033cbc94dfb821b404a9ba528ec14e - https://github.com/GlasgowEmbedded/glasgow
<_whitenotifier-2> [glasgow] github-merge-queue[bot] deleted branch gh-readonly-queue/main/pr-805-34e4bd252f033cbc94dfb821b404a9ba528ec14e - https://github.com/GlasgowEmbedded/glasgow
redstarcomrade has quit [Read error: Connection reset by peer]
redstarcomrade has joined #glasgow
hardkrash[m] has quit [Quit: Idle timeout reached: 172800s]
sigstoat[m] has quit [Quit: Idle timeout reached: 172800s]
redstarcomrade has quit [Read error: Connection reset by peer]
duskwuff[m] has quit [Quit: Idle timeout reached: 172800s]
figushki has joined #glasgow
figushki has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
figushki has joined #glasgow
figushki has quit [Ping timeout: 265 seconds]
Attie[m] has quit [Quit: Idle timeout reached: 172800s]
figushki has joined #glasgow
figushki has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
figushki has joined #glasgow
figushki has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
figushki has joined #glasgow
figushki has quit [Quit: Textual IRC Client: www.textualapp.com]
dne has quit [Remote host closed the connection]
dne has joined #glasgow
<jn> hm, there seems to be a regression in/around the jtag-probe applet. with a particular DUT, it worked (showed an IDCODE) at 2024-06-20, and fails (DR chain too long) with current main. is something like that known? otherwise i'll bisect
<whitequark[cis]> please bisect
<jn> ok
<jn> ah well, the error disappeared, even on current main, now sure why i saw it in the first place. sorry for the noise
<whitequark[cis]> probably just a bad connection
<whitequark[cis]> TDO fell off
<jn> possible, yea
<whitequark[cis]> or any other signal really
_whitelogger has joined #glasgow
jfsimon has quit [Remote host closed the connection]
jfsimon has joined #glasgow
jfsimon has quit [Max SendQ exceeded]
jfsimon has joined #glasgow
jfsimon has quit [Max SendQ exceeded]
jfsimon has joined #glasgow
jfsimon has quit [Remote host closed the connection]
jfsimon has joined #glasgow
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #glasgow
jfsimon has quit [Quit: Leaving]
jfsimon has joined #glasgow
<_whitenotifier-2> [glasgow] whitequark synchronize pull request #803: [WIP] Redesign and simplify gateware-to-software glue layer - https://github.com/GlasgowEmbedded/glasgow/pull/803
altracer[m] has quit [Quit: Idle timeout reached: 172800s]
<_whitenotifier-2> [glasgow] whitequark synchronize pull request #803: [WIP] Redesign and simplify gateware-to-software glue layer - https://github.com/GlasgowEmbedded/glasgow/pull/803
<_whitenotifier-2> [glasgow] whitequark synchronize pull request #803: [WIP] Redesign and simplify gateware-to-software glue layer - https://github.com/GlasgowEmbedded/glasgow/pull/803
Foxyloxy has joined #glasgow
redstarcomrade has joined #glasgow
redstarcomrade has joined #glasgow
redstarcomrade has quit [Changing host]
<_whitenotifier-2> [glasgow] whitequark synchronize pull request #803: [WIP] Redesign and simplify gateware-to-software glue layer - https://github.com/GlasgowEmbedded/glasgow/pull/803
isabelburgos[m] has joined #glasgow
<isabelburgos[m]> the syntax add_inout_pipe(in_stream = component.o_stream, out_stream = component.i_stream) makes complete sense when I consider that the output stream of Glasgow is the computer's input stream and vice versa. but it is the kind of thing that takes me an extra thinking step to get right. It makes me wonder if there's a way to make it semantically even clearer that HardwareInPipe and HardwareOutPipe are defining "in" and "out" from
<isabelburgos[m]> the perspective of the host, but I can't think of any better terminology