Changes in Makefile

7a14f78d - firewire: ohci: add static inline functions to deserialize for Self-ID DMA operation

Tue, 02 Jul 2024 22:20:32 +0000

firewire: ohci: add static inline functions to deserialize for Self-ID DMA operationThe SelfI-ID is one type of DMAs defined in 1394 OHCI specification. It isoperated by two registers, one interrupt, and has one format of buffer.This commit adds some static inline functions to deserialize the data inthe buffer and registers. Some KUnit tests are also added to check theirreliability.Link: https://lore.kernel.org/r/20240702222034.1378764-4-o-takashi@sakamocchi.jpSigned-off-by: Takashi Sakamoto List of files: /linux-6.15/drivers/firewire/Makefile

7bd10e0e - firewire: core: add enumerator of self ID sequences and its KUnit test

Wed, 05 Jun 2024 23:51:45 +0000

firewire: core: add enumerator of self ID sequences and its KUnit testWhen the state of bus reset finishes, 1394 OHCI driver constructs self IDsequences, then it calls fw_core_handle_bus_reset() in core function. Thecore function enumerates the self ID sequences to build bus topology.This commit adds a structure and some helper functions for the enumeration,and adds a KUnit test suite to ensure its expected behaviour.Link: https://lore.kernel.org/r/20240605235155.116468-2-o-takashi@sakamocchi.jpSigned-off-by: Takashi Sakamoto List of files: /linux-6.15/drivers/firewire/Makefile

21151fd8 - firewire: obsolete usage of *-objs in Makefile for KUnit test

Wed, 08 May 2024 10:53:51 +0000

firewire: obsolete usage of *-objs in Makefile for KUnit testNowadays *-objs list is just for user space programs.This commit obsolete the usage, and simplify Makefile for firewire KUnittests since the tests are not composite objects.Link: https://lore.kernel.org/r/20240508105351.532693-1-o-takashi@sakamocchi.jpSigned-off-by: Takashi Sakamoto List of files: /linux-6.15/drivers/firewire/Makefile

57614c28 - firewire: core: add support for Linux kernel tracepoints

Mon, 29 Apr 2024 04:32:14 +0000

firewire: core: add support for Linux kernel tracepointsThe Linux Kernel Tracepoints framework is enough useful to tracepacket data inbound to and outbound from core.This commit adds firewire subsystem to use the framework.Link: https://lore.kernel.org/r/20240429043218.609398-2-o-takashi@sakamocchi.jpSigned-off-by: Takashi Sakamoto List of files: /linux-6.15/drivers/firewire/Makefile

75527d8d - firewire: core: add common inline functions to serialize/deserialize asynchronous packet header

Sun, 28 Apr 2024 07:13:39 +0000

firewire: core: add common inline functions to serialize/deserialize asynchronous packet headerIn both core and 1394 OHCI driver, some hard-coded values and macros areused to serialize/deserialize the header of asynchronous packets. It isinconvenient to reuse them.This commit adds some helper inline functions with their tests for thepurpose.Link: https://lore.kernel.org/r/20240428071347.409202-2-o-takashi@sakamocchi.jpSigned-off-by: Takashi Sakamoto List of files: /linux-6.15/drivers/firewire/Makefile

dc7c5163 - firewire: add KUnit test to check layout of UAPI structures

Mon, 29 May 2023 23:12:39 +0000

firewire: add KUnit test to check layout of UAPI structuresIn future commits, some new structure will be added to express new typeof event. They are exposed to user space as the part of UAPI. It is likelyto get trouble in ioctl compatibility layer for 32 bit binaries in 64 bithost machine since the layout of structure could differ depending onSystem V ABI for these architectures. Actually the subsystem already gotsuch trouble at v2.6.27. It is preferable to decide the layout ofstructure carefully so that the layer is free from such trouble.This commit utilizes KUnit framework to check the layout of structure forthe purpose. A test is added for the existent issue.Cc: kunit-dev@googlegroups.comLink: https://lore.kernel.org/r/20230529113406.986289-2-o-takashi@sakamocchi.jpSigned-off-by: Takashi Sakamoto List of files: /linux-6.15/drivers/firewire/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/firewire/Makefile

1ef5b816 - ieee1394: move init_ohci1394_dma to drivers/firewire/

Sat, 09 Oct 2010 22:54:02 +0000

ieee1394: move init_ohci1394_dma to drivers/firewire/because drivers/ieee1394/ will be deleted.Additional changes: - add some #include directives - adjust to use firewire/ohci.h instead of ieee1394/ohci1394.h, replace struct ti_ohci by a minimal struct ohci, replace quadlet_t from ieee1394_types.h by u32 - two or three trivial stylistic changes - __iomem annotationSigned-off-by: Stefan Richter List of files: /linux-6.15/drivers/firewire/Makefile

28646821 - firewire: new driver: nosy - IEEE 1394 traffic sniffer

Tue, 27 Jul 2010 08:26:33 +0000

firewire: new driver: nosy - IEEE 1394 traffic snifferThis adds the traffic sniffer driver for Texas Instruments PCILynx/PCILynx2 based cards. The use cases for nosy are analysis ofnonstandard protocols and as an aid in development of drivers,applications, or firmwares.Author of the driver is Kristian Høgsberg. Known contributers areJody McIntyre and Jonathan Woithe.Nosy programs PCILynx chips to operate in promiscuous mode, which is afeature that is not found in OHCI-1394 controllers. Hence, only specialhardware as mentioned in the Kconfig help text is suitable for nosy.This is only the kernelspace part of nosy. There is a userspaceinterface to it, called nosy-dump, proposed to be added into the tools/subdirectory of the kernel sources in a subsequent change. Kernelspaceand userspave component of nosy communicate via a 'misc' characterdevice file called /dev/nosy with a simple ioctl() and read() basedprotocol, as described by nosy-user.h.The files added here are taken fromgit://anongit.freedesktop.org/~krh/nosy commit ee29be97 (2009-11-10)with the following changes by Stefan Richter: - Kconfig and Makefile hunks are written from scratch. - Commented out version printk in nosy.c. - Included missing , reported by Stephen Rothwell."git shortlog nosy{-user.h,.c,.h}" from nosy's git repository:Jonathan Woithe (2): Nosy updates for recent kernels Fix uninitialised memory (needed for 2.6.31 kernel)Kristian Høgsberg (5): Pull over nosy from mercurial repo. Use a misc device instead. Add simple AV/C decoder. Don't break down on big payloads. Set parent device for misc device.As a low-level IEEE 1394 driver, its files are placed intodrivers/firewire/ although nosy is not part of the firewire driverstack.I am aware of the following literature from Texas Instruments aboutPCILynx programming: SCPA020A - PCILynx 1394 to PCI Bus Interface TSB12LV21BPGF Functional Specification SLLA023 - Initialization and Asynchronous Programming of the TSB12LV21A 1394 DeviceSigned-off-by: Stefan Richter Acked-by: Kristian Høgsberg List of files: /linux-6.15/drivers/firewire/Makefile

b9530fd6 - firewire: net: add Kconfig item, rename driver

Sun, 07 Jun 2009 20:57:53 +0000

firewire: net: add Kconfig item, rename driverThe driver is now called firewire-net. It might implement the transportof other networking protocols in the future, notably IPv6 per RFC 3146.Signed-off-by: Stefan Richter List of files: /linux-6.15/drivers/firewire/Makefile

c76acec6 - firewire: add IPv4 support

Mon, 18 May 2009 17:08:06 +0000

firewire: add IPv4 supportImplement IPv4 over IEEE 1394 as per RFC 2734 for the newer firewirestack. This feature has only been present in the older ieee1394 stackvia the eth1394 driver.Still to do: - fix ipv4_priv and ipv4_node lifetime logic - fix determination of speeds and max payloads - fix bus reset handling - fix unaligned memory accesses - fix coding style - further testing/ improvement of fragment reassembly - perhaps multicast supportSigned-off-by: Jay Fenlason Signed-off-by: Stefan Richter (rebased, copyright note, changelog) List of files: /linux-6.15/drivers/firewire/Makefile

e71d31da - firewire: rename source files

Fri, 05 Jun 2009 14:26:18 +0000

firewire: rename source filesThe source files of firewire-core, firewire-ohci, firewire-sbp2, i.e. "drivers/firewire/fw-*.c"are renamed to "drivers/firewire/core-*.c", "drivers/firewire/ohci.c", "drivers/firewire/sbp2.c".The old fw- prefix was redundant to the directory name. The new core-prefix distinguishes the files according to which driver they belong to.This change comes a little late, but still before further firewiredrivers are added as anticipated RSN.Signed-off-by: Stefan Richter List of files: /linux-6.15/drivers/firewire/Makefile

9a60731d - firewire: prefix modules with firewire- instead of fw-

Fri, 25 May 2007 11:54:49 +0000

firewire: prefix modules with firewire- instead of fw-Of course everybody immediately associates "fw-" with FireWire, notfirmware or firewall or whatever. But "firewire-" has a nice ring toit too.Signed-off-by: Stefan Richter Acked-by: Kristian Hoegsberg List of files: /linux-6.15/drivers/firewire/Makefile

58e313b3 - firewire: Add to fw-core-y instead of assigning fw-core-objs in Makefile.

Tue, 08 May 2007 00:33:38 +0000

firewire: Add to fw-core-y instead of assigning fw-core-objs in Makefile.Signed-off-by: Kristian Hoegsberg Signed-off-by: Stefan Richter List of files: /linux-6.15/drivers/firewire/Makefile

9640d3d7 - firewire: Rename fw-device-cdev.c to fw-cdev.c and move header to include/linux.

Mon, 30 Apr 2007 19:03:15 +0000

firewire: Rename fw-device-cdev.c to fw-cdev.c and move header to include/linux.Signed-off-by: Kristian Høgsberg Signed-off-by: Stefan Richter List of files: /linux-6.15/drivers/firewire/Makefile

11f494ee - firewire: rename CONFIG_FW to CONFIG_FIREWIRE

Sun, 18 Mar 2007 00:39:28 +0000

firewire: rename CONFIG_FW to CONFIG_FIREWIREto avoid confusion with CONFIG_FW_LOADER.Signed-off-by: Stefan Richter Acked-by: Kristian Høgsberg List of files: /linux-6.15/drivers/firewire/Makefile

9ba136d0 - firewire: Add SBP-2 protocol driver for storage devices.

Wed, 20 Dec 2006 00:58:40 +0000

firewire: Add SBP-2 protocol driver for storage devices.Signed-off-by: Kristian Høgsberg Signed-off-by: Stefan Richter List of files: /linux-6.15/drivers/firewire/Makefile

ed568912 - firewire: Add driver for OHCI firewire host controllers.

Wed, 20 Dec 2006 00:58:35 +0000

firewire: Add driver for OHCI firewire host controllers.Signed-off-by: Kristian Høgsberg Signed-off-by: Stefan Richter List of files: /linux-6.15/drivers/firewire/Makefile

19a15b93 - firewire: Add device probing and sysfs integration.

Wed, 20 Dec 2006 00:58:31 +0000

firewire: Add device probing and sysfs integration.Signed-off-by: Kristian Høgsberg Signed-off-by: Stefan Richter List of files: /linux-6.15/drivers/firewire/Makefile

3038e353 - firewire: Add core firewire stack.

Wed, 20 Dec 2006 00:58:27 +0000

firewire: Add core firewire stack.Signed-off-by: Kristian Høgsberg Signed-off-by: Stefan Richter List of files: /linux-6.15/drivers/firewire/Makefile