All of lore.kernel.org
 help / color / mirror / Atom feed
From: Devin Heitmueller <dheitmueller@kernellabs.com>
To: SebaX75 <sebax75@yahoo.it>
Cc: linux-media@vger.kernel.org
Subject: Re: Possible em28xx regression for Pinnacle Dazzle Tv Hybrid Stick 320E
Date: Sat, 13 Feb 2010 21:04:16 -0500	[thread overview]
Message-ID: <829197381002131804p184ad1b6ndf11e1d713e9f335@mail.gmail.com> (raw)
In-Reply-To: <4B775931.8020208@yahoo.it>

On Sat, Feb 13, 2010 at 9:00 PM, SebaX75 <sebax75@yahoo.it> wrote:
> Hi,
> I've already wrote on the problem that I'll go to explain and that was
> already solved by Devin. It was solved and a call for tester was done, and
> all was working (em28xx DVB modeswitching change); logically I've used
> actual tree (updated with hg today).
> Now the problem: with scandvb, during a scan for channels, the adapter is
> able to recognize and tune only the first mux found in the list, for all the
> other mux the output is "tuning failed"; I can change the mux order, but
> always only first mux is tuned and channel recognized.

I would have to fall on my sword with this one - the modeswitching
changes weren't committed because of Mauro's concerns about power
management (and while I think he is incorrect in this regard, I never
took the time to prove it).  And I failed to check in the one line
change which was strobing the reset when the dvb gpio get called
(which was what was causing the zl10353 driver state to get out of
sync with the chip).

In other words, neither fix ever actually made it into the mainline
v4l-dvb tree.

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

      reply	other threads:[~2010-02-14  2:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-14  2:00 Possible em28xx regression for Pinnacle Dazzle Tv Hybrid Stick 320E SebaX75
2010-02-14  2:04 ` Devin Heitmueller [this message]

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=829197381002131804p184ad1b6ndf11e1d713e9f335@mail.gmail.com \
    --to=dheitmueller@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sebax75@yahoo.it \
    /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.