Hi Wim,
which kind of work is required to add new camera models?
Yuri
Hi Yuri,
Work required to produce another set of test cases:
All those *tc.zip products are in fact test cases for the initial high speed and high bandwidth isochronous transfer support in the usbehcd.sys host controller driver. To produce one for yet another webcam requires the output from lsusb -v for that webcam to be analyzed by me first. Then I would compose a rexx procedure to try and test the uvc probe and commit phases that I want these new test cases to use. From that I would also know how to setup the required bandwidth and alternate interface settings. Finally I would change the compile time options in the turbo assembler source code plus possibly some other changes necessary to get this webcam working and build the new product. Since the initial high speed and high bandwidth isochronous transfer support in the usbehcd.sys host controller drivers works, I don't think I should spend any more time doing this.
Work required to produce generic webcam support:
Since usbecd.sys is intended for prototyping, it has some drawbacks. First of all it cannot provide enough buffering to sustain reliably a continuous video stream. Secondly each webcam would require its own unique config.sys statement. Therefore support for isochronous transfers need to be added to usbresmg.sys so it can be used instead. This is something I am considering to dive into when time permits. Both weblook and webview have been coded in turbo assembler. As a starter some other programmer could convert/rewrite these using C instead. This would make adding support for other uvc webcams easier. Then the inspection of the usb descriptors need to be added and the outcome of the probe and commit phase need to be acted upon to setup the required alternate interfaces and the isochronous buffering.
Regards, Wim.