From: Jay Cliburn <jacliburn@bellsouth.net>
To: Chris Rankin <rankincj@yahoo.com>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: 2.6.25.3: serial problem (minicom)
Date: Sat, 17 May 2008 08:22:07 -0500 [thread overview]
Message-ID: <20080517082207.4b1e8556@osprey.hogchain.net> (raw)
In-Reply-To: <762763.57234.qm@web52903.mail.re2.yahoo.com>
On Sat, 17 May 2008 13:29:31 +0100 (BST)
Chris Rankin <rankincj@yahoo.com> wrote:
> --- Jay Cliburn <jacliburn@bellsouth.net> wrote:
> > Serial console using minicom works fine for me under 2.6.25 and
> > 2.6.25.4. Keystrokes are accepted normally.
>
> I have just replicated this problem between two Fedora 8 boxes;
> minicom reads the remote serial console fine, provided it is running
> on a 2.6.24.x kernel. (The serial console is from a 2.6.25.4 machine.)
>
> My serial console is defined using the kernel parameters
> "console=ttyS0,115200n8", and my minicom session as:
>
> pr port /dev/ttyS1
> pu baudrate 115200
> pu bits 8
> pu parity N
> pu stopbits 1
> #pu minit ^M
Mine still works. I was going to bisect it, but I don't encounter the
problem.
[jcliburn@sparrow ~]$ uname -a
Linux sparrow 2.6.25.4 #1 SMP Fri May 16 11:31:19 CDT 2008 i686 i686 i386 GNU/Linux
[jcliburn@sparrow ~]$ cat /etc/fedora-release
Fedora release 8 (Werewolf)
[jcliburn@sparrow ~]$ cat /etc/minirc.dfl
# Machine-generated file - use "minicom -s" to change parameters.
pu port /dev/ttyS0
pu baudrate 38400
pu bits 8
pu parity N
pu stopbits 1
jcliburn@sparrow ~]$ grep CONFIG_SERIAL linux-2.6.25.y.git/.config
CONFIG_SERIAL_NONSTANDARD=y
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_CS=m
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
# CONFIG_SERIAL_8250_FOURPORT is not set
# CONFIG_SERIAL_8250_ACCENT is not set
# CONFIG_SERIAL_8250_BOCA is not set
# CONFIG_SERIAL_8250_EXAR_ST16C554 is not set
# CONFIG_SERIAL_8250_HUB6 is not set
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_8250_DETECT_IRQ=y
CONFIG_SERIAL_8250_RSA=y
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_JSM=m
next prev parent reply other threads:[~2008-05-17 13:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 19:06 2.6.25.3: serial problem (minicom) Chris Rankin
2008-05-16 3:23 ` Andrew Morton
2008-05-16 7:28 ` Chris Rankin
2008-05-16 17:33 ` Jay Cliburn
2008-05-17 12:29 ` Chris Rankin
2008-05-17 13:22 ` Jay Cliburn [this message]
2008-05-17 13:32 ` Jay Cliburn
2008-05-17 14:49 ` Chris Rankin
2008-05-17 15:10 ` Jay Cliburn
2008-05-17 18:46 ` Bart Van Assche
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=20080517082207.4b1e8556@osprey.hogchain.net \
--to=jacliburn@bellsouth.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rankincj@yahoo.com \
/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