FYI: here is the quick description of the various HP models supported under
Utah BSD (PAC/VAC refer to physically and virtually addressed external
caches).

This may be useful for deciphering the hp300 code (note that net2 doesn't have
the 68040 stuff).  In rough order of introduction:

320:	16Mhz 68020 CPU + 16Mhz 68881 FPU + HP proprietary MMU + 16k VAC.
350:	25Mhz 68020 + 20Mhz 68881 + HP MMU + 32k VAC.
330:	16Mhz 68020 + 16Mhz 68881 + ??Mhz 68851 Motorola MMU.
318/319: 16Mhz 68020 + 16Mhz 68881 + ??Mhz 68851 Motorola MMU.
370:	33Mhz 68030 (includes MMU) + 33Mhz 68882 FPU + 64k PAC.
360:	25Mhz 68030 + 25Mhz 68882.
340:	16Mhz 68030 + 16Mhz 68882.
375:	50Mhz 68030 + 50Mhz 68882 + 32k PAC.
345:	50Mhz 68030 + 50Mhz 68882 + 32k PAC.
380/425: 25Mhz 68040 (includes FPU and MMU).
433:	33Mhz 68040 (includes FPU and MMU).

Kernel config "cpu" types (ifdefs):

HP320:	Includes HP MMU, old 16-bit only DMA, VAC support.
HP330:	Motorola 68851 MMU support.
HP350:	Always together with 320 except with newer 32-bit DMA support.
HP360:	Together with 330 for MMU support (68030 MMU is subset of 68851).
HP370:	Always together with 360 except for additional PAC support.
HP380:	68040 support.

HP330 should be defined for 318/319 support.
HP370 should be defined for 345/375 support.
HP380 should be defined for 425/433 support.

On the 320/350 VACs you can separately flush the supervisor and user "sides"
of the cache, hence the 'U' in things like "DCIU".

BTW: "cachctl" is an HP-UX originated call, I take no responsibility for the
interface :-)

------------------------------------------------------------------------------