20 Feb, 2007

1 commit

• 269dd2b25   [MIPS] Fix struct sigcontext for N32 userland ... Browse Code »

  The kernel use 64-bit for sc_regs[0], and both N32/N64 userland
  expects it was 64-bit. But size of 'long' on N32 is actually 32-bit.
  So this definition make some confusion. Use __u32 and __u64 for
  N32/N64 sigcontext to get rid of this confusion.

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

  Atsushi Nemoto

  2007-02-20 09:26:42 +0800  

11 Feb, 2007

1 commit

• 6bfe96616   [MIPS] signal32: no need to save c0_status register in setup_sigcontext32() ... Browse Code »

  All the information in the MIPS c0_status register is priviledged.
  Nothing that would constitute part of the thread context.

  The one flag one could possibly argument about might be c0_status.fr
  but none of the ABIs or tools or application software can make use
  of it.

  So for consistency with restore_sigcontext32(), which does not
  restore c0_status register, this patch remove the saving part.

  Signed-off-by: Franck Bui-Huu
  Signed-off-by: Ralf Baechle

  Franck Bui-Huu

  2007-02-11 06:38:47 +0800  

01 Jun, 2006

1 commit

• 1c0c1ae4f   [MIPS] Update struct sigcontext member names ... Browse Code »

  Rename the 64-bit sc_hi and sc_lo arrays to use the same names
  as the 32-bit struct sigcontext (sc_mdhi, sc_hi1, et cetera).

  Signed-off-by: Daniel Jacobowitz
  Signed-off-by: Ralf Baechle

  Daniel Jacobowitz

  2006-06-01 07:28:31 +0800  

30 Oct, 2005

1 commit

• e50c0a8fa   Support the MIPS32 / MIPS64 DSP ASE. ... Browse Code »

  Signed-off-by: Ralf Baechle

  Ralf Baechle

  2005-10-30 02:31:17 +0800  

05 Sep, 2005

1 commit

• 42a3b4f25   [PATCH] mips: nuke trailing whitespace ... Browse Code »

  Signed-off-by: Ralf Baechle
  Signed-off-by: Andrew Morton
  Signed-off-by: Linus Torvalds

  Ralf Baechle

  2005-09-05 15:06:07 +0800  

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

  2005-04-17 06:20:36 +0800