Nick Rees wrote:
>
> While I'm on it, I was using a PowerPC mvme2402 for some of these tests. I
> am running Tornado 2.0.2. Whenever the PPC reboots it spends ages doing
> apparently nothing (i.e. about 3 minutes) just before it prints out the
> Attaching TCP/IP and network interface messages (i.e. very eearly in the
> boot).
>
> Does anyone have any idea how to get rid of this. It does it twice, so
> waiting 5-6 minutes every boot is a bit of a bore.
Yes, reduce the size of any unnecessary memory areas defined in
sysPhysMemDesc[]. You may have added a large block for VME A32 space,
which will take the CPU a long time (and lots of memory, about 1K/MB IIRC)
to set up the page tables for. Use the sysBatDesc[] table instead for
large areas, but note that there are only 4 DBATs and they can only cover
a maximum of 256MB each, so you're limited to a 1GB address range. We
only put VME boards in the A32 range 0x80000000-0xbfffffff because of
this.
- Andrew
--
Perfection is reached, not when there is no longer anything to add,
but when there is no longer anything to take away.
- Antoine de Saint-Exupery
- Replies:
- Re: PowerPC woes john sinclair
- References:
- PowerPC woes Nick Rees
- Navigate by Date:
- Prev:
PowerPC woes Nick Rees
- Next:
Re: PowerPC woes john sinclair
- Index:
1994
1995
1996
1997
1998
1999
2000
<2001>
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
PowerPC woes Nick Rees
- Next:
Re: PowerPC woes john sinclair
- Index:
1994
1995
1996
1997
1998
1999
2000
<2001>
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|