URL
https://opencores.org/ocsvn/or1k/or1k/trunk
Subversion Repositories or1k
[/] [or1k/] [trunk/] [rc203soc/] [sw/] [uClinux/] [include/] [asm-sparc/] [memreg.h] - Rev 1772
Go to most recent revision | Compare with Previous | Blame | View Log
/* $Id: memreg.h,v 1.1 2005-12-20 11:32:11 jcastillo Exp $ */ #ifndef _SPARC_MEMREG_H #define _SPARC_MEMREG_H /* memreg.h: Definitions of the values found in the synchronous * and asynchronous memory error registers when a fault * occurs on the sun4c. * * Copyright (C) 1995 David S. Miller (davem@caip.rutgers.edu) */ /* First the synchronous error codes, these are usually just * normal page faults. */ #define SUN4C_SYNC_WDRESET 0x0001 /* watchdog reset */ #define SUN4C_SYNC_SIZE 0x0002 /* bad access size? whuz this? */ #define SUN4C_SYNC_PARITY 0x0008 /* bad ram chips caused a parity error */ #define SUN4C_SYNC_SBUS 0x0010 /* the SBUS had some problems... */ #define SUN4C_SYNC_NOMEM 0x0020 /* translation to non-existent ram */ #define SUN4C_SYNC_PROT 0x0040 /* access violated pte protections */ #define SUN4C_SYNC_NPRESENT 0x0080 /* pte said that page was not present */ #define SUN4C_SYNC_BADWRITE 0x8000 /* while writing something went bogus */ #define SUN4C_SYNC_BOLIXED \ (SUN4C_SYNC_WDRESET | SUN4C_SYNC_SIZE | SUN4C_SYNC_SBUS | \ SUN4C_SYNC_NOMEM | SUN4C_SYNC_PARITY) /* Now the asynchronous error codes, these are almost always produced * by the cache writing things back to memory and getting a bad translation. * Bad DVMA transactions can cause these faults too. */ #define SUN4C_ASYNC_BADDVMA 0x0010 /* error during DVMA access */ #define SUN4C_ASYNC_NOMEM 0x0020 /* write back pointed to bad phys addr */ #define SUN4C_ASYNC_BADWB 0x0080 /* write back points to non-present page */ #endif /* !(_SPARC_MEMREG_H) */
Go to most recent revision | Compare with Previous | Blame | View Log