From: Russell King <rmk@arm.linux.org.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Bogus serial port ttyS02
Date: Wed, 13 Aug 2003 19:34:18 +0100 [thread overview]
Message-ID: <20030813193418.D20676@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.GSO.4.21.0308131601070.11378-100000@vervain.sonytel.be>; from geert@linux-m68k.org on Wed, Aug 13, 2003 at 05:40:23PM +0200
On Wed, Aug 13, 2003 at 05:40:23PM +0200, Geert Uytterhoeven wrote:
> Linux always finds 3 serial ports instead of 2:
>
> | ttyS00 at 0x03f8 (irq = 4) is a 16550A
> | ttyS01 at 0x02f8 (irq = 3) is a 16550A
> | ttyS02 at 0x03e8 (irq = 4) is a 16450
>
> The last one is bogus.
Do you know that it absolutely does not exist? Can it exist on any
PPC box? If the answer to both those questions is no, I suggest
you don't probe for it in the first place.
You could enable DEBUG_AUTOCONF in 8250.c in 2.6.0-test3 and give
further probing information. 8)
Looking at PPC's pc_serial.h, it seems that you've told it to probe
there using ASYNC_BOOT_AUTOCONF | ASYNC_SKIP_TEST | ASYNC_AUTO_IRQ.
ASYNC_SKIP_TEST means that we use a reduced test to probe for a port -
we just check that we can read back a value written to 0x3e9. If this
suceeds, we decide that there is a port present, and go on to try and
derive its type.
If you want to enable the more rigorous tests, remove ASYNC_SKIP_TEST
from the port flags. This will make us check that the device behaves
like a UART before deciding that it is one.
--
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-08-13 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 15:40 Bogus serial port ttyS02 Geert Uytterhoeven
2003-08-13 16:16 ` Richard B. Johnson
2003-08-13 16:26 ` Geert Uytterhoeven
2003-08-13 18:34 ` Russell King [this message]
2003-08-13 21:08 ` Geert Uytterhoeven
2003-08-16 15:23 ` Geert Uytterhoeven
2003-08-16 20:00 ` Russell King
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=20030813193418.D20676@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.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