usbatm xusbatm.c,NONE,1.1

Roman Kagan rkagan at
Mon Apr 4 01:25:24 EDT 2005

On Sat, Apr 02, 2005 at 11:50:59PM +0200, matthieu castet wrote:
> Roman Kagan wrote:
> >  Hi,
> >
> >I've added to CVS a new driver, xusbatm (couldn't come up with a better
> >name).  This is a dumb usbatm-based driver, whose purpose is to handle
> >the devices which are not taken care of by dedicated drivers.  Such
> >modems are supposed to be initialized in user space, and then handed
> >over to this driver, specifying vendor ID, product ID, rx and tx
> >endpoints and, if needed, rx and tx padding, as module parameters.
> >(Support for different interfaces will be added later.)
> Why don't you use array as module parameter (644 permision will allow to 
> edit them via sysfs), and then in the xusbatm_usb_probe set this value 
> in the struct ?

I'm not sure I understand...  Do you suggest using arrays for each
parameter as a means to support multiple differnet modems at the same

As to editing the parameters in sysfs, modifying vendor / product IDs
wont probably work, and then for the rest it wont make sense.


More information about the Usbatm mailing list