I'm trying to get rid of all remaining instances of "slave" in the fwupd codebase. The advice is primary and secondary, but for i2c that's just not accurate as it is the master _telling_ the slave what to do, rather than the slave being a fallback. Other ideas welcome too!
-
-
Replying to @hughsient
Anisse Retweeted Hector Martin
initiator/target ? It might confuse those new to the code that are just reading the standard though.https://twitter.com/marcan42/status/1268051590084087809 …
Anisse added,
Hector Martin @marcan42In the I²C example... what does the master do? It doesn't drive the bus alone (the slave does too), it doesn't imply control (upper layers might), it can't enforce the protocol (slaves can jam the bus), and a device can switch roles. What it does is *initiate* a transaction.Show this thread1 reply 0 retweets 2 likes -
Replying to @Aissn @hughsient
Hector Martin Retweeted whitequark
Yeah, about that standard...https://twitter.com/whitequark/status/990497828723089409 …
Hector Martin added,
2 replies 0 retweets 3 likes -
So a master is basically the transmitter? And the slave is the receiver?
1 reply 0 retweets 0 likes
The "master" initiates the communication and the "slave" answers. Both transmit and receive, both can reject a transmission of the other side, and both control the speed/clock of the communications (but in different ways). So the master/slave terminology is *terrible*.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.