From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Thomas Richter <thor@math.TU-Berlin.DE>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] NetMOS 9805 ParPort interface
Date: Thu, 5 Aug 2004 19:42:44 -0300 [thread overview]
Message-ID: <20040805224244.GC18155@logos.cnet> (raw)
In-Reply-To: <200408051143.NAA23740@cleopatra.math.tu-berlin.de>
On Thu, Aug 05, 2004 at 01:43:13PM +0200, Thomas Richter wrote:
>
> Hi folks,
>
> here's a tiny patch against parport/parport_pc.c for kernel 2.4.26.
> It adds support for the NetMOS 9805 chip, used in several popular
> parallel port extension cards available here in germany. The patch below
> has been found working in a beige G3 Mac and a Canon BJC just fine.
Hi Thomas,
Looks good, I've queued it for 2.4.28-pre.
Care to write a v2.6 version of it ?
Most of NetMos support has been merged recently in v2.4.27 and v2.6.7/v2.6.8.
Thanks!
> --- parport_pc_old.c Wed Jul 28 10:26:23 2004
> +++ parport_pc.c Wed Jul 28 10:28:16 2004
> @@ -2692,6 +2692,7 @@
> syba_2p_epp,
> syba_1p_ecp,
> titan_010l,
> + titan_1284p1,
> titan_1284p2,
> avlab_1p,
> avlab_2p,
> @@ -2759,6 +2760,7 @@
> /* syba_2p_epp AP138B */ { 2, { { 0, 0x078 }, { 0, 0x178 }, } },
> /* syba_1p_ecp W83787 */ { 1, { { 0, 0x078 }, } },
> /* titan_010l */ { 1, { { 3, -1 }, } },
> + /* titan_1284p1 */ { 1, { { 0, 1 }, } },
> /* titan_1284p2 */ { 2, { { 0, 1 }, { 2, 3 }, } },
> /* avlab_1p */ { 1, { { 0, 1}, } },
> /* avlab_2p */ { 2, { { 0, 1}, { 2, 3 },} },
> @@ -2826,6 +2828,7 @@
> PCI_ANY_ID, PCI_ANY_ID, 0, 0, syba_1p_ecp },
> { PCI_VENDOR_ID_TITAN, PCI_DEVICE_ID_TITAN_010L,
> PCI_ANY_ID, PCI_ANY_ID, 0, 0, titan_010l },
> + { 0x9710, 0x9805, 0x1000, 0x0010, 0, 0, titan_1284p1 },
> { 0x9710, 0x9815, 0x1000, 0x0020, 0, 0, titan_1284p2 },
> /* PCI_VENDOR_ID_AVLAB/Intek21 has another bunch of cards ...*/
> { 0x14db, 0x2120, PCI_ANY_ID, PCI_ANY_ID, 0, 0, avlab_1p}, /* AFAVLAB_TK9902 */
>
> The same patch should also apply to more modern kernels since it just adds
> some PCI ids.
>
> Similar patches for other NetMOS products might be easy since they're all
> documented; I could add a couple of PCI Ids to the parport_pc - I just don't
> have the hardware for testing.
next prev parent reply other threads:[~2004-08-05 23:28 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 [this message]
2004-08-23 12:59 ` Marcelo Tosatti
2004-08-23 18:32 ` Andrew Morton
2004-08-24 10:52 ` Thomas Richter
[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=20040805224244.GC18155@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thor@math.TU-Berlin.DE \
/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