Why two pci_attach_device() calls?

QNX Newsgroups (Archives) qdn.public.qnxrtp.os
1

In the description of the pci_attach_device() call, the second example
shows two calls to this function. My system crashes when I make the
first call as shown. Another example in the Article “Talking to hardware
under QNX Neutrino” shows only one call.

Also, do we reallt pass the info member info.CpuBaseAddress[0]? What are
the macros PCI_MEM_ADDR, etc. for?

–

John H. Zouck
The Johns Hopkins University
Applied Physics Laboratory

2

Previously, John H. Zouck wrote in qdn.public.qnxrtp.os:

In the description of the pci_attach_device() call, the second example
shows two calls to this function. My system crashes when I make the
first call as shown. Another example in the Article “Talking to hardware
under QNX Neutrino” shows only one call.

The output from ‘pci -v’ will help, as well as the device and vendor that
you are trying to attach to.

Also, do we reallt pass the info member info.CpuBaseAddress[0]? What are
the macros PCI_MEM_ADDR, etc. for?

Some CPUs (non-x86) have different CPU and PCI addresses and that is the
reason for having the CpuBaseAddress member.

–

John H. Zouck
The Johns Hopkins University
Applied Physics Laboratory


\

–

Hugh Brown (613) 591-0931 ext. 209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8