<p>Copy from drivers/include/net/netdev.h, What is this mean?</p>
<pre><code> * # The Interrupt Context Problem
* Network devices are typically connected to the host CPU via some sort of bus,
* most commonly via SPI. This type of connection has the
* disadvantage, that the bus is not used by the network device alone, but it
* may be shared with other devices. This makes it necessary to synchronize
* access to the bus to prevent bus access collisions.
* To illustrate this behavior, let's look at a typical error situation, that
* leads to a very hard to find and debug latent failure: say we have two
* devices A and B on the same SPI bus. Our CPU is now transferring a chunk of
* 100 bytes to device A. After 20 bytes were transferred, device B triggers
* an external interrupt on the host CPU. The interrupt handling now typically
* requires the reading of some sort of status register on the 'triggering'
* device, device B in this case. So what would happen here, is that the device
* driver for device B would initiate a new SPI transfer on the already used bus
* to read B's status register -> BAM.
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/RIOT-OS/RIOT/issues/11815?email_source=notifications&email_token=ABE7WYCHDBHOZGAYKMUTKALP6L467A5CNFSM4H6ZJ242YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G5ZKH7A">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABE7WYABG42JL42FUJBJ47LP6L467ANCNFSM4H6ZJ24Q">mute the thread</a>.<img src="https://github.com/notifications/beacon/ABE7WYCVLSUDQPSOXQUNHWLP6L467A5CNFSM4H6ZJ242YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G5ZKH7A.gif" height="1" width="1" alt="" /></p>
"name": "View Issue"
"description": "View this Issue on GitHub",