Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 25 12月, 2008 1 次提交
    • M
      [S390] arch_setup_additional_pages arguments · fc5243d9
      由 Martin Schwidefsky 提交于 
      arch_setup_additional_pages currently gets two arguments, the binary
format descripton and an indication if the process uses an executable
stack or not. The second argument is not used by anybody, it could
be removed without replacement.

What actually does make sense is to pass an indication if the process
uses the elf interpreter or not. The glibc code will not use anything
from the vdso if the process does not use the dynamic linker, so for
statically linked binaries the architecture backend can choose not
to map the vdso.
Acked-by: NIngo Molnar <mingo@elte.hu>
Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      fc5243d9
  3. 16 12月, 2008 1 次提交
  5. 13 11月, 2008 5 次提交
  7. 12 11月, 2008 2 次提交
  9. 10 11月, 2008 1 次提交
  11. 31 10月, 2008 6 次提交
  13. 28 10月, 2008 6 次提交
    • P
      sh: Kill off long-dead HD64465 cchip support. · 3eeebf17
      由 Paul Mundt 提交于 
      This code has been dead for many years. The last update it received
was in 2003 in order to update it for the driver model changes, though
it had already been in disarray and unused before that point. The only
boards that ever used this chip have not had users in many years either,
so it is finally safe to just kill it off and move on with life.
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      3eeebf17
    • 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: Add on-chip RTC support for SH7722. · b4d36a25
      由 Paul Mundt 提交于 
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      b4d36a25
    • K
      sh: Provide a sample defconfig for the UL2 (SH7366) board. · e00afb64
      由 Kuninori Morimoto 提交于 
      Signed-off-by: NKuninori Morimoto <morimoto.kuninori@renesas.com>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      e00afb64
    • 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
  15. 27 10月, 2008 1 次提交
  17. 23 10月, 2008 3 次提交
  19. 22 10月, 2008 4 次提交
  21. 21 10月, 2008 10 次提交