All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timo Teras <timo.teras@iki.fi>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Terratec Grabby hwrev 2
Date: Mon, 25 Mar 2013 19:48:20 +0200	[thread overview]
Message-ID: <20130325194820.7c122834@vostro> (raw)
In-Reply-To: <20130325143647.3da1360f@redhat.com>

On Mon, 25 Mar 2013 14:36:47 -0300
Mauro Carvalho Chehab <mchehab@redhat.com> wrote:

> Em Mon, 25 Mar 2013 19:08:46 +0200
> Timo Teras <timo.teras@iki.fi> escreveu:
> 
> > I just bought a Terratec Grabby hardware revision 2 in hopes that it
> > would work on my linux box.
> > 
> > But alas, I got only sound working. It seems that analog video
> > picture grabbing does not work.
> > 
> > I tried kernels 3.4.34-grsec, 3.7.1 (vanilla), 3.8.2-grsec and
> > 3.9.0-rc4 (vanilla). And all fail the same way - no video data
> > received.
> > 
> > The USB ID is same as on the revision 1 board:
> > Bus 005 Device 002: ID 0ccd:0096 TerraTec Electronic GmbH
> > 
> > And it is properly detected as Grabby.
> > 
> > It seems that the videobuf2 changes for 3.9.0-rc4 resulted in better
> > debug logging, and it implies that the application (ffmpeg 1.1.4) is
> > behaving well: all buffers are allocated, mmapped, queued, streamon
> > called. But no data is received from the dongle. I also tested
> > mencoder and it fails in similar manner.
> > 
> > Dmesg (on 3.9.0-rc4) tells after module load the following:
> >  
> > [ 1250.076845] em2860 #0: AC97 vendor ID = 0x60f160f1
> > [ 1250.086814] em2860 #0: AC97 features = 0x60f1
> 
> That looks weird on my eyes: 3 AC97 reads returned 0x60f1. I suspect
> that the GPIOs for this device are different than on version 1.

Yes, I just noticed this now too. It seems something went wrong when
loading em28xx with a bunch of debug logging enabled. On normal load it
returns instead:

[   12.453631] em2860 #0: AC97 vendor ID = 0x83847650
[   12.463650] em2860 #0: AC97 features = 0x6a90
[   12.463658] em2860 #0: Empia 202 AC97 audio processor detected

> > Any suggestions how to debug/fix this?
> 
> The better is to run the original driver at a recent version of KVM
> with USB port forward enabled, and capture the USB logs. There are
> some pages at LinuxTV wiki explaining how to do it.

Oh, ok. Seems Wireshark/USBPcap might be better option for me as I
don't have KVMed Windows install handy. Will try to get traces from it.

- Timo

  reply	other threads:[~2013-03-25 17:47 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25 17:08 Terratec Grabby hwrev 2 Timo Teras
2013-03-25 17:36 ` Mauro Carvalho Chehab
2013-03-25 17:48   ` Timo Teras [this message]
2013-03-25 18:32     ` Mauro Carvalho Chehab
2013-03-25 19:12       ` Timo Teras
2013-03-26  8:20         ` Timo Teras
2013-03-27 14:10           ` Timo Teras
2013-03-28  8:52             ` Timo Teras
2013-03-28 12:40               ` Mauro Carvalho Chehab
2013-03-28 13:35                 ` Timo Teras
2013-03-28 14:54                   ` Timo Teras
2013-05-01 17:11                     ` Jon Arne Jørgensen
2013-05-02  7:04                       ` Timo Teras
2013-05-03  5:47                         ` Timo Teras
2013-05-03  9:13                           ` Jon Arne Jørgensen
2013-05-03 11:12                             ` Ezequiel Garcia
2013-03-28 15:22                   ` Mauro Carvalho Chehab
2013-03-30  9:54                     ` Timo Teras
2013-04-01 17:26                       ` Frank Schäfer
2013-04-02  5:43                         ` Timo Teras
2013-04-02 16:39                           ` Frank Schäfer
2013-04-03  8:27                             ` Timo Teras
2013-04-05 15:33                               ` Frank Schäfer
2013-04-29 12:26                                 ` Timo Teras
2013-05-03  5:50                                   ` Timo Teras
2013-05-10 11:04         ` Tomasz Moń
2013-03-27 17:37 ` Frank Schäfer
2013-03-27 17:57   ` Timo Teras
2013-03-27 18:04     ` Timo Teras
2013-03-27 20:12       ` Frank Schäfer

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=20130325194820.7c122834@vostro \
    --to=timo.teras@iki.fi \
    --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 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.