aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/media/dvb
Commit message (Collapse)AuthorAge
...
* | | [media] dm1105: handle errors from dvb_net_initJonathan Nieder2012-01-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Clean up and error out if dvb_net_init fails (for example due to ENOMEM). This involves moving the dvb_net_init call to before frontend_init to make cleaning up a little easier. From an audit of dvb_net_init callers, now that dvb_net_init lets callers know about errors. Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb-bt8xx: handle errors from dvb_net_initJonathan Nieder2012-01-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Clean up and error out if dvb_net_init fails (for example when running out of memory). From an audit of dvb_net_init callers, now that dvb_net_init has learned to return a nonzero value from time to time. [mchehab.redhat.com: codingstyle fix: printk() should include KERN_ facility level] Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] flexcop: handle errors from dvb_net_initJonathan Nieder2012-01-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | Bail out if dvb_net_init encounters an error (for example an out-of-memory condition), now that it reports them. [mchehab@redhat.com: CodingStyle fix: don't use "if ((ret = foo()) < 0)"] Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] ttusb-budget: use goto for exception handlingJonathan Nieder2012-01-06
| | | | | | | | | | | | | | | | | | | | | | | | Avoid some repetition by adopting the usual "goto err" idiom for error handling. Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb-bt8xx: use goto based exception handlingJonathan Nieder2012-01-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Repeating the same cleanup code in each error handling path makes life unnecessarily difficult for reviewers, who much check each instance of the same copy+pasted code separately. A "goto" to the end of the function is more maintainable and conveys the intent more clearly. While we're touching this code, also lift some assignments from "if" conditionals for simplicity. No functional change intended. Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] DVB: dvb_net_init: return -errno on errorJonathan Nieder2012-01-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | dvb_net_init unconditionally returns 0. Callers such as videobuf_dvb_register_frontend examine dvbnet->dvbdev instead of the return value to tell whether the operation succeeded. If it has been set to a valid pointer, success; if it was left equal to NULL, failure. Alas, there is an edge case where that logic does not work as well: when network support has been compiled out (CONFIG_DVB_NET=n), we want dvb_net_init and related operations to behave as no-ops and always succeed, but there is no appropriate value to which to set dvb->dvbdev to indicate this. Let dvb_net_init return a meaningful error code, as preparation for adapting callers to look at that instead. The only immediate impact of this patch should be to make the few callers that already check for an error code from dvb_net_init behave a little more sensibly when it fails. Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] it913x ver 1.18 Turn pid filter off by caps option onlyMalcolm Priestley2012-01-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Turn the pid filter off by caps option only. This is so the full stream is passed to demuxer and not limited by pid count. Signed-off-by: Malcolm Priestley <tvboxspy@gmail.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] lmedm04 DM04/QQBOX ver 1.91 turn pid filter off by caps option onlyMalcolm Priestley2012-01-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Turn the pid filter off by caps option only. This is so the full stream is passed to demuxer and not limited by pid count. Signed-off-by: Malcolm Priestley <tvboxspy@gmail.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dw2102: use symbolic names for dw2102_table indicesJonathan Nieder2012-01-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | dw2102_properties et al refer to entries in the USB-id table using hard-coded indices, as in "&dw2102_table[6]", which means adding new entries before the end of the list has the potential to introduce bugs in code elsewhere in the file. Use C99-style initializers with symbolic names for each index to avoid this. This way, other device tables wanting to reuse the USB ids can use expressions like "&dw2102_table[TEVII_S630]" that do not change as the entries in the table are reordered. Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] it913x add support for IT9135 9006 devicesMalcolm Priestley2012-01-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Support for IT1935 9006 devices. 9006 have version 2 type chip. 9006 devices should use dvb-usb-it9135-02.fw firmware. On the device tested the tuner id was set to 0 which meant the driver used tuner id 0x38. The device functioned normally. Signed-off-by: Malcolm Priestley <tvboxspy@gmail.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] drxk_hard: fix locking issues when changing the delsysMauro Carvalho Chehab2012-01-05
| | | | | | | | | | | | Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] drxk: create only one frontend for both DVB-C and DVB-TMauro Carvalho Chehab2012-01-05
| | | | | | | | | | | | | | | | | | | | | | | | Instead of creating two DVB frontend entries for the same device, create just one entry, and fill the delivery_system according with the supported standards. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] drxk: remove ops.info.frequency_stepsize from DVB-CMauro Carvalho Chehab2012-01-05
| | | | | | | | | | | | | | | | | | | | | ops.info.frequency_stepsize is used only for DVB-T & friends. For DVB-C, the step size is calculated using the symbol rate. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb_frontend: improve documentation on set_delivery_system()Mauro Carvalho Chehab2012-01-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | While this patch change some things, the updated fields there are used just on printk, so it shouldn't cause any functional changes. Yet, this routine is a little complex, so explain a little more how it works. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb_frontend: Update the dynamic info->typeMauro Carvalho Chehab2012-01-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of changing the ops.info.type struct, updates only the data that will be returned to userspace. Also add some debug messages to help tracking such issues. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb_frontend: regression fix: add a missing inc inside the loopMauro Carvalho Chehab2012-01-05
| | | | | | | | | | | | | | | | | | without it, the loop will run forever! Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] Don't test for ops->info.type inside driversMauro Carvalho Chehab2012-01-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Now, ops->info.type is handled inside the dvb_frontend core, only for DVBv3 calls, and according with the delivery system. So, drivers should not care or use it, otherwise, it may have issues with DVBv5 calls. The drivers that were still using it were detected via this small temporary hack: --- a/include/linux/dvb/frontend.h +++ b/include/linux/dvb/frontend.h @@ -29,13 +29,16 @@ #include <linux/types.h> typedef enum fe_type { +#if defined(__DVB_CORE__) || !defined (__KERNEL__) FE_QPSK, FE_QAM, FE_OFDM, FE_ATSC +#else +FE_FOOO +#endif } fe_type_t; - typedef enum fe_caps { FE_IS_STUPID = 0, FE_CAN_INVERSION_AUTO = 0x1, Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] drxk: Add support for parallel mode and prints mpeg modeMauro Carvalho Chehab2012-01-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | While the driver has support for both serial and parallel mode, There's was way to select serial mode via configuration. Add a config option for that, while keeping the default in serial mode. Also, at debug mode, it will now print a message when mpeg is enabled/disabled, and showing if parallel or serial mode were selected, helping developers to double-check if the DRX-K is at the right mode. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] drxk: Improve a few debug messagesMauro Carvalho Chehab2012-01-04
| | | | | | | | | | | | Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb: Remove ops->info.type from frontendsMauro Carvalho Chehab2012-01-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | Now that this field is deprecated, and core generates it for DVBv3 calls, remove it from the drivers. It also adds .delsys on the few drivers where this were missed. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb: get rid of fepriv->parameters_inMauro Carvalho Chehab2012-01-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This var were used during DVBv3 times, in order to keep a copy of the parameters used by the events. This is not needed anymore, as the parameters are now dynamically generated from the DVBv5 structure. So, just get rid of it. That means that a DVBv5 pure call won't use anymore any DVBv3 parameters. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb-core: Fix ISDB-T defaultsMauro Carvalho Chehab2012-01-04
| | | | | | | | | | | | | | | | | | using -1 for ISDB-T parameters do the wrong thing. Fix it. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb_frontend: Fix DVBv3 emulationMauro Carvalho Chehab2012-01-04
| | | | | | | | | | | | | | | | | | | | | | | | For frontends with ISDB-T, DVB-T2, CMDBTH, etc, some code is needed, in order to provide emulation. Add such code, and check if the desired delivery system is supported by the frontend. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb_frontend: Don't use ops->info.type anymoreMauro Carvalho Chehab2012-01-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Get rid of using ops->info.type defined on DVB drivers, as it doesn't apply anymore. Currently, one driver (cxd2820) supports more than one different info.type, as it can be used for DVB-T/T2 and DVB-C. There are more drivers like that to come. So, the same frontend will have different DVBv3 types, depending on the current delivery system. This breaks the existing logic at dvb_frontend, that assumes that just one delivery system DVBv3 type is supported by all delsys. In order to easy the DVBv3->DVBv5 conversion, an ancillary function that maps DVBv3 delivery systems into DVBv5 were added. Also, on all places, except for the event logic, the DVBv5 cache will be used to check parameters, instead of the DVBv5 copy. This patch simplifies the cache sync logic, and warrants that the cache will be in a clear state at DVB frontend register. This way, ops->info.type will be filled to reflect the first delivery system, providing backward compatibility support for it. For example, in the cases like cxd2820, where the delivery systems are defined as: .delsys = { SYS_DVBT, SYS_DVBT2, SYS_DVBC_ANNEX_A }, A pure DVBv3 will be able to use both DVB-T and DVB-T2, as, at DVB cache clear, the ops->info.type will be equal to FE_OFDM. However, DVB-C won't be visible. A quick workaround would be to do a DVBv5 call to set the delivery system to SYS_DVBC_ANNEX_A. After such call, ops->info.type will be equal to FE_QAM, and a DVBv3 application will see the frontend as a DVB-C one. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb: move dvb_set_frontend logic into a separate routineMauro Carvalho Chehab2012-01-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change is there in order to prepare the code to avoid calling dvb_frontend_ioctl_legacy() from FE_SET_PROPERTY. A call to dvb_frontend_ioctl_legacy() would require to update the DVBv3 cache without need, mangling calls for newer delivery system without any reason. No functional changes here. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb_frontend: Handle all possible DVBv3 values for bandwidthMauro Carvalho Chehab2012-01-04
| | | | | | | | | | | | | | | | | | | | | | | | Due to DVB-T2, several new possible values for bandwidth were added. As the DVBv3 struct were updated to handle them, the core needs to handle all of them, as a DVBv3 application might try to use it. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb: Initialize all cache valuesMauro Carvalho Chehab2012-01-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | By default, initialize the frontend current delivery system with the first one. This warrants that a DVBv3 application will be able to tune to it, after the removal of ops->init.type filling at the drivers. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] stb6100: Properly retrieve symbol rateMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | stv0297: Fix delivery systemMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb: Add ops.delsys to the remaining frontendsMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | A few drivers don't have .delsys. Add it, in order to allow future patches for dvb_frontend.c to not use info.type. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb: don't require a parameter for get_frontendMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Just like set_frontend, use the dvb cache properties for get_frontend. This is more consistent, as both functions are now symetric. Also, at the places get_frontend is called, it makes sense to update the cache. Most of this patch were generated by this small perl script: while (<>) { $file .= $_; } if ($file =~ m/\.get_frontend\s*=\s*([\d\w_]+)/) { my $get = $1; $file =~ s/($get)(\s*\([^\,\)]+)\,\s*struct\s+dtv_frontend_properties\s*\*\s*([_\d\w]+)\)\s*\{/\1\2)\n{\n\tstruct dtv_frontend_properties *\3 = &fe->dtv_property_cache;/g; } print $file; Of course, the changes at dvb_frontend.[ch] were made by hand, as well as the changes on a few other places, where get_frontend() is called internally inside the driver. On some places, get_frontend() were just a void function. Those occurrences were removed, as the DVB core handles such cases. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb_frontend: Fix inversion breakage due to DVBv5 conversionMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | | | | On several places inside dvb_frontend, only the DVBv3 parameters were updated. Change it to be sure that, on all places, the DVBv5 parameters will be changed instead. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] s921: Properly report the delivery systemMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | Before this patch, a query for the delivery systems were returned SYS_UNDEFINED. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb-core: be sure that drivers won't use DVBv3 internallyMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | | | | Now that all frontends are implementing DVBv5, don't export the DVBv3 specific stuff to the drivers. Only the core should be aware of that, as it will keep providing DVBv3 backward compatibility. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb: don't use DVBv3 bandwidth macrosMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | Every frontend now uses DVBv5 way. So, let's not use the DVBv3 macros internally anymore. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb-core: don't use fe_bandwidth_t on driverMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | Now that everybody is talking DVBv5 API dialect, using this DVBv3 macro internally is not ok. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb: remove the track() fopsMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This callback is not used anywhere. Maybe it were used in the past to optimize the custom algo, but, as it is not used anymore, let's just remove it. If later needed, some patch may re-add it with a proper implementation. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb: don't pass a DVBv3 parameter for search() fopsMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Just like the other DVB algorithms, drivers should use the DVBv5 way to retrieve parameters: via the cache struct. Actually, several drivers were partially using the DVBv3 struct and partially using the DVBv5 way, with is confusing and may lead into troubles. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb-core: Don't pass DVBv3 parameters on tune() fopsMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | | | | | | | As all parameters are passed via DVBv5 to the frontends, there's no need to pass them again via fops. Also, most drivers weren't using it anyway. So, instead, just pass a parameter to indicate if the hardware algorithm wants the driver to re-tune or not. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb: simplify get_tune_settings() structMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the past, dvb_frontent_parameters were passed inside the struct where get_tuner_settings should store their result. This is not needed anymore, as all parameters needed are stored already at the fe property cache. So, use it, where needed. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] dvb-core: remove get|set_frontend_legacyMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | Now that all drivers were converted, we can get rid of those emulation calls. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] af9015: convert set_fontend to use DVBv5 parametersMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of using dvb_frontend_parameters struct, that were designed for a subset of the supported standards, use the DVBv5 cache information. Also, fill the supported delivery systems at dvb_frontend_ops struct. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] af9013: convert get|set_fontend to use DVBv5 parametersMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of using dvb_frontend_parameters struct, that were designed for a subset of the supported standards, use the DVBv5 cache information. Also, fill the supported delivery systems at dvb_frontend_ops struct. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] cxd2820: convert get|set_fontend to use DVBv5 parametersMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of using dvb_frontend_parameters struct, that were designed for a subset of the supported standards, use the DVBv5 cache information. Also, fill the supported delivery systems at dvb_frontend_ops struct. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] ttusb-dec: convert set_fontend to use DVBv5 parametersMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of using dvb_frontend_parameters struct, that were designed for a subset of the supported standards, use the DVBv5 cache information. Also, fill the supported delivery systems at dvb_frontend_ops struct. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] siano: convert set_fontend to use DVBv5 parametersMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of using dvb_frontend_parameters struct, that were designed for a subset of the supported standards, use the DVBv5 cache information. Also, fill the supported delivery systems at dvb_frontend_ops struct. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] firedtv: convert set_fontend to use DVBv5 parametersMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of using dvb_frontend_parameters struct, that were designed for a subset of the supported standards, use the DVBv5 cache information. Also, fill the supported delivery systems at dvb_frontend_ops struct. Cc: Stefan Richter <stefanr@s5r6.in-berlin.de> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] vp7045-fe: convert set_fontend to use DVBv5 parametersMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of using dvb_frontend_parameters struct, that were designed for a subset of the supported standards, use the DVBv5 cache information. Also, fill the supported delivery systems at dvb_frontend_ops struct. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] vp702x-fe: convert set_fontend to use DVBv5 parametersMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of using dvb_frontend_parameters struct, that were designed for a subset of the supported standards, use the DVBv5 cache information. Also, fill the supported delivery systems at dvb_frontend_ops struct. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
* | | [media] mxl111sf-demod: convert set_fontend to use DVBv5 parametersMauro Carvalho Chehab2011-12-31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of using dvb_frontend_parameters struct, that were designed for a subset of the supported standards, use the DVBv5 cache information. Also, fill the supported delivery systems at dvb_frontend_ops struct. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
generated by cgit v1.2.2 (git 2.25.0) at 2025-04-06 22:47:20 -0400