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
<duskwuff[m]> Indeed. All good on the pinout then, just wanted to make sure this was an intended change.
<duskwuff[m]> As far as addressing modes go, I've been having a think about this and I'm curious how you'd feel about a class-based approach along these lines, rather than a bunch of branches in the Interface class - https://gist.github.com/duskwuff/a4008360dd52c433441d019e3a8c0624
redstarcomrade has joined #glasgow
redstarcomrade has quit [Changing host]
redstarcomrade has joined #glasgow
redstarcomrade has quit [Read error: Connection reset by peer]
bvernoux has joined #glasgow
<whitequark[m]> I don't like it--that is just a branch with more ceremony and indirection
<whitequark[m]> inheritance hierarchies are only useful in cases where there is open recursion
<whitequark[m]> the set of addressing modes should be closed, it's not an API we should be providing
<whitequark[m]> (you will find that Glasgow, and my code in general, uses inheritance exceptionally; either when open recursion is needed, or as replacement for nonexistent sum types; not many other cases)
<duskwuff[m]> Noted; this is exactly why I asked before getting too far into that design. I'll proceed with the original approach
<whitequark[m]> I don't think there is anything wrong with an enum, and if you want, you can put the addressing related code in the enum members (but I think that keeping it without members is probably slightly nicer)
<whitequark[m]> generally I like separating data and behavior
<whitequark[m]> if all of the behavior lies in the *Interface class, that's easier to think about a bit
<_whitenotifier-3> [glasgow] whitequark opened pull request #670: manual: exempt GitHub from anchor checking as a whole - https://github.com/GlasgowEmbedded/glasgow/pull/670
<_whitenotifier-3> [glasgow] whitequark closed pull request #544: Hardware description documentation for Glasgow revC3 - https://github.com/GlasgowEmbedded/glasgow/pull/544
<_whitenotifier-3> [glasgow] whitequark commented on pull request #544: Hardware description documentation for Glasgow revC3 - https://github.com/GlasgowEmbedded/glasgow/pull/544#issuecomment-2295983002
<_whitenotifier-3> [glasgow] github-merge-queue[bot] created branch gh-readonly-queue/main/pr-670-97f8db871c537091cd1bceeca638145d0e41a0e2 - https://github.com/GlasgowEmbedded/glasgow
<_whitenotifier-3> [GlasgowEmbedded/glasgow] github-merge-queue[bot] pushed 1 commit to main [+0/-0/±1] https://github.com/GlasgowEmbedded/glasgow/compare/97f8db871c53...1ab644d613fb
<_whitenotifier-3> [GlasgowEmbedded/glasgow] whitequark 1ab644d - manual: exempt GitHub from anchor checking as a whole.
<_whitenotifier-3> [glasgow] whitequark closed pull request #670: manual: exempt GitHub from anchor checking as a whole - https://github.com/GlasgowEmbedded/glasgow/pull/670
<_whitenotifier-3> [glasgow] github-merge-queue[bot] deleted branch gh-readonly-queue/main/pr-670-97f8db871c537091cd1bceeca638145d0e41a0e2 - https://github.com/GlasgowEmbedded/glasgow
<_whitenotifier-3> [glasgow] whitequark synchronize pull request #669: Finalised revC3 hardware description documentation. - https://github.com/GlasgowEmbedded/glasgow/pull/669
<_whitenotifier-3> [glasgow] whitequark commented on pull request #669: Finalised revC3 hardware description documentation. - https://github.com/GlasgowEmbedded/glasgow/pull/669#issuecomment-2296014305
bgamari has quit [Quit: ZNC 1.8.2 - https://znc.in]
bgamari has joined #glasgow
opticron has quit [Ping timeout: 252 seconds]
<_whitenotifier-3> [glasgow] whitequark synchronize pull request #669: Finalised revC3 hardware description documentation. - https://github.com/GlasgowEmbedded/glasgow/pull/669
<_whitenotifier-3> [glasgow] github-merge-queue[bot] created branch gh-readonly-queue/main/pr-669-1ab644d613fb06669b97c509e4b093a24d1cd44a - https://github.com/GlasgowEmbedded/glasgow
<_whitenotifier-3> [GlasgowEmbedded/glasgow] github-merge-queue[bot] pushed 2 commits to main [+5/-3/±3] https://github.com/GlasgowEmbedded/glasgow/compare/1ab644d613fb...c3fee747d7d2
<_whitenotifier-3> [glasgow] whitequark closed pull request #669: Finalised revC3 hardware description documentation. - https://github.com/GlasgowEmbedded/glasgow/pull/669
<_whitenotifier-3> [glasgow] github-merge-queue[bot] deleted branch gh-readonly-queue/main/pr-669-1ab644d613fb06669b97c509e4b093a24d1cd44a - https://github.com/GlasgowEmbedded/glasgow
dne has quit [Remote host closed the connection]
dne has joined #glasgow
fridtjof[m] has joined #glasgow
<fridtjof[m]> After reading the new technical description (Really like it, btw!), i remembered wondering about whether fluctuations on the +5V rail affect current measurements on the VSENSE pins (in short - do measurements taken by INA233 depend on stable vbus/vs?)
<fridtjof[m]> (vbus/vs from the perspective of INA233)
<fridtjof[m]> so for example, if +5V drops to 4.5V or something (4.0V seems to be the reset threshold given the supervisor part), does that skew measurements of some external voltage I attach to vsense?
nyanotech has quit [Remote host closed the connection]
nyanotech has joined #glasgow
jstein has joined #glasgow
<_whitenotifier-3> [glasgow] id43 opened pull request #671: U13 function description updated. U13 has same function as U20 (was same as U21). - https://github.com/GlasgowEmbedded/glasgow/pull/671
jstein_ has joined #glasgow
jstein has quit [Read error: Connection reset by peer]
<_whitenotifier-3> [glasgow] gsuberland commented on pull request #669: Finalised revC3 hardware description documentation. - https://github.com/GlasgowEmbedded/glasgow/pull/669#issuecomment-2297057748
<_whitenotifier-3> [glasgow] whitequark commented on pull request #669: Finalised revC3 hardware description documentation. - https://github.com/GlasgowEmbedded/glasgow/pull/669#issuecomment-2297064911
<_whitenotifier-3> [glasgow] whitequark commented on pull request #671: U13 function description updated. U13 has same function as U20 (was same as U21). - https://github.com/GlasgowEmbedded/glasgow/pull/671#issuecomment-2297066340
jstein_ has quit [Ping timeout: 245 seconds]