20 Feb, 2014
3 commits
-
Now we are ready to switch over to real Kbuild.
This commit disables temporary scripts:
scripts/{Makefile.build.tmp, Makefile.host.tmp}
and enables real Kbuild scripts:
scripts/{Makefile.build,Makefile.host,Makefile.lib}.This switch is triggered by the line in scripts/Kbuild.include
-build := -f $(if $(KBUILD_SRC),$(srctree)/)scripts/Makefile.build.tmp obj
+build := -f $(if $(KBUILD_SRC),$(srctree)/)scripts/Makefile.build objWe need to adjust some build scripts for U-Boot.
But smaller amount of modification is preferable.Additionally, we need to fix compiler flags which are
locally added or removed.In Kbuild, it is not allowed to change CFLAGS locally.
Instead, ccflags-y, asflags-y, cppflags-y,
CFLAGS_$(basetarget).o, CFLAGS_REMOVE_$(basetarget).o
are prepared for that purpose.Signed-off-by: Masahiro Yamada
Tested-by: Gerhard Sittig -
This commit changes the working directory
where the build process occurs.Before this commit, build process occurred under the source
tree for both in-tree and out-of-tree build.That's why we needed to add $(obj) prefix to all generated
files in makefiles like follows:
$(obj)u-boot.bin: $(obj)u-bootHere, $(obj) is empty for in-tree build, whereas it points
to the output directory for out-of-tree build.And our old build system changes the current working directory
with "make -C " syntax when descending into the
sub-directories.On the other hand, Kbuild uses a different idea
to handle out-of-tree build and directory descending.The build process of Kbuild always occurs under the output tree.
When "O=dir/to/store/output/files" is given, the build system
changes the current working directory to that directory and
restarts the make.Kbuild uses "make -f $(srctree)/scripts/Makefile.build obj="
syntax for descending into sub-directories.
(We can write it like "make $(obj)=" with a shorthand.)
This means the current working directory is always the top
of the output directory.Signed-off-by: Masahiro Yamada
Tested-by: Gerhard Sittig -
This commit moves suffix rules from config.mk
to scripts/Makefile.build, which will allow us
to switch smoothly to real Kbuild.Note1:
post/lib_powerpc/fpu/Makefile has
its own rule to compile C sources.
We need to tweak it to keep the same behavior.Note2:
There are two file2 with the same name:
arch/arm/lib/crt0.S and eamples/api/crt0.S.
To keep the same build behavior,
examples/api/Makefile also has to be treaked.Signed-off-by: Masahiro Yamada
16 Dec, 2013
1 commit
-
Convert like follows:
CPU mpc83xx -> CONFIG_MPC83xx
CPU mpc85xx -> CONFIG_MPC85xx
CPU mpc86xx -> CONFIG_MPC86xx
CPU mpc5xxx -> CONFIG_MPC5xxx
CPU mpc8xx -> CONFIG_8xx
CPU mpc8260 -> CONFIG_8260
CPU ppc4xx -> CONFIG_4xx
CPU x86 -> CONFIG_X86
ARCH x86 -> CONFIG_X86
ARCH powerpc -> CONFIG_PPCSigned-off-by: Masahiro Yamada
13 Dec, 2013
1 commit
-
All objects under post/ directory are enabled by CONFIG_HAS_POST.
(post/tests.o is enabled by CONFIG_POST_STD_LIST.
But CONFIG_POST_STD_LIST depends on CONFIG_HAS_POST.)We can move CONFIG_HAS_POST switch to the top Makefile.
Signed-off-by: Masahiro Yamada
25 Nov, 2013
1 commit
-
Signed-off-by: Masahiro Yamada
01 Nov, 2013
1 commit
-
This commit also deletes post/rules.mk,
which in not necessary any more.Signed-off-by: Masahiro Yamada
15 Oct, 2013
1 commit
-
Signed-off-by: Wolfgang Denk
[trini: Drop changes for PEP 4 following python tools]
Signed-off-by: Tom Rini
20 Sep, 2013
1 commit
-
Fix various misspellings of things like "environment", "kernel",
"default" and "volatile", and throw in a couple grammar fixes.Signed-off-by: Robert P. J. Day
24 Jul, 2013
1 commit
-
Signed-off-by: Wolfgang Denk
[trini: Fixup common/cmd_io.c]
Signed-off-by: Tom Rini
01 May, 2013
1 commit
-
Devices in CONFIG_SYS_POST_I2C_IGNORES list may be absent
and the rule is not to report I2C POST failure for devices
in this list. Currently this doesn't work since probing for
these devices isn't done and thus they are not marked as
successfully probed. Ignore optional devices when checking
for devices that didn't respond.Signed-off-by: Anatolij Gustschin
29 Oct, 2012
1 commit
-
These boards have long reached EOL, and there has been no indication
of any active users of such hardware for years. Get rid of the dead
weight.Signed-off-by: Wolfgang Denk
Cc: Wolfgang Grandegger
16 Oct, 2012
1 commit
-
Remove the parts depending either on disabled CONFIG_SERIAL_MULTI
or ifdefs around CONFIG_SERIAL_MULTI parts since CONFIG_SERIAL_MULTI
is now enabled by default.Signed-off-by: Marek Vasut
Cc: Marek Vasut
Cc: Tom Rini
Cc: Anatolij Gustschin
Cc: Stefan Roese
31 Mar, 2012
1 commit
-
Since commit 96f5c4b the needed functions (get_ticks() and get_tbclk() )
are defined for kirkwood CPUs as well. This warning is then not relevant
anymore.Signed-off-by: Valentin Longchamp
cc: Holger Brunck
cc: Prafulla Wadaskar
cc: Albert Aribaud
19 Mar, 2012
3 commits
-
These calls should not be made directly any more, since bootstage
will call the show_boot_...() functions as needed.Signed-off-by: Simon Glass
-
Signed-off-by: Simon Glass
-
Rather than the caller negating our progress numbers to indicate an
error has occurred, which seems hacky, add a function to indicate this.Signed-off-by: Simon Glass
Acked-by: Mike Frysinger
12 Mar, 2012
1 commit
-
This reverts commit 3e16abe0e468c568b30acb7d8583e3dbed6f177b.
The logic of this patch is broken - testing for CONFIG_SYS_POST_FPU in
the Makefile cannot work, as this is only a bit that may (or may not)
be set in the CONFIG_POST variable.The patch cases build errors on a number of boards, so we revert it.
Signed-off-by: Wolfgang Denk
13 Feb, 2012
1 commit
-
Signed-off-by: Mike Frysinger
14 Jan, 2012
1 commit
-
Signed-off-by: Kumar Gala
24 Dec, 2011
4 commits
-
The code and comment disagreed: the comment claimed that r6...r31
were copied, and consequently the arrays for "src" and "dst" were
declared with 26 entries, but the actual code ("lmw r5,0(r3)" and
"stmw r5,0(r4)") copied _27_ words (r5 through r31), which resulted
in false "POST cpu Error at multi test" messages.Fix the comment and the array sizes.
Signed-off-by: Wolfgang Denk
Cc: Anatolij Gustschin
Cc: Stefan Roese
Cc: Kumar Gala
Cc: Kim Phillips
Cc: Andy Fleming
Acked-by: Anatolij Gustschin
Tested-by: Anatolij Gustschin -
Clean up and document the code:
- get rid of unneeded code block
- add comment which code is generatedSigned-off-by: Wolfgang Denk
Cc: Anatolij Gustschin
Cc: Stefan Roese
Cc: Kumar Gala
Cc: Kim Phillips
Cc: Andy Fleming
Acked-by: Anatolij Gustschin -
Signed-off-by: Wolfgang Denk
Cc: Anatolij Gustschin
Cc: Stefan Roese
Cc: Kumar Gala
Cc: Kim Phillips
Cc: Andy Fleming
Acked-by: Anatolij Gustschin -
It appears that with recent versions of GCC the explicit
"-mhard-float" command line option takes precedence over the
``asm(".gnu_attribute 4, 2");'' in the source file, so this no longer
helps to avoid the warnings we get when linking code that uses FP
instructions with other code that was built using soft-float.We can remove the ".gnu_attribute" (which appears to carry no other
information, at least so far) from the object files, but we also have
to make sure we don't pull in the __gcc_qsub() and __gcc_qmul()
functions from the standard libgcc, as these would again "infect" our
linking. We copy this code from:
gcc-4.2.2/gcc/config/rs6000/darwin-ldouble.c
This old version was chosen because it was still available under a
compatible license (GCC v2+). The file was stripped down to the
needed parts, and reformatted so it passes checkpatch with only one
warning (do not add new typedefs).Signed-off-by: Wolfgang Denk
Cc: Kumar Gala
Cc: Stefan Roese
Cc: Andy Fleming
Cc: Kim Phillips
Tested-by: Stefan Roese
Tested-by: Anatolij Gustschin
11 Dec, 2011
2 commits
-
commit f31a911fe (arm, post: add missing post_time_ms for arm)
enables get_ticks and get_tbclk for all arm based boards,
but kirkwood has currently no implementation for this. So
undefine this for kirkwood boards.Signed-off-by: Holger Brunck
cc: Heiko Schocher
cc: Prafulla Wadaskar
cc: Valentin Longchamp -
Signed-off-by: Christian Riesch
Cc: Tom Rini
Cc: Heiko Schocher
Cc: Wolfgang Denk
02 Dec, 2011
1 commit
-
Fix:
gdc.c: In function 'gdc_test_reg_one':
gdc.c:66:6: warning: variable 'ret' set but not used
[-Wunused-but-set-variable]Signed-off-by: Wolfgang Denk
Cc: Stefan Roese
Acked-by: Stefan Roese
17 Nov, 2011
1 commit
-
Fix:
20001122-1.c: In function 'fpu_post_test_math1':
20001122-1.c:37:22: warning: variable 'p' set but not used [-Wunused-but-set-variable]Signed-off-by: Stefan Roese
04 Nov, 2011
2 commits
-
Fix:
post.c: In function 'post_log':
post.c:425:7: warning: variable 'i' set but not used
[-Wunused-but-set-variable]Signed-off-by: Wolfgang Denk
-
Make checkpatch-clean..
Signed-off-by: Wolfgang Denk
Acked-by: Marek Vasut
28 Oct, 2011
2 commits
-
Signed-off-by: Heiko Schocher
Cc: Albert ARIBAUD -
Signed-off-by: Heiko Schocher
24 Oct, 2011
1 commit
-
commit 8d3fcb5e60b6c8e1d530dbc2e2e33ec6a44670da breaks post
memory support for sdram base != 0x00000000. Fix this.Signed-off-by: Heiko Schocher
Cc: Valentin Longchamp
Cc: Holger Brunck
Acked-by: Mike Frysinger
06 Oct, 2011
4 commits
-
This test is similar to the actual POST memory test but quicker and
far less complete. It checks the address and data lines and then only
tests some regularly placed sub regions of the RAM.
This can be useful when we want to test the RAM but we do not have enough
time to run the full memory test.The POST memory test code was rearranged in order to avoid code duplication
between the two tests but the memory test functionnality remains the same.Signed-off-by: Valentin Longchamp
Signed-off-by: Holger Brunck
Ackey-by: Mike Frysinger -
This is needed for a further patch adding a new memory test.
Signed-off-by: Valentin Longchamp
Acked-by: Mike Frysinger -
Some boards have the environment variables defined in a slow EEPROM. post_run
accesses these environment variables to define which tests have to be run (in
post_get_flags). This is very slow before the code relocation on some boards
with a slow I2C EEPROM for environement variables.This patch adds a config option to skip the fetching of the test flags in the
environment variables. The test flags assigned to the tests then only are the
ones statically defined for the test in post/tests.c.Signed-off-by: Valentin Longchamp
Signed-off-by: Holger Brunck -
The current post_log_word in global data is currently split into 2x
16 bits: half for the test start, half for the test success.
Since we alredy have more than 16 POST tests defined and more could
be defined, this may result in an overflow and the post_output_backlog
would not work for the tests defined further of these 16 positions.An additional field is added to global data so that we can now support up
to 32 (depending of architecture) tests. The post_log_word is only used
to record the start of the test and the new field post_log_res for the
test success (or failure). The post_output_backlog is for this change
also adapted.Signed-off-by: Valentin Longchamp
30 Sep, 2011
1 commit
-
Make it easy for any Blackfin board to enable led/push button tests.
Signed-off-by: Mike Frysinger
28 Jul, 2011
2 commits
-
change bd->bi_memsize to gd->ram_size, as this is defined
on all archs, so this post test can used on none powerpc
archs too.Signed-off-by: Heiko Schocher
cc: Wolfgang Denk
cc: Mike Frysinger -
Signed-off-by: Heiko Schocher