Re: Load Firmware with comedi_config

> On Wed, Nov 13, 2002 at 03:22:04PM +0100, Markus Dostal wrote:
> > I want load a firmware code with comedi_config, but I use the "opt1" and
> > "opt2" options for the bus and  slot indices (comedi_config [OPTIONS]
> > <device file> [<driver> <opt1>,<opt2>,...]).
> > In the first place the comedi_config function write the "opt1" and
"opt2"
> > options to the
> > "it.options[0]" and "it.options[1]". When the -i option is used the
> > "it.options[0]" and
> > "it.options[1]" are overwritten from the "init_data" pointer address and
the
> > "init_size". What can I do to use both: "driver initialization data" and
> > "bus/slot indices".

On Wednesday, November 13, 2002 9:40 PM, David Schleef wrote:
> The init_data, init_size options should probably be moved to
> COMEDI_NDEVCONFOPTS-2 and -1.  However, this needs to be done
> backwards-compatibly, which means comedi_config has to set
> _both_ 0,1 and 30,31 (unless 0,1 are otherwise set), and Comedi
> needs to be changed to use 30,31 (if non-zero), and fall back
> to 0,1.

This is a good idea. I implement this in the comedi_config function.
Do you also implement this for the next comedi version?


Markus Dostal

Received on 2002-11-14Z09:47:04