Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

New sentence, new line. Remove another esl(4) reference.

This commit is contained in:
wiz 2009-01-03 18:27:36 +00:00
parent 238aa4a6a2
commit 5eea853f3e
1 changed files with 24 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

41
share/man/man4/pcmcia.4
View File

@ -1,4 +1,4 @@
.\" $NetBSD: pcmcia.4,v 1.35 2009/01/03 17:44:20 christos Exp $
.\" $NetBSD: pcmcia.4,v 1.36 2009/01/03 18:27:36 wiz Exp $
.\"
.\" Copyright (c) 1999, 2002 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -140,7 +140,6 @@ Cypress/ScanLogic SL811HS USB Host Controller driver.
.Xr cnw 4 ,
.Xr com 4 ,
.Xr ep 4 ,
.Xr esl 4 ,
.Xr esp 4 ,
.Xr intro 4 ,
.Xr isa 4 ,
@ -172,11 +171,14 @@ probes the
IO bus width and uses that information to decide
where to map
.Tn PCMCIA
IO space. For 10-bit wide cards, 0x300-0x3ff is
used. For 12-bit wide cards, 0x400-0x4ff is used.
IO space.
For 10-bit wide cards, 0x300-0x3ff is used.
For 12-bit wide cards, 0x400-0x4ff is used.
.Pp
Neither choice is perfect. In the 12-bit case, 0x400 appears to work
on substantially more devices than 0x300. In the event that
Neither choice is perfect.
In the 12-bit case, 0x400 appears to work
in substantially more devices than 0x300.
In the event that
.Tn PCMCIA
devices are mapped in 0x400-0x4ff and appear to be nonfunctional,
remapping to 0x300-0x3ff may be appropriate; consult
@ -196,31 +198,36 @@ options PCIC_ISA_ALLOC_IOSIZE=0x0ff
.Nx
attempts to probe for available interrupts to assign to
.Tn PCMCIA
devices. In some cases, it is not possible to detect
devices.
In some cases, it is not possible to detect
all interrupts in use; in such cases, use of
.Cd options PCIC_ISA_INTR_ALLOC_MASK
may be necessary. See
may be necessary.
See
.Xr options 4 .
.Ss Unconfigured devices
During autoconfiguration, if a message is displayed saying that your card
is "not configured" it indicates that there isn't support for your card
compiled into the kernel. To fix this problem, it may simply be a matter
compiled into the kernel.
To fix this problem, it may simply be a matter
of adding the manufacturer and product IDs to the
.Tn PCMCIA
database or adding a front-end attachment to an existing driver. In
the latter case, it is normally always necessary to get a dump of the
CIS table from the card. You can do this by adding
database or adding a front-end attachment to an existing driver.
In the latter case, it is normally always necessary to get a dump
of the CIS table from the card.
You can do this by adding
.Cd options PCMCIACISDEBUG
and
.Cd options PCMCIADEBUG
into your kernel config file. Additionally, you will have to patch the
kernel to enable run-time debugging. This can be done in the source
by changing the variables
into your kernel config file.
Additionally, you will have to patch the kernel to enable run-time
debugging.
This can be done in the source by changing the variables
.Va pcmcia_debug
and
.Va pcmciacis_debug
to 0xff. Alternatively, you can patch the same variables at run-time
using
to 0xff.
Alternatively, you can patch the same variables at run-time using
.Xr ddb 4 .
For most drivers you should also consider enabling any driver-specific
debugging options.