Changes in Makefile

74708497 - video: Move HP PARISC STI core code to shared location

Mon, 17 Apr 2023 12:56:43 +0000

video: Move HP PARISC STI core code to shared locationSTI core files have been located in console and fbdev code. Movethe source code and header to the directories for video helpers.Also update the config and build rules such that the code dependson the config symbol CONFIG_STI_CORE, which STI console and STIframebuffer select automatically.Cleans up the console makefile and prepares PARISC to implementfb_is_primary_device() within the arch/ directory. No functionalchanges.Signed-off-by: Thomas Zimmermann Acked-by: Arnd Bergmann Acked-by: Helge Deller Link: https://patchwork.freedesktop.org/patch/msgid/20230417125651.25126-12-tzimmermann@suse.de List of files: /linux-6.15/drivers/video/console/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/console/Makefile

6104c370 - fbcon: Make fbcon a built-time depency for fbdev

Tue, 01 Aug 2017 15:32:07 +0000

fbcon: Make fbcon a built-time depency for fbdevThere's a bunch of folks who're trying to make printk lesscontended and faster, but there's a problem: printk uses theconsole_lock, and the console lock has become the BKL for all thingsfbdev/fbcon, which in turn pulled in half the drm subsystem under thatlock. That's awkward.There reasons for that is probably just a historical accident:- fbcon is a runtime option of fbdev, i.e. at runtime you can pick whether your fbdev driver instances are used as kernel consoles. Unfortunately this wasn't implemented with some module option, but through some module loading magic: As long as you don't load fbcon.ko, there's no fbdev console support, but loading it (in any order wrt fbdev drivers) will create console instances for all fbdev drivers.- This was implemented through a notifier chain. fbcon.ko enumerates all fbdev instances at load time and also registers itself as listener in the fbdev notifier. The fbdev core tries to register new fbdev instances with fbcon using the notifier.- On top of that the modifier chain is also used at runtime by the fbdev subsystem to e.g. control backlights for panels.- The problem is that the notifier puts a mutex locking context between fbdev and fbcon, which mixes up the locking contexts for both the runtime usage and the register time usage to notify fbcon. And at runtime fbcon (through the fbdev core) might call into the notifier from a printk critical section while console_lock is held.- This means console_lock must be an outer lock for the entire fbdev subsystem, which also means it must be acquired when registering a new framebuffer driver as the outermost lock since we might call into fbcon (through the notifier) which would result in a locking inversion if fbcon would acquire the console_lock from its notifier callback (which it needs to register the console).- console_lock can be held anywhere, since printk can be called anywhere, and through the above story, plus drm/kms being an fbdev driver, we pull in a shocking amount of locking hiercharchy underneath the console_lock. Which makes cleaning up printk really hard (not even splitting console_lock into an rwsem is all that useful due to this).There's various ways to address this, but the cleanest would be tomake fbcon a compile-time option, where fbdev directly calls the fbconregister functions from register_framebuffer, or dummy static inlineversions if fbcon is disabled. Maybe augmented with a runtime knob todisable fbcon, if that's needed (for debugging perhaps).But this could break some users who rely on the magic "loadingfbcon.ko enables/disables fbdev framebuffers at runtime" thing, evenif that's unlikely. Hence we must be careful:1. Create a compile-time dependency between fbcon and fbdev in theleast minimal way. This is what this patch does.2. Wait at least 1 year to give possible users time to scream abouthow we broke their setup. Unlikely, since all distros make fbconcompile-in, and embedded platforms only compile stuff they know theyneed anyway. But still.3. Convert the notifier to direct functions calls, with dummy staticinlines if fbcon is disabled. We'll still need the fb notifier for theother uses (like backlights), but we can probably move it into the fbcore (atm it must be built-into vmlinux).4. Push console_lock down the call-chain, until it is down inconsole_register again.5. Finally start to clean up and rework the printk/console locking.For context of this saga seecommit 50e244cc793d511b86adea24972f3a7264cae114Author: Alan Cox Date: Fri Jan 25 10:28:15 2013 +1000 fb: rework locking to fix lock ordering on takeoverplus the pile of commits on top that tried to make this all workwithout terminally upsetting lockdep. We've uncovered all this whenconsole_lock lockdep annotations where added incommit daee779718a319ff9f83e1ba3339334ac650bb22Author: Daniel Vetter Date: Sat Sep 22 19:52:11 2012 +0200 console: implement lockdep support for console_lockOn the patch itself:- Switch CONFIG_FRAMEBUFFER_CONSOLE to be a boolean, using the overall CONFIG_FB tristate to decided whether it should be a module or built-in.- At first I thought I could force the build depency with just a dummy symbol that fbcon.ko exports and fb.ko uses. But that leads to a module depency cycle (it works fine when built-in). Since this tight binding is the entire goal the simplest solution is to move all the fbcon modules (and there's a bunch of optinal source-files which are each modules of their own, for no good reason) into the overall fb.ko core module. That's a bit more than what I would have liked to do in this patch, but oh well.Signed-off-by: Daniel Vetter Cc: Alan Cox Cc: Sergey Senozhatsky Cc: Steven Rostedt Reviewed-by: Sean Paul Signed-off-by: Bartlomiej Zolnierkiewicz List of files: /linux-6.15/drivers/video/console/Makefile

ee89bd6b - lib: Move fonts from drivers/video/console/ to lib/fonts/

Sun, 09 Jun 2013 09:46:43 +0000

lib: Move fonts from drivers/video/console/ to lib/fonts/Several drivers need font support independent of CONFIG_VT, cfr. commit9cbce8d7e1dae0744ca4f68d62aa7de18196b6f4, "console/font: Refactor fontsupport code selection logic").Hence move the fonts and their support logic from drivers/video/console/ toits own library directory lib/fonts/.This also allows to limit processing of drivers/video/console/Makefile toCONFIG_VT=y again.[Kevin Hilman : Update arch/arm/boot/compressed/Makefile]Signed-off-by: Geert Uytterhoeven List of files: /linux-6.15/drivers/video/console/Makefile

d1e183c8 - console/font: Refactor font support code selection logic

Wed, 15 May 2013 11:26:20 +0000

console/font: Refactor font support code selection logicThe current Makefile rules to build font support are messy and buggy.Replace them by Kconfig rules: - Introduce CONFIG_FONT_SUPPORT, which controls the building of all font code, - Select CONFIG_FONT_SUPPORT for all drivers that use fonts, - Select CONFIG_FONT_8x16 for all drivers that default to the VGA8x16 font, - Drop the bogus console dependency for CONFIG_VIDEO_VIVI, - Always process drivers/video/console/Makefile, as some drivers need fonts even if CONFIG_VT is not set.This fixes (if CONFIG_SOLO6X10=y and there are no built-in consoledrivers):drivers/built-in.o: In function `solo_osd_print':drivers/staging/media/solo6x10/solo6x10-enc.c:144: undefined reference to `.find_font'This fixes (if CONFIG_VT=n):drivers/built-in.o: In function `vivi_init':vivi.c:(.init.text+0x1a3da): undefined reference to `find_font'Signed-off-by: Geert Uytterhoeven Acked-by: Hans Verkuil [original part]Acked-by: Randy Dunlap [drivers/video/Makefile] List of files: /linux-6.15/drivers/video/console/Makefile

866f3213 - Revert "staging/solo6x10: depend on CONFIG_FONTS"

Mon, 27 May 2013 07:32:54 +0000

Revert "staging/solo6x10: depend on CONFIG_FONTS"This reverts commit 8c090cfbf980581454ae4caae731574fedd7dce8.CONFIG_FONTS is not about enabling font support, but about enablingmanual selection of built-in fonts.Signed-off-by: Geert Uytterhoeven List of files: /linux-6.15/drivers/video/console/Makefile

8c090cfb - staging/solo6x10: depend on CONFIG_FONTS

Thu, 02 May 2013 15:16:23 +0000

staging/solo6x10: depend on CONFIG_FONTSThe new SOLO6X10 driver needs the built-in console fonts, specificallythe VGA8x16 font and building it without console support results ina link error error.drivers/built-in.o: In function `solo_osd_print': :(.text+0x7d3424): undefined reference to `find_font'This adds a dependency on the CONFIG_FONTS symbol and changes theconsole code to always build the base driver even if there areno specific fonts built-in.Cc: Greg Kroah-Hartman Cc: Hans Verkuil Cc: Mauro Carvalho Chehab Signed-off-by: Arnd Bergmann Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/video/console/Makefile

09d3f3f0 - sparc: Kill PROM console driver.

Wed, 16 Sep 2009 00:04:38 +0000

sparc: Kill PROM console driver.Many years ago when this driver was written, it had a use, but thesedays it's nothing but trouble and distributions should not enable itin any situation.Pretty much every console device a sparc machine could see has abonafide real driver, making the PROM console hack unnecessary.If any new device shows up, we should write a driver instead ofdepending upon this crutch to save us. We've been able to take careof this even when no chip documentation exists (sunxvr500, sunxvr2500)so there are no excuses.Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/video/console/Makefile

353076fe - [VIDEO]: Fix section mismatch warning in promcon.

Tue, 05 Jun 2007 06:52:45 +0000

[VIDEO]: Fix section mismatch warning in promcon.Fix the following warnings in promcon:WARNING: o-sparc64/drivers/video/console/built-in.o(.text+0x480): Section mismatch: reference to .init.data:promfont_unitable (between 'promcon_init_unimap' and 'promcon_init')WARNING: o-sparc64/drivers/video/console/built-in.o(.text+0x488): Section mismatch: reference to .init.data:promfont_unitable (between 'promcon_init_unimap' and 'promcon_init')WARNING: o-sparc64/drivers/video/console/built-in.o(.text+0x48c): Section mismatch: reference to .init.data:promfont_unicount (between 'promcon_init_unimap' and 'promcon_init')WARNING: o-sparc64/drivers/video/console/built-in.o(.text+0x490): Section mismatch: reference to .init.data:promfont_unicount (between 'promcon_init_unimap' and 'promcon_init')The warnings happens because the function: promcon_init_unimap()references promfont_unitable and promfont_unicount which are marked__initdata by the conmakehash command in the drivers/video/console/MakefileFix the warning by removing the __initdata marker on the two variables.Signed-off-by: Sam Ravnborg Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/video/console/Makefile

0fde7f59 - Revert "[PATCH] fbcon: Add rl (Roman Large) font"

Sat, 12 Nov 2005 18:14:02 +0000

Revert "[PATCH] fbcon: Add rl (Roman Large) font"This reverts 998e6d51162707685336ff99c029c8911b270d32 commit. List of files: /linux-6.15/drivers/video/console/Makefile

ed8c0e99 - [PATCH] fbcon: Console Rotation - Add support for 270-degree rotation

Wed, 09 Nov 2005 05:39:14 +0000

[PATCH] fbcon: Console Rotation - Add support for 270-degree rotationAdd support for 270-degree (counterclockwise) rotation of the console. Toactivate, boot with:fbcon=rotate:3Signed-off-by: Antonino Daplas Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/video/console/Makefile

33ee8297 - [PATCH] fbcon: Console Rotation - Add support for 180-degree console rotation

Wed, 09 Nov 2005 05:39:13 +0000

[PATCH] fbcon: Console Rotation - Add support for 180-degree console rotationAdd support for 180-degree (upside down) rotation of the console. Toactivate, boot with:fbcon=rotate:2Signed-off-by: Antonino Daplas Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/video/console/Makefile

dbcbfe1e - [PATCH] fbcon: Console Rotation - Add support for 90-degree console rotation

Wed, 09 Nov 2005 05:39:12 +0000

[PATCH] fbcon: Console Rotation - Add support for 90-degree console rotationAdd support for 90-degree (clockwise) rotation of the console. To activate,boot with:fbcon=rotate:1Signed-off-by: Antonino Daplas Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/video/console/Makefile

6cc50e1c - [PATCH] fbcon: Console Rotation - Add support to rotate font bitmap

Wed, 09 Nov 2005 05:39:11 +0000

[PATCH] fbcon: Console Rotation - Add support to rotate font bitmapAdd support to rotate the font bitmap. To save on processing time, the entirefontdata will be rotated on a console switch, then stored in a buffer privateto fbcon. To further save on processing, the fontdata will only be rotated ifthe font has changed or if the angle of rotation has changed. Only a singlecopy of the rotated fontdata will be kept.Signed-off-by: Antonino Daplas Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/video/console/Makefile

998e6d51 - [PATCH] fbcon: Add rl (Roman Large) font

Mon, 07 Nov 2005 09:00:52 +0000

[PATCH] fbcon: Add rl (Roman Large) fontI converted the "rl" console font from the kbd utility to be a built-in fontfor the framebuffer console, and I was wondering if you would be OK withincluding it. I've generated a font_rl.c file and related minormodifications. I find it's the most visually appealing of the kbd fonts whichis why I use it and selected it for conversion. I believe the font is GPL'd.Signed-off-by: Antonino Daplas Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/video/console/Makefile

c465e05a - [PATCH] fbcon/fbdev: Move softcursor out of fbdev to fbcon

Mon, 07 Nov 2005 09:00:35 +0000

[PATCH] fbcon/fbdev: Move softcursor out of fbdev to fbconAccording to Jon Smirl, filling in the field fb_cursor with soft_cursor fordrivers that do not support hardware cursors is redundant. The soft_cursorfunction is usable by all drivers because it is just a wrapper aroundfb_imageblit. And because soft_cursor is an fbcon-specific hook, the file ismoved to the console directory.Thus, drivers that do not support hardware cursors can leave the fb_cursorfield blank. For drivers that do, they can fill up this field with their ownversion.The end result is a smaller code size. And if the framebuffer console is notloaded, module/kernel size is also reduced because the soft_cursor module willalso not be loaded.Signed-off-by: Antonino Daplas Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/video/console/Makefile

1bbb4f20 - [PATCH] USB: sisusb[vga] update

Mon, 29 Aug 2005 15:01:16 +0000

[PATCH] USB: sisusb[vga] updatehere is a new and extended version of the sisusbvga (previously: sisusb)driver. The patch is against 2.6.13 and updates the driver to version 0.0.8.Additions include complete VGA/EGA text console support and a build-indisplay mode infrastructure for userland applications that don't know about the graphics internals.Fixes include some BE/LE issues and a get/put_dev bug in the previousversion.Other changes include a change of the module name from "sisusb" to"sisusbvga". The previous one was too generic IMHO.Please note that the patch also affects the Makefile indrivers/video/console as the driver requires the VGA 8x16 font in casethe text console part is selected.Heavily tested, as usual. Please apply.One thing though: I already prepared for removal of the "mode" field andthe changed "name" field in the usb_class_driver structure. This willperhaps need some refinement depending on whether you/Linus merge therespective core changes before or after 2.6.14.Signed-off-by: Thomas Winischhofer Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/video/console/Makefile

303b86d9 - [PATCH] New framebuffer fonts + updated 12x22 font available

Wed, 22 Jun 2005 00:17:06 +0000

[PATCH] New framebuffer fonts + updated 12x22 font availableImprove the fonts for use with the framebuffer.I've added all the characters marked 'FIXME' in the sun12x22 font andcreated a 10x18 font (based on the sun12x22 font) and a 7x14 font (basedon the vga8x16 font).This patch is non-intrusive, no options are enabled by default so mostusers won't notice a thing.I am placing my changes under the GPL, however, I've not seen any copyrightnotices on the sun12x22 font and the vga8x16 font which I derived my newfonts from so I don't know what the copyright status is.Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/video/console/Makefile

1da177e4 - Linux-2.6.12-rc2

Sat, 16 Apr 2005 22:20:36 +0000

Linux-2.6.12-rc2Initial git repository build. I'm not bothering with the full history,even though we have it. We can create a separate "historical" gitarchive of that later if we want to, and in the meantime it's about3.2GB when imported into git - space that would just make the earlygit days unnecessarily complicated, when we don't have a lot of goodinfrastructure for it.Let it rip! List of files: /linux-6.15/drivers/video/console/Makefile