All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Will Manley <will@williammanley.net>
Cc: linux-media@vger.kernel.org, amy.zhou@magewell.net
Subject: Re: Driver for Magewell PCIe capture cards
Date: Mon, 9 May 2016 07:31:15 -0300	[thread overview]
Message-ID: <20160509073115.714c0c74@recife.lan> (raw)
In-Reply-To: <1462464586.3004166.599182921.0162873F@webmail.messagingengine.com>

Hi Will,

Em Thu, 05 May 2016 17:09:46 +0100
Will Manley <will@williammanley.net> escreveu:

> Hi There
> 
> Magewell are a manufacturer of video-capture devices.  They have both
> USB and PCIe devices.  The USB devices use the upstream uvcvideo driver
> and Magewell currently provide proprietary drivers for their PCIe
> products.
> 
> http://www.magewell.com/
> 
> I've approached Magewell about having upstream Linux drivers for these
> PCIe devices and they are open to sharing hardware documentation and the
> sources to their proprietary drivers under an NDA for the purpose of
> developing an upstream Linux driver.  This is where I'm hoping that the
> linux driver project can help out.
> 
> My interest in this is that I want to be using Magewell PCIe capture
> cards in my company's products ( https://stb-tester.com/ ), but I don't
> want to be stuck with proprietary drivers.  I'm hoping I can facilitate
> because I have some limited kernel developer experience, but I wouldn't
> be confident enough to write an entire v4l driver myself.

The main question here is who will be developing the driver. It should
be someone with time, interest and access to the hardware and their
specs. It is probably easier if you're willing to do it, as you have
already what is needed. People at this mailing list can help you by
reviewing the patches once done, pointing you on how to correct things
that are not ok.

If you're not willing to do it yourself, then you'll likely need to 
sponsor someone to do it (either finding a hobbyist and donating him some
hardware or hiring some professional).

The need of a NDA can make it harder for hobbyists, as several won't
sign such documents. Also, the NDA should be carefully written to
allow to release the open source drivers after the job is done.

> 
> I'd originally posted this to the linux driver project mailing list[1]. 
> Greg KH suggested I repost here as there aren't many v4l developers on
> that list.
> 
> [1]:
> http://thread.gmane.org/gmane.linux.drivers.driver-project.devel/88218
> 
> Please let me know what additional information I can provide to get this
> process started.
> 
> Thanks
> 
> Will
> ---
> William Manley
> stb-tester.com
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 
Thanks,
Mauro

      reply	other threads:[~2016-05-09 10:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-05 16:09 Driver for Magewell PCIe capture cards Will Manley
2016-05-09 10:31 ` Mauro Carvalho Chehab [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=20160509073115.714c0c74@recife.lan \
    --to=mchehab@osg.samsung.com \
    --cc=amy.zhou@magewell.net \
    --cc=linux-media@vger.kernel.org \
    --cc=will@williammanley.net \
    /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.