The following line in cpu/ppc4xx/start.S:
mtsprtsr,r1/* clear all timer exception status */
has the effect of clearing WRS, making it impossible for a watchdog device
driver (such as Linux's booke-wdt) to later check those bits to determine
whether a reset occurred. I assume
-off-by: Mike Nuss <[EMAIL PROTECTED]>
Cc: Stefan Roese <[EMAIL PROTECTED]>
diff --git a/cpu/ppc4xx/cpu_init.c b/cpu/ppc4xx/cpu_init.c
index 2e0dd6f..14682c6 100644
--- a/cpu/ppc4xx/cpu_init.c
+++ b/cpu/ppc4xx/cpu_init.c
@@ -99,10 +99,21 @@ DECLARE_GLOBAL_DATA_PTR;
# e
The option CONFIG_I2C_MULTI_BUS does not have any effect on Sequoia, the
PPC440EPx reference platform, because IIC1 is never enabled. Add Sequoia board
code to turn on IIC1 if CONFIG_I2C_MULTI_BUS is selected.
Signed-off-by: Mike Nuss <[EMAIL PROTECTED]>
Cc: Stefan Roese <[EMAIL PROTECTE
Stefan Roese wrote:
> Hi Mike,
>
> sorry for the late response.
No problem.
> I think it makes sense to move these PLL checking/reconfiguration
stuff
> into a
> separate function. Perhaps like this:
(snip)
> I think this is clearer. What do you think? Please clean up and
resend.
I agree. I'll
and PLB frequency of 166MHz, without the need for an
external EEPROM.
Signed-off-by: Mike Nuss <[EMAIL PROTECTED]>
Cc: Stefan Roese <[EMAIL PROTECTED]>
--
Sorry for the duplicate - updated the patch description.
Addresses changes suggested by Stefan; move PLL reconfiguration int
-off-by: Mike Nuss <[EMAIL PROTECTED]>
Cc: Stefan Roese <[EMAIL PROTECTED]>
--
Addresses changes suggested by Stefan; move PLL reconfiguration into a separate
function.
diff --git a/cpu/ppc4xx/cpu_init.c b/cpu/ppc4xx/cpu_init.c
index 2e0dd6f..fd663af 100644
--- a/cpu/ppc4xx/cpu_init
Matthias Fuchs wrote:
>
> Hi Mike,
>
> don't you think this is a little bit to shortsighted?
> There are many other parameters beyond the CPU clock that could be
> modified in such a way. We have some code in the PMC440 board
> code that sets up the PCI sync clock dynamically dependant on
> a GP
Larry Johnson wrote:
>
> Hi Stefan and group,
>
> When I was checking the LM75/AD7414 driver using my Sequoia board, I
> found that the AD7414 on the Sequoia does not appear to update its
> temperature as its documentation describes. I had to reset U-Boot to
> get the temperature reading to chan
I'm using a PPC440EPx with a Marvell PHY (same as on Sequoia). If I connect to
a PC with a crossover Ethernet cable, U-Boot sees a link but the PC does not.
The PC (running Linux) reports "Autonegotiation failed (remote fault)" and
ethtool reports no link.
However if I let the PowerPC boot up i
Stefan Roese wrote:
> On Monday 03 March 2008, Mike Nuss wrote:
> > I'm using a PPC440EPx with a Marvell PHY (same as on
> Sequoia). If I connect
> > to a PC with a crossover Ethernet cable, U-Boot sees a link
> but the PC does
> > not. The PC (running Linux)
Wolfgang Denk wrote:
> It seems every now and then a report pops up that the Sequoia board
> (or now on equivalent hardware) has problems connecting to a Gigabit
> capable network interface. In our case, it's when the Sequoia is
> attached to a HP Procurve switch.
There were differences i
ausing the issue, but I removed T4 also, to match up with Linux.
Signed-off-by: Mike Nuss <[EMAIL PROTECTED]>
diff --git a/cpu/ppc4xx/miiphy.c b/cpu/ppc4xx/miiphy.c
index 4216f0b..f48e68d 100644
--- a/cpu/ppc4xx/miiphy.c
+++ b/cpu/ppc4xx/miiphy.c
@@ -143,7 +143,7 @@ int phy_setup_aneg (char *d
Stefan wrote:
> >
> > At this point all possibilities are on the table and I'm
> looking for any
> > input from anyone with experience (good, bad, or whatever) with this
> > processor and/or designs similar to the Sequoia.
>
> If you scan the U-Boot mailing list for 440EPx/Denali DDR2
> problems
13 matches
Mail list logo
