From: Russell King <rmk@arm.linux.org.uk>
To: Ed Vance <EdV@macrolink.com>
Cc: "'Adam J. Richter'" <adam@yggdrasil.com>,
driver@jpl.nasa.gov, dwmw2@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: devfs + PCI serial card = no extra serial ports
Date: Fri, 14 Mar 2003 20:07:46 +0000 [thread overview]
Message-ID: <20030314200746.I23686@flint.arm.linux.org.uk> (raw)
In-Reply-To: <11E89240C407D311958800A0C9ACF7D1A33DE3@EXCHANGE>; from EdV@macrolink.com on Fri, Mar 14, 2003 at 11:49:54AM -0800
On Fri, Mar 14, 2003 at 11:49:54AM -0800, Ed Vance wrote:
> Anybody know of any other (worse) technical issues with PCI/setserial
> on the 2.4 kernels?
Please note that one of the things I've recently done is to put a lot
of effort into re-working the PCI serial code in 2.5, hopefully without
breaking too much other stuff. It works here with my, ah hem, limited
PCI serial devices.
One of the areas I've tried to improve is our "port guessing" algorithm.
Hopefully, this will allow more serial cards to just work like the one
which started this thread, but only time will tell if this is successful.
It hasn't hit Linus' tree yet, so please don't go looking there for it
yet.
I'm also not going to suggest backporting it to 2.4 either, but if some
one is feeling brave enough, they're welcome to try (this is what Open
Source is all about!) 8)
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-03-14 19:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 19:49 devfs + PCI serial card = no extra serial ports Ed Vance
2003-03-14 20:07 ` Russell King [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-15 0:54 Ed Vance
2003-03-15 0:02 Adam J. Richter
2003-03-14 20:28 Adam J. Richter
2003-03-14 20:43 ` Russell King
2003-03-14 19:06 Adam J. Richter
2003-03-10 18:37 Adam J. Richter
2003-03-10 17:12 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-08 1:30 Ed Vance
2003-03-07 23:57 Ed Vance
2003-03-08 0:59 ` Bryan Whitehead
2003-03-11 9:07 ` Theodore Ts'o
2003-03-07 23:40 Ed Vance
2003-03-08 0:15 ` Marek Michalkiewicz
2003-03-07 23:04 Ed Vance
2003-03-07 23:17 ` Bryan Whitehead
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
2003-03-07 23:38 ` Theodore Ts'o
2003-03-11 23:12 ` whitnl73
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=20030314200746.I23686@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=EdV@macrolink.com \
--cc=adam@yggdrasil.com \
--cc=driver@jpl.nasa.gov \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@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