OS/2, eCS & ArcaOS - Technical > Web applications
What are we mising to run "Jitsi" on the Browser ?
Martin Iturbide:
Hi.
I also forgot that we have libusb ported to OS/2. Libusb.dll (the one ported to OS/2) connects to USBCALLS.DLL.
So maybe that can be interesting, but not sure if Firefox uses it on other platforms.
Regards
Wim Brul:
Hi Martin,
--- Quote ---Outside Firefox I think we also miss a way to connect Wim Brul's USBECD (webcam driver) to firefox.
--- End quote ---
The way to go is via the generic usbcalls interface. My specific usbecd.sys driver should not be used. The current OS/2 port of libusb needs to be enhanced to include support for isochronous transfers.
Perhaps an implementation based on Webcamd - a FreeBSD userspace Linux Kernal Drive framework could be used? Webcamd is a small daemon that enables about 1500 different USB based webcam, DVB and remote control USB devices under the FreeBSD-8.0 and later operating system. The webcam daemon is basically an application which is a port of Video4Linux USB drivers into userspace on FreeBSD. The daemon currently depends on libc, pthreads, libusb and libcuse4bsd.
Perhaps one or more of the Webcam programs working with webcamd in FreeBSD could be ported?
Martin Iturbide:
Hi Wim
--- Quote from: Wim Brul on January 05, 2017, 07:56:42 pm ---The way to go is via the generic usbcalls interface. My specific usbecd.sys driver should not be used.
--- End quote ---
Just curious, when you say "usbecd.sys driver should not be used" do you mean that it should not be called directly by an application? or that is should not be used at all?
Regards
Ian Manners:
Hi Martin,
I think Wim means that HIS version of usbecd.sys should not be used. usbecd.sys is the USB v2.x specific driver so it is required for USB v2.x devices. By using the standard version with the usbcalls library, it ensures we do not end up with different USB driver versions going forward.
At least that is how I've interpreted it :)
usbecd.sys = USB 2.0 Extended Control Driver
Wim Brul:
Hi Martin,
--- Quote from: Martin Iturbide on January 06, 2017, 09:59:16 pm ---
--- Quote from: Wim Brul on January 05, 2017, 07:56:42 pm ---The way to go is via the generic usbcalls interface. My specific usbecd.sys driver should not be used.
--- End quote ---
Just curious, when you say "usbecd.sys driver should not be used" do you mean that it should not be called directly by an application? or that is should not be used at all?
--- End quote ---
No and No. This is what I meant: To access webcams from an application like firefox you should not use my usbecd.sys driver. There are 2 reasons for that. First of all you would need a very specific device driver statement in config.sys for the particular webcam that a user wants to use. Plugging in a different webcam would require config.sys to be changed. And secondly usbecd.sys has by design insufficient isochronous buffering capability to sustain high speed and high bandwidth operation especially on larger image sizes.
Navigation
[0] Message Index
[*] Previous page
Go to full version