1. 29 Oct, 2005 3 commits
    • Marcelo Tosatti's avatar
      [PATCH] MPC8xx PCMCIA driver · de957c89
      Marcelo Tosatti authored
      Here is an uptodated version of the MPC8xx PCMCIA driver for v2.6,
      addressing comments by Jeff and Dominik:
      
      - use IO accessors instead of direct device memory referencing
      - avoid usage of non-standard "uint/uchar" data types
      - kill struct typedef's
      
      Will submit it for inclusion once v2.6.14 is out.
      
      Testing on 8xx platforms is more than welcome! Works like a charm
      on our custom hardware (CONFIG_PRxK).
      
      Cc: Dominik Brodowski <linux@dominikbrodowski.net>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarPaul Mackerras <paulus@samba.org>
      de957c89
    • Marcelo Tosatti's avatar
      [PATCH] ppc32 8xx: use io accessor macros instead of direct memory reference · e37b0c96
      Marcelo Tosatti authored
      Convert core 8xx drivers to use in_xxxbe/in_xxx macros instead of direct
      memory references.
      
      Other than making IO accesses explicit (which is a plus for readability), a
      common set of macros provides a unified place for the volatile flag to
      constraint compiler code reordering.
      
      There are several unlucky places at the moment which lack the volatile
      flag.
      Signed-off-by: default avatarMarcelo Tosatti <marcelo.tosatti@cyclades.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarPaul Mackerras <paulus@samba.org>
      e37b0c96
    • 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>
      9e3699ea
  2. 28 Oct, 2005 21 commits
  3. 27 Oct, 2005 16 commits