From: Marek Michalkiewicz <marekm@amelek.gda.pl>
To: Bryan Whitehead <driver@jpl.nasa.gov>
Cc: linux-kernel@vger.kernel.org, linux-newbie@vger.kernel.org
Subject: Re: devfs + PCI serial card = no extra serial ports
Date: Sat, 8 Mar 2003 01:10:05 +0100 [thread overview]
Message-ID: <20030308001005.GA20120@alf.amelek.gda.pl> (raw)
In-Reply-To: <3E692B1C.5010607@jpl.nasa.gov>
On Fri, Mar 07, 2003 at 03:28:28PM -0800, Bryan Whitehead wrote:
> I just found this:
> http://www.uwsg.iu.edu/hypermail/linux/kernel/0212.2/0845.html
>
> Has this patch been accepted into the new kernel series? Or should I
> just toss this card (the NetMos PCI I/O card)?
No, and no. Try these patches (apply in this order, may need
some hand-patching to apply to the current 2.4.21-pre source):
http://www.amelek.gda.pl/linux-patches/2.4.20-pre9/00_parport_serial
http://www.amelek.gda.pl/linux-patches/2.4.20-pre9/01_netmos
Please test - I'd like to know if it works for you. It should -
I have 3 such cards in 2 servers, running patched 2.4.20 kernel
in production use for 3 months now (mainly serial ports used, but
2S1P cards were cheaper than 2S cards...). Attempts to submit
the changes have been ignored, so I gave up...
NetMos support was already in early 2.4.x kernels, later removed:
* parport_serial.c: Remove NetMos support, since it causes problems
for some people.
No idea what exactly these problems are, who "some people" are, why
NetMos support was not simply made a config option conditional on
CONFIG_EXPERIMENTAL, and why the link order bugfix (separate patch,
which only fixes an obvious bug) has been ignored too.
Perhaps you will have more luck than I did - test your card with the
patches for some time, if it works try to submit the patches again...
> >I hoped after "setting up" the serial ports with setserial some magic
> >would happen and they would apear in /dev/tts... but I was wrong.
I don't use devfs, so I never had this problem.
Hope this helps,
Marek
next prev parent reply other threads:[~2003-03-08 0:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 22:51 Bryan Whitehead
2003-03-07 22:55 ` Bryan Whitehead
2003-03-07 23:28 ` Bryan Whitehead
2003-03-08 0:10 ` Marek Michalkiewicz [this message]
2003-03-07 23:38 ` Theodore Ts'o
2003-03-11 23:12 ` whitnl73
2003-03-07 23:04 Ed Vance
2003-03-07 23:17 ` Bryan Whitehead
2003-03-07 23:40 Ed Vance
2003-03-08 0:15 ` Marek Michalkiewicz
2003-03-07 23:57 Ed Vance
2003-03-08 0:59 ` Bryan Whitehead
2003-03-11 9:07 ` Theodore Ts'o
2003-03-08 1:30 Ed Vance
2003-03-08 19:48 Adam J. Richter
2003-03-10 18:25 ` Bryan Whitehead
2003-03-14 15:23 ` David Woodhouse
2003-03-10 17:12 Ed Vance
2003-03-10 18:37 Adam J. Richter
2003-03-14 19:06 Adam J. Richter
2003-03-14 19:49 Ed Vance
2003-03-14 20:07 ` Russell King
2003-03-14 20:28 Adam J. Richter
2003-03-14 20:43 ` Russell King
2003-03-15 0:02 Adam J. Richter
2003-03-15 0:54 Ed Vance
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=20030308001005.GA20120@alf.amelek.gda.pl \
--to=marekm@amelek.gda.pl \
--cc=driver@jpl.nasa.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-newbie@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
all inboxes | Powered by JetHome®