From: Andrey Panin <pazke@orbita1.ru>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] pci: make pci_direct_conf1 structure nonstatic
Date: Tue, 4 Feb 2003 11:45:26 +0300 [thread overview]
Message-ID: <20030204084526.GA361@pazke> (raw)
[-- Attachment #1: Type: text/plain, Size: 509 bytes --]
Hi,
this triial patch is needed to use pci access functions from
i386/pci/direct.c by the visws pci code. To achieve this patch
makes pci_direct_conf1 structure (which hold pci pointers of access
functions) nonstatic. PCI id for SGI lithium hostbridge is added also.
SGI visws supports pci type 1 pci access, but needs different
bus and irq enumeration logic.
Please consider applying.
Best regards.
--
Andrey Panin | Embedded systems software developer
pazke@orbita1.ru | PGP key: wwwkeys.pgp.net
[-- Attachment #2: patch-pci --]
[-- Type: text/plain, Size: 926 bytes --]
diff -urN -X /usr/share/dontdiff linux-2.5.59.vanilla/arch/i386/pci/direct.c linux-2.5.59/arch/i386/pci/direct.c
--- linux-2.5.59.vanilla/arch/i386/pci/direct.c Wed Jan 15 20:37:20 2003
+++ linux-2.5.59/arch/i386/pci/direct.c Mon Feb 3 15:55:11 2003
@@ -83,7 +83,7 @@
PCI_FUNC(devfn), where, size, value);
}
-static struct pci_ops pci_direct_conf1 = {
+struct pci_ops pci_direct_conf1 = {
.read = pci_conf1_read,
.write = pci_conf1_write,
};
diff -urN -X /usr/share/dontdiff linux-2.5.59.vanilla/include/linux/pci_ids.h linux-2.5.59/include/linux/pci_ids.h
--- linux-2.5.59.vanilla/include/linux/pci_ids.h Wed Jan 15 20:28:37 2003
+++ linux-2.5.59/include/linux/pci_ids.h Mon Feb 3 15:55:12 2003
@@ -844,6 +844,7 @@
#define PCI_VENDOR_ID_SGI 0x10a9
#define PCI_DEVICE_ID_SGI_IOC3 0x0003
+#define PCI_VENDOR_ID_SGI_LITHIUM 0x1002
#define PCI_VENDOR_ID_ACC 0x10aa
#define PCI_DEVICE_ID_ACC_2056 0x0000
next reply other threads:[~2003-02-04 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 8:45 Andrey Panin [this message]
2003-02-04 8:59 ` [PATCH] pci: make pci_direct_conf1 structure nonstatic Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030204084526.GA361@pazke \
--to=pazke@orbita1.ru \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.