Getting Started with QNX Neutrino - QNX Software Systems

Alphabetical listing of connect and I/O functions
© 2009, QNX Software Systems GmbH & Co. KG.
typedef union {
struct _io_notify i;
struct _io_notify_reply o;
} io_notify_t;
Description: The handler is responsible for installing, polling, or removing a
notification handler. The action and flags determine the kind of notification operation
and conditions; the event is a struct sigevent structure that defines the
notification event (if any) that the client wishes to be signaled with. You’d use the
MsgDeliverEvent() or iofunc_notify_trigger() functions to deliver the event to the
client.
Returns: The status via the helper macro _RESMGR_STATUS; the flags are returned
via message reply.
io_open()
int io_open (resmgr_context_t *ctp, io_open_t *msg,
RESMGR_HANDLE_T *handle, void *extra)
Classification: Connect
Default handler: iofunc_open_default()
Helper functions: iofunc_open(), iofunc_ocb_attach()
Client functions: open(), fopen(), sopen() (and others)
Messages: _IO_CONNECT with one of _IO_CONNECT_COMBINE,
_IO_CONNECT_COMBINE_CLOSE or _IO_CONNECT_OPEN subtypes.
Data structure:
struct _io_connect {
// internal fields (as described above)
uint16_t path_len;
uint8_t extra_type;
uint16_t extra_len;
char path [1];
};
struct _io_connect_link_reply {
uint32_t reserved1 [2];
uint8_t eflag;
uint8_t reserved2 [3];
uint32_t umask;
uint16_t nentries;
uint16_t path_len;
};
typedef union {
struct _io_connect
connect;
struct _io_connect_link_reply link_reply;
} io_open_t;
Description: This is the main entry point into the resource manager. It checks that the
client indeed has the appropriate permissions to open the file, binds the OCB to the
internal library structures (via resmgr_bind_ocb(), oriofunc_ocb_attach()), and
242 Chapter 5 • Resource Managers April 30, 2009