From: Chris Rankin <rankincj@yahoo.com>
To: Jay Cliburn <jacliburn@bellsouth.net>
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 13:29:31 +0100 (BST) [thread overview]
Message-ID: <762763.57234.qm@web52903.mail.re2.yahoo.com> (raw)
In-Reply-To: <20080516123321.5674952c@osprey.hogchain.net>
--- 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
Cheers,
Chris
__________________________________________________________
Sent from Yahoo! Mail.
A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html
next prev parent reply other threads:[~2008-05-17 12:29 UTC|newest]
Thread overview: 24+ 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 [this message]
2008-05-17 13:22 ` Jay Cliburn
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
-- strict thread matches above, loose matches on Subject: below --
2008-06-13 21:36 R.L. Horn
2008-06-14 9:29 ` Alan Cox
2008-06-15 7:04 ` R.L. Horn
2008-06-16 10:13 ` Alan Cox
2008-06-17 4:22 ` R.L. Horn
2008-06-17 8:58 ` Alan Cox
2008-06-17 11:03 ` R.L. Horn
2008-06-18 0:15 ` Hans-Peter Jansen
2008-06-18 17:55 ` Alan Cox
2008-06-18 20:07 ` Olivier Galibert
2008-06-19 8:20 ` R.L. Horn
2008-06-19 23:46 ` Hans-Peter Jansen
2008-06-20 11:22 ` R.L. Horn
2008-06-17 10:50 ` R.L. Horn
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=762763.57234.qm@web52903.mail.re2.yahoo.com \
--to=rankincj@yahoo.com \
--cc=jacliburn@bellsouth.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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