From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 1/2] serial_mxc: return question mark for chars received with high bit set
Date: Wed, 14 May 2014 11:45:24 -0700 [thread overview]
Message-ID: <5373B9C4.4040901@boundarydevices.com> (raw)
In-Reply-To: <1400090674-10586-2-git-send-email-eric.nelson@boundarydevices.com>
Hi all,
On 05/14/2014 11:04 AM, Eric Nelson wrote:
> This patch allows testing of patch 2/2 in the series by forcing
> bytes read from the i.MX serial port to be printable.
>
> Without this, it's very hard to tell that a series of in-bound
> '\xff' characters are being produced, because they'll be
> silently ignored.
>
An even easier test is to use stty at a Linux shell:
# stty -F /dev/ttymxc1 19200
And then enter a 'b' at 115200.
next prev parent reply other threads:[~2014-05-14 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 18:04 [U-Boot] RFC: i.MX UART failures with baud-rate mis-match Eric Nelson
2014-05-14 18:04 ` [U-Boot] [RFC PATCH 1/2] serial_mxc: return question mark for chars received with high bit set Eric Nelson
2014-05-14 18:45 ` Eric Nelson [this message]
2014-05-14 18:04 ` [U-Boot] [RFC PATCH 2/2] serial_mxc: disable new features of autobaud detection Eric Nelson
2014-05-14 23:36 ` Fabio Estevam
2014-05-14 23:55 ` Eric Nelson
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=5373B9C4.4040901@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=u-boot@lists.denx.de \
/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;
as well as URLs for NNTP newsgroup(s).