Lines Matching refs:platform

81 as little OS platform support code as possible.
100 driver that is specifically designed for a single platform and a single
105 implementation of platform differences must not clutter up the common
106 code with platform specific defines. Instead, some reasonable layering
107 semantics are defined such that platform specifics can be kept in the
108 platform specific code.
221 The driver is split into a core (machine independent) module and platform
235 The platform/bus specific modules (and definitions) depend on each
236 platform, and they provide both definitions and functions for the core
237 module's use.  Generally a platform module set is split into a bus
239 support functions reside) and relatively thin platform specific layer
240 which serves as the interconnect with the rest of this platform's SCSI
277 	MEMZERO(dst, src)                       platform zeroing function
294 Typically a bus specific module for a platform (e.g., one that wants
295 to configure a PCI card) is entered via that platform's configuration
298 dependent vector as well as any other platform specific information that
314 of interrupts should this platform be able to finish configuration in
321 platform dependent module that takes the appropriate steps to 'register'
322 this HBA with this platform's SCSI subsystem.  Examining either the
329 itself with this platform's SCSI subsystem. One assumed action for this
330 is the registry of a function that the SCSI subsystem for this platform
333 The platform specific module function that receives this will do whatever
336 a complete marshalling/demarshalling of this platform's SCSI command
357 left to the machine dependent platform function which called isp_start. In
379 informs the SCSI subsystem for this platform that a command is complete.
389 Each platform module has to provide an isp_async entry point that will
419 Because almost no platform provides basic SCSI Subsystem target mode
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
445 masking could be dropped. It's now up to each platform to figure out how
452 The driver core or platform dependent architecture issues that are specific