- Oct 15, 2011
-
-
Mike Frysinger authored
The top level Makefile does not do any recursion into subdirs when cleaning, so these clean/distclean targets in random arch/board dirs never get used. Punt them all. MAKEALL didn't report any errors related to this that I could see. Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
- Jun 03, 2011
-
-
Mike Frysinger authored
Now that the zlib code has been relocated to a dedicated subdir, make sure we still build it with -O2 for boards that want speed over size. Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
- Apr 08, 2011
-
-
Mike Frysinger authored
This is a revert of 821ad16f as Wolfgang doesn't like the new code. Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
Mike Frysinger authored
Unify this convention for all Blackfin boards. Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
Mike Frysinger authored
We don't want/use this value for Blackfin boards, so punt it and have the common code error out when people try to use it. Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
- Nov 17, 2010
-
-
Sebastien Carlier authored
Before this commit, weak symbols were not overridden by non-weak symbols found in archive libraries when linking with recent versions of binutils. As stated in the System V ABI, "the link editor does not extract archive members to resolve undefined weak symbols". This commit changes all Makefiles to use partial linking (ld -r) instead of creating library archives, which forces all symbols to participate in linking, allowing non-weak symbols to override weak symbols as intended. This approach is also used by Linux, from which the gmake function cmd_link_o_target (defined in config.mk and used in all Makefiles) is inspired. The name of each former library archive is preserved except for extensions which change from ".a" to ".o". This commit updates references accordingly where needed, in particular in some linker scripts. This commit reveals board configurations that exclude some features but include source files that depend these disabled features in the build, resulting in undefined symbols. Known such cases include: - disabling CMD_NET but not CMD_NFS; - enabling CONFIG_OF_LIBFDT but not CONFIG_QE. Signed-off-by:
Sebastien Carlier <sebastien.carlier@gmail.com>
-
- Oct 18, 2010
-
-
Wolfgang Denk authored
The change is currently needed to be able to remove the board configuration scripting from the top level Makefile and replace it by a simple, table driven script. Moving this configuration setting into the "CONFIG_*" name space is also desirable because it is needed if we ever should move forward to a Kconfig driven configuration system. Signed-off-by:
Wolfgang Denk <wd@denx.de>
-
- Oct 02, 2010
-
-
Mike Frysinger authored
The CONFIG_BFIN_CPU option is largely used in the build system, so move it out of the board config.h and into the board config.mk. It'd be nice to keep everything in the config.h, but the patch to extract that value early was rejected. Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
- Apr 13, 2010
-
-
Peter Tyser authored
Now that the other architecture-specific lib directories have been moved out of the top-level directory there's not much reason to have the '_generic' suffix on the common lib directory. Signed-off-by:
Peter Tyser <ptyser@xes-inc.com>
-
Peter Tyser authored
Previously, a specific file or directory could be compiled with custom CFLAGS by adding a Makefile variable such as: CFLAGS_dlmalloc.o = <custom flags for common/dlmalloc.c> or CFLAGS_lib = <custom flags for lib directory> This method breaks down once multiple files or directories share the same path. Eg FLAGS_fileA = <custom flags> would incorrectly result in both dir1/fileA.c and dir2/fileA.c being compiled with <custom flags>. This change allows finer grained control which we need once we move lib_$ARCH to arch/$ARCH/lib/ and lib_generic/ to lib/. Without this change all lib/ directories would share the same custom CFLAGS. Signed-off-by:
Peter Tyser <ptyser@xes-inc.com>
-
- Jan 17, 2010
-
-
Mike Frysinger authored
While the initdram() function makes sense on some arches, it doesn't for Blackfin systems as it's always implemented the same way. Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
- Oct 05, 2009
-
-
Ben Warren authored
All in-tree boards that use this controller have CONFIG_NET_MULTI added Also: - changed CONFIG_DRIVER_SMC91111 to CONFIG_SMC91111 - cleaned up line lengths - modified all boards that override weak function in this driver - modified all eeprom standalone apps to work with new driver - updated blackfin standalone EEPROM app after testing Signed-off-by:
Ben Warren <biggerbadderben@gmail.com> Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
- Jun 15, 2009
-
-
Mike Frysinger authored
Building the compression code in lib_generic/ with -O2 rather than -Os gives a nice speed boost without too much code size increase. Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
Mike Frysinger authored
All the Blackfin linker scripts were duplicated across the board dirs with no difference save from the semi-often used ENV_IS_EMBEDDED option. So unify all of them in the lib_blackfin/ dir and for the few boards that need to embedded the environment directly, add a LDS_BOARD_TEXT define for them to customize via their board config file. This is much simpler than forcing them to duplicate the rest of the linker script. Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
- May 06, 2009
-
-
Mike Frysinger authored
When dropping jump block support, the assumption was that all bootroms supported entry point redirection via the EVT1 register. Unfortunately, this turned out to be incorrect for the oldest Blackfin parts (BF533-0.2 and older and BF561). No one really noticed earlier because these parts usually are booted by bypassing the bootrom entirely, and older BF533 parts are not supported at all (too many anomalies). Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
- Mar 23, 2009
-
-
Mike Frysinger authored
The Boot ROM uses EVT1 as the entry point so set that rather than having to use a tiny jump block in the default EVT1 location. Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
- Jan 28, 2009
-
-
Mike Frysinger authored
Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
Mike Frysinger authored
The DEBUG code in initdram() is quite old and was never really useful, so just drop it altogether. Common Blackfin debug code does a better job. Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
- Jan 07, 2009
-
-
Mike Frysinger authored
Many of the Blackfin board linker scripts are preprocessed, so make sure we output the linker script into the build tree rather than the source tree. Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
Mike Frysinger authored
Make sure all .text sections get pulled in and the entry point is properly referenced so they don't get discarded when linking with --gc-sections. Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
Mike Frysinger authored
In order to boot an LDR out of parallel flash, the ldr utility needs a few flags to tell it to generate the right header. Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
- Oct 23, 2008
-
-
Mike Frysinger authored
Common Blackfin code already announces CPU information. Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
Mike Frysinger authored
The USB/LAN register settings are not actually used/needed in order to drive things from U-Boot, so drop the code. Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
Mike Frysinger authored
Make sure that the start.o object is always the first object in our linker script regardless of configuration settings, and add some linker symbols so the ldr utility can properly locate the initcode when generating a LDR. Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
- Oct 18, 2008
-
-
Jean-Christophe PLAGNIOL-VILLARD authored
Signed-off-by:
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
-
- Sep 10, 2008
-
-
Jean-Christophe PLAGNIOL-VILLARD authored
Signed-off-by:
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
-
- Jul 02, 2008
-
-
Wolfgang Denk authored
Signed-off-by:
Wolfgang Denk <wd@denx.de>
-
- Jun 12, 2008
-
-
Becky Bruce authored
This patch changes the return type of initdram() from long int to phys_size_t. This is required for a couple of reasons: long int limits the amount of dram to 2GB, and u-boot in general is moving over to phys_size_t to represent the size of physical memory. phys_size_t is defined as an unsigned long on almost all current platforms. This patch *only* changes the return type of the initdram function (in include/common.h, as well as in each board's implementation of initdram). It does not actually modify the code inside the function on any of the platforms; platforms which wish to support more than 2GB of DRAM will need to modify their initdram() function code. Build tested with MAKEALL for ppc, arm, mips, mips-el. Booted on powerpc MPC8641HPCN. Signed-off-by:
Becky Bruce <becky.bruce@freescale.com>
-
- Mar 30, 2008
-
-
Mike Frysinger authored
All of the duplicated code for Blackfin processors and boot modes have been unified. After all, the core is the same for all processors, just the peripheral set differs (which gets handled in the drivers). Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
- Feb 05, 2008
-
-
Mike Frysinger authored
Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
Mike Frysinger authored
Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
- Sep 15, 2007
-
-
Wolfgang Denk authored
Signed-off-by:
Wolfgang Denk <wd@denx.de>
-
- Apr 05, 2007
-
-
Aubrey Li authored
-
- Mar 20, 2007
-
-
Aubrey Li authored
-