From: Mark S. Mathews <hidden> Date: 2000-05-30 15:11:31
Hi,
I just noticed the following snippet in rpx_cfg() :
iic_read(0xa8, eebuf, 0, 128);
iic_read(0xa8, &eebuf[128], 128, 128);
{
int i;
cp = (u_char *)0xfa000000;
for (i=0; i<256; i++)
*cp++ = eebuf[i];
}
It appears to be copying the eeprom data to NVRAM. Is anyone using this?
Can I safely take it out? We have RPX boards that don't have NVRAM and
this seems a little pointless.
I'm in the process of changing head.S and embed_config.c to work with the
new EP bootloader.
-Mark
Mark S. Mathews
AbsoluteValue Systems Web: http://www.absoval.com
P.O. Box 941149 e-mail: mark@absoval.com
Maitland, FL 32794-1149 Phone: 407.644.8582
USA Fax: 407.539.1294
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
From: Matthew Locke <hidden> Date: 2000-05-30 16:03:01
I'm in the process of changing head.S and embed_config.c to work with the
new EP bootloader.
Why? You don't need to change anything. There are two configuration
variables in the eeprom that need to be set.
SYPCR needs to be set to turn the watchdog off. Can't remember the value and
I don't have the docs in front of me.
NVRAM needs to be set to non-zero, even if the board doesn't have any nvram.
I don't think this info was sent to the beta-testers, sorry.
Matt
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
From: Dan Malek <hidden> Date: 2000-05-30 16:22:07
"Mark S. Mathews" wrote:
It appears to be copying the eeprom data to NVRAM. Is anyone using this?
No, get rid of it. It is some forgotten debug code from long ago.
I'll remove it from all of the sources I can find.
Sorry about that. Thanks for pointing it out.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
From: Mark S. Mathews <hidden> Date: 2000-05-30 16:30:42
On Tue, 30 May 2000, Matthew Locke wrote:
quoted
I'm in the process of changing head.S and embed_config.c to work with the
new EP bootloader.
Why? You don't need to change anything. There are two configuration
variables in the eeprom that need to be set.
Why? the HZ key is no longer present and the value of the SB key is now
baud instead of baud/100.
Additionally, based on my read of the bootldr docs, EP (you? ;-) is trying
to set things up so that (in the future) they can change the contents or
format of the eeprom without warning. Therefore, the bootldr does a
'conversion' of the eeprom data to the RPXU key=value similar format and
writes it to dpram.
I get the sense that the keys and value formats won't change whereas the
contents of eeprom might be changed in the future.
SYPCR needs to be set to turn the watchdog off. Can't remember the value
and I don't have the docs in front of me.
I'm using 0xffffff89
NVRAM needs to be set to
non-zero, even if the board doesn't have any nvram.
I'm using a 'no-nvram' rpxlite and I have NVRam set to zero. Works just
fine. Is this an issue with the bootldr or with what Linux wants from
eeprom?
-Mark
Mark S. Mathews
AbsoluteValue Systems Web: http://www.absoval.com
P.O. Box 941149 e-mail: mark@absoval.com
Maitland, FL 32794-1149 Phone: 407.644.8582
USA Fax: 407.539.1294
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
From: Mark S. Mathews <hidden> Date: 2000-05-30 16:34:34
Thanks Dan, I'm using ffffff89, don't think that last bit matters much
since SW is turned off anyway.
;-)
BTW: I'll send the mods to head.S and embed_config.c later today, once I'm
sure they work.
Thanks,
-Mark
On Tue, 30 May 2000, Dan Malek wrote:
Matthew Locke wrote:
quoted
SYPCR needs to be set to turn the watchdog off. Can't remember the value and
I don't have the docs in front of me.
0xffffff88
-- Dan
Mark S. Mathews
AbsoluteValue Systems Web: http://www.absoval.com
P.O. Box 941149 e-mail: mark@absoval.com
Maitland, FL 32794-1149 Phone: 407.644.8582
USA Fax: 407.539.1294
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/