mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marek Michalkiewicz <marekm@amelek.gda.pl>
To: marcelo@conectiva.com.br
Cc: twaugh@redhat.com, linux-kernel@vger.kernel.org,
	linux-parport@torque.net
Subject: [patch] 2.4.21 parport_serial link order fix, NetMos support
Date: Sun, 22 Jun 2003 00:01:44 +0200	[thread overview]
Message-ID: <20030621220144.GA528@alf.amelek.gda.pl> (raw)

Hi,

that's me again, trying to submit this since 2.4.19 or so, with no
success so far.  Please consider for 2.4.22 if it ever happens...

I've been successfully using a few low cost PCI multi-IO cards (only
"made in China" on the PCB, "STLab" on the box) based on the NetMos
NM9835 chip (1 parallel port, 2 serial ports), for a few months now.
Patches (now updated for 2.4.21) are available here:

http://www.amelek.gda.pl/linux-patches/2.4.21/00_parport_serial
http://www.amelek.gda.pl/linux-patches/2.4.21/01_netmos

00_parport_serial fixes a link order bug (parport_serial didn't work
at all when compiled into the kernel, only as a module).  The patch
file is big, but most of it just moves drivers/parport/parport_serial.c
to drivers/char/ without changing a single line.  This way the driver
is initialised after serial, but still before any other drivers which
need the parport subsystem, such as: lp, paride, plip, ...

01_netmos (must be applied after 00_parport_serial) adds support for
the NetMos PCI parallel port and multi-IO chips.  This is based on an
old (2001) patch by Tim Waugh, without significant changes.

Apparently, some people had system lockups with NetMos cards when
trying to use the parport IRQ.  This patch does not do this -
polling mode works, and is better than nothing.  Anyway, I've also
added a config option (CONFIG_PARPORT_PC_NETMOS, conditional on
CONFIG_EXPERIMENTAL), with Documentation/Configure.help description.
Hopefully this will help to get the patch accepted into the kernel.

Thanks,
Marek


                 reply	other threads:[~2003-06-21 21:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030621220144.GA528@alf.amelek.gda.pl \
    --to=marekm@amelek.gda.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parport@torque.net \
    --cc=marcelo@conectiva.com.br \
    --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

all inboxes | Powered by JetHome®