Bug 118038 - dvbd cannot cope with dvb-t channels.conf file produced by dvbscan
Summary: dvbd cannot cope with dvb-t channels.conf file produced by dvbscan
Status: VERIFIED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Final
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Forgotten User ZhJd0F0L3x
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 97395
  Show dependency treegraph
 
Reported: 2005-09-20 15:51 UTC by Forgotten User ZhJd0F0L3x
Modified: 2007-06-05 11:20 UTC (History)
2 users (show)

See Also:
Found By: Component Test
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
allow to parse all tune parameters uttered by dvbscan (1.91 KB, patch)
2005-09-20 16:36 UTC, Forgotten User ZhJd0F0L3x
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User ZhJd0F0L3x 2005-09-20 15:51:47 UTC
If i scan in Nürnberg with
dvbscan /usr/share/dvb/scan/dvb-t/de-Nuernberg > channels.conf
and later try to use this channels.conf, dvbd does not start.

/var/log/dvbd/dvbd.log says:
Fatal Error: no translation for "FEC_AUTO" in dvbtuneparamscommon.cpp:47

channels.conf contains
arte:184500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_AUTO:QAM_16:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE:33:34:2
Comment 1 Forgotten User ZhJd0F0L3x 2005-09-20 16:36:42 UTC
Created attachment 50440 [details]
allow to parse all tune parameters uttered by dvbscan

This is my proposed fix. It is a bit broader and just covers all possibilities
that dvbscan can generate.
I did this by reading include/linux/dvb/frontend.h and dump-zap.c from
dvb-utils :-)

Torsten, Ludwig, could you give it an eye if there are obvious errors? It
compiled fine ;-)
Comment 2 Ludwig Nussel 2005-09-26 09:28:07 UTC
I have no clue about that stuff so it doesn't look wrong to me. 
Comment 3 Forgotten User ZhJd0F0L3x 2005-09-26 13:02:38 UTC
thanks. I tested it at home and it did not crash immediately => submitted to
STABLE :-)