All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timo Teras <timo.teras@iki.fi>
To: Timo Teras <timo.teras@iki.fi>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>, linux-media@vger.kernel.org
Subject: Re: Terratec Grabby hwrev 2
Date: Thu, 28 Mar 2013 16:54:59 +0200	[thread overview]
Message-ID: <20130328165459.6231a5b1@vostro> (raw)
In-Reply-To: <20130328153556.0b58d1aa@vostro>

On Thu, 28 Mar 2013 15:35:56 +0200
Timo Teras <timo.teras@iki.fi> wrote:

> On Thu, 28 Mar 2013 09:40:52 -0300
> Mauro Carvalho Chehab <mchehab@redhat.com> wrote:
> 
> > Em Thu, 28 Mar 2013 10:52:01 +0200
> > Timo Teras <timo.teras@iki.fi> escreveu:
> > 
> > > On Wed, 27 Mar 2013 16:10:49 +0200
> > > Timo Teras <timo.teras@iki.fi> wrote:
> > > 
> > > > On Tue, 26 Mar 2013 10:20:56 +0200
> > > > Timo Teras <timo.teras@iki.fi> wrote:
> > > > 
> > > > > I did manage to get decent traces with USBlyzer evaluation
> > > > > version.
> > > > 
> > > > Nothing _that_ exciting there. Though, there's quite a bit of
> > > > differences on certain register writes. I tried copying the
> > > > changed parts, but did not really help.
> > > > 
> > > > Turning on saa7115 debug gave:
> > > > 
> > > > saa7115 1-0025: chip found @ 0x4a (ID 000000000000000) does not
> > > > match a known saa711x chip.
> > > 
> > > Well, I just made saa7115.c ignore this ID check, and defeault to
> > > saa7113 which is apparently the chip used.
> > > 
> > > And now it looks like things start to work a lot better.
> > > 
> > > Weird that the saa7113 chip is missing the ID string. Will
> > > continue testing.
> > 
> > That could happen if saa7113 is behind some I2C bridge and when
> > saa7113 is not found when the detection code is called.
> 
> Smells to me that they replaced the saa7113 with cheaper clone that
> does not support the ID string.
> 
> Sounds like the same issue as:
> http://www.spinics.net/lists/linux-media/msg57926.html
> 
> Additionally noted that something is not initialized right:
> 
> With PAL signal:
> - there's some junk pixel in beginning of each line (looks like pixes
>   from previous lines end), sync issue?
> - some junk lines at the end
> - distorted colors when white and black change between pixels

Still have not figured out this one. Could be probably related to the
saa7113 differences.

> With NTSC signal:
> - unable to get a lock, and the whole picture looks garbled

NTSC started working after I removed all the saa711x writes to
following registers:
 R_14_ANAL_ADC_COMPAT_CNTL
 R_15_VGATE_START_FID_CHG
 R_16_VGATE_STOP
 R_17_MISC_VGATE_CONF_AND_MSB

- Timo

  reply	other threads:[~2013-03-28 14:54 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
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 [this message]
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=20130328165459.6231a5b1@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.