All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Unicap Imaging API
Date: Tue, 04 May 2010 16:57:47 +0200	[thread overview]
Message-ID: <hrpclb$dhp$1@dough.gmane.org> (raw)
In-Reply-To: <108741502.29960271272980979803.JavaMail.root@sz0029a.westchester.pa.mail.comcast.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04-05-10 15:49, John Buckley wrote:
> 
> 
> Hello, 
> 
> Does anyone have any experience getting the Unicap imaging API working on OpenEmbedded? 

OE has recipes for 'ucview' and 'unicap'. Angstrom should have binaries
from both in the arm feeds.

regards,

Koen

> 
> 
> 
> This API that was specifically written for cameras from The Imaging Source.com ( www.theimagingsource.com ) 
> 
> 
> 
> I just recently found out that the cameras are not UVC compliant and require the Unicap API to communicate with them. 
> 
> One of their cameras is listed on the UVC compliant hardware list!!!  The salesman convinced me it was UVC compliant and now the API developer is telling me it is not UVC compliant. 
> 
> 
> 
> I had developed a large application in GStreamer with a UVC compliant camera and I have made great progress.  I don't want to lose ground by heading down a dead end. 
> 
> 
> 
> John 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFL4DXrMkyGM64RGpERAutUAKCkP4OAnjtNXYssPV64Gj8ycPD32gCeKW3f
tC6/ly7AhmcWQHrqLF8sOhE=
=kARb
-----END PGP SIGNATURE-----




      reply	other threads:[~2010-05-04 15:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04 13:49 Unicap Imaging API John Buckley
2010-05-04 14:57 ` Koen Kooi [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='hrpclb$dhp$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.