From: Thomas Richter <thor@math.TU-Berlin.DE>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, marcelo.tosatti@cyclades.com
Subject: Re: [PATCH] NetMOS 9805 ParPort interface
Date: Tue, 24 Aug 2004 12:52:14 +0200 (CEST) [thread overview]
Message-ID: <200408241052.MAA09594@cleopatra.math.tu-berlin.de> (raw)
In-Reply-To: <20040823113206.7ca77d79.akpm@osdl.org>
Hi Andrew, hi Marcelo,
sorry, my time is currently pretty limited.
So here we go:
i) Apply the following to drivers/parport_pc.c:
/* snip */
--- parport_pc.c.old Tue Aug 24 11:53:22 2004
+++ parport_pc.c Tue Aug 24 12:12:31 2004
@@ -2636,6 +2636,10 @@
netmos_9805,
netmos_9815,
netmos_9855,
+ netmos_9735,
+ netmos_9835,
+ netmos_9755,
+ netmos_9715
};
@@ -2709,6 +2713,10 @@
/* netmos_9805 */ { 1, { { 0, -1 }, } }, /* untested */
/* netmos_9815 */ { 2, { { 0, -1 }, { 2, -1 }, } }, /* untested */
/* netmos_9855 */ { 2, { { 0, -1 }, { 2, -1 }, } }, /* untested */
+ /* netmos_9735 */ { 1, { { 2, 3 }, } }, /* untested */
+ /* netmos_9835 */ { 1, { { 2, 3 }, } }, /* untested */
+ /* netmos_9755 */ { 2, { { 0, 1 }, { 2, 3 },} }, /* untested */
+ /* netmos_9715 */ { 2, { { 0, 1 }, { 2, 3 },} }, /* untested */
};
static struct pci_device_id parport_pc_pci_tbl[] = {
@@ -2786,6 +2794,14 @@
PCI_ANY_ID, PCI_ANY_ID, 0, 0, netmos_9815 },
{ PCI_VENDOR_ID_NETMOS, PCI_DEVICE_ID_NETMOS_9855,
PCI_ANY_ID, PCI_ANY_ID, 0, 0, netmos_9855 },
+ { PCI_VENDOR_ID_NETMOS, PCI_DEVICE_ID_NETMOS_9735,
+ PCI_ANY_ID, PCI_ANY_ID, 0, 0, netmos_9735 },
+ { PCI_VENDOR_ID_NETMOS, PCI_DEVICE_ID_NETMOS_9835,
+ PCI_ANY_ID, PCI_ANY_ID, 0, 0, netmos_9835 },
+ { PCI_VENDOR_ID_NETMOS, PCI_DEVICE_ID_NETMOS_9755,
+ PCI_ANY_ID, PCI_ANY_ID, 0, 0, netmos_9755 },
+ { PCI_VENDOR_ID_NETMOS, PCI_DEVICE_ID_NETMOS_9715,
+ PCI_ANY_ID, PCI_ANY_ID, 0, 0, netmos_9715 },
{ 0, } /* terminate list */
};
MODULE_DEVICE_TABLE(pci,parport_pc_pci_tbl);
/* snip */
and the following to include/linux/pci_ids.h:
/* snip */
--- pci_ids.h.old Tue Aug 24 12:05:44 2004
+++ pci_ids.h Tue Aug 24 12:15:21 2004
@@ -2313,6 +2313,8 @@
#define PCI_DEVICE_ID_NETMOS_9815 0x9815
#define PCI_DEVICE_ID_NETMOS_9835 0x9835
#define PCI_DEVICE_ID_NETMOS_9855 0x9855
+#define PCI_DEVICE_ID_NETMOS_9755 0x9755
+#define PCI_DEVICE_ID_NETMOS_9715 0x9715
#define PCI_SUBVENDOR_ID_EXSYS 0xd84d
#define PCI_SUBDEVICE_ID_EXSYS_4014 0x4014
/* snip */
NetMOS 9805 support is already in the kernel, this patch adds the support
for the missing 9735,9855,9755 and 9715 chips.
And another remark: The 9735 and 9835 seem to be chips with serial *and*
parallel interfaces, so I suppose they are already claimed somewhere in
the serial driver. I don't know whether this causes any problems. I'm sorry
that I can't test, I've only a 9805 here. Any idea how these "dual" chips have
to be handled by the kernel?
So long,
Thomas
next prev parent reply other threads:[~2004-08-24 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 11:43 [PATCH] NetMOS 9805 ParPort interface Thomas Richter
2004-08-05 22:42 ` Marcelo Tosatti
2004-08-23 12:59 ` Marcelo Tosatti
2004-08-23 18:32 ` Andrew Morton
2004-08-24 10:52 ` Thomas Richter [this message]
[not found] <200408061641.SAA17413@cleopatra.math.tu-berlin.de>
2004-08-06 16:42 ` Thomas Richter
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=200408241052.MAA09594@cleopatra.math.tu-berlin.de \
--to=thor@math.tu-berlin.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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.