u-boot.git/arch/powerpc/cpu/ppc4xx/cpu_init.c, branch master

powerpc: remove 4xx support

2017-07-03T21:35:28+00:00

There was for long time no activity in the 4xx area.
We need to go further and convert to Kconfig, but it
turned out, nobody is interested anymore in 4xx,
so remove it.

Signed-off-by: Heiko Schocher

powerpc: Drop unused code related to generic board

2016-05-27T19:39:54+00:00

Since generic board init is enabled, this is not used. Drop it.

Signed-off-by: Simon Glass

powerpc: ppc4xx: canyonlands: Move to generic board

2015-02-12T17:35:30+00:00

Switch to generic board so that this board will not be broken/removed.

Signed-off-by: Simon Glass

ppc: Fix ppc4xx CONFIG_SYS_GENERIC_BOARD

2014-11-05T09:23:50+00:00

I realized that with v2014.10 u-boot is not starting up on
ppc4xx boards with CONFIG_SYS_GENERIC_BOARD set.

I bisected it down to this:
d54d7eb support blackfin board initialization in generic board_f

With
d29437a ppc: Make ppc4xx ready for CONFIG_SYS_GENERIC_BOARD
I set gd to a defined value for ppc4xx in cpu_init_f().
I did not realize that the gd struct has also to be memset()
to zero at this point.

But at least commit d54d7eb assumes it is:
@@ -516,11 +528,13 @@ static int reserve_malloc(void)
 /* (permanently) allocate a Board Info struct */
 static int reserve_board(void)
 {
-	gd->start_addr_sp -= sizeof(bd_t);
-	gd->bd = (bd_t *)map_sysmem(gd->start_addr_sp, sizeof(bd_t));
-	memset(gd->bd, '\0', sizeof(bd_t));
-	debug("Reserving %zu Bytes for Board Info at: %08lx\n",
-			sizeof(bd_t), gd->start_addr_sp);
+	if (!gd->bd) {
+		gd->start_addr_sp -= sizeof(bd_t);
+		gd->bd = (bd_t *)map_sysmem(gd->start_addr_sp, sizeof(bd_t));
+		memset(gd->bd, '\0', sizeof(bd_t));
+		debug("Reserving %zu Bytes for Board Info at: %08lx\n",
+		      sizeof(bd_t), gd->start_addr_sp);
+	}
 	return 0;
 }
 #endif

This might also be an issue on other architectures, so maintainers should
check.

Signed-off-by: Dirk Eibach 
Signed-off-by: Stefan Roese

powerpc: ppc4xx: remove board support for bluestone

2014-10-10T13:44:43+00:00

This board has been orphaned for more than 6 months.

It is the last board defining CONFIG_APM821XX.
The code inside #ifdef CONFIG_APM821XX should be removed too.

Signed-off-by: Masahiro Yamada

ppc: Make ppc4xx ready for CONFIG_SYS_GENERIC_BOARD

2014-07-25T08:55:49+00:00

The generic board  infrastructure assumes that gd is set by
arch code.

Signed-off-by: Dirk Eibach 
Signed-off-by: Stefan Roese

ppc4xx: Remove support for PPC405CR CPUs

2013-08-20T15:35:24+00:00

This patch removes support for the APM 405CR CPU.
This CPU is EOL and no board uses this chip.

Signed-off-by: Matthias Fuchs

Add GPL-2.0+ SPDX-License-Identifier to source files

2013-07-24T13:44:38+00:00

Signed-off-by: Wolfgang Denk 
[trini: Fixup common/cmd_io.c]
Signed-off-by: Tom Rini

PPC405EX CHIP_21 erratum

2011-05-12T14:10:51+00:00

APM errata CHIP_21 for the 405EX/EXr (from the rev 1.09 document dated
4/27/11) states that rev D processors may wake up with the wrong feature
set.  This patch implements the APM-proposed workaround.

To enable this patch for your board, add the appropriate define for your
CPU to your board header file.  See kilauea.h for more information.  The
following variants are supported:

#define CONFIG_SYS_4xx_CHIP_21_405EX_NO_SECURITY
#define CONFIG_SYS_4xx_CHIP_21_405EX_SECURITY
#define CONFIG_SYS_4xx_CHIP_21_405EXr_NO_SECURITY
#define CONFIG_SYS_4xx_CHIP_21_405EXr_SECURITY

Please note that if you select the wrong define, your board will not
boot, and JTAG will be required to recover.

Tested on custom boards using:

CONFIG_SYS_4xx_CHIP_21_405EX_NO_SECURITY  
CONFIG_SYS_4xx_CHIP_21_405EX_SECURITY     

Signed-off-by: Steve Falco 
Acked-by: Dirk Eibach 
Signed-off-by: Stefan Roese

ppc4xx: Change tsr/tcr macros to upper case

2010-10-20T08:07:55+00:00

Remove uneccessary functions to access the TCR/TSR registers as well.

Signed-off-by: Stefan Roese