From: Bryan Whitehead <driver@jpl.nasa.gov>
To: Ed Vance <EdV@macrolink.com>
Cc: 'Theodore Ts'o' <tytso@mit.edu>,
linux-kernel@vger.kernel.org, linux-newbie@vger.kernel.org
Subject: Re: devfs + PCI serial card = no extra serial ports
Date: Fri, 07 Mar 2003 16:59:04 -0800 [thread overview]
Message-ID: <3E694058.50101@jpl.nasa.gov> (raw)
In-Reply-To: 11E89240C407D311958800A0C9ACF7D1A33DD5@EXCHANGE
Quick question: What PCI serial port add on card works with devfs in
kernel 2.4.19 out of the box? No pissing around?
While I'm messing around with the one I got (that doesn't work) I need
one that does... any suggestions??
Thanks to all for the help!!
Ed Vance wrote:
> On Fri, Mar 07, 2003 at 3:39 PM, Theodore Ts'o wrote:
>
>>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,
>
> Will Bryan get the proper devfs entries if he patches serial.c to
> recognize his card at kernel initialization, or is there more
> weirdness expected?
>
> Best regards,
> Ed
>
> ----------------------------------------------------------------
> Ed Vance edv (at) macrolink (dot) com
> Macrolink, Inc. 1500 N. Kellogg Dr Anaheim, CA 92807
> ----------------------------------------------------------------
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Bryan Whitehead
SysAdmin - JPL - Interferometry Systems and Technology
Phone: 818 354 2903
driver@jpl.nasa.gov
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
WARNING: multiple messages have this Message-ID (diff)
From: Bryan Whitehead <driver@jpl.nasa.gov>
To: Ed Vance <EdV@macrolink.com>
Cc: "'Theodore Ts'o'" <tytso@mit.edu>,
linux-kernel@vger.kernel.org, linux-newbie@vger.kernel.org
Subject: Re: devfs + PCI serial card = no extra serial ports
Date: Fri, 07 Mar 2003 16:59:04 -0800 [thread overview]
Message-ID: <3E694058.50101@jpl.nasa.gov> (raw)
In-Reply-To: 11E89240C407D311958800A0C9ACF7D1A33DD5@EXCHANGE
Quick question: What PCI serial port add on card works with devfs in
kernel 2.4.19 out of the box? No pissing around?
While I'm messing around with the one I got (that doesn't work) I need
one that does... any suggestions??
Thanks to all for the help!!
Ed Vance wrote:
> On Fri, Mar 07, 2003 at 3:39 PM, Theodore Ts'o wrote:
>
>>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,
>
> Will Bryan get the proper devfs entries if he patches serial.c to
> recognize his card at kernel initialization, or is there more
> weirdness expected?
>
> Best regards,
> Ed
>
> ----------------------------------------------------------------
> Ed Vance edv (at) macrolink (dot) com
> Macrolink, Inc. 1500 N. Kellogg Dr Anaheim, CA 92807
> ----------------------------------------------------------------
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Bryan Whitehead
SysAdmin - JPL - Interferometry Systems and Technology
Phone: 818 354 2903
driver@jpl.nasa.gov
next prev parent reply other threads:[~2003-03-08 0:59 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 23:57 devfs + PCI serial card = no extra serial ports Ed Vance
2003-03-07 23:57 ` Ed Vance
2003-03-08 0:59 ` Bryan Whitehead [this message]
2003-03-08 0:59 ` Bryan Whitehead
2003-03-11 9:07 ` Theodore Ts'o
2003-03-11 9:07 ` Theodore Ts'o
-- 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:49 Ed Vance
2003-03-14 20:07 ` 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:40 Ed Vance
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:04 ` Ed Vance
2003-03-07 23:17 ` Bryan Whitehead
2003-03-07 22:51 Bryan Whitehead
2003-03-07 22:51 ` Bryan Whitehead
2003-03-07 22:55 ` 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-08 0:10 ` Marek Michalkiewicz
2003-03-07 23:38 ` Theodore Ts'o
2003-03-11 23:12 ` whitnl73
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=3E694058.50101@jpl.nasa.gov \
--to=driver@jpl.nasa.gov \
--cc=EdV@macrolink.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-newbie@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.