public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: CityK <cityk@rogers.com>
To: Jay Novak <novakjs@umich.edu>,
	Devin Heitmueller <devin.heitmueller@gmail.com>,
	V4L <video4linux-list@redhat.com>
Subject: Re: AVerMedia EZMaker USB Gold
Date: Sun, 16 Nov 2008 13:02:37 -0500	[thread overview]
Message-ID: <4920603D.20906@rogers.com> (raw)
In-Reply-To: <f3ae23390811140559i5e235c3bvabe8d5004d57165@mail.gmail.com>

Jay Novak wrote:
> >I don't believe there is a driver that supports the 7136 part.
>
> do you know when one is coming? or how hard it world be to developing
> my own is that part that much deferent from the saa713x? Im a computer
> science student at UofM and i think i could help with it with some
> guidance.
>
> Jay Novak
>
> On Thu, Nov 13, 2008 at 7:04 PM, CityK <cityk@rogers.com
> <mailto:cityk@rogers.com>> wrote:
>
>     >
>     > Im using the AVerMedia EZMaker USB Gold it has a SAA7136AE. is
>     there any
>     > support for this device in linux?
>
>     I don't believe there is a driver that supports the 7136 part.
>
>     --
>     video4linux-list mailing list
>     Unsubscribe mailto:video4linux-list-request@redhat.com
>     <mailto:video4linux-list-request@redhat.com>?subject=unsubscribe
>     https://www.redhat.com/mailman/listinfo/video4linux-list
>
>

Hi Jay,

Please make sure to "reply to all" so that the messages don't get
dropped from the list. (also please don't top post)

Re: 7136

Currently there haven't been many reports of devices using this IC. 
Last spring, Janneg obtained a device using the 7136 and this lead to a
brief discussion on irc about it.  IIRC, Manu Abrahams, who had access
to the datasheet at the time and upon a cursory inspection of its info,
thought that it was likely that support for the chip could be
incorporated into the existing 713x driver.  I forget any specifics
about the chip, but I seem to recall that there is something unique
about it.  (I also seem to recall that it has component input that is
good enough for capturing full res HDTV...not that many vendors would
ever implement access to that though).

Anyway, I haven't seen much mention of the chip since, but did happen to
coincidently catch this post just the other day:
* http://marc.info/?l=linux-video&m=122675953217105&w=2
The importance of which becomes clear when seeing:
*
http://www.linuxtv.org/wiki/index.php/Pinnacle_PCTV_HD_Ultimate_Stick_(808e)

So I have cc'ed Devin in on the message as perhaps you two could
collaborate on this, and I imagine Devin would appreciate any help once
all the "fun" legal aspect is settled with NXP.


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

  parent reply	other threads:[~2008-11-16 18:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14  0:04 AVerMedia EZMaker USB Gold CityK
     [not found] ` <f3ae23390811140559i5e235c3bvabe8d5004d57165@mail.gmail.com>
2008-11-16 18:02   ` CityK [this message]
2008-11-16 18:16     ` Devin Heitmueller
2008-11-16 18:45       ` CityK
2008-11-16 18:54         ` CityK
     [not found] <f3ae23390811100801g717a1793ge23c904b820da6ba@mail.gmail.com>
2008-11-13  1:06 ` Jay Novak

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=4920603D.20906@rogers.com \
    --to=cityk@rogers.com \
    --cc=devin.heitmueller@gmail.com \
    --cc=novakjs@umich.edu \
    --cc=video4linux-list@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