1. 28 Oct, 2005 1 commit
    • Lee Nicks's avatar
      [PATCH] ppc: prevent GCC 4 from generating AltiVec instructions in kernel · 9e3699ea
      Lee Nicks authored
      Depending on how GCC is built, GCC 4 may generate altivec instructions without
      user explicitly requesting vector operations in the code.  Although this is a
      performance booster for user applications, it is a problem for kernel.
      This patch explicitly instruct GCC to NOT generate altivec instructions while
      building the kernel.
      Here are some test cases I ran.
      (1) build gcc 4.0.1 with '--with-cpu=7450 --enable-altivec
          --enable-cxx-flags=-mcpu=7450', and use this gcc to build kernel WITHOUT
          this kernel patch.  Kernel fail to boot up on a 7450 board because of
          altivec instructions in kernel.
      (2) build gcc 4.0.1 with "--with-cpu=7450 --enable-altivec
          --enable-cxx-flags=-mcpu=7450", and use this gcc to build kernel WITH this
          kernel patch.  Kernel boot up on a 7450 board without any problem.
      (3) build gcc 4.0.1 with "--with-cpu=750 --enable-cxx-flags=-mcpu=750",
          and use this gcc to build kernel with or without this kernel patch.
          Kernel boot up on a 7450 board without any problem.
      This patch should also work with GCC 3 or even earlier GCC 2.95.3.
      Signed-off-by: default avatarLee Nicks <allinux@gmail.com>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarPaul Mackerras <paulus@samba.org>
  2. 26 Oct, 2005 1 commit
  3. 11 Oct, 2005 1 commit
    • Paul Mackerras's avatar
      ppc: Various minor compile fixes · fd582ec8
      Paul Mackerras authored
      This fixes up a variety of minor problems in compiling with ARCH=ppc
      arising from using the merged versions of various header files.
      A lot of the changes are just adding #include <asm/machdep.h> to
      files that use ppc_md or smp_ops_t.
      This also arranges for us to use semaphore.c, vecemu.c, vector.S and
      fpu.S from arch/powerpc/kernel when compiling with ARCH=ppc.
      Signed-off-by: default avatarPaul Mackerras <paulus@samba.org>
  4. 21 Sep, 2005 1 commit
  5. 11 Sep, 2005 1 commit
    • Sam Ravnborg's avatar
      kbuild: rename prepare to archprepare to fix dependency chain · 5bb78269
      Sam Ravnborg authored
      When introducing the generic asm-offsets.h support the dependency
      chain for the prepare targets was changed. All build scripts expecting
      include/asm/asm-offsets.h to be made when using the prepare target would broke.
      With the limited number of prepare targets left in arch Makefiles
      the trivial solution was to introduce a new arch specific target: archprepare
      The dependency chain looks like this now:
        +--> prepare0
               +--> archprepare
      		+--> scripts_basic
                      +--> prepare1
                             +---> prepare2
                                     +--> prepare3
      So prepare 3 is processed before prepare2 etc.
      This guaantees that the asm symlink, version.h, scripts_basic
      are all updated before archprepare is processed.
      prepare0 which build the asm-offsets.h file will need the
      actions performed by archprepare.
      The head target is now named prepare, because users scripts will most
      likely use that target, but prepare-all has been kept for compatibility.
      Updated Documentation/kbuild/makefiles.txt.
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
  6. 10 Sep, 2005 1 commit
  7. 09 Sep, 2005 1 commit
  8. 29 Aug, 2005 1 commit
  9. 25 Jun, 2005 1 commit
  10. 01 May, 2005 1 commit
  11. 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!