public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bryan Whitehead <driver@jpl.nasa.gov>
To: Bryan Whitehead <driver@jpl.nasa.gov>
Cc: linux-kernel@vger.kernel.org, linux-newbie@vger.kernel.org,
	marekm@amelek.gda.pl
Subject: Re: devfs + PCI serial card = no extra serial ports
Date: Fri, 07 Mar 2003 15:28:28 -0800	[thread overview]
Message-ID: <3E692B1C.5010607@jpl.nasa.gov> (raw)
In-Reply-To: 3E692281.10906@jpl.nasa.gov

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)?

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?
> 
> 03:05.0 Serial controller: NetMos Technology 222N-2 I/O Card (2S+1P) 
> (rev 01) (prog-if 02 [16550])
>     Subsystem: LSI Logic / Symbios Logic (formerly NCR): Unknown device 
> 0002
>     Flags: medium devsel, IRQ 17
>     I/O ports at ecf8 [size=8]
>     I/O ports at ece8 [size=8]
>     I/O ports at ecd8 [size=8]
>     I/O ports at ecc8 [size=8]
>     I/O ports at ecb8 [size=8]
>     I/O ports at eca0 [size=16]
> 
> 
> mknod ttyS2 c 4 66
> mknod ttyS3 c 4 67
> setserial ttyS2 port 0xecf8 UART 16550A irq 17 Baud_base 9600
> setserial ttyS3 port 0xece8 UART 16550A irq 17 Baud_base 9600
> 
> 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.
> 
> gets me working serial ports... but it's not in /dev... :O
> 
> Am I just screwed?
> 
> If so, what would be a good add on PCI based solution for more serial 
> ports that WORKS with devfsd? (I don't want to disable devfs as this 
> opens up a different set of problems)
> 
> Thanks for any replay!
> 


-- 
Bryan Whitehead
SysAdmin - JPL - Interferometry Systems and Technology
Phone: 818 354 2903
driver@jpl.nasa.gov


  parent reply	other threads:[~2003-03-07 23:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-07 22:51 devfs + PCI serial card = no extra serial ports Bryan Whitehead
2003-03-07 22:55 ` Bryan Whitehead
2003-03-07 23:28 ` Bryan Whitehead [this message]
2003-03-08  0:10   ` Marek Michalkiewicz
2003-03-07 23:38 ` Theodore Ts'o
2003-03-11 23:12 ` whitnl73
  -- strict thread matches above, loose matches on Subject: below --
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=3E692B1C.5010607@jpl.nasa.gov \
    --to=driver@jpl.nasa.gov \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-newbie@vger.kernel.org \
    --cc=marekm@amelek.gda.pl \
    /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