Lines Matching full:dependent

42 and MD (Machine Dependent) portions. The original design therefore was
221 and bus specific outer modules (machine dependent).
237 dependent module (where configuration is begun from and bus specific
244 soft state structure contains a machine/bus dependent vector (mdvec)
250 The machine dependent outer module must provide functional entry points
257 The machine dependent outer module code must also provide a set of
297 dependent vector as well as any other platform specific information that
306 Part of the isp_reset call may cause callbacks out to the bus dependent
309 Channel HBA).  The reason this is considered 'bus dependent' is that
310 only the bus dependent module may have the information that says how
311 one could perform I/O mapping and dependent (e.g., on a Solaris system)
320 platform dependent module that takes the appropriate steps to 'register'
342 this command. It also calls through the machine dependent vector
346 DMA mapping can be done in this bus dependent function. This is
356 left to the machine dependent platform function which called isp_start. In
358 SCSI subsystem. In other platforms, the machine dependent code has to
376 the machine dependent code supplied function isp_done is called with the
411 the bus dependent DMA mapping function). If this entry completes the
432 The platform dependent code may also therefore assume that if it is
435 to the platform dependent code to worry about avoiding any lock nesting
451 The driver core or platform dependent architecture issues that are specific
518 machine dependent layers with the ISPASYNC_CHANGE_NOTIFY code.
559 point. Other platforms manage this from the machine dependent layers. The