1. 20 11月, 2012 1 次提交
    • K
      menuconfig: fix extended colors ncurses support · 7d5bb966
      Krzysztof Mazur 提交于
      The ncurses library allows for extended colors. The support for extended
      colors support depends on wide-character support. ncurses headers
      enable extended colors (NCURSES_EXT_COLORS) only when wide-character
      support is enabled (NCURSES_WIDECHAR).
      
      The "make menuconfig" uses wide-character ncursesw library, which can be
      compiled with wide-character support, but does not define NCURSES_WIDECHAR
      and it's using headers without wide-character (and extended colors) support.
      
      This fixes problems with colors on systems with enabled extended colors
      (like PLD Linux). Without this patch "make menuconfig" is hard to use.
      Signed-off-by: NKrzysztof Mazur <krzysiek@podlesie.net>
      Signed-off-by: NMichal Marek <mmarek@suse.cz>
      7d5bb966
  2. 03 10月, 2012 1 次提交
    • J
      kbuild: Fix gcc -x syntax · b1e0d8b7
      Jean Delvare 提交于
      The correct syntax for gcc -x is "gcc -x assembler", not
      "gcc -xassembler". Even though the latter happens to work, the former
      is what is documented in the manual page and thus what gcc wrappers
      such as icecream do expect.
      
      This isn't a cosmetic change. The missing space prevents icecream from
      recognizing compilation tasks it can't handle, leading to silent kernel
      miscompilations.
      
      Besides me, credits go to Michael Matz and Dirk Mueller for
      investigating the miscompilation issue and tracking it down to this
      incorrect -x parameter syntax.
      Signed-off-by: NJean Delvare <jdelvare@suse.de>
      Acked-by: NIngo Molnar <mingo@kernel.org>
      Cc: stable@vger.kernel.org
      Cc: Bernhard Walle <bernhard@bwalle.de>
      Cc: Michal Marek <mmarek@suse.cz>
      Cc: Ralf Baechle <ralf@linux-mips.org>
      Signed-off-by: NMichal Marek <mmarek@suse.cz>
      b1e0d8b7
  3. 02 10月, 2012 1 次提交
  4. 28 9月, 2012 7 次提交
  5. 31 8月, 2012 1 次提交
  6. 30 8月, 2012 1 次提交
  7. 17 8月, 2012 4 次提交
  8. 26 7月, 2012 3 次提交
    • S
      kconfig: Document oldnoconfig to what it really does · 67d34a6a
      Steven Rostedt 提交于
      The make target 'oldnoconfig' is a misnomer. It doesn't set new symbols
      to 'n', but instead sets it to their default values.
      
      Unfortunately, assuming that it actually did this, broke ktest in some
      of its tests. For example, the tests to create a minimum config and even
      a config bisect, depends on removing various configs and using
      oldnoconfig to get rid of other configs that may have depended on it.
      
      But because some configs that it was trying to disable, were in fact
      default enabled, this caused those configs to re-enable and corrupt the
      test.
      
      I thought about fixing oldnoconfig, but I'm afraid that people are
      already dependent on its current behavior. Instead, I'm just updating
      the documentation to state that it sets the new symbols to their default
      values and not to 'n'.
      
      Ideally, this would be called, 'olddefconfig' and we have an
      'oldnoconfig' that actually disables the new symbols. But it's useless
      for me now. If it changed, ktest would need to be consistent between
      each version, and that would be to difficult to detect. I'll handle this
      issue with ktest with other means.
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      Signed-off-by: NMichal Marek <mmarek@suse.cz>
      67d34a6a
    • B
      nconf: add u, d command keys in scroll windows · d68e818b
      Benjamin Poirier 提交于
      They function just like they do in less(1).
      Also correct some discrepancy between the help text and the code wrt
      function keys.
      Signed-off-by: NBenjamin Poirier <bpoirier@suse.de>
      Signed-off-by: NMichal Marek <mmarek@suse.cz>
      d68e818b
    • B
      menuconfig: add u, d, q command keys in text boxes · 9d4792c9
      Benjamin Poirier 提交于
      They function just like they do in less(1).
      Signed-off-by: NBenjamin Poirier <bpoirier@suse.de>
      Signed-off-by: NMichal Marek <mmarek@suse.cz>
      9d4792c9
  9. 14 7月, 2012 2 次提交
  10. 13 7月, 2012 3 次提交
  11. 05 7月, 2012 3 次提交
  12. 20 6月, 2012 4 次提交
    • S
      localmodconfig: Add debug environment variable LOCALMODCONFIG_DEBUG · 4503379c
      Steven Rostedt 提交于
      If the environment variable LOCALMODCONFIG_DEBUG is set, then debug output
      will appear in the make localmodconfig. This will simplify debugging what
      people get with their output, as I can just tell people to do:
      
        LOCALMODCONFIG_DEBUG=1 make localmodconfig 2>out.txt
      
      and have them send me the out.txt. I'll be able to see why things are not
      working as they think it should be.
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      4503379c
    • S
      localmodconfig: Check if configs are already set for selects · d4bb58b5
      Steven Rostedt 提交于
      There are some cases that a required module does not have a prompt
      and needs to have another module enabled that selects it to be set.
      As localmodconfig is conservative and tries to make the minimum config
      without breaking the user's kernel, or keeping the user from using
      devices that were loaded when the lsmod was done, all modules that
      select this module will also be enabled.
      
      If you needed module A, but module A did not have a prompt but needed
      module B to be selected, localmodconfig would make sure B was still
      enabled. If not only B selected A, but C, D, E, F, and G also
      selected A, then all of those would also be included, as well as the
      modules they depend on. This ballooned the number of configs that
      localmodconfig would keep.
      
      The fix here is to process the depends first, and then record those
      configs that did not have a prompt and needed to be selected.
      After the depends are done, check what configs are needed to select
      the configs in the list, and if a config that selects it is already
      set, then we don't need to do anything else.
      
      If no config that selects the config is set, then just pick one and
      try again.
      
      This change brought down the number of selected modules from 290
      to 67! Both before and after were run against a config that had 3095
      modules enabled.
      
      Tested-by: John David Yost <johnyost@ptd.net> # AlleyTrotter
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      d4bb58b5
    • S
      localmodconfig: Read in orig config file to avoid extra processing · 4f4c51c9
      Steven Rostedt 提交于
      Read in the entire config file. If there's a config that we depend on
      that happens to be in the core set (not a module) then we do not need
      to process it as a module.
      
      Currently, we follow the entire depend and selects even if they
      are enabled as core and not modules. By checking to make sure that we
      only look at modules we can drop the count a little.
      
      From one of my tests, localmodconfig went from taking 3095 set modules
      down to 356 before this patch, and down to 290 modules after the change.
      
      Tested-by: John David Yost <johnyost@ptd.net> # AlleyTrotter
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      4f4c51c9
    • S
      localmodconfig: Comments and cleanup for streamline_config.pl · 0b58a99e
      Steven Rostedt 提交于
      Added some more comments and cleaned up part of the the code to use
      a named variable instead of one of the special $1 perl variables.
      
      No functional changes.
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      0b58a99e
  13. 18 5月, 2012 1 次提交
    • P
      MCA: delete all remaining traces of microchannel bus support. · bb8187d3
      Paul Gortmaker 提交于
      Hardware with MCA bus is limited to 386 and 486 class machines
      that are now 20+ years old and typically with less than 32MB
      of memory.  A quick search on the internet, and you see that
      even the MCA hobbyist/enthusiast community has lost interest
      in the early 2000 era and never really even moved ahead from
      the 2.4 kernels to the 2.6 series.
      
      This deletes anything remaining related to CONFIG_MCA from core
      kernel code and from the x86 architecture.  There is no point in
      carrying this any further into the future.
      
      One complication to watch for is inadvertently scooping up
      stuff relating to machine check, since there is overlap in
      the TLA name space (e.g. arch/x86/boot/mca.c).
      
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: James Bottomley <JBottomley@Parallels.com>
      Cc: x86@kernel.org
      Acked-by: NIngo Molnar <mingo@elte.hu>
      Acked-by: NH. Peter Anvin <hpa@zytor.com>
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      bb8187d3
  14. 08 5月, 2012 1 次提交
    • E
      kbuild: all{no,yes,mod,def,rand}config only read files when instructed to. · 9f420bf0
      Eric W. Biederman 提交于
      Prevent subtle surprises to both people working on the kconfig code
      and people using make allnoconfig allyesconfig allmoconfig and
      randconfig by only attempting to read a config file if
      KCONFIG_ALLCONFIG is set.
      
      Common sense suggests attempting to read the extra config files does
      not make sense unless requested.  The documentation says the code
      won't attempt to read the extra config files unless requested.
      Current usage does not appear to include people depending on the code
      reading the config files without the variable being set So do the
      simple thing and stop reading config files when passed
      all{no,yes,mod,def,rand}config unless KCONFIG_ALLCONFIG environment
      variable is set.
      Signed-off-by: NEric W. Biederman <ebiederm@xmission.com>
      Reported-by: NStephen Rothwell <sfr@canb.auug.org.au>
      Signed-off-by: NMichal Marek <mmarek@suse.cz>
      9f420bf0
  15. 05 5月, 2012 1 次提交
    • E
      kconfig: Add error handling to KCONFIG_ALLCONFIG · 5efe241e
      Eric W. Biederman 提交于
      - Only try to read the file specified if KCONFIG_ALL_CONFIG is set to
        something other than the empty string or "1".
      
      - Don't use stat to check the name passed to conf_read_simple so that
        zconf_fopen can find the file in the current directory or in SRCTREE
        removing a extremely source of confusing failure, where KCONFIG_ALL_CONFIG
        was not interpreted with respect to the directory make was called in.
      
      - If conf_read_simple fails complain clearly and stop processing.
        Allowing the simple debugging of typos.
      
      - Clearly document the behavior so it is clear to users which
        values are treated as flags and which values are treated as
        filenames.
      Signed-off-by: NEric W. Biederman <ebiederm@xmission.com>
      Signed-off-by: NMichal Marek <mmarek@suse.cz>
      5efe241e
  16. 13 4月, 2012 2 次提交
  17. 30 3月, 2012 2 次提交
  18. 25 3月, 2012 1 次提交
  19. 26 1月, 2012 1 次提交
    • A
      kconfig: fix new choices being skipped upon config update · 5d09598d
      Arnaud Lacombe 提交于
      Running `oldconfig' after any of the following configuration change:
      
      either trivial addition, such as:
      
      config A
      	bool "A"
      
      choice
      	prompt "Choice ?"
      	depends on A
      
      	config CHOICE_B
      		bool "Choice B"
      
      	config CHOICE_C
      		bool "Choice C"
      endchoice
      
      or more tricky change:
      
      OLD KCONFIG                      |  NEW KCONFIG
                                       |
                                       |  config A
                                       |          bool "A"
                                       |
      choice                           |  choice
              prompt "Choice ?"        |          prompt "Choice ?"
                                       |
              config CHOICE_C          |          config CHOICE_C
                      bool "Choice C"  |                  bool "Choice C"
                                       |
              config CHOICE_D          |          config CHOICE_D
                      bool "Choice D"  |                  bool "Choice D"
      endchoice                        |
                                       |          config CHOICE_E
                                       |                  bool "Choice E"
                                       |                  depends on A
                                       |  endchoice
      
      will not cause the choice to be considered as NEW, and thus not be
      asked. The cause of this behavior is that choice's novelty are computed
      statically right after the saved configuration has been read. At this
      point, the new dependency's value is still unknown and asserted to be
      `no'. Moreover, no update to this decision is made afterward.
      
      Correct this by dynamically evaluating a choice's novelty, and removing the
      static evaluation.
      Reported-and-tested-by: NUwe Kleine-König <u.kleine-koenig@pengutronix.de>
      Signed-off-by: NArnaud Lacombe <lacombar@gmail.com>
      Signed-off-by: NMichal Marek <mmarek@suse.cz>
      5d09598d