ChanServ changed the topic of #glasgow to: glasgow interface explorer · code https://github.com/GlasgowEmbedded/glasgow · logs https://freenode.irclog.whitequark.org/glasgow · discord https://1bitsquared.com/pages/chat · production https://www.crowdsupply.com/1bitsquared/glasgow · no ETAs at the moment
FFY00 has quit [Remote host closed the connection]
FFY00 has joined #glasgow
thaytan has quit [Ping timeout: 264 seconds]
thaytan has joined #glasgow
egg|laptop|egg has quit [Remote host closed the connection]
electronic_eel has quit [Ping timeout: 256 seconds]
electronic_eel has joined #glasgow
PyroPeter_ has joined #glasgow
PyroPeter_ is now known as PyroPeter
PyroPeter has quit [Ping timeout: 272 seconds]
Getorix_ has joined #glasgow
Getorix has quit [Ping timeout: 246 seconds]
Getorix has joined #glasgow
Getorix_ has quit [Read error: Connection reset by peer]
Getorix has quit [Ping timeout: 240 seconds]
Getorix has joined #glasgow
Getorix_ has joined #glasgow
Getorix has quit [Ping timeout: 272 seconds]
tomtastic has quit [Ping timeout: 264 seconds]
tomtastic has joined #glasgow
<d1b2> <Attie> amazing! well done whitequark 😊
<whitequark> thank you :)
<whitequark> let me tick that one task off...
<whitequark> next one is prob yowasp
<d1b2> <Attie> if I'm understanding correctly... does this paired with e412494 make use on Windows "simple"?
<whitequark> with... what?
<d1b2> <Attie> oh, that's a commit id
<whitequark> oh!
<d1b2> <Attie> did the bridge mess it up?
<whitequark> i just had no idea it's a commit id.
<d1b2> <Attie> e412...
<whitequark> it's an sha, it's literally designed to look random
<d1b2> <Attie> ah
<d1b2> <Attie> yeah, fair
<whitequark> the answer is "yes and no"
<whitequark> bitarray is the remaining elephant in the room
<whitequark> having to manually do a bunch of `set` for yowasp is a papercut, though certainly annoying
<d1b2> <Attie> ah, I missed that issue, thanks
<d1b2> <Attie> is there any work on that yet? (replacing bitarray) ... I was thinking of having a go, but when I last looked, it was perhaps a little over my head... at least on an initial rummage
<whitequark> not really. what's needed is something like support.bits but mutable
<whitequark> i'm not sure what's more effort, to implement it or to review it
<d1b2> <Attie> ok, I don't really have time at the moment, so I'll leave it for now, but may ask again
<whitequark> sgtm
<Qyriad> (whitequark: btw I'll review those ViewSB PRs on Monday or so; I'm technically on vacation-ish right now)
<whitequark> no prob
<whitequark> i kinda forgot what i was even doing by this point
<electronic_eel> nice progress with that one, whitequark! as far as i see it, it is the only issue that depends on cooperation from others (python-libusb1 maintainer in this case). so getting it done gives more control over the progress
<whitequark> electronic_eel: strangely that was not actually the case
<whitequark> the issue was sitting there since summer, waiting for me to do a PoC
<whitequark> then it got resolved within a day
<whitequark> in general, nothing is stopping us from e.g. shipping a fork of python-libusb1. i mean, we ship two forks of yosys.
<electronic_eel> such things depend very much on the maintainer and if you communicate well with them. in this case it looks like the maintainer was nice to work with
<electronic_eel> but i've had cases where pull requests were rotting for 2 years
<whitequark> sure
<whitequark> in that case (since libusb is core functionality) it would be wise to take over maintenance, fork it, or rewrite it
<whitequark> wouldn't be the first time i do that
<electronic_eel> yeah, just another additional level of yak...
egg|laptop|egg has joined #glasgow
egg|laptop|egg has quit [Ping timeout: 265 seconds]
egg|laptop|egg has joined #glasgow
egg|laptop|egg has quit [Ping timeout: 246 seconds]
Getorix has joined #glasgow
Getorix_ has quit [Ping timeout: 256 seconds]
egg|laptop|egg has joined #glasgow
ExeciN has joined #glasgow
egg|laptop|egg has quit [Remote host closed the connection]
egg|laptop|egg has joined #glasgow
<_whitenotifier-f> [GlasgowEmbedded/glasgow] electroniceel pushed 3 commits to wip-revC2-firmware [+3/-1/±13] https://git.io/Jkpsq
<_whitenotifier-f> [GlasgowEmbedded/glasgow] Electronic Eel f9060fb - firmware: rename adc file and functions to prepare supporting the INA233 ADC too
<_whitenotifier-f> [GlasgowEmbedded/glasgow] Electronic Eel af653d7 - firmware: implement voltage reading for the INA233
<_whitenotifier-f> [GlasgowEmbedded/glasgow] Electronic Eel 1dc3759 - firmware: implement initializing and reading alert limits for the INA233
egg|laptop|egg_ has joined #glasgow
egg|laptop|egg has quit [Ping timeout: 260 seconds]
egg|laptop|egg_ has quit [Remote host closed the connection]
egg|laptop|egg has joined #glasgow
_whitelogger has joined #glasgow
egg|laptop|egg has quit [Remote host closed the connection]
egg|laptop|egg has joined #glasgow
egg|laptop|egg has quit [Remote host closed the connection]
egg|laptop|egg has joined #glasgow
<electronic_eel> does anybody know if i can use the analyzer applet on the internal i2c bus?
<electronic_eel> i mean i can solder wires to the testpoints, but since the internal i2c is connected to the fpga, it would be nice to be able to directly analyze it
Stormwind_mobile has joined #glasgow
egg|laptop|egg has quit [Remote host closed the connection]
bvernoux has quit [Quit: Leaving]
<_whitenotifier-f> [GlasgowEmbedded/glasgow] electroniceel pushed 1 commit to wip-revC2-firmware [+0/-0/±1] https://git.io/JkpQC
<_whitenotifier-f> [GlasgowEmbedded/glasgow] electroniceel 949b003 - firmware: fix ~ALERT interrupt handling
ExeciN has quit [Quit: so long king Bowser]
FFY00 has quit [Remote host closed the connection]
FFY00 has joined #glasgow
<whitequark> you cannot presently use it on the internal i2c bus
Getorix_ has joined #glasgow
Getorix has quit [Ping timeout: 256 seconds]
Sellerie has quit [Quit: The Lounge - https://thelounge.chat]
Sellerie has joined #glasgow
Stormwind_mobile has quit [Ping timeout: 260 seconds]
Stormwind_mobile has joined #glasgow