Changes in Makefile

b8ac14d3 - tty: hvc: remove tile driver

Fri, 09 Mar 2018 10:41:32 +0000

tty: hvc: remove tile driverThe Tile architecture is obsolete and getting removed from the kernel,this removes the corresponding console driver as well.Acked-by: Greg Kroah-Hartman Signed-off-by: Arnd Bergmann List of files: /linux-6.15/drivers/tty/hvc/Makefile

e6bf3cc5 - tty: remove bfin_jtag_comm and hvc_bfin_jtag drivers

Fri, 09 Mar 2018 16:16:06 +0000

tty: remove bfin_jtag_comm and hvc_bfin_jtag driversThe blackfin architecture is getting removed, so these driversare not needed any more.Acked-by: Greg Kroah-Hartman Acked-by: Aaron Wu Signed-off-by: Arnd Bergmann List of files: /linux-6.15/drivers/tty/hvc/Makefile

afa6b1cc - tty: New RISC-V SBI console driver

Thu, 08 Mar 2018 22:27:34 +0000

tty: New RISC-V SBI console driverThe RISC-V ISA defines a simple console that is availiable via SBI callson all systems. The SBI console is designed to be availiable at alltimes, so while it's most natural to use this as an early printk targetit's also possible to use this as the system console when there isn't abetter one availiable.This patch adds support for the RISC-V SBI console via the HVCinfastructure. It's entirely independent from our early printk support,which results in early boot messages appearing twice over the SBIconsole. As far as I can tell that's the fault of our early printksupport (we should support earlycon) as opposed to this driver.There is one checkpatch.pl warning here: to check the MAINTAINERS file.They're all matched by the "K: riscv" line.Signed-off-by: Palmer Dabbelt Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/tty/hvc/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/tty/hvc/Makefile

80463501 - tty/hvc: remove celleb-only beat driver

Tue, 14 Apr 2015 05:28:46 +0000

tty/hvc: remove celleb-only beat driverThe beat hvc driver is only used by celleb.celleb has been dropped [1], so drop the drivers.[1] http://patchwork.ozlabs.org/patch/451730/CC: Greg Kroah-Hartman CC: Jiri Slaby CC: Valentin Rothberg CC: mpe@ellerman.id.auCC: linuxppc-dev@lists.ozlabs.orgSigned-off-by: Daniel Axtens Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/tty/hvc/Makefile

b6680891 - tty: powerpc: remove hvc_iseries

Wed, 07 Mar 2012 18:37:40 +0000

tty: powerpc: remove hvc_iseriesThe PowerPC legacy iSeries platform is being removed, so this code is nolonger needed.Cc: Greg Kroah-Hartman Signed-off-by: Stephen Rothwell Signed-off-by: Benjamin Herrenschmidt List of files: /linux-6.15/drivers/tty/hvc/Makefile

daea1175 - powerpc/powernv: Support for OPAL console

Mon, 19 Sep 2011 17:44:59 +0000

powerpc/powernv: Support for OPAL consoleThis adds a udbg and an hvc console backend for supporting a consoleusing the OPAL console interfaces.On OPAL v1 we have hvc0 mapped to whatever console the system wasconfigured for (network or hvsi serial port) via the serviceprocessor.On OPAL v2 we have hvcN mapped to the Nth console provided by OPALwhich generally corresponds to: hvc0 : network console (raw protocol) hvc1 : serial port S1 (hvsi) hvc2 : serial port S2 (hvsi)Note: At this point, early debug console only works with OPAL v1and shouldn't be enabled in a normal kernel.Signed-off-by: Benjamin Herrenschmidt List of files: /linux-6.15/drivers/tty/hvc/Makefile

17bdc6c0 - powerpc/pseries: Move hvsi support into a library

Fri, 29 Apr 2011 06:44:24 +0000

powerpc/pseries: Move hvsi support into a libraryThis will allow a different backend to share itSigned-off-by: Benjamin Herrenschmidt List of files: /linux-6.15/drivers/tty/hvc/Makefile

4d2bb3f5 - powerpc/pseries: Re-implement HVSI as part of hvc_vio

Thu, 12 May 2011 03:46:38 +0000

powerpc/pseries: Re-implement HVSI as part of hvc_vioOn pseries machines, consoles are provided by the hypervisor usinga low level get_chars/put_chars type interface. However, this isreally just a transport to the service processor which implementsthem either as "raw" console (networked consoles, HMC, ...) or as"hvsi" serial ports.The later is a simple packet protocol on top of the raw characterinterface that is supposed to convey additional "serial port" stylesemantics. In practice however, all it does is provide a way toread the CD line and set/clear our DTR line, that's it.We currently implement the "raw" protocol as an hvc console backend(/dev/hvcN) and the "hvsi" protocol using a separate tty driver(/dev/hvsi0).However this is quite impractical. The arbitrary difference betweenthe two type of devices has been a major source of user (and distro)confusion. Additionally, there's an additional mini -hvsi implementationin the pseries platform code for our low level debug console and earlyboot kernel messages, which means code duplication, though that lowlevel variant is impractical as it's incapable of doing the initialprotocol negociation to establish the link to the FSP.This essentially replaces the dedicated hvsi driver and the platformudbg code completely by extending the existing hvc_vio backend usedin "raw" mode so that: - It now supports HVSI as well - We add support for hvc backend providing tiocm{get,set} - It also provides a udbg interface for early debug and boot consoleThis is overall less code, though this will only be obvious once weremove the old "hvsi" driver, which is still available for now. Whenthe old driver is enabled, the new code still kicks in for the lowlevel udbg console, replacing the old mini implementation in the platformcode, it just doesn't provide the higher level "hvc" interface.In addition to producing generally simler code, this has several benefitsover our current situation: - The user/distro only has to deal with /dev/hvcN for the hypervisorconsole, avoiding all sort of confusion that has plagued us in the past - The tty, kernel and low level debug console all use the same codebase which supports the full protocol establishment process, thus theconsole is now available much earlier than it used to be with theold HVSI driver. The kernel console works much earlier and udbg isavailable much earlier too. Hackers can enable a hard coded very-earlydebug console as well that works with HVSI (previously that was onlysupported for the "raw" mode).I've tried to keep the same semantics as hvsi relative to how I reactto things like CD changes, with some subtle differences though: - I clear DTR on close if HUPCL is set - Current hvsi triggers a hangup if it detects a up->down transition on CD (you can still open a console with CD down). My new implementation triggers a hangup if the link to the FSP is severed, and severs it upon detecting a up->down transition on CD.Signed-off-by: Benjamin Herrenschmidt List of files: /linux-6.15/drivers/tty/hvc/Makefile

5427bcf5 - hvc: add Blackfin JTAG console support

Sat, 05 Feb 2011 01:45:49 +0000

hvc: add Blackfin JTAG console supportThis converts the existing bfin_jtag_comm TTY driver to the HVC layer sothat the common HVC code can worry about all of the TTY/polling crap andleave the Blackfin code to worry about the Blackfin bits.Signed-off-by: Mike Frysinger Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/tty/hvc/Makefile

51df0acc - virtio: console: Move file back to drivers/char/

Tue, 01 Feb 2011 04:01:25 +0000

virtio: console: Move file back to drivers/char/Commit 728674a7e466628df2aeec6d11a2ae1ef968fb67 moved virtio_console.cto drivers/tty/hvc/ under the perception of this being an hvc driver.It was such once, but these days it has generic communicationcapabilities as well, so move it to drivers/char/.In the future, the hvc part from this file can be split off and movedunder drivers/tty/hvc/.Signed-off-by: Amit Shah CC: Rusty Russell Acked-by: Arnd Bergmann Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/tty/hvc/Makefile

728674a7 - tty: move hvc drivers to drivers/tty/hvc/

Thu, 13 Jan 2011 20:03:00 +0000

tty: move hvc drivers to drivers/tty/hvc/As requested by Arnd Bergmann, the hvc drivers are nowmoved to the drivers/tty/hvc/ directory. The virtio_console.c driverwas also moved, as it required the hvc_console.h file to be able to bebuilt, and it really is a hvc driver.Cc: Arnd Bergmann Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/tty/hvc/Makefile