public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
* linux/include/dvb/frontend.h : missing capability flags
@ 2009-02-18 18:41 wk
  0 siblings, 0 replies; only message in thread
From: wk @ 2009-02-18 18:41 UTC (permalink / raw)
  To: linux-media

Some time ago two new members were added in frontend.h  to
enum fe_code_rate:

-  FEC_3_5
-  FEC_9_10

But the matching capability flags for that are still missing, signalling 
applications support for those:

- FE_CAN_FEC_3_5
- FE_CAN_FEC_9_10

It would be possible to use  0x1000000, 0x2000000 for that to get some 
consistent and logically understandable file,
but there would be also the second possibility to remove
    FE_CAN_FEC_1_2
    FE_CAN_FEC_2_3
    FE_CAN_FEC_3_4
    FE_CAN_FEC_4_5
    FE_CAN_FEC_5_6
    FE_CAN_FEC_6_7
    FE_CAN_FEC_7_8
    FE_CAN_FEC_8_9

This would assume, that all related drivers supports all of these (what 
they should do anyway..).
This would also make sense, since all other frontend related properties 
except modulation are also not explicitly stated
(for example there's also no "FE_CAN_BANDWIDTH_6_MHZ or 
FE_CAN_GUARD_INTERVAL_1_8")

Opinions?


Secondly, inside frontend.h  "DTV_API_VERSION" is defined twice, line 
302 and 303:

#define DTV_API_VERSION                35
#define DTV_API_VERSION                35



Regards,
Winfried









^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2009-02-18 18:41 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-02-18 18:41 linux/include/dvb/frontend.h : missing capability flags wk

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox