From: "André Weidemann" <Andre.Weidemann@web.de>
To: Guy Martin <gmsoft@tuxicoman.be>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] TT S2-1600 allow more current for diseqc
Date: Wed, 28 Apr 2010 14:29:10 +0200 [thread overview]
Message-ID: <4BD82A16.5020301@web.de> (raw)
In-Reply-To: <20100428103303.2fe4c9ea@zombie>
Hello Guy,
On 28.04.2010 10:33, Guy Martin wrote:
> On Wed, 28 Apr 2010 09:45:39 +0200
> André Weidemann<Andre.Weidemann@web.de> wrote:
>
>> I advise not to pull this change into the kernel sources.
>> The card has only been testet with the a maximum current of 515mA.
>> Anything above is outside the specification for this card.
>
>
> I'm currently running two of these cards in the same box with this
> patch.
> Actually, later on I've even set curlim = SEC_CURRENT_LIM_OFF because
> sometimes diseqc wasn't working fine and that seemed to solve the
> problem.
>
> I used to have skystar2 cards before and I did not run into those
> issues. Diseqc just worked fine.
>
> For reference each tt s2 is plugged to a diseqc switch with 4 output,
> each output connected to a quad lnb.
How come there is such a high current drain to drive the switch plus the
LNBs? From what I understand, the switch should only power one LNB at a
time. Usually the switch plus the LNB should not drain more than
300-400mA, or am I wrong here?
> Is there another way to solve this ?
> Maybe add a module parameter for people who want to override the
> default ?
I think this could be done. Nevertheless, the card would still operate
outside its specification.
Regards
André
next prev parent reply other threads:[~2010-04-28 12:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 21:18 [PATCH] TT S2-1600 allow more current for diseqc Guy Martin
2010-04-28 7:45 ` André Weidemann
2010-04-28 8:33 ` Guy Martin
2010-04-28 12:29 ` André Weidemann [this message]
2010-04-28 13:19 ` Guy Martin
2010-04-28 13:13 ` Manu Abraham
2010-04-30 0:31 ` hermann pitton
2010-04-30 5:44 ` André Weidemann
2010-04-30 22:53 ` 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=4BD82A16.5020301@web.de \
--to=andre.weidemann@web.de \
--cc=gmsoft@tuxicoman.be \
--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