1. 17 Nov, 2007 1 commit
    • Sam Ravnborg's avatar
      x86: simplify "make ARCH=x86" and fix kconfig all.config · 6840999b
      Sam Ravnborg authored
      Simplify "make ARCH=x86" and fix kconfig so we again can set 64BIT in
      all.config.
      
      For a fix the diffstat is nice:
       6 files changed, 3 insertions(+), 36 deletions(-)
      
      The patch reverts these commits:
       - 0f855aa6 ("kconfig: add helper to set
         config symbol from environment variable")
       - 2a113281
      
       ("kconfig: use $K64BIT to
         set 64BIT with all*config targets")
      
      Roman Zippel pointed out that kconfig supported string compares so
      the additional complexity introduced by the above two patches were
      not needed.
      
      With this patch we have following behaviour:
      
        # make {allno,allyes,allmod,rand}config [ARCH=...]
        option \ host arch      | 32bit         | 64bit
        =====================================================
        ./.                     | 32bit         | 64bit
        ARCH=x86                | 32bit         | 32bit
        ARCH=i386               | 32bit         | 32bit
        ARCH=x86_64             | 64bit         | 64bit
      
      The general rule are that ARCH= and native architecture takes
      precedence over the configuration.
      
      So make ARCH=i386 [whatever] will always build a 32-bit kernel
      no matter what the configuration says.  The configuration will
      be updated to 32-bit if it was configured to 64-bit and the
      other way around.
      
      This behaviour is consistent with previous behaviour so no
      suprises here.
      
      make ARCH=x86 will per default result in a 32-bit kernel but as
      the only ARCH= value x86 allow the user to select between 32-bit
      and 64-bit using menuconfig.
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      Cc: Roman Zippel <zippel@linux-m68k.org>
      Cc: Andreas Herrmann <aherrman@arcor.de>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: "H. Peter Anvin" <hpa@zytor.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      6840999b
  2. 12 Nov, 2007 2 commits
  3. 17 Jul, 2007 1 commit
    • Roman Zippel's avatar
      kconfig: reset generated values only if Kconfig and .config agree. · d8982ba1
      Roman Zippel authored
      
      
      Normally generated values (Kconfig entries without a prompt) are cleared as
      they are regenerated anyway and so they appear as new should they become
      visible and defaults work as expected (once a value is set defaults aren't
      used anymore).
      
      The detection whether a value is generated or not is only based on its
      visibility status, which can quickly change for a lot of symbols by just
      removing a single line from .config or adding a dependency to Kconfig as you
      noticed.
      
      The patch now suppresses this logic when .config and Kconfig aren't in sync
      and .config needs to be updated, so that you can remove now a random value
      from .config and oldconfig won't reask for many other values.
      Signed-off-by: default avatarRoman Zippel <zippel@linux-m68k.org>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      d8982ba1
  4. 13 Dec, 2006 3 commits
  5. 01 Oct, 2006 1 commit
  6. 25 Sep, 2006 1 commit
  7. 01 Aug, 2006 1 commit
  8. 09 Jun, 2006 7 commits
  9. 11 Apr, 2006 1 commit
  10. 12 Mar, 2006 1 commit
  11. 16 Jan, 2006 1 commit
    • Sam Ravnborg's avatar
      kbuild: create .kernelrelease at *config step · 2244cbd8
      Sam Ravnborg authored
      
      
      To enable 'make kernelrelease' earlier now create .kernelrelease when
      one of the *config targets are used.
      Also introduce KERNELVERSION - only user is kconfig.
      KERNELVERSION was needed to display kernel version in menuconfig -
      KERNELRELEASE is not valid until configuration has completed.
      kconfig files modified to use KERNELVERSION.
      Bug reported by: Rene Rebe <rene@exactcode.de>
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      2244cbd8
  12. 09 Nov, 2005 2 commits
  13. 25 Jun, 2005 1 commit
  14. 05 May, 2005 1 commit
    • Arnaldo Carvalho de Melo's avatar
      [PATCH] Kconfig i18n support · 3b9fa093
      Arnaldo Carvalho de Melo authored
      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: default avatarArnaldo Carvalho de Melo <acme@conectiva.com.br>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: Linus Torvalds <torvalds@osdl.org
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      3b9fa093
  15. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      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