Remove trailing whitespace and fix a typo.

This commit is contained in:
wiz 2011-12-05 10:36:39 +00:00
parent 6533efb150
commit a4d43dc119

View File

@ -1,4 +1,4 @@
.\" $NetBSD: mppb.4,v 1.3 2011/12/03 23:09:42 rkujawa Exp $ .\" $NetBSD: mppb.4,v 1.4 2011/12/05 10:36:39 wiz Exp $
.\" .\"
.\" Copyright (c) 2011 The NetBSD Foundation, Inc. .\" Copyright (c) 2011 The NetBSD Foundation, Inc.
.\" All rights reserved. .\" All rights reserved.
@ -52,7 +52,7 @@ Matay Prometheus. Manufacturer 44359, product 1.
.Sh DIAGNOSTICS .Sh DIAGNOSTICS
.Bl -diag .Bl -diag
.It Unable to allocate space in parent map. .It Unable to allocate space in parent map.
The kernel has ran out of virtual memory space. The kernel has run out of virtual memory space.
.El .El
.Sh SEE ALSO .Sh SEE ALSO
.Xr pci 4 .Xr pci 4
@ -71,16 +71,16 @@ driver was written by
The hardware does not support DMA to host memory. The hardware does not support DMA to host memory.
.Pp .Pp
The Prometheus does not support repeating of PCI transations, instead if the The Prometheus does not support repeating of PCI transations, instead if the
PCI card demands a retry of transaction, it returns value 0xFFFFFFFF. PCI card demands a retry of transaction, it returns value 0xFFFFFFFF.
This is currently not handled by the This is currently not handled by the
.Nm .Nm
driver and will confuse some PCI card drivers. driver and will confuse some PCI card drivers.
.Pp .Pp
The system may run out of kernel virtual memory space if Prometheus is present. The system may run out of kernel virtual memory space if Prometheus is present.
This is due to fact that m68k-specific This is due to fact that m68k-specific
.Xr pmap 9 .Xr pmap 9
code places User Page Table base address at statically defined address code places User Page Table base address at statically defined address
0x10000000, which does not leave enough kernel space to fit a 512MB board, such 0x10000000, which does not leave enough kernel space to fit a 512MB board, such
as the Prometheus. as the Prometheus.
It is possible to work around this problem, by moving User Page Table base It is possible to work around this problem, by moving User Page Table base
to higher address. to higher address.