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.irclog.whitequark.org/glasgow · matrix #glasgow-interface-explorer:matrix.org · discord https://1bitsquared.com/pages/chat
balrog has joined #glasgow
ari has quit [Quit: leaving]
ari has joined #glasgow
jstein has quit [Ping timeout: 252 seconds]
balrog has quit [Quit: Bye]
balrog has joined #glasgow
maki0728[m] has quit [Quit: Idle timeout reached: 172800s]
<_whitenotifier-4> [glasgow] ahmedcharles opened pull request #733: Use Simulation.add_testbench for i2c tests. - https://github.com/GlasgowEmbedded/glasgow/pull/733
redstarcomrade has joined #glasgow
Cattus[m] has quit [Quit: Idle timeout reached: 172800s]
coderobe has quit [Ping timeout: 265 seconds]
<_whitenotifier-4> [glasgow] ahmedcharles synchronize pull request #733: Use Simulation.add_testbench for i2c tests. - https://github.com/GlasgowEmbedded/glasgow/pull/733
\dev\ice has quit [Remote host closed the connection]
redstarcomrade has quit [Read error: Connection reset by peer]
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #glasgow
jstein has joined #glasgow
wiebel[m] has quit [Quit: Idle timeout reached: 172800s]
<whitequark[cis]1> <RobTaylor[m]> "Catherine: I'm looking at..." <- that's the layout of data associated with each submitted change in pin states
meklort has quit [Quit: ZNC 1.7.5+deb4 - https://znc.in]
meklort has joined #glasgow
meklort has quit [Client Quit]
meklort has joined #glasgow
meklort has quit [Ping timeout: 252 seconds]
meklort has joined #glasgow
mattvenn[m] has joined #glasgow
<mattvenn[m]> rp2350 laser fault injection rig uses Glasgow: https://courk.cc/rp2350-challenge-laser
<whitequark[cis]1> nice
<whitequark[cis]1> we don't necessarily have the best experience for programmatically launching an applet, but this is basically how you would do it yourself
<whitequark[cis]1> a bit verbose
f_[m] has joined #glasgow
redstarcomrade has joined #glasgow
coderobe has joined #glasgow
Wanda[cis] has joined #glasgow
<Wanda[cis]> so I got a documentation bug report, regarding memory-25x applet; the problem is that the documentation string talks of COPI/CIPO/WP/HOLD (and presents pinout accordingly), while the actual pins argument the applet takes is just called io and the correspondence between that and the presented pinout is not obvious unless you hold QSPI documentation in your hands
<whitequark[cis]1> yes
<whitequark[cis]1> can you fix that?
<Wanda[cis]> should I just note the correspondence of COPI/... to IO0/IO1/IO2/IO3 in the docstring? I don't think we have a way to attach documentation to individual pin arguments?
<whitequark[cis]1> i'd update the pinout in the docs too
<Wanda[cis]> mhmm
<whitequark[cis]1> and then explain in --pins-io help string the correspondence
<whitequark[cis]1> (help="" should work, if it doesn't, add it to add_pin_argument)
<Wanda[cis]> hmmm
<Wanda[cis]> yeah, we don't have that yet
<Wanda[cis]> ... wtf is wrong with multidict again
<whitequark[cis]1> sigh
<whitequark[cis]1> they poke python internals in ways that don't work
<Wanda[cis]> is this a private struct I am seeing
<whitequark[cis]1> and very few people care, and they're overloaded enough to fix it promptly
<Wanda[cis]> and they wonder why catgirls bite people
<whitequark[cis]1> yes
<whitequark[cis]1> very yes.
<whitequark[cis]1> apparently it's webscale though
<whitequark[cis]1> like, literally, that's why it uses an extension
<whitequark[cis]1> "10x faster than the python impl"
<Wanda[cis]> ... okay blowing up pdm.lock fixed the issue, apparently 6.0.5 is good
sknebel has left #glasgow [#glasgow]
<_whitenotifier-4> [glasgow] wanda-phi opened pull request #734: applet.{memory.25x,interface.qspi_controller}: improve pins help message. - https://github.com/GlasgowEmbedded/glasgow/pull/734
jn_ is now known as jn
<Wanda[cis]> ... sigh
<Wanda[cis]> CI failed because of broken link (https://www.sparkfun.com/products/retired/9694) which, of all things, uses a gen-AI image for the 404 page.
<whitequark[cis]1> why do we even link to sparkful
<whitequark[cis]1> s/sparkful/sparkfun/
<whitequark[cis]1> buspirate?
<whitequark[cis]1> oh
<whitequark[cis]1> why do we link to that
duskwuff[m] has joined #glasgow
<whitequark[cis]1> ohhh
<_whitenotifier-4> [glasgow] wanda-phi opened pull request #735: docs: fix a dead link. - https://github.com/GlasgowEmbedded/glasgow/pull/735
<_whitenotifier-4> [glasgow] wanda-phi synchronize pull request #735: docs: fix a dead link. - https://github.com/GlasgowEmbedded/glasgow/pull/735
<Wanda[cis]> sigh.
<Wanda[cis]> now https://www.gnu.org/software/make/ fails linkcheck because of some connectivity problems?
<whitequark[cis]1> how does that even happen
<Wanda[cis]> shrug BGP weirdness?
<Wanda[cis]> I'll just rerun this thing in a few hours or something
<whitequark[cis]1> why would that return "network is unreachable"
<whitequark[cis]1> thanks, useless manpage
<whitequark[cis]1> i wonder if it's an ipv6 thing
<whitequark[cis]1> probably not
redstarcomrade has quit [Read error: Connection reset by peer]