<_whitenotifier-f>
[GlasgowEmbedded/glasgow] whitequark pushed 1 commit to master [+1/-0/±0] https://git.io/JTfgD
<_whitenotifier-f>
[GlasgowEmbedded/glasgow] attie-argentum 5307005 - examples: add an example PCF8574 script
<_whitenotifier-f>
[glasgow] whitequark commented on pull request #213: Add support for Out-of-Tree applets - https://git.io/JTfg7
<whitequark>
does anyone want to update SPI stuff to use COPI/CIPO?
<whitequark>
it's actually kind of a pain because there's so much code that indirectly (or, sometimes, worse, implicitly) depends on those in our codebase
<whitequark>
but it's a PR that would be most welcome
<whitequark>
i think i tried to update SPI to use DI/DO once and it got too tangled up with other changes, i'm glad that attempt failed though because at the time i had no idea CIPO/COPI will be adopted in just a few months and it'd suck to rename everything *twice*
<whitequark>
plus DI/DO isn't even that good
<whitequark>
the naming got extremely confusing
<sorear>
always a good sign when I can't tell what the new abbreviation stands for without searching
<_whitenotifier-f>
[glasgow] attie opened pull request #215: Update SPI signal terms to COPI / CIPO - https://git.io/JTU4c
<d1b2>
<Attie> I've just opened #215 to address SPI signal naming - hopefully I've caught everything
<d1b2>
<Attie> I also noticed that "slave" is used in software/glasgow/applet/interface/uart/__init__.py - I don't know if that's something worth resolving / addressing too... or if that's the preferred terminology here, as it matches the docs.
<_whitenotifier-f>
[glasgow] attie synchronize pull request #213: Add support for Out-of-Tree applets - https://git.io/JTfm8
<_whitenotifier-f>
[glasgow] attie synchronize pull request #213: Add support for Out-of-Tree applets - https://git.io/JTfm8
<_whitenotifier-f>
[glasgow] attie synchronize pull request #215: Update SPI signal terms to COPI / CIPO - https://git.io/JTU4c
<whitequark>
that's actually what the i2c spec uses
<_whitenotifier-f>
[glasgow] attie synchronize pull request #215: Update SPI signal terms to COPI / CIPO - https://git.io/JTU4c
<whitequark>
and it's the only terms that make sense, because in i2c you don't have roles permanently assigned, they are per-transaction
<d1b2>
<Attie> yeah
<d1b2>
<Attie> my initial reading of yorick's comment was a "point of view" thing... i.e: if you're working in a micro, and you have an internal I2C "peripheral"
<whitequark>
ohh
<d1b2>
<Attie> on SPI, then you'd have an SPI peripheral (internally to the IC), communicating with a discrete I2C peripheral elsewhere on the bus / board