<Jarrett[m]>
PICO and POCI are easier to say, is there a reason to declare their wrongness, other than it being a little weird to start with the peripheral?
<Jarrett[m]>
with COPI/CIPO, we got another JIG/GIF situation for the next decade
<Jarrett[m]>
SDI and SDO are definitely wrong though, that's how we got to the point where we have a whole standard layout for resistors to fix TX/RX miswiring
<josHua[m]>
because MOSI and MISO are the traditional, and when you have in your schematic a controller that says 'MOSI/MISO', and a peripheral that says 'POCI/PICO', you will *absolutely* fuck it up if you're tired
<omnitechnomancer>
I have definitely seen individual peripheral parts that label the data pins just SI and SO
<sigstoat[m]>
shouldn't the bottom right-most TX/RX be flipped?
<sigstoat[m]>
or the top right-most, depending on how you want to interpret it. just doesn't seem like top right-most and bottom right-most should match
<Jarrett[m]>
the point is that you can orient your resistors differently to correct for doing a bad job in layout
<sigstoat[m]>
sure, it's a great idea, i'm tempted to make it a single footprint so i can be lazy ass and slap that down and then figure it out later.
<sigstoat[m]>
i'm just bothered by the labelling, but maybe that's sort of the point, also
<Jarrett[m]>
can you make a single footprint with two PNP positions? I guess it depends on the package
duskwuff[m] has joined #glasgow
<duskwuff[m]>
I'm not sure poka-yoke is quite the right term for this, btw. that refers more to mechanisms which prevent errors, not ones which allow errors to be corrected
<Jarrett[m]>
I didn't design that
redstarcomrade has joined #glasgow
notgull has joined #glasgow
notgull has quit [Ping timeout: 264 seconds]
redstarcomrade has quit [Read error: Connection reset by peer]
redstarcomrade has joined #glasgow
redstarcomrade has quit [Read error: Connection reset by peer]
jess has quit []
redstarcomrade has joined #glasgow
redstarcomrade has quit [Changing host]
redstarcomrade has joined #glasgow
<theorbtwo[m]>
IMHO, the solution for all this naming stuff is to decide on a terminology we want to use, and note the other ones in the documentation, along with how they map. Or, possibly better, find somebody else who has written such a document, and link to theirs... such as https://en.wikipedia.org/wiki/Serial_Peripheral_Interface#Alternative_terminology
<whitequark[cis]>
we can extend the spi-controller --help text with a mapping for sure
maki0728[m] has quit [Quit: Idle timeout reached: 172800s]
redstarcomrade has quit [Read error: Connection reset by peer]
galibert[m] has quit [Quit: Idle timeout reached: 172800s]
WilfriedKlaebe[m has quit [Quit: Idle timeout reached: 172800s]
notgull has joined #glasgow
notgull has quit [Ping timeout: 252 seconds]
tpw_rules has quit [Ping timeout: 255 seconds]
tpw_rules has joined #glasgow
Eli2_ has joined #glasgow
Eli2 has quit [Ping timeout: 268 seconds]
bvernoux has joined #glasgow
nekrondev[m] has quit [Quit: Idle timeout reached: 172800s]
nf6x[m] has quit [Quit: Idle timeout reached: 172800s]
bvernoux has quit [Quit: Leaving]
<grazianom[m]>
If only there were a mapping that has been in use for 40 years
ali_as has quit [Quit: Ping timeout (120 seconds)]
ali_as has joined #glasgow
<Jarrett[m]>
ah yes, the "tradition and nothing better is ever possible" approach