Searched hist:151891 (Results 1 - 4 of 4) sorted by relevance

/freebsd-9.3-release/sys/powerpc/aim/
H A Dlocore.Sdiff 151891 Sun Oct 30 19:29:59 MST 2005 grehan Copy SPRG0-3 registers at boot-time and restore when calling into
OpenFirmware. FreeBSD/ppc uses SPRG0 as the per-cpu data area pointer,
and SPRG1-3 as temporary registers during exception handling. There
have been a few instances where OpenFirmware does require these to
be part of it's context, such as cd-booting an eMac.

reported by: many
MFC after: 3 days
H A Dlocore32.Sdiff 151891 Sun Oct 30 19:29:59 MST 2005 grehan Copy SPRG0-3 registers at boot-time and restore when calling into
OpenFirmware. FreeBSD/ppc uses SPRG0 as the per-cpu data area pointer,
and SPRG1-3 as temporary registers during exception handling. There
have been a few instances where OpenFirmware does require these to
be part of it's context, such as cd-booting an eMac.

reported by: many
MFC after: 3 days
H A Dlocore64.Sdiff 151891 Sun Oct 30 19:29:59 MST 2005 grehan Copy SPRG0-3 registers at boot-time and restore when calling into
OpenFirmware. FreeBSD/ppc uses SPRG0 as the per-cpu data area pointer,
and SPRG1-3 as temporary registers during exception handling. There
have been a few instances where OpenFirmware does require these to
be part of it's context, such as cd-booting an eMac.

reported by: many
MFC after: 3 days
/freebsd-9.3-release/sys/powerpc/ofw/
H A Dofw_machdep.cdiff 151891 Sun Oct 30 19:29:59 MST 2005 grehan Copy SPRG0-3 registers at boot-time and restore when calling into
OpenFirmware. FreeBSD/ppc uses SPRG0 as the per-cpu data area pointer,
and SPRG1-3 as temporary registers during exception handling. There
have been a few instances where OpenFirmware does require these to
be part of it's context, such as cd-booting an eMac.

reported by: many
MFC after: 3 days

Completed in 88 milliseconds