Prev: uninstall mirror display driver
Next: NdisMIndicateReceivePacket from ProtocolReceive problem
From: Bruce on 7 Sep 2005 02:16
Hi,

We are using an OmniVision imaging board, that uses the 3620 chip, which is
bridged by a Cypress board. I am fairly new to device drivers and not sure
what i need to do to implement a device driver that will treat this board as
an imaging board. I need to be able to use DirectX to stream video and
capture images off the USB device, which the supplied Cpress device drivers
do not support.

From what i understand at the moment, the driver is made of a collection of
system drivers and a custom driver. The firware for the USB device does not
fully implement the Imaging specification, so i suspect that the cutom device
driver will mimic that the board is an imaging device.

I have implemented the inf file, which includes and uses the DirectX support:

[CyUsb.NT]
Include=ks.inf, kscaptur.inf, ksfilter.inf
Needs=KS.Registration,KSCAPTUR.Registration.NT

Any help would be most appreciated.

Many Thanks,

--
Bruce Philp
Software Engineer
Astron Clinica Ltd
From: Tim Roberts on 8 Sep 2005 00:17
"Bruce" <bruce.philp(a)astronclinica.com> wrote:
>
>We are using an OmniVision imaging board, that uses the 3620 chip, which is
>bridged by a Cypress board. I am fairly new to device drivers and not sure
>what i need to do to implement a device driver that will treat this board as
>an imaging board. I need to be able to use DirectX to stream video and
>capture images off the USB device, which the supplied Cpress device drivers
>do not support.

What DO the supplied drivers support?

>From what i understand at the moment, the driver is made of a collection of
>system drivers and a custom driver. The firware for the USB device does not
>fully implement the Imaging specification, so i suspect that the cutom device
>driver will mimic that the board is an imaging device.

Possible. It's also possible that it's just a TWAIN driver. The only
references to the 3620 I found were for still image cameras. Is this
designed to be used in a streaming environment? What do you see in the USB
descriptors? Is there an isochronous endpoint, or just bulk?
--
- Tim Roberts, timr(a)probo.com
Providenza & Boekelheide, Inc.
From: Bruce on 8 Sep 2005 04:10
Hi Tim,

There is bulk transfer, so we can stream data from the chip. At the moment,
as when we install the CYUSB driver, we can capture a single frame, but
through writting our simple C++ app that talks uses the CYUSB interface
supplied.

Many Thanks,
Bruce



--
Bruce Philp
Software Engineer
Astron Clinica Ltd


"Tim Roberts" wrote:

> "Bruce" <bruce.philp(a)astronclinica.com> wrote:
> >
> >We are using an OmniVision imaging board, that uses the 3620 chip, which is
> >bridged by a Cypress board. I am fairly new to device drivers and not sure
> >what i need to do to implement a device driver that will treat this board as
> >an imaging board. I need to be able to use DirectX to stream video and
> >capture images off the USB device, which the supplied Cpress device drivers
> >do not support.
>
> What DO the supplied drivers support?
>
> >From what i understand at the moment, the driver is made of a collection of
> >system drivers and a custom driver. The firware for the USB device does not
> >fully implement the Imaging specification, so i suspect that the cutom device
> >driver will mimic that the board is an imaging device.
>
> Possible. It's also possible that it's just a TWAIN driver. The only
> references to the 3620 I found were for still image cameras. Is this
> designed to be used in a streaming environment? What do you see in the USB
> descriptors? Is there an isochronous endpoint, or just bulk?
> --
> - Tim Roberts, timr(a)probo.com
> Providenza & Boekelheide, Inc.
>
From: Tim Roberts on 9 Sep 2005 23:29
"Bruce" <bruce.philp(a)astronclinica.com> wrote:
>
>There is bulk transfer, so we can stream data from the chip.

Do you understand that your conclusion does not necessarily follow from
your premise? Bulk does not imply streaming.
--
- Tim Roberts, timr(a)probo.com
Providenza & Boekelheide, Inc.
 | 
Pages: 1
Prev: uninstall mirror display driver
Next: NdisMIndicateReceivePacket from ProtocolReceive problem