On 30/08/15 16:07, Johann Klammer wrote:
On 08/30/2015 11:53 AM, Malcolm Priestley wrote:
On 24/08/15 16:19, Johann Klammer wrote:
from gdb dump:
[...]
info = {
name = "ST STV0299 DVB-S", '\000' <repeats 111 times>, type = FE_QPSK,
frequency_min = 950000, frequency_max = 2150000,
frequency_stepsize = 125, frequency_tolerance = 0,
symbol_rate_min = 1000000, symbol_rate_max = 45000000,
symbol_rate_tolerance = 500, notifier_delay = 0,
caps = (FE_CAN_INVERSION_AUTO | FE_CAN_FEC_1_2 | FE_CAN_FEC_2_3 | FE_CAN_FEC_3_4 | FE_CAN_FEC_5_6 | FE_CAN_FEC_7_8 | FE_CAN_FEC_AUTO | FE_CAN_QPSK)},
[...]
when tuning:
[...]
Hi
..
[331020.207352] stv0299 does not support auto-inversion
[331020.507480] stv0299 does not support auto-inversion
[331020.807610] stv0299 does not support auto-inversion
[331021.107747] stv0299 does not support auto-inversion
[...]
(but how the heck should I know?)
I am using the stv0299 with no problems at all, the code hasn't changed much in years. I am using linux 4.2-rc6
boot/vmlinuz-4.1.0-1-586
Something must have changed. I updated kernel and got those messages.
I did not get then before. The vmlinuz.old
points to: boot/vmlinuz-3.14.15
vmlinuz points to: boot/vmlinuz-4.1.0-1-586
(debian testing binary .deb)
You shouldn't be getting that message as dvb core does the auto inversion for the driver.
It may have been exposed by trying oneshot tuning mode... not sure...
Yes, it is with setting oneshot.
Looks like the FE_CAN_INVERSION_AUTO flag is only bogus in
FE_TUNE_MODE_ONESHOT mode.
Obversely don't set INVERSION_AUTO bearing in mind when you do it
manually you have to tune first with it off and if that fails again with
it on.
Regards
Malcolm
--
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
