public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jelle de Jong <jelledejong@powercraft.nl>
To: Markus Rechberger <mrechberger@gmail.com>
Cc: Devin Heitmueller <dheitmueller@kernellabs.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Call for testers: Terratec Cinergy T XS USB support
Date: Fri, 03 Jul 2009 18:09:08 +0200	[thread overview]
Message-ID: <4A4E2D24.8070504@powercraft.nl> (raw)
In-Reply-To: <d9def9db0907030313t4ea3685m8f63981696d63c96@mail.gmail.com>

Markus Rechberger wrote:
> Hi all,
> 
> On Mon, Jun 29, 2009 at 4:00 PM, Devin
> Heitmueller<dheitmueller@kernellabs.com> wrote:
>> Hello all,
>>
>> A few weeks ago, I did some work on support for the Terratec Cinergy T
>> XS USB product. �I successfully got the zl10353 version working and
>> issued a PULL request last week
>> (http://www.kernellabs.com/hg/~dheitmueller/em28xx-terratec-zl10353)
>>
> 
> There will be an alternative driver entirely in userspace available
> which works across all major kernelversions and distributions. It will
> support the old em28xx devices and handle audio routing for the most
> popular TV applications directly.
> 
> This system makes compiling the drivers unnecessary across all
> available linux systems between 2.6.15 and ongoing. This package also
> allows commercial drivers from vendors, the API itself is almost the
> same as the video4linux/linuxdvb API. Installing a driver takes less
> than five seconds without having to take care about the kernel API or
> having to set up a development system. Aside of that it's operating
> system independent (working on Linux, MacOSX and FreeBSD).
> I think this is the way to go for the future since it adds more
> possibilities to the drivers, and it eases up and speeds up driver
> development dramatically.

Still keep feeling an itch to response to this. I am not interested in
any proprietary driver binaries and I tried to work with you and
contributed documentation, testing and lot of time to your em28xx
project. I feel mislead and wasted my time trying to help you. Please
don't response to this mail in this thread make a separate public thread
if you want to discus it. I don't like thread highjacking. You are more
then welcome to contribute code back in small patches for one change at
a time that meets the Linux kernel licensing and coding guidelines. I
sometimes got the feeling you are doing more good then harm working for
Empiatech.

Best regards,

Jelle de Jong

  parent reply	other threads:[~2009-07-03 16:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29 14:00 Call for testers: Terratec Cinergy T XS USB support Devin Heitmueller
2009-07-03 10:13 ` Markus Rechberger
2009-07-03 16:06   ` Simon Kenyon
2009-07-03 16:09   ` Jelle de Jong [this message]
2009-07-03 16:14     ` Jelle de Jong
2009-07-03 15:21 ` Jelle de Jong
2009-07-09 11:50   ` Jelle de Jong

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=4A4E2D24.8070504@powercraft.nl \
    --to=jelledejong@powercraft.nl \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mrechberger@gmail.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