Changes in Makefile

76c47323 - video: fbdev: omap2: remove rfbi

Fri, 21 Jun 2019 13:13:14 +0000

video: fbdev: omap2: remove rfbiEquivalent of drm's commit aa61321d4c08 ("drm/omap: remove rfbi").The RFBI driver has been marked as BROKEN and has not beenincluded in the kernel build for many years. Just remove it(it can be trivially brought back from git repository ifever needed).Cc: Tomi Valkeinen Cc: Laurent Pinchart Cc: Aaro Koskinen Cc: Tony Lindgren Signed-off-by: Bartlomiej Zolnierkiewicz List of files: /linux-6.15/drivers/video/fbdev/omap2/omapfb/dss/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/video/fbdev/omap2/omapfb/dss/Makefile

35b522cf - omapfb/dss: change CONFIG_OMAP* to CONFIG_FB_OMAP*

Wed, 09 Dec 2015 17:24:58 +0000

omapfb/dss: change CONFIG_OMAP* to CONFIG_FB_OMAP*We need to change the config symbols of omapfb's private copy ofomapdss so that we won't have config symbol conflicts.This patch changes the symbols from omapdss using simple replacement ofCONFIG_OMAP* to CONFIG_FB_OMAP*.Signed-off-by: Tomi Valkeinen Acked-by: Dave Airlie Acked-by: Rob Clark List of files: /linux-6.15/drivers/video/fbdev/omap2/omapfb/dss/Makefile

f76ee892 - omapfb: copy omapdss & displays for omapfb

Wed, 09 Dec 2015 16:28:28 +0000

omapfb: copy omapdss & displays for omapfbThis patch makes a copy of the omapdss driver and the omap panel &encoder drivers for omapfb. The purpose is to separate omapdrm andomapfb drivers from each other.Note that this patch only does a direct copy of the files without anyother modifications. The files are not yet used.The original files are in:drivers/video/fbdev/omap2/dss/drivers/video/fbdev/omap2/displays-new/Here's a more detailed explanation about this and the following patches,from the introduction mail of the patch series:A short background on the current status. We have the followingentities:* omapdss, located in drivers/video/fbdev/omap2/dss/. This is a driver for the display subsystem IPs used on OMAP (and related) SoCs. It offers only a kernel internal API, and does not implement anything for fbdev or drm.* omapdss panels and encoders, located in drivers/video/fbdev/omap2/displays-new/. These are panel and external encoder drivers, which use APIs offered by omapdss driver. These also don't implement anything for fbdev or drm.* omapdrm, located in drivers/gpu/drm/omapdrm/. This is a drm driver, which uses omapdss and the panel/encoder drivers to operate the hardware.* omapfb, located in drivers/video/fbdev/omap2/omapfb/. This is an fbdev driver, which uses omapdss and the panel/encoder drivers to operate the hardware.* omap_vout, located in drivers/media/platform/omap/. This is a v4l2 driver, which uses omapdss and omapfb to implement a v4l2 API for the video overlays.So, on the top level, we have either omapdrm, or omapfb+omap_vout. Both ofthose use the same low level drivers. Without going to the historical detailswhy the architecture is like that, I think it's finally time to change that.The situation with omapfb+omap_vout is that it still works, but no new featureshave been added for a long time, and I want to keep it working as it's stillbeing used. At some point in the future I'd like to remove omapfb andomap_vout altogether.Omapdrm, on the other hand, is being actively developed. Sharing the low levelparts with omapfb makes that development more difficult than it should be. Italso "hides" half of the development, as everything happening in the low levelparts resides under fbdev directory, not in the drm directory.I've been wanting to clean this up for a long time, but I haven't figured out avery good way to do it. I still haven't, but here's the best way I have come upwith.This series makes a full copy of the low level parts, omapdss and panel/encoderdrivers. Both omapfb+omap_vout and omapdrm will have their own versions. Thecopy omapfb+omap_vout get is a new copy, and the copy that omapdrm gets is justthe current files moved. This way git will associate the omapdrm version withthe old files.The omapfb+omap_vout versions won't be touched unless there are some big issuesthere.The omapdrm versions can be refactored and cleaned up, as the omapfb supportcode is no longer needed. We can perhaps also merge omapdss and omapdrm intothe same kernel module.This series only does the copy, and the absolutely necessary parts. No furthercleanups are done yet.Signed-off-by: Tomi Valkeinen Acked-by: Dave Airlie Acked-by: Rob Clark List of files: /linux-6.15/drivers/video/fbdev/omap2/omapfb/dss/Makefile