u-boot.git/microblaze_config.mk, branch master Unnamed repository; edit this file 'description' to name the repository. Move architecture specific config.mk files into subdirs 2009-07-20T22:12:35+00:00 Peter Tyser ptyser@xes-inc.com 2009-07-10T16:03:15+00:00 b220c64d86f7c705a183302c3b50076d7e5d876c This cleans up U-Boot's toplevel directory a bit and makes the architecture 'config.mk' file naming and location similar to board and cpu 'config.mk' files Signed-off-by: Peter Tyser <ptyser@xes-inc.com> 
This cleans up U-Boot's toplevel directory a bit and makes the
architecture 'config.mk' file naming and location similar to board
and cpu 'config.mk' files

Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
push CROSS_COMPILE out to $(ARCH)_config.mk 2009-07-19T19:36:11+00:00 Mike Frysinger vapier@gentoo.org 2009-06-15T03:33:14+00:00 1ea6bcd8590b3ff9fe2bfbb0eb29a3b0edaa9460 Each arch should handle setting a proper default CROSS_COMPILE value in their own config.mk file rather than having to maintain a large ugly list in the Makefile. By using conditional assignment, we don't have to worry about the variable already being set (env/cmdline/etc...). The common config.mk file takes care of exporting CROSS_COMPILE already, and while a few variables (toolchain ones) utilize CROSS_COMPILE before including the arch config.mk, they do so with deferred assignment. Signed-off-by: Mike Frysinger <vapier@gentoo.org> 
Each arch should handle setting a proper default CROSS_COMPILE value in
their own config.mk file rather than having to maintain a large ugly list
in the Makefile.  By using conditional assignment, we don't have to worry
about the variable already being set (env/cmdline/etc...).

The common config.mk file takes care of exporting CROSS_COMPILE already,
and while a few variables (toolchain ones) utilize CROSS_COMPILE before
including the arch config.mk, they do so with deferred assignment.

Signed-off-by: Mike Frysinger <vapier@gentoo.org>
microblaze: clean microblaze_config.mk 2008-04-08T13:38:15+00:00 Michal Simek monstr@monstr.eu 2008-03-28T10:58:45+00:00 62032deb7214c6d9b4396297e2aaa559bc2f8495 FLAGS are generated by U-BOOT generator. Board specific FLAGS are in board directory Signed-off-by: Michal Simek <monstr@monstr.eu> 
FLAGS are generated by U-BOOT generator.
Board specific FLAGS are in board directory

Signed-off-by: Michal Simek <monstr@monstr.eu>
[Microblaze][PATCH] part 2 2007-03-11T12:48:24+00:00 Michal Simek monstr@monstr.eu 2007-03-11T12:48:24+00:00 cfc67116a706fd18b8f6a9c11a16753c5626d689 timer support interrupt controller support flash support ethernet support cache support board information support env support booting image support adding support for Xilinx ML401 
timer support
interrupt controller support
flash support
ethernet support
cache support
board information support
env support
booting image support

adding support for Xilinx ML401
Patches by Yasushi Shoji, 29 Jun 2004: 2004-07-10T23:48:41+00:00 wdenk wdenk 2004-07-10T23:48:41+00:00 857cad37a41c431582a74be56f858ee0476cd0d9 - add empty include/asm-microblaze/processor.h - add to CREDITS and MAINTAINERS - add gd initialization - add MicroBlaze and SUZAKU board to MAKEALL script - add reset support for SUZAKU - add flush_cache() for MicroBlaze - add CFG_FLASH_SIZE to include/configs/suzaku.h since we have fixed size flash memory on SUZAKU 
- add empty include/asm-microblaze/processor.h
- add to CREDITS and MAINTAINERS
- add gd initialization
- add MicroBlaze and SUZAKU board to MAKEALL script
- add reset support for SUZAKU
- add flush_cache() for MicroBlaze
- add CFG_FLASH_SIZE to include/configs/suzaku.h since we have fixed
  size flash memory on SUZAKU
* Patch by Yasushi Shoji, 07 Apr 2004: 2004-04-18T21:13:41+00:00 wdenk wdenk 2004-04-18T21:13:41+00:00 507bbe3e8084a82c20399367801da87db7d14e65 - add support for microblaze processors - add support for AtmarkTechno "suzaku" board 
  - add support for microblaze processors
  - add support for AtmarkTechno "suzaku" board