sun4/sys/fcode.h

42  * The FCode driver presents a private interface to the fcode
44  * at any time and is only provided for use by the fcode interpreter.
50  * The interpreter does an FC_GET_PARAMETERS ioctl to get the fcode
52  * of the device's fcode.
81  * data structure which is filled in by the driver with the fcode
83  * Offset 0 .. fcode len may be used as the offset to an mmap call to
84  * provide access to a copy of the device fcode. The unit address is
161  * FC_GET_FCODE_DATA: This ioctl allows userland portion of the fcode
162  * interpreter to get the fcode into a local buffer without having
165  * fcode buffer is allocated.
168  * has the fcode_size field set with the expected fcode length.
170  * copyout() to fill in the fcode_ptr buffer with fcode data.
294 #define	FC_GET_FCODE_SIZE	"sunos,get-fcode-size"
295 #define	FC_GET_FCODE		"sunos,get-fcode"
308 #define	FC_NO_FCODE	-3		/* Interpreter couldn't find fcode */
314  * for the fcode interpreter.
457 	void *fcode;			/* fcode kernel address */
458 	size_t fcode_size;		/* fcode size or zero */
480  * associated with this fcode request including the address of
481  * the mapped in and copied in fcode and it's size or NULL, 0
482  * if there is no fcode (the interpreter may look for a drop-in
483  * driver if there is no fcode), the unit address of child and
489  * about any allocations of kernel resources that the fcode
496     void *fcode, size_t fcode_size, char *unit_address, void *bus_args);
500     void *fcode, size_t fcode_size, char *unit_address,
505     void *fcode, size_t fcode_size, char *unit_address,
523  * and is defined in fcode.h
543  * Internal structure used to enque an fcode request
552 	fc_ops_t	*ap_ops;	/* driver's fcode ops function */
568  * Function to call to invoke the fcode interpreter.
576  * eventd to start the userland fcode interpreter process. The interpreter
577  * opens /dev/fcode, which clones an instance of the driver, and then
596  * The fcode implementation uses this function to wait for and 'de-queue'
597  * an fcode request.  It's triggered by a 'read' request from the
604  * When the fcode implementation is finished servicing a request, it calls this
611  * The fcode implementation uses these functions to manage