| Age | Commit message (Collapse) | Author | Files | Lines |
|
The Analog Devices Blackfin port was added in 2007 and was rather
active for a while, but all work on it has come to a standstill
over time, as Analog have changed their product line-up.
Aaron Wu confirmed that the architecture port is no longer relevant,
and multiple people suggested removing blackfin independently because
of some of its oddities like a non-working SMP port, and the amount of
duplication between the chip variants, which cause extra work when
doing cross-architecture changes.
Link: https://docs.blackfin.uclinux.org/
Acked-by: Aaron Wu <[email protected]>
Acked-by: Bryan Wu <[email protected]>
Cc: Steven Miao <[email protected]>
Cc: Mike Frysinger <[email protected]>
Signed-off-by: Arnd Bergmann <[email protected]>
|
|
We have the build infrastructure to generate uImages so we should ignore
the resulting generated files.
Signed-off-by: Mark Brown <[email protected]>
Acked-by: Mike Frysinger <[email protected]>
|
|
rename vmImage to uImage
update blackfin targets name
Signed-off-by: Sonic Zhang <[email protected]>
Signed-off-by: Steven Miao <[email protected]>
|
|
All ARCHs have the same definition of MKIMAGE. Move it to Makefile.lib
to avoid duplication.
All ARCHs have similar definitions of cmd_uimage. Place a sufficiently
parameterized version in Makefile.lib to avoid duplication.
Signed-off-by: Stephen Warren <[email protected]>
Acked-by: Nicolas Pitre <[email protected]>
Tested-by: Mike Frysinger <[email protected]> [Blackfin]
Tested-by: Michal Simek <[email protected]> [Microblaze]
Tested-by: Guan Xuetao <[email protected]> [unicore32]
Signed-off-by: Michal Marek <[email protected]>
|
|
Encoding the cpu family name apparently confuses people when they try to
boot an image on a sub-variant, so encode the specific cpu name and the
silicon rev instead.
Signed-off-by: Mike Frysinger <[email protected]>
|
|
Signed-off-by: Mike Frysinger <[email protected]>
|
|
Signed-off-by: Barry Song <[email protected]>
Signed-off-by: Mike Frysinger <[email protected]>
|
|
This is useful for quick tests where networks are faster than compression,
and/or the compression code is broken.
Reported-by: Magnus Damm <[email protected]>
Signed-off-by: Mike Frysinger <[email protected]>
|
|
Replace the use of CROSS_COMPILE to select a customized
installkernel script with the possibility to set INSTALLKERNEL
to select a custom installkernel script when running make:
make INSTALLKERNEL=arm-installkernel install
With this patch we are now more consistent across
different architectures - they did not all support use
of CROSS_COMPILE.
The use of CROSS_COMPILE was a hack as this really belongs
to gcc/binutils and the installkernel script does not change
just because we change toolchain.
The use of CROSS_COMPILE caused troubles with an upcoming patch
that saves CROSS_COMPILE when a kernel is built - it would no
longer be installable.
[Thanks to Peter Z. for this hint]
This patch undos what Ian did in commit:
0f8e2d62fa04441cd12c08ce521e84e5bd3f8a46
("use ${CROSS_COMPILE}installkernel in arch/*/boot/install.sh")
The patch has been lightly tested on x86 only - but all changes
looks obvious.
Acked-by: Peter Zijlstra <[email protected]>
Acked-by: Mike Frysinger <[email protected]> [blackfin]
Acked-by: Russell King <[email protected]> [arm]
Acked-by: Paul Mundt <[email protected]> [sh]
Acked-by: "H. Peter Anvin" <[email protected]> [x86]
Cc: Ian Campbell <[email protected]>
Cc: Tony Luck <[email protected]> [ia64]
Cc: Fenghua Yu <[email protected]> [ia64]
Cc: Hirokazu Takata <[email protected]> [m32r]
Cc: Geert Uytterhoeven <[email protected]> [m68k]
Cc: Kyle McMartin <[email protected]> [parisc]
Cc: Benjamin Herrenschmidt <[email protected]> [powerpc]
Cc: Martin Schwidefsky <[email protected]> [s390]
Cc: Thomas Gleixner <[email protected]> [x86]
Cc: Ingo Molnar <[email protected]> [x86]
Signed-off-by: Sam Ravnborg <[email protected]>
|
|
Rather than use "Linux" in the boot image name (as this is redundant --
the image type is already set to "linux"), use the CPU name. This makes
it fairly obvious when a wrong image is accidentally booted. Otherwise
there is no kernel output and you waste time scratching your head
wondering wtf just happened.
Signed-off-by: Robin Getz <[email protected]>
Signed-off-by: Mike Frysinger <[email protected]>
|
|
Since U-Boot can support these compression types, add appropriate targets
to the Blackfin boot files.
Signed-off-by: Mike Frysinger <[email protected]>
|
|
Convert a few echos in the build system to new $(kecho) so we get correct
output according to build verbosity.
Signed-off-by: Mike Frysinger <[email protected]>
[sam: added kecho in a few more places for O=... builds]
Signed-off-by: Sam Ravnborg <[email protected]>
|
|
Signed-off-by: Mike Frysinger <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Bryan Wu <[email protected]>
|
|
Signed-off-by: Mike Frysinger <[email protected]>
Signed-off-by: Bryan Wu <[email protected]>
|
|
extract the entry point from the linked kernel rather than
assuming entry point == load address
Signed-off-by: Bryan Wu <[email protected]>
|
|
This adds support for the Analog Devices Blackfin processor architecture, and
currently supports the BF533, BF532, BF531, BF537, BF536, BF534, and BF561
(Dual Core) devices, with a variety of development platforms including those
avaliable from Analog Devices (BF533-EZKit, BF533-STAMP, BF537-STAMP,
BF561-EZKIT), and Bluetechnix! Tinyboards.
The Blackfin architecture was jointly developed by Intel and Analog Devices
Inc. (ADI) as the Micro Signal Architecture (MSA) core and introduced it in
December of 2000. Since then ADI has put this core into its Blackfin
processor family of devices. The Blackfin core has the advantages of a clean,
orthogonal,RISC-like microprocessor instruction set. It combines a dual-MAC
(Multiply/Accumulate), state-of-the-art signal processing engine and
single-instruction, multiple-data (SIMD) multimedia capabilities into a single
instruction-set architecture.
The Blackfin architecture, including the instruction set, is described by the
ADSP-BF53x/BF56x Blackfin Processor Programming Reference
http://blackfin.uclinux.org/gf/download/frsrelease/29/2549/Blackfin_PRM.pdf
The Blackfin processor is already supported by major releases of gcc, and
there are binary and source rpms/tarballs for many architectures at:
http://blackfin.uclinux.org/gf/project/toolchain/frs There is complete
documentation, including "getting started" guides available at:
http://docs.blackfin.uclinux.org/ which provides links to the sources and
patches you will need in order to set up a cross-compiling environment for
bfin-linux-uclibc
This patch, as well as the other patches (toolchain, distribution,
uClibc) are actively supported by Analog Devices Inc, at:
http://blackfin.uclinux.org/
We have tested this on LTP, and our test plan (including pass/fails) can
be found at:
http://docs.blackfin.uclinux.org/doku.php?id=testing_the_linux_kernel
[[email protected]: balance parenthesis in blackfin header files]
Signed-off-by: Bryan Wu <[email protected]>
Signed-off-by: Mariusz Kozlowski <[email protected]>
Signed-off-by: Aubrey Li <[email protected]>
Signed-off-by: Jie Zhang <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
|