From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] RFC: Add XON/XOFF support
Date: Sun, 30 Oct 2011 17:30:55 -0400 [thread overview]
Message-ID: <201110301730.56033.vapier@gentoo.org> (raw)
In-Reply-To: <1319514744-18697-2-git-send-email-sjg@chromium.org>
On Monday 24 October 2011 23:52:24 Simon Glass wrote:
> This is just for testing - please try it out and report back with results.
> For me it works on Minicom but not ser2net.
>
> This needs to be controlled by an environment variable, CONFIG option or
> both. We may need a way of specifying flow control on a per-device basis.
> We may need to do something special for X-modem transfers, etc. This might
> turn out to be a can of worms.
we have CONFIG_HWFLOW already, so CONFIG_SWFLOW would probably be the natural
choice. and then have the funcs be named swflow_xxx (although the hwflow code
does it via one and uses its arg to figure out what to do).
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20111030/e2f12354/attachment.pgp
next prev parent reply other threads:[~2011-10-30 21:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 3:52 [U-Boot] [PATCH 1/2] Create a single cmd_call() function to handle command execution Simon Glass
2011-10-25 3:52 ` [U-Boot] [PATCH 2/2] RFC: Add XON/XOFF support Simon Glass
2011-10-25 8:09 ` Graeme Russ
2011-10-25 23:56 ` Simon Glass
2011-10-30 21:30 ` Mike Frysinger [this message]
2011-10-30 23:53 ` Albert ARIBAUD
2011-10-25 7:46 ` [U-Boot] [PATCH 1/2] Create a single cmd_call() function to handle command execution Wolfgang Denk
2011-10-25 8:03 ` Graeme Russ
2011-10-25 13:33 ` Simon Glass
2011-10-25 18:20 ` Wolfgang Denk
2011-10-25 13:57 ` Mike Frysinger
2011-10-25 23:05 ` Simon Glass
2011-10-30 21:28 ` Mike Frysinger
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=201110301730.56033.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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