From: Ruud Linders <rkmp@xs4all.nl>
To: linux-kernel@vger.kernel.org
Subject: Serial port numbering (ttyS..) wrong for 2.5.61+
Date: Sun, 01 Jun 2003 13:14:45 +0200 [thread overview]
Message-ID: <3ED9E025.1060801@xs4all.nl> (raw)
Since I tried the 2.5 kernel versions somewhere in the 2.5.6x range, I
see rather odd port naming for the extra 4 serial ports on a PCI-card.
The first two are numered as ttyS14, ttyS15 while the last two are
ttyS2 and ttyS3 !
I tried to find where these numbers are coming from but couldn't really
find an obvious place in the various drivers/char/* or drivers/serial/*
files.
Note that the ttyS14 port actually works so this seems only a bug in
the numbering.
Regards,
Ruud Linders
Kernel version 2.5.70
---------------------
dmesg:
======
Serial: 8250/16550 driver $Revision: 1.90 $ IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
ttyS14 at I/O 0xbc00 (irq = 21) is a 16550A <<<<<< 14 ????
ttyS15 at I/O 0xbc08 (irq = 21) is a 16550A <<<<<<
ttyS2 at I/O 0xbc10 (irq = 21) is a 16550A
ttyS3 at I/O 0xbc18 (irq = 21) is a 16550A
4-port PCI serial controller:
=============================
# lspci -d 10b5:1077 -v
02:0b.0 Serial controller: PLX Technology, Inc. VScom 400 4 port serial
adaptor
(rev 02) (prog-if 00 [8250])
Subsystem: PLX Technology, Inc. VScom 400 4 port serial adaptor
Flags: medium devsel, IRQ 21
Memory at de004000 (32-bit, non-prefetchable) [size=128]
I/O ports at b800 [size=128]
I/O ports at bc00 [size=32]
I/O ports at c000 [size=8]
Expansion ROM at <unassigned> [disabled] [size=2K]
next reply other threads:[~2003-06-01 11:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-01 11:14 Ruud Linders [this message]
2003-06-01 12:48 ` Serial port numbering (ttyS..) wrong for 2.5.61+ Paul Rolland
2003-06-02 17:51 ` Russell King
2003-06-02 18:43 ` Paul Rolland
2003-06-03 16:58 ` Ruud Linders
-- strict thread matches above, loose matches on Subject: below --
2003-06-02 16:21 Ruud Linders
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=3ED9E025.1060801@xs4all.nl \
--to=rkmp@xs4all.nl \
--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