From: Julian Scheel <julian@jusst.de>
To: Steffen Barszus <steffenbpunkt@googlemail.com>
Cc: "H. Ellenberger" <tuxoholic@hotmail.de>,
linux-media@vger.kernel.org,
Manu Abraham <abraham.manu@gmail.com>
Subject: Re: S2-3200 switching-timeouts on 2.6.38
Date: Thu, 24 Mar 2011 20:39:55 +0100 [thread overview]
Message-ID: <4D8B9E0B.5070901@jusst.de> (raw)
In-Reply-To: <AANLkTinbUxqwH0Cgi5Rx7TNx33W7ckFavYD9gCv4OC_H@mail.gmail.com>
Am 24.03.2011 19:32, schrieb Steffen Barszus:
> It has been done some work (and effort), to prove its having positive
> effect. you should allways
> have more then 1000 stations at any time on that SAT, if you see that maximum
> number of stations is somewhere at 1600. everything around 400 is
> broken hardware or driver.
Agreed, but this is why I asked about the difference between the channel
search with stb6100 patch only and both patches applied.
Nobody says that 400 channels are expected behaviour.
But the difference of less than 20 channels between both patches could
easily be caused by temporal availability of services. This is all I
said and all I suggested to proof.
Even a simple diff of both searches would be helpful. Just to check
which channels are missing.
I am not in the position to accept or reject this driver, just wanted to
be helpful in finding out if it's really needed.
> Please dont consider his post as single experience of a single user. The general
> perception was more like "Wow i can finally use that card and don't
> throw it away."
> from 10+ Users which i know of. So no matter if its considered done
> right or not.
> The tuning patch is out of question of improving the usability of the
> affected cards.
>
> The request has been, to prove that the changes at the stb6100 is not
> enough to actually
> fix the problem. This prove has been done now . The changes on the
> stb6100 is not enough,
> the changes at the stb0899 still has quite positive effect.
>
> So taking into account that the patch improves situation and doesn't
> have negative side
> effects for others, it might be wise to consider inclusion of the
> patch, even if it might not
> be the perfect solution from technical/theoretical perspective.
>
> I dont want to complain until the patch is in, its just: We have a
> problem, we have a solution.
> Lets use it and make this hardware useful for the people and lets do
> it right when time permits.
>
> There is still a handful of other patches for the same hardware
> floating around to improve other parts of that driver.
>
> I mean this hardware is known to work "less then perfect" since years, really.
>
> So please do something about it. Accept the helping hands.
>
> Thanks
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-03-24 19:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 18:19 S2-3200 switching-timeouts on 2.6.38 H. Ellenberger
2011-03-24 16:57 ` Julian Scheel
2011-03-24 18:32 ` Steffen Barszus
2011-03-24 19:39 ` Julian Scheel [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-25 15:01 Paul Franke
2011-03-25 17:53 ` Manu Abraham
2011-03-25 19:56 ` Paul Franke
2011-03-21 19:46 Rico Tzschichholz
2011-03-21 20:16 ` Randy Dunlap
2011-03-21 20:31 ` Manu Abraham
2011-03-22 9:53 ` Bjørn Mork
2011-03-22 10:15 ` Mauro Carvalho Chehab
2011-03-22 20:21 ` Manu Abraham
2011-03-22 11:33 ` Rico Tzschichholz
2011-03-22 13:07 ` Bjørn Mork
2011-03-22 20:54 ` Manu Abraham
2011-03-23 7:10 ` Rico Tzschichholz
2011-08-10 23:49 ` P. van Gaans
2011-08-11 20:45 ` P. van Gaans
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=4D8B9E0B.5070901@jusst.de \
--to=julian@jusst.de \
--cc=abraham.manu@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=steffenbpunkt@googlemail.com \
--cc=tuxoholic@hotmail.de \
/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