I've done more investigation and tried to understand what scan does.
Basically everything depends on the ability of the chip to tune a
channel with parameters set to XXX_AUTO.
So I was able to track down the "problem" (still don't know whether it
is a problem or not) to this specific issue.
This is BBC ONE in London uk-CrystalPalace.
A:505833330:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_3_4:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:600:601:4164
B:505833330:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_AUTO:600:601:4164
C:505833330:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_AUTO:600:601:4164
A is the usual channel
B is the attempt to move as much as possible to AUTO
C is the wished configuration (the one that would let kaffeine do the AUTO scan)
output of tzap (I needed to change slightly the parsing to accept
XXX_AUTO everywhere)
channel A
status 1f | signal 8b2e | snr 0000 | ber 001fffff | unc 00000000 | FE_HAS_LOCK
status 1f | signal 8b1c | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
channel B
status 1f | signal 8b1c | snr 0000 | ber 001fffff | unc 00000000 | FE_HAS_LOCK
status 1f | signal 8b0e | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
channel C
status 01 | signal 8b06 | snr 0000 | ber 001fffff | unc 00000000 |
status 01 | signal 8b26 | snr 0000 | ber 001fffff | unc 00000000 |
Is it an issue or am I lost in the blue?
I enabled the debug in dib3000mc and dibx000_common but I had no
output during those attempts.
I'm sorry if I had already written other mails about that, but I need
time to understand how all those pieces are linked together. I would
like to help somehow, to do some testing changing some of the settings
in the driver but I still haven't found any documentation about the
dib3000mc. Is there a datasheet available of this chip? or reverse
engineering the Windows driver is the only way?
Thanks for your time.