linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zwane Mwaikambo <zwane@linuxpower.ca>
To: Marek Michalkiewicz <marekm@amelek.gda.pl>
Cc: twaugh@redhat.com, <serial24@macrolink.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] fix parport_serial / serial link order (for 2.4.20-pre8)
Date: Sun, 29 Sep 2002 15:14:42 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0209291511250.24805-100000@montezuma.mastecende.com> (raw)
In-Reply-To: <E17viMz-0006UO-00@alf.amelek.gda.pl>

On Sun, 29 Sep 2002, Marek Michalkiewicz wrote:

> I haven't heard anything from the kernel people yet - any chances of
> getting these changes into the official 2.4.x source?  I can make
> a second patch (NetMos support) after the first one is accepted...

I submitted both a parport sharing (i am using interrupt driven parport, 
which is needed due to both serial ports using the same irq) and netmos 
patch a while ago, Tim was concerned about issues encountered 
by folks previously wrt the netmos.

Tests run with this setup was copying a cd from a parport cd drive and 
doing heavy serial i/o on both serial ports. the md5sum on the resultant 
cd image was verified.

	Zwane


-- 
function.linuxpower.ca


  reply	other threads:[~2002-09-29 19:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-26 20:05 [patch] fix parport_serial / serial link order (for 2.4.20-pre8) Marek Michalkiewicz
2002-09-27  1:18 ` Zwane Mwaikambo
2002-09-27  6:35   ` Marek Michalkiewicz
2002-09-28  4:24     ` Zwane Mwaikambo
2002-09-29 18:00       ` Marek Michalkiewicz
2002-09-29 19:14         ` Zwane Mwaikambo [this message]
2002-09-29 20:24           ` Marek Michalkiewicz
2002-09-30  9:20             ` Zwane Mwaikambo
2002-09-30 10:27               ` Marek Michalkiewicz
2002-09-30  9:40 ` Tim Waugh
2002-09-30  9:49   ` Russell King
2002-09-30 10:07   ` Marek Michalkiewicz

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=Pine.LNX.4.44.0209291511250.24805-100000@montezuma.mastecende.com \
    --to=zwane@linuxpower.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marekm@amelek.gda.pl \
    --cc=serial24@macrolink.com \
    --cc=twaugh@redhat.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 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).