Scott Long 50736a153b Fix a problem with tag->boundary inheritence that has existed since day one ... and was propagated to nearly every platform. The boundary of the child needs to consider the boundary of the parent and pick the minimum of the two, not the maximum. However, if either is 0 then pick the appropriate one. This bug was exposed by a recent change to ATA, which should now be fixed by this change. The alignment and maxsegsz tag attributes likely also need a similar review in the near future. This is a MT5 candidate. Reviewed by: marcel Submitted by: sos (in part)		2004-09-08 04:54:19 +00:00
..
aim	Refactor a bunch of scheduler code to give basically the same behaviour	2004-09-05 02:09:54 +00:00
compile
conf	Always compile PFIL_HOOKS into the kernel and remove the associated kernel	2004-08-27 15:16:24 +00:00
include	Move the kernel-specific logic to adjust frompc from MI to MD. For	2004-08-27 19:42:35 +00:00
ofw	Instead of "OpenFirmware", "openfirmware", etc. use the official spelling	2004-08-16 15:45:27 +00:00
powermac	Instead of "OpenFirmware", "openfirmware", etc. use the official spelling	2004-08-16 15:45:27 +00:00
powerpc	Fix a problem with tag->boundary inheritence that has existed since day one	2004-09-08 04:54:19 +00:00
psim	- Use the rman_get_* functions instead of reaching into struct resource.	2004-08-11 21:09:40 +00:00