From: poma <pomidorabelisima@gmail.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>,
linux-media@vger.kernel.org
Subject: Re: pctv452e
Date: Wed, 11 Jul 2012 00:54:28 +0200 [thread overview]
Message-ID: <4FFCB2A4.4040108@gmail.com> (raw)
In-Reply-To: <CAGoCfizj8buVoMc8qOY-NxKa53KnXNnZLekpr6-wLU08PM5kEw@mail.gmail.com>
On 07/10/2012 05:58 PM, Devin Heitmueller wrote:
> On Tue, Jul 10, 2012 at 11:51 AM, poma <pomidorabelisima@gmail.com> wrote:
>>> Is this pctv452e device known to have poor reception?
>
> Traditionally speaking, these problems are usually not the hardware
> itself - it tends to be crappy Linux drivers. Somebody gets support
> working for a chip on some product, and then somebody else does a
> cut/paste of the code to make some other product work. They see it
> getting signal lock under optimal tuning conditions and declare
> success.
>
> Making any given device work *well* tends to be much harder than
> making it work at all.
>
> Want to rule out bad hardware design? Drop it into a Windows machine
> and see how it performs. If it works fine under Windows but poorly
> under Linux, then you definitely have a Linux driver problem.
>
> Devin
>
This one is for Marx?
cheers,
poma
next prev parent reply other threads:[~2012-07-10 22:54 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 16:04 pctv452e Steve Hill
2012-07-04 16:22 ` pctv452e Antti Palosaari
2012-07-04 18:46 ` pctv452e Marx
2012-07-04 18:53 ` pctv452e André Weidemann
2012-07-04 19:01 ` pctv452e Antti Palosaari
2012-07-05 13:14 ` pctv452e Marx
2012-07-05 14:23 ` pctv452e Antti Palosaari
2012-07-06 6:13 ` pctv452e Marx
2012-07-06 9:34 ` pctv452e Antti Palosaari
2012-07-06 11:04 ` pctv452e Marx
2012-07-06 18:24 ` pctv452e Antti Palosaari
2012-07-06 22:23 ` pctv452e Marx
2012-07-07 0:00 ` pctv452e Antti Palosaari
2012-07-07 23:07 ` pctv452e Marx
2012-07-08 12:32 ` pctv452e Antti Palosaari
2012-07-09 6:24 ` pctv452e Marx
2012-07-09 8:42 ` pctv452e Antti Palosaari
2012-07-09 16:44 ` pctv452e Marx
2012-07-09 17:38 ` pctv452e Antti Palosaari
2012-07-09 17:46 ` pctv452e Antti Palosaari
2012-07-10 6:39 ` pctv452e Marx
2012-07-10 9:33 ` pctv452e Antti Palosaari
2012-07-10 21:08 ` pctv452e Marx
2012-07-10 23:13 ` pctv452e Antti Palosaari
2012-07-11 6:25 ` pctv452e Marx
2012-07-11 10:00 ` pctv452e Antti Palosaari
2012-07-09 18:21 ` pctv452e poma
2012-07-10 6:43 ` pctv452e Marx
2012-07-10 15:51 ` pctv452e poma
2012-07-10 15:58 ` pctv452e Devin Heitmueller
2012-07-10 22:54 ` poma [this message]
2012-08-03 16:56 ` pctv452e Steve Hill
-- strict thread matches above, loose matches on Subject: below --
2012-07-02 16:33 pctv452e Steve Hill
2012-07-03 7:46 ` pctv452e Marx
2012-07-03 23:04 ` pctv452e Antti Palosaari
2012-07-04 7:51 ` pctv452e Marx
2013-07-06 13:29 ` pctv452e Antti Palosaari
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=4FFCB2A4.4040108@gmail.com \
--to=pomidorabelisima@gmail.com \
--cc=dheitmueller@kernellabs.com \
--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.