a HAVE_GCC28 check-variable that can now be used to add other gcc-2.8
flags in cases where they may be useful, or to remove gcc 2.7.2 "bug
workaround" flags.)
By not doing so, a very obscure bug followed where the config search
stuff stopped at the bridge (pceb) and didn't even call match for the
two Qlogic ISP cards that followed.
locore.s:
- cpu_switch "returns" to proc_trampoline after cpu_fork. cpu_switch is
called with an argument, remove it from the stack when not compiled
with -DMRTD.
- use KENTRY instead of ENTRY for all functions called from C.
- when calling C code, don't clean up the stack when compiled with -DMRTD.
- need to split fusubail into fubail and subail, because fu and su
take different number of arguments.
machdep.c:
- set sf_p when dumping
- new function do_softclock (that just calls softclock) because softclock
doesn't take an argument.
mainbus.c:
- establish softclock interrupt to call do_softclock
trap.c:
- trap() and syscall() allways use std C calling conventions.
- need to split fusubail into fubail and subail, because fu and su
take different number of arguments.
- make child_return take only one argument like the other functions
"called" via cpu_set_kpc.
vm_machdep.c:
- set sf_p in cpu_fork.
up on systems that have Zorro I/O space allocated outside the Z2 I/O
region, and then only if kvm usage is high enough to begin allocating
pages already mapped for hardware mappings. Found and fixed by Niklas
Hallqvist on OpenBSD.
From niklas@cvs.openbsd.org:
Yay! This fixes a bug that has been there since day one of the amiga port.
We have never protected the kvm area that maps Zorro I/O registers in the
Z2 memory space from being allocated by the kmem_* routines. Lately kvm
usage has increased and we have needed more kvm allocated than earlier thus
this area have got allocated with random results. Most often resulting in
MMU fault panics, but also in hangs. This bug has stalled the amiga port
release builds for several weeks, but now I *hope* the amiga will have a
chance to be built and tested in time for 2.3.
* In the bus tag structure, keep a reference to the parent bus.
* Express all bus space methods as inline functions in stead of macros
and use the parent bus tag reference to find the nearest "upstream"
bus that implements the method.
already in progress (as is done in the suspend case). Suggested
by Soren S. Jorvang in PR 5246, but diff in that PR cleaned up so
it'd still work right when debugging printfs were enabled.
scottr