From: John McMaster <johndmcmaster@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>, mchehab@redhat.com
Cc: linux-media@vger.kernel.org
Subject: Re: Anchor Chips V4L2 driver
Date: Sun, 05 Jun 2011 22:40:50 -0700 [thread overview]
Message-ID: <4DEC6862.8000006@gmail.com> (raw)
In-Reply-To: <4DE8E018.7070007@redhat.com>
On 06/03/2011 06:22 AM, Hans de Goede wrote:
> Hi,
>
> On 06/03/2011 02:15 PM, Mauro Carvalho Chehab wrote:
>> 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.
>
> I can second that you should definitely use gspca for usb webcam(ish)
> device
> drivers. As for how to go about this, first of all grep through the
> windows drivers
> for strings which may hint on the actual bridge chip used, chances are
> good
> there is an already supported bridge inside the camera.
>
> If not then make usb dumps, and start reverse engineering ...
>
> Usually it is enough to replay the windows init sequence to get the
> device
> to stream over either an bulk or iso endpoint, and then it is time to
> figure out what that stream contains (jpeg, raw bayer, some custom
> format ???)
>
> Regards,
>
> Hans
Thanks for the response. I replayed some packets (using libusb) and am
able to get something resembling the desired image through its bulk
endpoint. So now I just need to figure out how to decode it better,
options, etc. I'll post back to the list once I get something
moderately stable running and have taken a swing at the kernel driver.
John
next prev parent reply other threads:[~2011-06-06 5:40 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
2011-06-03 13:22 ` Hans de Goede
2011-06-06 5:40 ` John McMaster [this message]
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=4DEC6862.8000006@gmail.com \
--to=johndmcmaster@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
/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