Changes in Makefile

9a33a27e - media: ddbridge: use the ddbridge's own dummy fe driver

Thu, 26 Mar 2020 14:23:34 +0000

media: ddbridge: use the ddbridge's own dummy fe driverCleanup the ddbridge's dummy driver by removing the partsthat aren't needed by ddbridge, adding it to the buildingsystem and changing the binding at the driver to use thenewer function name.Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/media/pci/ddbridge/Makefile

14340de5 - media: prefix header search paths with $(srctree)/

Mon, 13 May 2019 06:22:15 +0000

media: prefix header search paths with $(srctree)/Currently, the Kbuild core manipulates header search paths in a crazyway [1].To fix this mess, I want all Makefiles to add explicit $(srctree)/ tothe search paths in the srctree. Some Makefiles are already written inthat way, but not all. The goal of this work is to make the notationconsistent, and finally get rid of the gross hacks.Having whitespaces after -I does not matter since commit 48f6e3cf5bc6("kbuild: do not drop -I without parameter").[1]: https://patchwork.kernel.org/patch/9632347/Signed-off-by: Masahiro Yamada Reviewed-by: Sakari Ailus List of files: /linux-6.15/drivers/media/pci/ddbridge/Makefile

e5526848 - media: ddbridge/mci: split MaxSX8 specific code off to ddbridge-sx8.c

Sat, 23 Jun 2018 15:36:11 +0000

media: ddbridge/mci: split MaxSX8 specific code off to ddbridge-sx8.cSplit off all code specific to the MaxSX8 cards to a separate ddbridge-sx8module and hook it up in the Makefile. This also adds evaluation of themci_type to allow for using different attach handling for different cards.As different cards can implement things differently (ie. support differingfrontend_ops, and have different base structs being put ontop of thecommon mci_base struct), this introduces the mci_cfg struct which isinitially used to hold a few specifics to the -sx8 submodule. While at it,the handling of the i/q mode is adjusted slightly. Besides this andhandling mci_base and sx8_base struct pointers where needed, all codeis copied unmodified from ddbridge-mci.c.Picked up from the upstream dddvb GIT.Signed-off-by: Daniel Scheller Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/media/pci/ddbridge/Makefile

daeeb131 - media: ddbridge: initial support for MCI-based MaxSX8 cards

Mon, 09 Apr 2018 16:47:48 +0000

media: ddbridge: initial support for MCI-based MaxSX8 cardsThis adds initial support for the new MCI-based (micro-code interface)DD cards, with the first one being the MaxSX8 eight-tuner DVB-S/S2/S2XPCIe card. The MCI is basically a generalized interface implemented inthe card's FPGA firmware and usable for all kind of cards, without theneed to implement any demod/tuner drivers as this interface "hides" anyI2C interface to the actual ICs, in other words any required driver isimplemented in the card firmware.At this stage, the MCI interface is quite rudimentary with things likesignal statistics reporting missing, but is already working to serveDVB streams to DVB applications. Missing functionality will be enabledover time.This implements only the ddbridge-mci sub-object and hooks it up to theMakefile so the object gets build. The upcoming commits hook this moduleinto all other ddbridge parts where required, including device IDs etc.Picked up from the upstream dddvb-0.9.33 release.Signed-off-by: Daniel Scheller Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/media/pci/ddbridge/Makefile

15f757bb - media: cxd2099: move driver out of staging into dvb-frontends

Thu, 08 Feb 2018 19:53:17 +0000

media: cxd2099: move driver out of staging into dvb-frontendsAccording to the TODO file, this driver only landed in staging because ofthe way device nodes and data transfers are handled. Besides that this way(use of secX devices) has become sort of standard to date (ie. VDRsupports this literally since ages via the ddci plugin, TVHeadend receivedthis functionality lately, and minisatip being currently worked onregarding this), most importantly this I2C client only driver isn't evenresponsible for setting up device nodes, not for handling datatransfer and so on, but only serves as interface for the dvb_ca_en50221subsystem, just like every other DVB card out in the wild, with hard-wiredor such flexible CA interfaces. And, it would even work with cards havingthe cxd2099 controller hard-wired.Also, this driver received quite some love and even is a proper I2C clientdriver by now. So, as this driver acts as a EN50221 frontend device, moveit to dvb-frontends. There is no need to keep it buried in staging.This commit also updates all affected Kconfig and Makefile's, and addsMEDIA_AUTOSELECT depends to ddbridge and ngene.Signed-off-by: Daniel Scheller Signed-off-by: Jasmin Jessich Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/media/pci/ddbridge/Makefile

fada1935 - media: move dvb kAPI headers to include/media

Thu, 28 Dec 2017 18:03:51 +0000

media: move dvb kAPI headers to include/mediaExcept for DVB, all media kAPI headers are at include/media.Move the headers to it.Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/media/pci/ddbridge/Makefile

2d8c98b8 - media: ddbridge/max: rename ddbridge-maxs8.[c|h] to ddbridge-max.[c|h]

Sun, 15 Oct 2017 20:51:54 +0000

media: ddbridge/max: rename ddbridge-maxs8.[c|h] to ddbridge-max.[c|h]Rename the MaxS4/8 support files following upstream. References to thesefiles and descriptions have been updated aswell.Signed-off-by: Daniel Scheller Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/media/pci/ddbridge/Makefile

70d3ae1b - media: ddbridge: split off CI (common interface) from ddbridge-core

Sun, 15 Oct 2017 20:51:52 +0000

media: ddbridge: split off CI (common interface) from ddbridge-coreMove all CI device support related code from ddbridge-core to ddbridge-ci,following the previously split off MaxS4/8 support.Signed-off-by: Daniel Scheller Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/media/pci/ddbridge/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/media/pci/ddbridge/Makefile

bb4cec96 - media: ddbridge: support MaxLinear MXL5xx based cards (MaxS4/8)

Sun, 09 Jul 2017 19:42:44 +0000

media: ddbridge: support MaxLinear MXL5xx based cards (MaxS4/8)This enables MaxS4/S8 and Octopus Max card support in ddbridge by addingglue code into ddbridge-core, having another PCI ID, and have the LNB ICcontrol code (and all other MaxS4/8 related code) in ddbridge-maxs8.c(rather than another ~400 LoC in ddbridge-core.c like it's done in theoriginal vendor driver package).Signed-off-by: Daniel Scheller Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/media/pci/ddbridge/Makefile

69716934 - media: ddbridge: split off hardware definitions and mappings

Sat, 12 Aug 2017 11:55:54 +0000

media: ddbridge: split off hardware definitions and mappingsFurther cleanup of ddbridge-core and ddbridge-main, and moves all suchhw definitions into one single place, making things easier to maintain.Signed-off-by: Daniel Scheller Tested-by: Richard Scobie Tested-by: Jasmin Jessich Tested-by: Dietmar Spingler Tested-by: Manfred Knick Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/media/pci/ddbridge/Makefile

a96e5ab8 - media: ddbridge: split code into multiple files

Sat, 29 Jul 2017 11:28:36 +0000

media: ddbridge: split code into multiple filesAs of 0.9.9b, the ddbridge code has been split from one single file(ddbridge-core.c) into multiple files, with the purpose of taking care ofdifferent topics, and to be able to reuse code in different kernel modules(ddbridge.ko and octonet.ko). This applies the same code split, with anotable difference:In the vendor package, the split was done by moving all code parts intoseparate files, and in the "main" code files (ddbridge.c and octonet.c),a simple "#include ddbridge-core.c" was done.In this patch, the same split (codewise) is done, but all resulting .c/.ofiles will be handled by the makefile, with proper prototyping of allshared functions done in ddbridge.h. To avoid conflicts wrt the globalspace, the I2C functions and necessary prototypes for ddbridge-i2c.c aremoved into ddbridge-i2c.h, which is to be included wherever required.Signed-off-by: Daniel Scheller Tested-by: Richard Scobie Tested-by: Jasmin Jessich Tested-by: Dietmar Spingler Tested-by: Manfred Knick Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/media/pci/ddbridge/Makefile

ccae7af2 - [media] common: move media/common/tuners to media/tuners

Thu, 14 Jun 2012 19:35:59 +0000

[media] common: move media/common/tuners to media/tunersMove the tuners one level up, as the "common" directory will be usedby drivers that are shared between more than one driver.Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/media/pci/ddbridge/Makefile

25aee3de - [media] Rename media/dvb as media/pci

Thu, 14 Jun 2012 19:35:57 +0000

[media] Rename media/dvb as media/pciThe remaining dvb drivers are pci, so rename them to match thebus.Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/media/pci/ddbridge/Makefile