Eric Lee / smarc-fsl-linux-kernel

31 Mar, 2011

1 commit

05 Aug, 2010

1 commit

  • 22b0763a2   MIPS: uasm: Add option to export uasm API. ... Browse Code »

    A 'select EXPORT_UASM' in Kconfig will cause the uasm to be exported
    for use in modules. When it is exported, all the uasm data and code
    cease to be __init and __initdata.

    Also daddiu_bug cannot be __cpuinitdata if uasm is exported. The
    cleanest thing is to just make it normal data.

    Signed-off-by: David Daney
    To: linux-mips@linux-mips.org
    To: wim@iguana.be
    Cc: linux-kernel@vger.kernel.org
    Patchwork: https://patchwork.linux-mips.org/patch/1500/
    Signed-off-by: Ralf Baechle

    David Daney
     

18 Sep, 2009

1 commit

12 May, 2008

1 commit

12 Mar, 2008

1 commit

29 Jan, 2008

1 commit

  • 20d60d997   [MIPS] R4000/R4400 errata workarounds ... Browse Code »

    This is the gereric part of R4000/R4400 errata workarounds. They include
    compiler and assembler support as well as some source code modifications
    to address the problems with some combinations of multiply/divide+shift
    instructions as well as the daddi and daddiu instructions.

    Changes included are as follows:

    1. New Kconfig options to select workarounds by platforms as necessary.

    2. Arch top-level Makefile to pass necessary options to the compiler; also
    incompatible configurations are detected (-mno-sym32 unsupported as
    horribly intrusive for little gain).

    3. Bug detection updated and shuffled -- the multiply/divide+shift problem
    is lethal enough that if not worked around it makes the kernel crash in
    time_init() because of a division by zero; the daddiu erratum might
    also trigger early potentially, though I have not observed it. On the
    other hand the daddi detection code requires the exception subsystem to
    have been initialised (and is there mainly for information).

    4. r4k_daddiu_bug() added so that the existence of the erratum can be
    queried by code at the run time as necessary; useful for generated code
    like TLB fault and copy/clear page handlers.

    5. __udelay() updated as it uses multiplication in inline assembly.

    Note that -mdaddi requires modified toolchain (which has been maintained
    by myself and available from my site for ~4years now -- versions covered
    are GCC 2.95.4 - 4.1.2 and binutils from 2.13 onwards). The -mfix-r4000
    and -mfix-r4400 have been standard for a while though.

    Signed-off-by: Maciej W. Rozycki
    Signed-off-by: Ralf Baechle

    Maciej W. Rozycki
     

12 Oct, 2007

1 commit

20 Sep, 2007

1 commit

27 Aug, 2007

1 commit

  • c99dcac43   [MIPS] Fix gcc 3.3 warning. ... Browse Code »

    CC arch/mips/kernel/cpu-bugs64.o
    arch/mips/kernel/cpu-bugs64.c: In function 'align_mod':
    arch/mips/kernel/cpu-bugs64.c:23: warning: asm operand 0 probably doesn't match constraints
    arch/mips/kernel/cpu-bugs64.c:23: warning: asm operand 1 probably doesn't match constraints

    Signed-off-by: Ralf Baechle

    Ralf Baechle
     

01 Jul, 2006

1 commit

06 Jun, 2006

1 commit

  • 460c0422c   [MIPS] Fix sparse warnings about too big constants. ... Browse Code »

    Fix following warnings:
    linux/arch/mips/kernel/setup.c:249:12: warning: constant 0xffffffff00000000 is so big it is unsigned long
    linux/arch/mips/kernel/cpu-bugs64.c:209:10: warning: constant 0xffffffffffffdb9a is so big it is unsigned long
    linux/arch/mips/kernel/cpu-bugs64.c:227:10: warning: constant 0xffffffffffffdb9a is so big it is unsigned long
    linux/arch/mips/kernel/cpu-bugs64.c:283:10: warning: constant 0xffffffffffffdb9a is so big it is unsigned long
    linux/arch/mips/kernel/cpu-bugs64.c:299:10: warning: constant 0xffffffffffffdb9a is so big it is unsigned long

    Signed-off-by: Atsushi Nemoto
    Signed-off-by: Ralf Baechle

    Atsushi Nemoto
     

05 Sep, 2005

1 commit

17 Apr, 2005

1 commit

  • 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

    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!

    Linus Torvalds