public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Rakitnican <semirocket@gmail.com>
To: "hermann pitton" <hermann-pitton@arcor.de>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: Report: Compro Videomate Vista T750F
Date: Mon, 13 Jul 2009 16:36:15 +0200	[thread overview]
Message-ID: <op.uw0f6php80yj81@localhost> (raw)
In-Reply-To: <1247434386.5152.28.camel@pc07.localdom.local>

  Hi Hermann,

  On Sun, 12 Jul 2009 23:33:06 +0200, hermann pitton
  <hermann-pitton@arcor.de> wrote:

  [snip]
> Hm, if I get it right, without using windows previously the XCeive at
> 0x61 is not found and then it is tried in vain to use the qt1010 at
> 0x62.
>
> Also, after using windows gpio20 seems to be high.
> Maybe that is the gpio to get the tuner out of reset.
>
> Please try the attached patch as a shot into the dark.
>
  [snip]

No, I pay attention when I test for channel that XCeive gets recognized
as 0x61. When I do cold boot, or windows reboot its always gets
recognized at 0x61. Sometimes (I don't know exactly what triggers that)
the 0x61 gets omitted, and the result is that XCeive get recognized as
0x62. The result is that channel is not showing any more, apparently.

I think that xc2028-27.fw file load failures triggers that behavior,
because when I reboot linux with loading firmware failures, that
behavior is showing (from what I have noticed).

Sorry for the gpio alert, but I did some logging, and the gpio value
varies, and depends on computer state. But it seems that is same in both
cases after all. (details http://pastebin.com/f4c511dfc)

I tried your patch, too, and it's not working. Thank you for trying.

  reply	other threads:[~2009-07-13 14:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-12 11:30 Report: Compro Videomate Vista T750F Samuel Rakitnican
2009-07-12 21:33 ` hermann pitton
2009-07-13 14:36   ` Samuel Rakitnican [this message]
2009-07-15  0:51     ` hermann pitton
2009-07-15 18:35   ` Samuel Rakitnican
2009-07-18  0:58     ` hermann pitton
2009-07-18 10:40       ` Samuel Rakitničan
2009-07-19 23:16         ` hermann pitton

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=op.uw0f6php80yj81@localhost \
    --to=semirocket@gmail.com \
    --cc=hermann-pitton@arcor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox