to 1, hold on tight to your hat, and call recycle. The reason is
that we might pick up extra references such as from lookup and we
don't really care about tracking those. For example with p2k,
puffs in the kernel already does all the refcounting we could ever
dream of, and therefore it's left to the client and unnecessary.
just options CPU_IN_CKSUM.
Include std.arm in all arm platform std files.
This should reenable the asm in_cksum code for all arm platforms.
Also remove the now unused in_cksum_arm.S.
in a manner that is endianness independant.
Should mean the amd64 will return correct offsets > 2^32 (sparc64 had a
special define).
Any new netbsd32 ports should work regardless of the endianness.
needed to keep track of the kernel process that opened a device in
order to close it with the right credentials. Flash forward to today
where curlwp is now quite sufficient.
in-kernel priority is used. Reported by <drochner>.
Minor fixes for scheduling calls to conform the POSIX:
- If pid is equal to zero, use the calling process;
- In case of permission problem, return EPERM instead of EACESS;
- sched_setscheduler() should return previously used policy;
- pthread_* calls should return the error code or zero;
Should fix the namespace problems (and builds of some packages):
- Move cpuset_t defintion from pset.h to sched.h;
- Remove the #include of pset.h in pthread.h;
use "-march=r3900" for CPUFLAGS in TX3912 and TX3922.
The "-mips2" option seems to imply "-mdivide-traps" and
gcc4 with the option generates "teq" instruction on division ops,
but teq is not supported by TX39xx CPUs.
The problem is reported and the fix (-mdevide-breaks) is
provided by Risto Sainio. Tested on his PenCentra 200,
and also tested on Telios HC-AJ2 by nakayama@.
This should be pulled up to netbsd-4.
- also stop DMA in mec_reset() before resetting chip
- set MAC address to MAC_STATION reg in mec_attach(), not in mec_reset()
Possibly fixes occasional interrupt storm from mec(4) (i.e. hangup) at boot.
an 'ssize_t' or 'long' variable to 'register_t'.
If the sizes were different it would either overwrite stack or return
uninitialised stack. On big-endian systems things would be worse!
