Lines Matching refs:dependent

222 and bus specific outer modules (machine dependent).
238 dependent module (where configuration is begun from and bus specific
245 soft state structure contains a machine/bus dependent vector (mdvec)
251 The machine dependent outer module must provide functional entry points
258 The machine dependent outer module code must also provide a set of
298 dependent vector as well as any other platform specific information that
307 Part of the isp_reset call may cause callbacks out to the bus dependent
310 Channel HBA).  The reason this is considered 'bus dependent' is that
311 only the bus dependent module may have the information that says how
312 one could perform I/O mapping and dependent (e.g., on a Solaris system)
321 platform dependent module that takes the appropriate steps to 'register'
343 this command. It also calls through the machine dependent vector
347 DMA mapping can be done in this bus dependent function. This is
357 left to the machine dependent platform function which called isp_start. In
359 SCSI subsystem. In other platforms, the machine dependent code has to
377 the machine dependent code supplied function isp_done is called with the
412 the bus dependent DMA mapping function). If this entry completes the
433 The platform dependent code may also therefore assume that if it is
436 to the platform dependent code to worry about avoiding any lock nesting
452 The driver core or platform dependent architecture issues that are specific
519 machine dependent layers with the ISPASYNC_CHANGE_NOTIFY code.
560 point. Other platforms manage this from the machine dependent layers. The