1. 14 Jun, 2018 1 commit
  2. 19 May, 2018 2 commits
  3. 02 Nov, 2017 1 commit
    • Greg Kroah-Hartman's avatar
      License cleanup: add SPDX GPL-2.0 license identifier to files with no license · b2441318
      Greg Kroah-Hartman authored
      
      
      Many source files in the tree are missing licensing information, which
      makes it harder for compliance tools to determine the correct license.
      
      By default all files without license information are under the default
      license 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 binding
      shorthand, which can be used instead of the full boiler plate text.
      
      This patch is based on work done by Thomas Gleixner and Kate Stewart and
      Philippe Ombredanne.
      
      How this work was done:
      
      Patches were generated and checked against linux-4.14-rc6 for a subset of
      the 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 cases
      where non-standard license headers were used, and references to license
      had to be inferred by heuristics based on keywords.
      
      The analysis to determine which SPDX License Identifier to be applied to
      a file was done in a spreadsheet of side by side results from of the
      output of two independent scanners (ScanCode & Windriver) producing SPDX
      tag:value files created by Philippe Ombredanne.  Philippe prepared the
      base 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 files
      assessed.  Kate Stewart did a file by file comparison of the scanner
      results in the spreadsheet to determine which SPDX license identifier(s)
      to be applied to the file. She confirmed any determination that was not
      immediately 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 license
      identifiers 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 the
      spreadsheet to determine the SPDX license identifiers to apply to the
      source files by Kate, Philippe, Thomas and, in some cases, confirmation
      by lawyers working with the Linux Foundation.
      
      Kate also obtained a third independent scan of the 4.13 code base from
      FOSSology, and compared selected files where the other two scanners
      disagreed against that SPDX file, to see if there was new insights.  The
      Windriver scanner is based on an older version of FOSSology in part, so
      they are related.
      
      Thomas did random spot checks in about 500 files from the spreadsheets
      for the uapi headers and agreed with SPDX license identifier in the
      files he inspected. For the non-uapi files Thomas did random spot checks
      in about 15000 files.
      
      In initial set of patches against 4.14-rc6, 3 files were found to have
      copy/paste license identifier errors, and have been fixed to reflect the
      correct identifier.
      
      Additionally Philippe spent 10 hours this week doing a detailed manual
      inspection and review of the 12,461 patched files from the initial patch
      version 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 correct
      
      This produced a worksheet with 20 files needing minor correction.  This
      worksheet was then exported into 3 different .csv files for the
      different types of files to be modified.
      
      These .csv files were then reviewed by Greg.  Thomas wrote a script to
      parse the csv files and add the proper SPDX tag to the file, in the
      format that the file expected.  This script was further refined by Greg
      based on the output to detect more types of files automatically and to
      distinguish between header and source .c files (which need different
      comment types.)  Finally Greg ran the script using the .csv files to
      generate the patches.
      Reviewed-by: default avatarKate Stewart <kstewart@linuxfoundation.org>
      Reviewed-by: default avatarPhilippe Ombredanne <pombredanne@nexb.com>
      Reviewed-by: default avatarThomas Gleixner <tglx@linutronix.de>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      b2441318
  4. 03 Oct, 2017 1 commit
    • Russell King's avatar
      ARM: decompressor: fix BSS size calculation · 429f7a06
      Russell King authored
      
      
      Assuming size(1) gives the size of the BSS is a mistake - it reports
      the size of the .bss section in the ELF image, which may not be the
      same as the region we mark with the __bss_start..__bss_stop symbols.
      
      We use the size of the BSS in the decompressor to know whether the
      kernel will overwrite the appended dtb, by adding the BSS size to the
      size of the Image (stored at the end of the compressed data) and adding
      the desired address of the decompressed image.
      
      If the BSS size is smaller than it really is, the decompressor can
      incorrectly assume that the BSS clearance will not overwrite the DTB.
      
      Here is an illustration:
      
      $ arm-linux-size vmlinux
         text    data      bss      dec     hex filename
      8136972 3098076 10240348 21475396 147b044 vmlinux
      $ arm-linux-nm vmlinux | grep __bss_
      c0ac0e34 B __bss_start
      c1484f9c B __bss_stop
      $ stat -c %s arch/arm/boot/Image
      11243060
      
      In the above case, we are 12 bytes short.  This is caused by the BSS
      section being aligned by one of its input sections:
      
      Idx Name          Size      VMA       LMA       File off  Algn
       23 __bug_table   00005d3c  c0abb0f8  c0abb0f8  00acb0f8  2**2
                        CONTENTS, ALLOC, LOAD, DATA
       24 .bss          009c415c  c0ac0e40  c0ac0e40  00ad0e34  2**6
                        ALLOC
      
      Note that there's an additional 12 bytes difference between the file
      offset and LMA compared with the bug table - this occurs because one
      of the input sections for the .bss section requires a 64 byte
      alignment.
      
      Fix this by using 'nm' and perl to obtain the address of the __bss_start
      and __bss_stop symbols, using their difference for the size of the BSS.
      Tested-by: default avatarTony Lindgren <tony@atomide.com>
      Tested-by: default avatarKeerthy <j-keerthy@ti.com>
      Signed-off-by: default avatarRussell King <rmk+kernel@armlinux.org.uk>
      429f7a06
  5. 22 Feb, 2016 8 commits
  6. 26 Jan, 2016 1 commit
  7. 14 Dec, 2015 1 commit
  8. 06 Jul, 2015 1 commit
  9. 27 May, 2015 1 commit
  10. 23 Feb, 2015 1 commit
  11. 26 Sep, 2014 1 commit
  12. 01 Jul, 2014 2 commits
  13. 29 Dec, 2013 1 commit
  14. 10 Dec, 2013 1 commit
  15. 17 Sep, 2013 1 commit
    • Linus Walleij's avatar
      ARM: delete mach-shark · 136dfa5e
      Linus Walleij authored
      
      
      The Shark machine sub-architecture (also known as DNARD, the
      DIGITAL Network Appliance Reference Design) lacks a maintainer
      able to apply and test patches to modernize the architecture.
      
      It is suspected that the current kernel, while it compiles,
      does not even boot on this machine. The listed maintainer has
      expressed that he will not be able to spend any time on the
      maintenance for the coming year.
      
      So let's delete it from the kernel for now. It can always be
      resurrected with git revert if maintenance is resumed.
      
      As the VIA82c505 PCI adapter was only used by this
      architecture, that gets deleted too.
      
      Cc: arm@kernel.org
      Cc: Alexander Schulz <alex@shark-linux.de>
      Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      136dfa5e
  16. 09 Jul, 2013 1 commit
  17. 28 Jun, 2013 1 commit
    • Geert Uytterhoeven's avatar
      lib: Move fonts from drivers/video/console/ to lib/fonts/ · ee89bd6b
      Geert Uytterhoeven authored
      
      
      Several drivers need font support independent of CONFIG_VT, cfr. commit
      9cbce8d7e1dae0744ca4f68d62aa7de18196b6f4, "console/font: Refactor font
      support code selection logic").
      Hence move the fonts and their support logic from drivers/video/console/ to
      its own library directory lib/fonts/.
      This also allows to limit processing of drivers/video/console/Makefile to
      CONFIG_VT=y again.
      
      [Kevin Hilman <khilman@linaro.org>: Update arch/arm/boot/compressed/Makefile]
      Signed-off-by: default avatarGeert Uytterhoeven <geert@linux-m68k.org>
      ee89bd6b
  18. 17 Jun, 2013 1 commit
  19. 05 Jun, 2013 1 commit
    • Arnd Bergmann's avatar
      ARM: 7743/1: compressed/head.S: work around new binutils warning · da94a829
      Arnd Bergmann authored
      In August 2012, Matthew Gretton-Dann checked a change into binutils
      labelled "Error on obsolete & warn on deprecated registers", apparently as
      part of ARMv8 support. Apparently, this was supposed to emit the message
      "Warning: This coprocessor register access is deprecated in ARMv8" when
      using certain mcr/mrc instructions and building for ARMv8. Unfortunately,
      the message that is actually emitted appears to be '(null)', which is
      less helpful in comparison.
      
      Even more unfortunately, this is biting us on every single kernel
      build with a new gas, because arch/arm/boot/compressed/head.S and some
      other files in that directory are built with -march=all since kernel
      commit 80cec14a
      
       "[ARM] Add -march=all to assembly file build in
      arch/arm/boot/compressed" back in v2.6.28.
      
      This patch reverts Russell's nice solution and instead marks the head.S
      file to be built for armv7-a, which fortunately lets us build all
      instructions in that file without warnings even on the broken binutils.
      
      Without this patch, building anything results in:
      
      arch/arm/boot/compressed/head.S: Assembler messages:
      arch/arm/boot/compressed/head.S:565: Warning: (null)
      arch/arm/boot/compressed/head.S:676: Warning: (null)
      arch/arm/boot/compressed/head.S:698: Warning: (null)
      arch/arm/boot/compressed/head.S:722: Warning: (null)
      arch/arm/boot/compressed/head.S:726: Warning: (null)
      arch/arm/boot/compressed/head.S:957: Warning: (null)
      arch/arm/boot/compressed/head.S:996: Warning: (null)
      arch/arm/boot/compressed/head.S:997: Warning: (null)
      arch/arm/boot/compressed/head.S:1027: Warning: (null)
      arch/arm/boot/compressed/head.S:1035: Warning: (null)
      arch/arm/boot/compressed/head.S:1046: Warning: (null)
      arch/arm/boot/compressed/head.S:1060: Warning: (null)
      arch/arm/boot/compressed/head.S:1092: Warning: (null)
      arch/arm/boot/compressed/head.S:1094: Warning: (null)
      arch/arm/boot/compressed/head.S:1095: Warning: (null)
      arch/arm/boot/compressed/head.S:1102: Warning: (null)
      arch/arm/boot/compressed/head.S:1134: Warning: (null)
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Cc: stable@vger.kernel.org
      Cc: Matthew Gretton-Dann <matthew.gretton-dann@arm.com>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      da94a829
  20. 15 Mar, 2013 1 commit
    • Shawn Guo's avatar
      ARM: 7672/1: uncompress debug support for multiplatform build · 3b4af9bc
      Shawn Guo authored
      
      
      Instead of giving zero support of uncompress debug for multiplatform
      build, the patch turns uncompress debug into one part of DEBUG_LL
      support.  When DEBUG_LL is turned on for a particular platform,
      uncompress debug works too for that platform.
      
      OMAP and Tegra are exceptions here.  OMAP low-level debug code places
      data in the .data section, and that is not allowed in decompressor.
      And Tegra code has reference to variable that's unavailable in
      decompressor but only in kernel.  That's why Kconfig symbol
      DEBUG_UNCOMPRESS controlling multiplatform uncompress debug support is
      defined with !DEBUG_OMAP2PLUS_UART && !DEBUG_TEGRA_UART.
      
      It creates arch/arm/boot/compressed/debug.S with CONFIG_DEBUG_LL_INCLUDE
      included there, implements a generic putc() using those macros, which
      will be built when DEBUG_UNCOMPRESS is defined.
      Signed-off-by: default avatarShawn Guo <shawn.guo@linaro.org>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      3b4af9bc
  21. 06 Mar, 2013 1 commit
    • Jonathan Austin's avatar
      ARM: 7666/1: decompressor: add -mno-single-pic-base for building the decompressor · b8083f86
      Jonathan Austin authored
      
      
      Before jumping to (position independent) C-code from the decompressor's
      assembler world we set-up the C environment. This setup currently does not
      set r9, which for arm-none-uclinux-uclibceabi toolchains is by default
      expected to be the PIC offset base register (IE should point to the
      beginning of the GOT).
      
      Currently, therefore, in order to build working kernels that use the
      decompressor it is necessary to use an arm-linux-gnueabi toolchain, or
      similar. uClinux toolchains cause a prefetch abort to occur at the beginning
      of the decompress_kernel function.
      
      This patch allows uClinux toolchains to build bootable zImages by forcing
      the -mno-single-pic-base option, which ensures that the location of the GOT
      is re-derived each time it is required, and r9 becomes free for use as a
      general purpose register.
      
      This has a small (4% in instruction terms) advantage over the alternative of
      setting r9 to point to the GOT before calling into the C-world.
      Signed-off-by: default avatarJonathan Austin <jonathan.austin@arm.com>
      Acked-by: default avatarNicolas Pitre <nico@linaro.org>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      b8083f86
  22. 21 Nov, 2012 1 commit
  23. 15 Oct, 2012 1 commit
  24. 19 Sep, 2012 1 commit
    • Dave Martin's avatar
      ARM: zImage/virt: hyp mode entry support for the zImage loader · 424e5994
      Dave Martin authored
      
      
      The zImage loader needs to turn on the MMU in order to take
      advantage of caching while decompressing the zImage.  Running this
      in hyp mode would require the LPAE pagetable format to be
      supported; to avoid this complexity, this patch switches out of hyp
      mode, and returns back to hyp mode just before booting the kernel.
      
      This implementation assumes that the Hyp mode view of memory and the
      PL1 view of memory are coherent, providing that the MMU and caches
      are off in both, as required by the boot protocol.  The zImage
      decompression code must drain the write buffer on completion anyway, and
      entry into Hyp mode should flush any prefetch buffer, avoiding hazards
      associated with local write buffers and the pipeline.
      Signed-off-by: default avatarDave Martin <dave.martin@linaro.org>
      Signed-off-by: default avatarMarc Zyngier <marc.zyngier@arm.com>
      424e5994
  25. 24 Mar, 2012 1 commit
  26. 03 Jan, 2012 1 commit
  27. 17 Oct, 2011 2 commits
  28. 14 Sep, 2011 3 commits