Moi
On 02/20/2015 01:33 AM, Eponymous - wrote:
Hi.
I have a couple of issues with the si2168.c dvb-frontend in kernel v
3.19.0. To get the firnware to load I've had to increase the #define
TIMEOUT to 150 from 50. I read another post
(http://www.spinics.net/lists/linux-media/msg84198.html) where another
user had to do the same modification.
@ Antti Palosaari: Since the 50ms value you came up with was just
based on some "trail and error", would it be possible to submit a
change upstream to increase this timeout since it's likely others are
going to encounter this issue?
It is increased to 70 ms already,
commit 551c33e729f654ecfaed00ad399f5d2a631b72cb
Author: Jurgen Kramer <gtmkramer@xxxxxxxxx>
Date: Mon Dec 8 05:30:44 2014 -0300
[media] Si2168: increase timeout to fix firmware loading
If it is not enough, then send patch which increased it even more.
Have to check if that fix never applied to stable, as there is no Cc
stable I added.... Mauro has applied patch from patchwork, not from pull
request I made:
https://patchwork.linuxtv.org/patch/27960/
http://git.linuxtv.org/cgit.cgi/anttip/media_tree.git/log/?h=si2168_fix
The second issue I have is that where I am based (UK) we have both
DVB-T and DVB-T2 muxes and I can't get a single tuner to be able to
tune to both transports, but looking through the Si2168.c code, I'm
having trouble working out how (if at all) this is achieved?
It's not the case where we can only tune to DVB-T OR DVB-T2 is it? If
so, that's far from ideal...
Are there any workarounds if true?
I don't understand what you mean. Likely you are not understanding how
DVB-T and DVB-T2 works. There is transmitter which uses DVB-T or DVB-T2,
not both standards same time. You have to select used standard according
to transmitter specs and make proper tuning request. Driver could do
DVB-T, DVB-T2 and DVB-C, but only one transmission is possible to
receive as once per tuner.
regards
Antti
--
http://palosaari.fi/
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
