patch: Documentation/pci.txt

Bret Indrelee (bindrelee@sbs-cp.com)
Wed, 3 Nov 1999 14:09:01 -0600


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01BF2637.4512F260
Content-Type: text/plain;
charset="iso-8859-1"

Attached.

Hopefully M$ OuchLook will not screw up the attachment, let me know if there
are any problems.

-Bret

-------------------------------------------------------------
SBS Technologies, Connectivity Products
... solutions for real-time connectivity

Bret Indrelee, Engineer
SBS Technologies, Inc., Connectivity Products
1284 Corporate Center Drive, St. Paul MN 55121
Direct: (651) 905-4731
Main: (651) 905-4700 Fax: (651) 905-4701
E-mail: bindrelee@sbs-cp.com http://www.sbs.com
-------------------------------------------------------------

------_=_NextPart_000_01BF2637.4512F260
Content-Type: text/plain;
name="patch-pci.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="patch-pci.txt"

--- linux-2.3.24/Documentation/pci.txt Fri Oct 15 20:55:26 1999=0A=
+++ linux/Documentation/pci.txt Wed Nov 3 14:49:16 1999=0A=
@@ -73,6 +73,25 @@=0A=
config space. You should use the values in the pci_dev structure as =
they might=0A=
have been remapped by the kernel.=0A=
=0A=
+ You still need to use the check_region(), request_region() and=0A=
+release_region() routines for PCI I/O space and check_mem_region(),=0A=
+request_mem_region() and release_mem_region() for PCI memory space.=0A=
+=0A=
+ Once you have the regions allocated, you use ioremap() to create=0A=
+a cookie, passing in the proper base_address[] from the struct =
pci_dev.=0A=
+This cookie is passed to the readb(), readw(), readl(), writeb(), =0A=
+writew(), and writel() routines when accessing PCI space. You must=0A=
+always use these routines when accessing PCI space from the kernel.=0A=
+Not all architechures allow memory-mapped access to PCI memory from=0A=
+the kernel.=0A=
+=0A=
+ DMA device drivers should review the IO-mapping.txt file for=0A=
+information about converting between the various address spaces.=0A=
+=0A=
+ PCI interrupt routines are always SA_SHIRQ and should use the=0A=
+(struct pci_dev *) dev->irq field for the interrupt number passed=0A=
+into request_irq().=0A=
+=0A=
5. Other interesting functions=0A=
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~=0A=
pci_find_slot() Find pci_dev corresponding to given bus and=0A=

------_=_NextPart_000_01BF2637.4512F260--

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/