Lines Matching refs:full
29 "full" and "not-in-use". An "empty" or "ready" descriptor is ready
30 to receive data from the hardware. A "full" descriptor has data in it,
32 descriptor is neither empty or full; it is simply not ready. It may
39 buffers, and marks them "full". The OS follows up, taking the full
46 marks it full, and advances the GDACTDPA by one. Thus, when there is
47 flowing RX traffic, every descr behind it should be marked "full",
53 hardware is ahead, the tail pointer will be pointing at a "full"
56 all of the descrs in front of the tail pointer should be "full", and
102 The status x4... corresponds to "full" and status xa... corresponds
109 "full" == SPIDER_NET_DESCR_FRAME_END == 0x4
113 The RX RAM full bug/feature
124 will be set in GHIINT1STS). When the RX ram full condition occurs,
144 net eth1: Spider RX RAM full, incoming packets might be discarded!
163 The HW pointer is at descr 0. This descr is marked 0x4.. or "full".
164 Since its already full, the hardware can do nothing more, and thus has
166 "full", while descr 254 and 255 are empty. (The "Last 1 descrs" is
176 search the ring for the next full descr, and the driver will resume
191 is full, the netdev is stopped. When there is room in the ring,