1. 13 8月, 2010 1 次提交
  2. 03 8月, 2010 2 次提交
    • S
      kconfig: add savedefconfig · 7cf3d73b
      Sam Ravnborg 提交于
      savedefconfig will save a minimal config to a file
      named "defconfig".
      
      The config symbols are saved in the same order as
      they appear in the menu structure so it should
      be possible to map them to the relevant menus
      if desired.
      
      The implementation was tested against several minimal
      configs for arm which was created using brute-force.
      
      There was one regression related to default numbers
      which had their valid range further limited by another symbol.
      
      Sample:
      
      config FOO
      	int "foo"
      	default 4
      
      config BAR
      	int "bar"
      	range 0 FOO
      
      If FOO is set to 3 then BAR cannot take a value higher than 3.
      But the current implementation will set BAR equal to 4.
      
      This is seldomly used and the final configuration is OK,
      and the fix was non-trivial.
      So it was documented in the code and left as is.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Acked-by: NUwe Kleine-König <u.kleine-koenig@pengutronix.de>
      Signed-off-by: NMichal Marek <mmarek@suse.cz>
      7cf3d73b
    • S
      kconfig: refactor code in symbol.c · c252147d
      Sam Ravnborg 提交于
      Move logic to determine default for a choice to
      a separate function.
      No functional changes.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Signed-off-by: NMichal Marek <mmarek@suse.cz>
      c252147d
  3. 02 2月, 2010 2 次提交
    • N
      kconfig: new configuration interface (nconfig) · 692d97c3
      nir.tzachar@gmail.com 提交于
      This patch was inspired by the kernel projects page, where an ncurses
      replacement for menuconfig was mentioned (by Sam Ravnborg).
      
      Building on menuconfig, this patch implements a more modern look
      interface using ncurses and ncurses' satellite libraries (menu, panel,
      form). The implementation does not depend on lxdialog, which is
      currently distributed with the kernel.
      Signed-off-by: NNir Tzachar <nir.tzachar@gmail.com>
      Signed-off-by: NMichal Marek <mmarek@suse.cz>
      692d97c3
    • V
      menuconfig: wrap long help lines · da60fbbc
      Vadim Bendebury (вб) 提交于
      Help text for certain config options is very extensive (the text
      includes the names of all  other options the option in question depends
      on). Long lines are not wrapped, making it impossible to see the list
      without scrolling horizontally.
      
      This patch adds some logic which wraps help screen lines at word
      boundaries to prevent truncating.
      
      Tested by running
      
        ARCH=powerpc make menuconfig O=/tmp/build
      
      which shows that the long lines are now wrapped, and
      
       ARCH=powerpc make xconfig O=/tmp/build
      
      to demonstrate that it still compiles and operates as expected.
      Signed-off-by: NVadim Bendebury <vbendeb@google.com>
      Signed-off-by: NMichal Marek <mmarek@suse.cz>
      da60fbbc
  4. 10 6月, 2009 1 次提交
  5. 26 7月, 2008 1 次提交
  6. 05 5月, 2008 1 次提交
  7. 29 1月, 2008 1 次提交
  8. 03 5月, 2007 1 次提交
  9. 14 12月, 2006 1 次提交
  10. 09 6月, 2006 4 次提交
  11. 09 11月, 2005 4 次提交
  12. 31 10月, 2005 1 次提交
  13. 29 7月, 2005 1 次提交
  14. 06 5月, 2005 1 次提交
    • A
      [PATCH] Kconfig i18n support · 3b9fa093
      Arnaldo Carvalho de Melo 提交于
      This patch adds i18n support for make *config, allowing users to have the
      config process in their own language.
      
      No printk was harmed in the process, don't worry, so all the bug reports,
      kernel messages, etc, remain in english, just the user tools to configure
      the kernel are internationalized.
      
      Users not interested in translations can just unset the related LANG,
      LC_ALL, etc env variables and have the config process in plain english,
      something like:
      
      LANG= make menuconfig
      
      is enough for having the whole config process in english. Or just don't
      install any translation file.
      
      Translations for brazilian portuguese are being done by a team of
      volunteers at:
      
      http://www.visionflex.inf.br/kernel_ptbr/pmwiki.php/Principal/Traducoes
      
      To start the translation process:
      
        make update-po-config
      
        This will generate the pot template named scripts/kconfig/linux.pot,
        copy it to, say, ~/es.po, to start the translation for spanish.
      
      To test your translation, as root issue this command:
      
        msgfmt -o /usr/share/locale/es/LC_MESSAGES/linux.mo ~/es.po
      
        Replace "es" with your language code.
      
        Then execute, for instance:
      
        make menuconfig
      
      The current patch doesn't use any optimization to reduce the size of the
      generated .mo file, it is possible to use the config option as a key, but
      this doesn't prevent the current patch from being used or the translations
      done under the current scheme to be in any way lost if we chose to do any
      kind of keying.
      
      Thanks to Fabricio Vaccari for starting the pt_BR (brazilian portuguese)
      translation effort, Thiago Maciera for helping me with the gconf.cc (QT
      frontent) i18n coding and to all the volunteers that are already working on
      the first translation, to pt_BR.
      
      I left the question on whether to ship the translations with the stock kernel
      sources to be discussed here, please share your suggestions.
      Signed-off-by: NArnaldo Carvalho de Melo <acme@conectiva.com.br>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: Linus Torvalds <torvalds@osdl.org
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      3b9fa093
  15. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4