Getting Started with QNX Neutrino - QNX Software Systems

More documents

Recommendations

Info

Alphabetical listing of connect and I/O functions © 2009, QNX Software Systems GmbH & Co. KG. member; the driver is to set the outgoing structure’s nbytes member to the number of bytes transferred. Note that the input and output data structures are zero-padded so that they align with each other. This means that the implicit data area begins at the same address in the input and output structures. If using the helper routine iofunc_devctl(), beware that it’ll return the constant _RESMGR_DEFAULT in the case where it can’t do anything with the devctl() message. This return value is there to decouple legitimate errno return values from an “unrecognized command” return value. Upon receiving a _RESMGR_DEFAULT, the base-layer library will respond with an errno of ENOSYS, which the client’s devctl() library function will translate into ENOTTY (which is the “correct” POSIX value). It’s up to your function to check the open mode against the operation; no checking is done anywhere in either the client’s devctl() library or in the resource manager library. For example, it’s possible to open a resource manager “read-only” and then issue a devctl() to it telling it to “format the hard disk” (which is very much a “write” operation). It would be prudent to verify the open mode first before proceeding with the operation. Note that the range of dcmd values you can use is limited (0x0000 through 0x0FFF inclusive is reserved for QSS). Other values may be in use; take a look through the include files that have the name . Returns: The status via the helper macro _RESMGR_STATUS and the reply buffer (with reply data, if required). For an example, take a look at “A simple io_devctl() example,” below. io_dup() int io_dup (resmgr_context_t *ctp, io_dup_t *msg, RESMGR_OCB_T *ocb) Classification: I/O Default handler: NULL — handled by base layer Helper functions: none Client functions: dup(), dup2(), fcntl(), fork(), spawn*(), vfork() Messages: _IO_DUP Data structure: struct _io_dup { uint16_t type; uint16_t combine_len; struct _msg_info info; uint32_t reserved; uint32_t key; }; typedef union { 234 Chapter 5 • Resource Managers April 30, 2009
© 2009, QNX Software Systems GmbH & Co. KG. Alphabetical listing of connect and I/O functions struct _io_dup i; } io_dup_t; Description: This is the dup() message handler. As with the io_close_dup(), you won’t likely handle this message yourself. Instead, the base-layer library will handle it. Returns: The status via the helper macro _RESMGR_STATUS. io_fdinfo() int io_fdinfo (resmgr_context_t *ctp, io_fdinfo_t *msg, RESMGR_OCB_T *ocb) Classification: I/O Default handler: iofunc_fdinfo_default() Helper functions: iofunc_fdinfo() Client function: iofdinfo() Messages: _IO_FDINFO Data structure: struct _io_fdinfo { uint16_t type; uint16_t combine_len; uint32_t flags; int32_t path_len; uint32_t reserved; }; struct _io_fdinfo_reply { uint32_t zero [2]; struct _fdinfo info; }; typedef union { struct _io_fdinfo i; struct _io_fdinfo_reply o; } io_fdinfo_t; Description: This function is used to allow clients to retrieve information directly about the attributes and pathname which is associated with a file descriptor. The client-side function iofdinfo() is used. The path string implicitly follows the struct _io_fdinfo_reply data structure. Use of the default function is sufficient for discretely-manifested pathname resource managers. Returns: The length of the path string being returned is set via the helper macro _IO_SET_FDINFO_LEN. io_link() int io_link (resmgr_context_t *ctp, io_link_t *msg, RESMGR_HANDLE_T *handle, io_link_extra_t *extra) Classification: Connect April 30, 2009 Chapter 5 • Resource Managers 235
Page 1 and 2:
QNX Neutrino RTOS Getting Started w
Page 3 and 4:
Contents About This Guide xi What y
Page 5 and 6:
© 2009, QNX Software Systems GmbH
Page 7 and 8:
Page 9 and 10:
List of Figures A process as a cont
Page 11:
About This Guide April 30, 2009 Abo
Page 14 and 15:
Typographical conventions © 2009,
Page 17:
Foreword to the First Edition by Pe
Page 20 and 21:
Page 23 and 24:
Page 25 and 26:
Page 27:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95:
Chapter 2 Message Passing In this c
Page 98 and 99:
Message passing and client/server
Page 100 and 101:
Message passing and client/server
Page 102 and 103:
Multiple threads © 2009, QNX Softw
Page 104 and 105:
Multiple threads © 2009, QNX Softw
Page 106 and 107:
Using message passing © 2009, QNX
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Pulses © 2009, QNX Software System
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Message passing over a network © 2
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Priority inheritance © 2009, QNX S
Page 148 and 149:
Priority inheritance © 2009, QNX S
Page 151:
Chapter 3 Clocks, Timers, and Getti
Page 154 and 155:
Clocks and timers © 2009, QNX Soft
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Using timers © 2009, QNX Software
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Advanced topics © 2009, QNX Softwa
Page 178 and 179:
Page 180 and 181:
Page 183:
Chapter 4 Interrupts In this chapte
Page 186 and 187:
Neutrino and interrupts © 2009, QN
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Writing interrupt handlers © 2009,
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201: TIME TIME Writing interrupt handler
Page 202 and 203: Writing interrupt handlers © 2009,
Page 204 and 205: Summary © 2009, QNX Software Syste
Page 207 and 208: © 2009, QNX Software Systems GmbH
Page 249: © 2009, QNX Software Systems GmbH
Page 299: © 2009, QNX Software Systems GmbH
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319:
Appendix B Calling 911 In this appe
Page 322 and 323:
Seeking professional help © 2009,
Page 324 and 325:
Seeking professional help © 2009,
Page 327:
Appendix C Sample Programs In this
Page 330 and 331:
atoz.c © 2009, QNX Software System
Page 332 and 333:
atoz.c © 2009, QNX Software System
Page 334 and 335:
time1.c © 2009, QNX Software Syste
Page 336 and 337:
time1.c © 2009, QNX Software Syste
Page 338 and 339:
tp1.c © 2009, QNX Software Systems
Page 340 and 341:
tt1.c © 2009, QNX Software Systems
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Index ! /dev/null resource manager
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
show all

Getting Started with QNX Neutrino - QNX Software Systems

Create successful ePaper yourself

Delete template?

Save as template?