From: Russell King <rmk@arm.linux.org.uk>
To: CaT <cat@zip.com.au>
Cc: dahinds@users.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: 2.5.64 - xircom realport no workie well
Date: Thu, 6 Mar 2003 14:09:45 +0000 [thread overview]
Message-ID: <20030306140945.B838@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030306134746.GE464@zip.com.au>; from cat@zip.com.au on Fri, Mar 07, 2003 at 12:47:46AM +1100
On Fri, Mar 07, 2003 at 12:47:46AM +1100, CaT wrote:
> On Thu, Mar 06, 2003 at 01:29:04PM +0000, Russell King wrote:
> > Can you check whether the attached patch fixes this for you? It's more
>
> Started compiling it and it just bombed out:
>
> drivers/serial/8250_pci.c:1920: `PCI_DEVICE_ID_XIRCOM_RBM56G' undeclared
> here (not in a function)
> drivers/serial/8250_pci.c:1920: initializer element is not constant
> drivers/serial/8250_pci.c:1920: (near initialization for
> `serial_pci_tbl[86].device')
Bah. You need this as well then:
--- orig/include/linux/pci_ids.h Wed Mar 5 19:51:58 2003
+++ linux/include/linux/pci_ids.h Wed Mar 5 09:58:27 2003
@@ -1235,6 +1235,7 @@
#define PCI_VENDOR_ID_XIRCOM 0x115d
#define PCI_DEVICE_ID_XIRCOM_X3201_ETH 0x0003
+#define PCI_DEVICE_ID_XIRCOM_RBM56G 0x0101
#define PCI_DEVICE_ID_XIRCOM_X3201_MDM 0x0103
#define PCI_VENDOR_ID_RENDITION 0x1163
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-03-06 13:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 13:03 2.5.64 - xircom realport no workie well CaT
2003-03-06 13:29 ` Russell King
2003-03-06 13:47 ` CaT
2003-03-06 14:09 ` Russell King [this message]
2003-03-06 15:20 ` CaT
2003-03-06 15:36 ` Russell King
2003-03-06 23:29 ` CaT
2003-03-07 7:44 ` 2.5.64p5 No USB support when APIC mode enabled Meino Christian Cramer
2003-03-07 12:52 ` Alan Cox
2003-03-07 13:37 ` Meino Christian Cramer
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=20030306140945.B838@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=cat@zip.com.au \
--cc=dahinds@users.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).