Changes in Makefile

5d42a685 - m68k: Move Sun 3 into a top-level platform option

Wed, 30 Oct 2024 19:56:13 +0000

m68k: Move Sun 3 into a top-level platform optionIt is possible to select an m68k MMU build but not actually enable anyof the three MMU options, which then results in a build failure: arch/m68k/include/asm/page.h:10:25: error: 'CONFIG_PAGE_SHIFT' undeclared here (not in a function); did you mean 'CONFIG_LOG_BUF_SHIFT'?Change the Kconfig selection to ensure that exactly one of the threeoptions is always enabled whenever an MMU-enabled kernel is built, butmoving CONFIG_SUN3 into a top-level option next to M68KCLASSIC andCOLDFIRE.All defconfig files should keep working without changes, butalldefconfig now builds support for the classic MMU.Reported-by: kernel test robot Closes: https://lore.kernel.org/oe-kbuild-all/202408032138.P7sBvIns-lkp@intel.com/Signed-off-by: Arnd Bergmann Acked-by: Greg Ungerer Reviewed-by: Geert Uytterhoeven Link: https://lore.kernel.org/20241030195638.22542-1-arnd@kernel.orgSigned-off-by: Geert Uytterhoeven List of files: /linux-6.15/arch/m68k/kernel/Makefile

9bad6b75 - m68k, kexec: fix the incorrect ifdeffery and build dependency of CONFIG_KEXEC

Fri, 08 Dec 2023 07:30:33 +0000

m68k, kexec: fix the incorrect ifdeffery and build dependency of CONFIG_KEXECThe select of KEXEC for CRASH_DUMP in kernel/Kconfig.kexec will bedropped, then compiling errors will be triggered if below config items areset:===CONFIG_CRASH_CORE=yCONFIG_KEXEC_CORE=yCONFIG_CRASH_DUMP=y===Here, change the dependency of buinding machine_kexec.o relocate_kernel.oand the ifdeffery in asm/kexe.h to CONFIG_KEXEC_CORE.Link: https://lkml.kernel.org/r/20231208073036.7884-3-bhe@redhat.comSigned-off-by: Baoquan He Cc: Eric DeVolder Cc: Ignat Korchagin Cc: kernel test robot Cc: Stephen Rothwell Signed-off-by: Andrew Morton List of files: /linux-6.15/arch/m68k/kernel/Makefile

9e28bf8b - m68k: use the coherent DMA code for coldfire without data cache

Tue, 17 Oct 2023 14:04:42 +0000

m68k: use the coherent DMA code for coldfire without data cacheColdfire cores configured without a data cache are DMA coherent andshould thus simply use the simple coherent version of dma-direct.Introduce a new COLDFIRE_COHERENT_DMA Kconfig symbol as a convenientshort hand for such configurations, and a M68K_NONCOHERENT_DMA symbolfor all cases where we need to build non-coherent DMA infrastructureto simplify the Kconfig and code conditionals.Not building the non-coherent DMA code slightly reduces the codesize for such configurations.Numers for m5249evb_defconfig below: text data bss dec hex filename2896158 401052 65392 3362602 334f2a vmlinux.before2895166 400988 65392 3361546 334b0a vmlinux.afterSigned-off-by: Christoph Hellwig Reviewed-by: Greg Ungerer Acked-by: Geert Uytterhoeven Tested-by: Greg Ungerer List of files: /linux-6.15/arch/m68k/kernel/Makefile

32164845 - kbuild: use obj-y instead extra-y for objects placed at the head

Sat, 24 Sep 2022 18:19:14 +0000

kbuild: use obj-y instead extra-y for objects placed at the headThe objects placed at the head of vmlinux need special treatments: - arch/$(SRCARCH)/Makefile adds them to head-y in order to place them before other archives in the linker command line. - arch/$(SRCARCH)/kernel/Makefile adds them to extra-y instead of obj-y to avoid them going into built-in.a.This commit gets rid of the latter.Create vmlinux.a to collect all the objects that are unconditionallylinked to vmlinux. The objects listed in head-y are moved to the headof vmlinux.a by using 'ar m'.With this, arch/$(SRCARCH)/kernel/Makefile can consistently use obj-yfor builtin objects.There is no *.o that is directly linked to vmlinux. Drop unneeded codein scripts/clang-tools/gen_compile_commands.py.$(AR) mPi needs 'T' to workaround the llvm-ar bug. The fix was suggestedby Nathan Chancellor [1].[1]: https://lore.kernel.org/llvm/YyjjT5gQ2hGMH0ni@dev-arch.thelio-3990X/Signed-off-by: Masahiro Yamada Tested-by: Nick Desaulniers Reviewed-by: Nicolas Schier List of files: /linux-6.15/arch/m68k/kernel/Makefile

05d51e42 - m68k: Introduce a virtual m68k machine

Wed, 06 Apr 2022 20:15:23 +0000

m68k: Introduce a virtual m68k machineThis machine allows to have up to 3.2 GiB and 128 Virtio devices.It is based on android goldfish devices.Signed-off-by: Laurent Vivier Link: https://lore.kernel.org/r/20220406201523.243733-5-laurent@vivier.euSigned-off-by: Geert Uytterhoeven List of files: /linux-6.15/arch/m68k/kernel/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/arch/m68k/kernel/Makefile

d13ffb56 - m68k: move exports to definitions

Mon, 11 Jan 2016 18:04:04 +0000

m68k: move exports to definitionsAcked-by: Geert Uytterhoeven Signed-off-by: Al Viro List of files: /linux-6.15/arch/m68k/kernel/Makefile

aa5ac789 - m68k: generalize uboot command line support

Mon, 05 Sep 2016 05:23:50 +0000

m68k: generalize uboot command line supportThe uboot command line support needs to be used by both MMU and no-MMUsetups, but currently we only have the code in the no-MMU code paths.Move the uboot command line processing code into its own file. Addappropriate calls to it from both the MMU and no-MMU arch setup code.Signed-off-by: Greg Ungerer Acked-by: Geert Uytterhoeven List of files: /linux-6.15/arch/m68k/kernel/Makefile

7913ad1a - m68k: Multi-platform EARLY_PRINTK

Sat, 12 Apr 2014 13:48:56 +0000

m68k: Multi-platform EARLY_PRINTKMake the boot console available to more m68k platforms by leveragingthe head.S debug console.The boot console is enabled by the "earlyprintk" command line argumentwhich is how most other architectures do this.This is a change of behaviour for the Mac but does not negatively impactthe common use-case which is not debugging.This is also a change of behaviour for other platforms because it meansthe serial port stays quiet when CONFIG_EARLY_PRINTK is not enabled. Thisis also an improvement for the common use-case.Signed-off-by: Finn Thain Tested-by: Stephen N Chivers [Geert: CONSOLE_DEBUG should depend on CONFIG_FONT_SUPPORT]Reported-by: kbuild test robot Signed-off-by: Geert Uytterhoeven List of files: /linux-6.15/arch/m68k/kernel/Makefile

7bc1e4d8 - m68k: Add support to export bootinfo in procfs

Wed, 21 Aug 2013 20:36:32 +0000

m68k: Add support to export bootinfo in procfsAdd optional support to export the bootinfo used to boot the kernel in a"bootinfo" file in procfs. This is useful with kexec.This is based on the similar feature for ATAGS on ARM.Signed-off-by: Geert Uytterhoeven List of files: /linux-6.15/arch/m68k/kernel/Makefile

7d5f5fa2 - m68k: Add kexec support

Tue, 20 Aug 2013 20:51:47 +0000

m68k: Add kexec supportSigned-off-by: Geert Uytterhoeven List of files: /linux-6.15/arch/m68k/kernel/Makefile

56183959 - m68k: Sort out !CONFIG_MMU_SUN3 vs. CONFIG_HAS_DMA

Thu, 27 Dec 2012 19:07:39 +0000

m68k: Sort out !CONFIG_MMU_SUN3 vs. CONFIG_HAS_DMAIn two places, we check !CONFIG_MMU_SUN3 while we should checkCONFIG_HAS_DMA instead.While fixing this, the check in became redundant( already handles this case), so just remove it.Signed-off-by: Geert Uytterhoeven List of files: /linux-6.15/arch/m68k/kernel/Makefile

e93a6bbe - m68k: common PCI support definitions and code

Mon, 28 Nov 2011 06:32:49 +0000

m68k: common PCI support definitions and codeBasic set of definitions and support code required to turn on CONFIG_PCIfor the m68k architecture. Nothing specific to any PCI implementation inany m68k class CPU hardware yet.Signed-off-by: Greg Ungerer Acked-by: Geert Uytterhoeven List of files: /linux-6.15/arch/m68k/kernel/Makefile

ab5fc1ff - m68k: Use generic init_task

Thu, 03 May 2012 09:02:54 +0000

m68k: Use generic init_taskSame code. Use the generic version.Signed-off-by: Thomas Gleixner Cc: Geert Uytterhoeven Link: http://lkml.kernel.org/r/20120503085034.816195285@linutronix.de List of files: /linux-6.15/arch/m68k/kernel/Makefile

3f0060b0 - m68k: do not use m68k startup or interrupt code for ColdFire CPUs

Wed, 19 Oct 2011 06:15:08 +0000

m68k: do not use m68k startup or interrupt code for ColdFire CPUsThe ColdFire CPUs have their own startup and interrupt code (in theplatform/coldfire directory), and do not use the general m68k startup andinterrupt code. In fact the use of the arch/m68k/kernel/head.o is not aboutCONFIG_MMU or not, it is really about the machine type we are compiling for.Modify the selection and use of head.o to be based on the machine type.Only select the local ints.o and vectors.o code if we are using the classic68k CPU types (that use the conventional Morotola MMU or SUN3 MMU).Signed-off-by: Greg Ungerer Acked-by: Matt Waddel Acked-by: Kurt Mahan List of files: /linux-6.15/arch/m68k/kernel/Makefile

409ee245 - m68k: merge the init_task code for mmu and non-mmu targets

Tue, 30 Aug 2011 06:11:05 +0000

m68k: merge the init_task code for mmu and non-mmu targetsThe init_task code can be the same for both mmu and non-mmu targets.None of the alignment carried out in the the current init_task codeis necessary. The linker script takes care of aligning the init_threadstructure to a THREAD SIZE boundary, and that is all we need.So use the init_task.c code for all target types, that makes m68kcode consistent with what most other architectures do.Signed-off-by: Greg Ungerer Acked-by: Geert Uytterhoeven List of files: /linux-6.15/arch/m68k/kernel/Makefile

d890d739 - m68k/irq: Remove obsolete m68k irq framework

Sun, 11 Sep 2011 09:28:04 +0000

m68k/irq: Remove obsolete m68k irq frameworkSigned-off-by: Geert Uytterhoeven List of files: /linux-6.15/arch/m68k/kernel/Makefile

4936f63c - m68k/irq: Add genirq support

Thu, 21 Apr 2011 20:50:52 +0000

m68k/irq: Add genirq supportDisabled on all platforms for nowSigned-off-by: Geert Uytterhoeven [v1] Acked-by: Thomas Gleixner List of files: /linux-6.15/arch/m68k/kernel/Makefile

bc4f4ac2 - m68k: move hardware vector setting from traps.c to its own file

Fri, 24 Jun 2011 06:15:40 +0000

m68k: move hardware vector setting from traps.c to its own fileMost of the trap.c code is general to all m68k arch members. But the codeit currently contains to set the hardware vector table is quite specific tothe 680x0 family. They can have the vector table at any address unlikeother family members (which either support only a single fixed address,or a limited range of addresses). So lets move that code out to a new file,vectors.c. This will make sharing the rest of the trap.c code easier andcleaner.Signed-off-by: Greg Ungerer List of files: /linux-6.15/arch/m68k/kernel/Makefile

0a01b310 - m68k: merge the mmu and non-mmu kernel/Makefiles

Tue, 21 Jun 2011 06:21:00 +0000

m68k: merge the mmu and non-mmu kernel/MakefilesThe few differences between the mmu and non-mmu kernel/Makefiles caneasily be handled inside of a single Makefile. Merge the 2 back intoa single Makefile.Signed-off-by: Greg Ungerer Acked-by: Sam Ravnborg List of files: /linux-6.15/arch/m68k/kernel/Makefile