Subject: Re: memecc.c ambiguity?
To: None <>
From: John E. Krokes <>
List: port-sparc
Date: 02/11/2003 13:24:25
> memecc_error() reads, in part,
>         printf("\taddress: 0x%x%x\n", efar0 & ECC_AFR_PAH, efar1);
> Surely that sbould be 0x%x%08x?  Otherwise (for example) a failure at
> PA 0x102030405 will print as 0x12030405.  Confusing at best (though
> not, strictly, ambiguous, since ECC_AFR_PAH is only one nibble wide and
> thus the first %x will always generate exactly one digit - does anyone
> have a NetBSD SPARC with enough RAM for the PAH bits to be nonzero?).

How much RAM would that be? I have an SS20 with 320mb and another with 512mb,
both running NetBSD 1.6.