Uniden Data 2000 Wireless CDPD PC Card Guía de usuario descargar pdf (Pagina 19)

The reason for the probe is to identify interrupts which appear to be free (i.e., are not reserved by any other

Linux device driver), yet are either not physically wired to the host controller, or are connected to another

device that does not have a driver.

In the system log, a successful probe might look like:

Intel PCIC probe:

TI 1130 CardBus at mem 0x10211000, 2 sockets

...

ISA irqs (scanned) = 5,7,9,10 status change on irq 10

There are two ways to proceed:

• The interrupt probe can be restricted to a list of interrupts using the irq_list parameter for the

socket drivers. For example, ``irq_list=5,9,10'' would limit the scan to three interrupts. All

PCMCIA devices will be restricted to using these interrupts (assuming they pass the probe). You may

need to use trial and error to find out which interrupts can be safely probed.

• The interrupt probe can be disabled entirely by loading the socket driver with the ``do_scan=0''

option. In this case, a default interrupt list will be used, which avoids interrupts already allocated for

other devices.

In either case, the probe options can be specified using the PCIC_OPTS definition in the PCMCIA startup

script, for example:

PCIC_OPTS="irq_list=5,9,10"

It should be noted that /proc/interrupts is completely useless when it comes to diagnosing interrupt

probe problems. The probe is sensible enough to never attempt to use an interrupt that is already in use by

another Linux driver. So, the PCMCIA drivers are already using all the information in

/proc/interrupts. Depending on system design, an inactive device can still occupy an interrupt and

cause trouble if it is probed for PCMCIA.

3.4 IO port scan failures

Symptoms:

• The system locks up when cardmgr is first started, even with no cards present.

• The system log shows a successful host controller probe, including interrupt probe results, but does

not show IO probe results.

• In some cases, the IO probe will succeed, but report large numbers of random exclusions.

When cardmgr processes IO port ranges listed in /etc/pcmcia/config.opts, the kernel probes

these ranges to detect latent devices that occupy IO space but are not associated with a Linux driver. The

Linux PCMCIA HOWTO

3.4 IO port scan failures 16

1 2 ... 14 15 16 17 18 19 20 21 22 23 24 ... 55 56

Sin comentarios

Uniden Data 2000 Wireless CDPD PC Card Guía de usuario Pagina 19