> -----Original Message-----
> From: Durwin De La Rue [mailto:community-noreply@qnx.com] 
> Sent: June 12, 2009 1:16 PM
> To: general-filesystems
> Subject: Re: RE: Driver startup sequence
> 
> > Durwin,
> > 
> > etfsctl parses arguments from left to right.  Doing
> > 
> > etfsctl -i -d /dev/etfs2
> > And
> > etfsctl -i -d /dev/etfs1
> > 
> > Will actually give you the information for /dev/etfs2 (the default 
> > value for -d) twice.
> 
> How do I get info on etfs1?  etfsctl -d /dev/etfs1 -i  ?

Yes.  You have to set the device before passing the operations to be
performed on the device.

> 
> > 
> > As for where the options are processed, that's done in the 
> options() 
> > function, called from 
> product/trunk/lib/etfs/main.c:etfs_main().  The 
> > "-D" option is processed by devio_options() called from 
> devio_init().
> 
> Is devio_options where the '-r' option gets parsed?  This 
> call has code for only the '-D'.  I would have expected and 
> error using '-r' since it is not handled.


devio_options() is only responsible for the string passed to the -D
argument.  The parsing of the reset of the options are done in the file
/product/trunk/lib/etfs/options.c, in the function options().   This
function is called from etfs_main() in the file
/product/trunk/lib/etfs/main.c

> 
> > 
> > David
> > 
> > > -----Original Message-----
> > > From: Durwin De La Rue [mailto:community-noreply@qnx.com]
> > > Sent: June 12, 2009 12:44 PM
> > > To: general-filesystems
> > > Subject: Driver startup sequence
> > > 
> > > I need to debug the code but can't find where the arguments are 
> > > getting parsed.  I start with this command.
> > > 
> > > > fs-etfs-nand -r 12800
> > > 
> > > To check things out, I do this.
> > > 
> > > > etfsctl -i -d /dev/etfs2
> > > 
> > > However, both etfs1 and etfs2 show the same information.
> > > 
> > > # etfsctl -i -d /dev/etfs2
> > > Device NAND2caa
> > >    Blocks Clusters/Block Clustersize Totalsize
> > >      2048             64        2048 268435456
> > > Pools
> > >    Clean Spare Filthy Inactive Xpool Cache
> > >        0     0   1947   124608  2048    64
> > > Counts
> > >     Erase    Avg     Read    Cache    Write     Mine     Copy 
> > >   Defrag  BadBlks
> > >         0      0        0        0        0        0        0 
> > >        0        1
> > > Errors
> > >    Ecc  Chksum   Device
> > >      0       0        0
> > > 
> > > So, I would like to follow the startup sequence to see 
> what all is 
> > > getting done.  I have a project which I think came from working 
> > > driver.  The name is os-efsys_efsys.  I have devio.c and 
> chipio.c.  
> > > The file chipio.c has the main function defined like this.
> > > 
> > > int main(int argc, char *argv[])
> > > {
> > > 	return(etfs_main(argc, argv));
> > > }
> > > 
> > > From here I am lost.  Some how etfs_main has to make 
> calls back to 
> > > the source in devio and chipio.  I can't find anyplace where the 
> > > commandline option '-r #' is parsed.  I am familiar with 
> how Linux 
> > > drivers are written so kernel can make calls to init, read, and 
> > > write, but this is different.
> > > 
> > > Any direction will help.
> > > 
> > > _______________________________________________
> > >...