azonenberg changed the topic of #scopehal to: libscopehal, libscopeprotocols, and glscopeclient development and testing | https://github.com/glscopeclient/scopehal-apps | Logs: https://libera.irclog.whitequark.org/scopehal
balrog has quit [*.net *.split]
balrog has joined #scopehal
Degi_ has joined #scopehal
Degi has quit [Ping timeout: 248 seconds]
Degi_ is now known as Degi
<azonenberg> Well, it looks like libscopehal is going to be getting a new device class for BERTs soon
<azonenberg> Starting with the signal generation and PLL lock status queries etc
<azonenberg> Then will work on readback
<azonenberg> have to figure out whether e.g. a BER eye should be considered the same as a regular eye or what
<azonenberg> or if it's a new data type
<_whitenotifier> [scopehal-docs] azonenberg pushed 1 commit to master [+1/-0/±2] https://github.com/glscopeclient/scopehal-docs/compare/db846a2afe7e...5f610d5a34f9
<_whitenotifier> [scopehal-docs] azonenberg 5f610d5 - Initial skeleton documentation for mlbert driver
<azonenberg> lain, @MP, @louis, balrog, @hansemro: Thoughts on how to handle channels in a BERT?
<azonenberg> in particular, normally you have N (4 in my case) PRBS generators and N receivers
<azonenberg> is this N or 2N channels?
<azonenberg> i.e. do we have four output only and four input only channels or four bidir channels, logically?
<azonenberg> i kinda feel like it might make sense to treat them as separate channels with some being input only and some being output only
<azonenberg> since the feature set they expose is totally different and there's no hardware restriction that TX and RX are connected to each other (although they normally do have to share a common VCO frequency, so you can't have TX at 1G and RX at 10G or something)
<azonenberg> But e.g. output channels allow you to control swing and emphasis taps, while input channels allow you to control equalizer settings
<azonenberg> both allow you to control the PRBS pattern in use, but it need not be the same
<azonenberg> also miek any thoughts?
<d1b2> <azonenberg> (reposting since discord bot failed, @mp @louis)
Darius has quit [Quit: Bye]
Darius has joined #scopehal
<_whitenotifier> [scopehal] azonenberg pushed 2 commits to master [+6/-0/±6] https://github.com/glscopeclient/scopehal/compare/e633ade465c5...1a01b3c3ff34
<_whitenotifier> [scopehal] azonenberg 8b42e82 - Initial class skeleton for BERTs. Doesn't do anything yet, no drivers
<_whitenotifier> [scopehal] azonenberg 1a01b3c - Initial skeleton of MultiLaneBERT driver
<_whitenotifier> [scopehal-apps] azonenberg pushed 4 commits to master [+12/-0/±11] https://github.com/glscopeclient/scopehal-apps/compare/fd0c62131556...09511c023d70
<_whitenotifier> [scopehal-apps] azonenberg eeb5927 - Initial BNC connector input icon
<_whitenotifier> [scopehal-apps] azonenberg a319b7f - Added banana jack icon for PSU and multimeter channels
<_whitenotifier> [scopehal-apps] azonenberg 97fcff2 - Initial dummy multiply icon
<_whitenotifier> [scopehal-apps] azonenberg 09511c0 - Initial skeleton code for creating BERTs and adding them to sessions
<azonenberg> ok i'm hitting the hay, the BERT software stack now exists but does nothing
<azonenberg> But all of the dialogs, creation tables, driver classes, and other boilerplate for the new type of instrument now exist
<azonenberg> Tomorrow i can work on making it actually do useful things
<azonenberg> i'm probably going to create one type of channel for a signal output and one for an input
bvernoux has joined #scopehal
<_whitenotifier> [scopehal] azonenberg pushed 2 commits to master [+4/-0/±9] https://github.com/glscopeclient/scopehal/compare/1a01b3c3ff34...de349028f784
<_whitenotifier> [scopehal] azonenberg 85525fa - Added BERT channel classes
<_whitenotifier> [scopehal] azonenberg de34902 - MultiLaneBERT: initial driver support for TX/RX pattern generation and channel polarity
bvernoux has quit [Read error: Connection reset by peer]