09 Mar, 2020

1 commit

  • Adjust indentation from spaces to tab (+optional two spaces) as in
    coding style with command like:
    $ sed -e 's/^ /\t/' -i */Kconfig

    Signed-off-by: Krzysztof Kozlowski
    Link: https://lore.kernel.org/r/20191120133721.12178-1-krzk@kernel.org
    Signed-off-by: Geert Uytterhoeven

    Krzysztof Kozlowski
     

23 Nov, 2018

2 commits

  • There is nothing architecture specific in the PCMCIA core, so allow
    building it everywhere. The actual host controllers will depend on ISA,
    PCI or a specific SOC.

    Signed-off-by: Christoph Hellwig
    Acked-by: Dominik Brodowski
    Acked-by: Thomas Gleixner
    Acked-by: Paul Burton
    Signed-off-by: Masahiro Yamada

    Christoph Hellwig
     
  • There is no good reason to duplicate the PCI menu in every architecture.
    Instead provide a selectable HAVE_PCI symbol that indicates availability
    of PCI support, and a FORCE_PCI symbol to for PCI on and the handle the
    rest in drivers/pci.

    Signed-off-by: Christoph Hellwig
    Reviewed-by: Palmer Dabbelt
    Acked-by: Max Filippov
    Acked-by: Thomas Gleixner
    Acked-by: Bjorn Helgaas
    Acked-by: Geert Uytterhoeven
    Acked-by: Paul Burton
    Signed-off-by: Masahiro Yamada

    Christoph Hellwig
     

28 May, 2018

1 commit

  • Up to now we have only had support for the PCI bus when running the
    ColdFire CPU family with the MMU enabled. The only reason for this was
    the incomplete state of the IO remapping and access functions when
    running with the MMU disabled.

    Recent fixes and improvements to the ColdFire IO access code means we
    can now support the PCI bus when running non-MMU enabled as well.
    So modify the configuration support to allow it to be selected no matter
    what choice of MMU mode is used.

    Signed-off-by: Greg Ungerer
    Reviewed-by: Angelo Dureghello
    Tested-by: Angelo Dureghello

    Greg Ungerer
     

02 Nov, 2017

1 commit

  • 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
    Reviewed-by: Philippe Ombredanne
    Reviewed-by: Thomas Gleixner
    Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     

17 Apr, 2013

1 commit

  • Atari ROM port ISA adapter support for EtherNEC and NetUSBee adapters

    16 bit access for ROM port adapters follows debugging and
    clarification by David Galvez . The NetUSBee
    ISP1160 USB chip uses these macros.

    Signed-off-by: Michael Schmitz
    Signed-off-by: Geert Uytterhoeven

    Michael Schmitz
     

14 Nov, 2012

1 commit

  • This config item has not carried much meaning for a while now and is
    almost always enabled by default. As agreed during the Linux kernel
    summit, remove it.

    CC: Geert Uytterhoeven
    Signed-off-by: Kees Cook
    Signed-off-by: Geert Uytterhoeven

    Kees Cook
     

17 Jul, 2012

1 commit


09 Nov, 2011

1 commit


18 Oct, 2011

1 commit

  • The current mmu and non-mmu Kconfig files can be merged to form
    a more general selection of options. The current break up of options
    is due to the simple brute force merge from the m68k and m68knommu
    arch directories.

    Many of the options are not at all specific to having the MMU enabled
    or not. They are actually associated with a particular CPU type or
    platform type.

    Ultimately as we support all processors with the MMU disabled we need
    many of these options to be selectable without the MMU option enabled.
    And likewise some of the ColdFire processors, which currently are only
    supported with the MMU disabled, do have MMU hardware, and will need
    to have options selected on CPU type, not MMU disabled.

    This patch removes the old mmu and non-mmu Kconfigs and instead breaks
    up the configuration into four areas: cpu, machine, bus, devices.

    The Kconfig.cpu lists all the options associated with selecting a CPU,
    and includes options specific to each CPU type as well.

    Kconfig.machine lists all options associated with selecting a machine
    type. Almost always the machines selectable is restricted by the chosen
    CPU.

    Kconfig.bus contains options associated with selecting bus types on the
    various machine types. That includes PCI bus, PCMCIA bus, etc.

    Kconfig.devices contains options for drivers and driver associated
    options.

    Signed-off-by: Greg Ungerer

    Greg Ungerer