Skip to content

K
Kernel

openeuler / Kernel
大约 1 年 前同步成功

通知 6
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 27 10月, 2009 1 次提交
  3. 26 10月, 2009 1 次提交
  5. 20 8月, 2009 1 次提交
  7. 14 8月, 2009 1 次提交
  9. 29 7月, 2009 2 次提交
  11. 23 7月, 2009 1 次提交
  13. 21 7月, 2009 1 次提交
  15. 11 7月, 2009 1 次提交
    • P
      sh: Decouple mcount from ftrace. · 473d1cf4
      由 Paul Mundt 提交于 
      This adds a general CONFIG_MCOUNT in order to permit mcount generation
without ftrace support. This is primarily for allowing platforms to
enable aggressive stack overflow checking without having to enable ftrace
support. Based on the sparc64 implementation.
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      473d1cf4
  17. 10 6月, 2009 1 次提交
  19. 26 5月, 2009 1 次提交
  21. 10 5月, 2009 1 次提交
  23. 09 5月, 2009 2 次提交
  25. 08 5月, 2009 2 次提交
  27. 10 3月, 2009 1 次提交
  29. 22 12月, 2008 7 次提交
  31. 31 10月, 2008 1 次提交
  33. 28 10月, 2008 3 次提交
    • P
      sh: Simplify and lock down the ISA tuning. · b2d86a3f
      由 Paul Mundt 提交于 
      The ISA tuning as it is today can not cope with all of the different
variations that are possible, so all we can do is a best attempt based on
the CPU family. The DSP and FPU generation are already at odds with each
other, and the nommu tuning we weren't handling at all.  Additionally,
for platforms that never had an FPU, the -nofpu variant never existed,
meaning that we would lose out on family granular tuning completely in
certain cases.

With tat out of the way, we were also using -up versions, allowing for
later instructions that branched off of a particular subset of the ISA,
but are not actually reflected on the hardware being targetted. This
leads to some confusion, and the possibility of bogus instructions on
older parts. Kill that off and lock it down to the family being built
for specifically.
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      b2d86a3f
    • P
      sh: sh7785lcr: Select uImage as default image target. · 1a306032
      由 Paul Mundt 提交于 
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      1a306032
    • P
      sh: Fix FPU tuning on toolchains with mismatched multilib targets. · 8a2fd5f3
      由 Paul Mundt 提交于 
      Presently there is very little standing in the way of using an SH-4
toolchain for building an SH-2 kernel, and vice versa. Binutils itself
has no limitations whatsoever and supports explicit ISA hinting, which
we already use with varying degrees of success today.

This leaves GCC as the odd one out, due to a rather dubious policy
decision by the GCC folks to not include all of the CPU family variants
in the default list of multilib targets in GCC4. Despite best efforts to
the contrary, libgcc itself already contains awareness of the various CPU
types and remains generally usable, allowing it to safely be referenced
even on a mismatched target (and indeed, explicit ISA tuning by binutils
keeps us honest in terms of ensuring that we do not link incompatible
objects in).

In order to support this, a couple of changes had to be made. Firstly,
the introduction of MAYBE_DECLARE_EXPORT(), which provides a __weak
extern reference for libgcc resident routines when finer-grained
-m<cpu-family> based tuning is not supported by the toolchain. This
fixes up the __sdivsi3_i4i and __udivsi3_i4i references when dealing
with SH-2 kernels linked with an SH-4 libgcc. Secondly, in case where we
are unable to find a suitable match for CPU family tuning but still
have a toolchain that defaults to FP instruction generation, a suitable
nofpu target must be selected. This is accomplished by selecting the
first nofpu multilib target supported by the toolchain, which is
also necessary for selecting the proper libgcc to link against.
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      8a2fd5f3
  35. 20 10月, 2008 1 次提交
  37. 12 9月, 2008 1 次提交
  39. 02 8月, 2008 2 次提交
    • A
      sh: fix LIBGCC · 49de935c
      由 Adrian Bunk 提交于 
      Commit f15cbe6f
(sh: migrate to arch/sh/include/) moved KBUILD_CFLAGS
(which is used by LIBGCC) below LIBGCC, causing build
errors like the following:

<--  snip  -->

...
  LD      .tmp_vmlinux1
arch/sh/kernel/built-in.o: In function `module_clk_recalc':
clock-sh4.c:(.text+0x80f0): undefined reference to `__udivsi3_i4i'
...
make[1]: *** [.tmp_vmlinux1] Error 1

<--  snip  -->
Reported-by: NAdrian Bunk <bunk@kernel.org>
Signed-off-by: NAdrian Bunk <bunk@kernel.org>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      49de935c
    • P
      sh: Revert the location change of auto-generated asm/machtypes.h · 4385e12b
      由 Paul Mundt 提交于 
      This ended up causing build breakage on O= builds, as reported by Adrian:

<--  snip  -->

...
  CC      init/main.o
In file included from /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/sh/include/asm/irq.h:4,
                 from /home/bunk/linux/kernel-2.6/git/linux-2.6/include/linux/irq.h:23,
                 from /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/sh/include/asm/hardirq.h:5,
                 from /home/bunk/linux/kernel-2.6/git/linux-2.6/include/linux/hardirq.h:7,
                 from /home/bunk/linux/kernel-2.6/git/linux-2.6/include/asm-generic/local.h:5,
                 from /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/sh/include/asm/local.h:4,
                 from /home/bunk/linux/kernel-2.6/git/linux-2.6/include/linux/module.h:19,
                 from /home/bunk/linux/kernel-2.6/git/linux-2.6/init/main.c:13:
/home/bunk/linux/kernel-2.6/git/linux-2.6/arch/sh/include/asm/machvec.h:15:27:
error: asm/machtypes.h: No such file or directory
make[2]: *** [init/main.o] Error 1

<--  snip  -->

So we simply move machtypes.h back to its original place. asm-offsets.h is
still generated there regardless, until such a time that we find a better place
to stash auto-generated files.
Reported-by: NAdrian Bunk <bunk@kernel.org>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      4385e12b
  41. 30 7月, 2008 1 次提交
  43. 29 7月, 2008 6 次提交
  45. 28 7月, 2008 1 次提交