From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: John McMaster <johndmcmaster@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Anchor Chips V4L2 driver
Date: Fri, 03 Jun 2011 09:15:33 -0300 [thread overview]
Message-ID: <4DE8D065.7020502@redhat.com> (raw)
In-Reply-To: <4DE873B4.4050306@gmail.com>
Em 03-06-2011 02:40, John McMaster escreveu:
> I'd like to write a driver for an Anchor Chips (seems to be bought by
> Cypress) USB camera Linux driver sold as an AmScope MD1800. It seems
> like this implies I need to write a V4L2 driver. The camera does not
> seem its currently supported (checked on Fedora 13 / 2.6.34.8) and I did
> not find any information on it in mailing list archives. Does anyone
> know or can help me identify if a similar camera might already be
> supported?
I've no idea. Better to wait for a couple days for developers to manifest
about that, if they're already working on it.
> lsusb gives the following output:
>
> Bus 001 Device 111: ID 0547:4d88 Anchor Chips, Inc.
>
> I've started reading the "Video for Linux Two API Specification" which
> seems like a good starting point and will move onto using source code as
> appropriate. Any help would be appreciated. Thanks!
You'll find other useful information at linuxtv.org wiki page. The better
is to write it as a sub-driver for gspca. The gspca core have already all
that it is needed for cameras. So, you'll need to focus only at the device-specific
stuff.
Cheers,
Mauro
next prev parent reply other threads:[~2011-06-03 12:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 5:40 Anchor Chips V4L2 driver John McMaster
2011-06-03 12:15 ` Mauro Carvalho Chehab [this message]
2011-06-03 13:22 ` Hans de Goede
2011-06-06 5:40 ` John McMaster
2011-06-06 7:43 ` Hans de Goede
2011-06-07 5:24 ` John McMaster
2011-06-07 7:35 ` Hans de Goede
2011-11-06 6:36 ` John McMaster
2011-11-06 9:02 ` Mauro Carvalho Chehab
2011-11-06 18:08 ` John McMaster
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=4DE8D065.7020502@redhat.com \
--to=mchehab@redhat.com \
--cc=johndmcmaster@gmail.com \
--cc=linux-media@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox