Project Home
Project Home
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - iofunc functions: (6 Items)
   
iofunc functions  
In Getting Started with QNX Neutrino, Rob Krten refers to a couple of iofunc functions that I couldn't find in the 
source:

  iofunc_close_default()
  iofunc_read()

Do these functions actually exist?

The book also refers to resmgr_start(), which is defined in <sys/resmgr_compat.h>, but isn't documented. Should it be?

Thanks.
Re: iofunc functions  
Steve Reid wrote:
> In Getting Started with QNX Neutrino, Rob Krten refers to a couple of 
> iofunc functions that I couldn't find in the source:
> 
>   iofunc_close_default()

This one doesn't exists - there is iofunc_close_ocb_default() and iofunc_close_dup_default()

>   iofunc_read()

Can't find this one anywhere.  There is an iofunc_read_default() though...

> Do these functions actually exist?
> 
> The book also refers to resmgr_start(), which is defined in 
> <sys/resmgr_compat.h>, but isn't documented. Should it be?

The compat stuff is only for people who wrote a resmgr back before we switched
to the dispatch callout interface.  Was resmgr_start() not documented back then? :-)

> 
> Thanks.
> 
> _______________________________________________
> OSTech
> http://community.qnx.com/sf/go/post6236
> 

-- 
cburgess@qnx.com
Re: iofunc functions  
Steve Reid wrote:
> In Getting Started with QNX Neutrino, Rob Krten refers to a couple of 
> iofunc functions that I couldn't find in the source:
> 
>   iofunc_close_default()
>   iofunc_read()

I can't find those in the source either.

But in lib/c/public/sys/iofunc.h there is an iofunc_read_default(). There
are also two closes:
iofunc_close_ocb_default() and iofunc_close_dup_default().

I suspect "iofunc_cread()" is a typo. Perhaps someone knows the history of
the iofunc_*close*_default() functions.

-ad
Re: iofunc functions  
iofunc_read() is listed in the doc page for io_read() as a helper function, along
with iofunc_read_verify()

iofunc_close_default() is listed as a helper for io_close_ocb(), so I think
it was a typo, and should be listed as iofunc_close_ocb_default()

Attilla Danko wrote:
> Steve Reid wrote:
>  > In Getting Started with QNX Neutrino, Rob Krten refers to a couple of
>  > iofunc functions that I couldn't find in the source:
>  >
>  >   iofunc_close_default()
>  >   iofunc_read()
> 
> I can't find those in the source either.
> 
> But in lib/c/public/sys/iofunc.h there is an iofunc_read_default(). There
> are also two closes:
> iofunc_close_ocb_default() and iofunc_close_dup_default().
> 
> I suspect "iofunc_cread()" is a typo. Perhaps someone knows the history of
> the iofunc_*close*_default() functions.
> 
> -ad
> 
> _______________________________________________
> OSTech
> http://community.qnx.com/sf/go/post6239
> 

-- 
cburgess@qnx.com
Re: iofunc functions  
I've created a doc PR. I'll correct the reference to iofunc_close_ocb_default(), and it sounds like I should just remove
 the one to iofunc_read().

Here's what the book says about resmgr_start():

The control structure (type resmgr_attr_t) is passed to the resmgr_start() function, which looks at the various members 
and handles the main receive loop of the resource manager. 

Should I change it to something like this?

The control structure (type resmgr_attr_t) is passed to the resmgr_attach() function, which puts the resource manager's 
path into the general pathname space and binds requests on this path to a dispatch handle. 

(The book already discusses the dispatch interface, and there are no other references to resmgr_start()).

Thanks for your help.


Re: iofunc functions  
On Fri, Mar 28, 2008 at 9:57 AM, Attilla Danko <adanko@qnx.com> wrote:

> Steve Reid wrote:
> > In Getting Started with QNX Neutrino, Rob Krten refers to a couple of
> > iofunc functions that I couldn't find in the source:
> >
> >   iofunc_close_default()
> >   iofunc_read()
>
> I can't find those in the source either.
>
> But in lib/c/public/sys/iofunc.h there is an iofunc_read_default(). There
> are also two closes:
> iofunc_close_ocb_default() and iofunc_close_dup_default().
>
> I suspect "iofunc_cread()" is a typo. Perhaps someone knows the history of
> the iofunc_*close*_default() functions.
>
Should be iofunc_read_default() (assuming I have the correct context) and
there
are two close functions deliberately, and with very different
functionalities.  The
one most people are interested in is iofunc_close_ocb_default().

Hope this helps,
 Thomas