"Hadess: What are the plans for the future? The Rio600 will soon
be out... Or you would prefer to shift to other projects?"
"Keith: As far as the rio500 utils, we're going
to push to integrate the userspace and kernel driver interfaces so
that they're more transparent to users. Basically, everyone can
grab the same tarball/rpm and use it. If you have the modular
driver, it'll use that or fall over to the userspace driver. This
will hopefully make things less confusing for users, leave an easy
transition to userspace drivers (if Linux-usb heads that direction
in 2.5), and leave the module interface in place for the BSD guys
and for those choosing not to utilize usbdevfs (embedded systems
comes to mind). Other things we have planned are a separation of
low level code into librio500 and higher level access code into
librio500_api for ease of longer term maintenance, and to present a
nicer interface for anyone writing gui interfaces. This will bring
us to v1.0 at which point I think we'll enter maintenance mode.
We've talked about the rio600 some, but I think the protocols
are going to be totally different, in the way that the rio500 was
different than the rio300. If this is true, my rio500 and I won't
be much help. I think the rio600 is going to be a new project for a
new group of people. I suspect I'll be moving into some new project
after v1.0, but who knows . ."
Some of the products that appear on this site are from companies from which QuinStreet receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. QuinStreet does not include all companies or all types of products available in the marketplace.