Lines Matching full:should

4 should be implemented this way. All new drivers should be written against the
33 Keep in mind that you should code the driver to avoid storing state in global
35 Any such information that is specific to an interface should be stored in a
102 need to pass more/less arguments, that's fine.  You should also add the
105 The return value for this function should be as follows:
110 xxx_register().  This is the old naming convention and should be avoided as it
113 Other than locating the MAC address in dedicated hardware storage, you should
132 and/or PHY, and waiting for the link to autonegotiate.  You should also take
138 size is specified by length (in bytes).  You should not return until the
139 transmission is complete, and you should leave the state such that the send
142 The recv function should process packets as long as the hardware has them
143 readily available before returning.  i.e. you should drain the hardware fifo.
144 For each packet you receive, you should call the net_process_received_packet() function on it
146 already in the .bss (net_rx_packets), so there should be no need to allocate your
168 The halt function should turn off / disable the hardware and place it back in
172 The write_hwaddr function should program the MAC address stored in dev->enetaddr
191 every device does), you should add support for the mii command.  Doing so is
213 The read function should read the register 'reg' from the phy at address 'addr'
215 should logically follow.