From: Knut Behrends <knb@gfz-potsdam.de>
To: linux-media@vger.kernel.org
Subject: terratec grabby 2 on linux - follow-up Q to discussion from mar/apr 2013
Date: Tue, 14 May 2013 18:00:16 +0200 [thread overview]
Message-ID: <51925F90.30305@gfz-potsdam.de> (raw)
Hi all,
my first post
I am a Linux user who bought a Terratec Grabby 2 analog-video-to-usb
encoding device, which I cannot get to work on Linux.
I noticed a thread on this mailing list a few weeks ago.
http://www.mail-archive.com/linux-media@vger.kernel.org/msg60286.html
I get exactly the same error messages (from dmesg) as the initiator of
that forum-thread.
In any event, I infer from the long forum-thread that the problem with
the new chips inside the Grabby 2 has been solved, or partly solved.
Some people posted patches to this mailing list.
I don't know how complete the new solution is.
Do I just need to grab an em28xx*.c file from the bleeding edge of the
kernel source tree?
How can I, as an interested end-user use that new driver code? Should I
simply wait for a new kernel being distributed by Canonical that will
have new patches included eventually?
Do I have to compile a patched .c file myself and copy it to
/lib/modules/3.8.0-19-generic/kernel/drivers/media/usb/em28xx/
directory on my linux box, replacing an older version? SHould I use DKMS
for this following a howto guide such as
http://wiki.centos.org/HowTos/BuildingKernelModules
My linux system is a raring ringtail Ubuntu,
Linux 3.8.0-19-generic #30-Ubuntu SMP Wed May 1 16:35:23 UTC 2013
x86_64 GNU/Linux
my need to use the grabby is not that urgent. Would be nice to use that
camcorder on my main desktop PC, which happens to be the most powerful
computer I have full access to.
Any hints?
Best regards,
Knut Behrends
--
____________________________________________________________________________
Knut Behrends Phone: +49 (0) 331 288 1688
Potsdam 14473 KeyID: 0xF22CACEF (PGP Public Key)
____________________________________________________________________________
reply other threads:[~2013-05-14 16:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51925F90.30305@gfz-potsdam.de \
--to=knb@gfz-potsdam.de \
--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 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.