From: "Theodore Ts'o" <tytso@mit.edu>
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: Fri, 7 Mar 2003 18:38:39 -0500 [thread overview]
Message-ID: <20030307233839.GB24572@think.thunk.org> (raw)
In-Reply-To: <3E692281.10906@jpl.nasa.gov>
On Fri, Mar 07, 2003 at 02:51:45PM -0800, Bryan Whitehead wrote:
> It seems devfsd has an annoying "feature". I bought a PCI card to get a
> couple (2) more serial ports. The kernel doesn't seem to set up the
> serial ports at boot, so devfs never creates an entry. However, post
> boot, since there is no entries, I cannot configure the serial ports
> with setserial. So basically devfsd = no PCI based serial add on?
Yep. This I pointed this out as a flaw to devfs a long, long time
(years!) ago, but Richard chose not to listen to me. Personally, I
solve this (and other) problems by simply refusing to use devfs.
- Ted
next prev parent reply other threads:[~2003-03-07 23:28 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
2003-03-07 23:38 ` Theodore Ts'o [this message]
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=20030307233839.GB24572@think.thunk.org \
--to=tytso@mit.edu \
--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®