All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert P. J. Day <rpjday@crashcourse.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] still ongoing problems using minicom to talk to u-boot?
Date: Wed, 19 Aug 2009 05:58:45 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.0908190554330.8008@localhost> (raw)


  the current u-boot manual suggests there are still problems using
minicom to connect to u-boot.  does anyone know what those problems
are, and if they still exist?

  i've been using minicom to connect to the pre-installed u-boot on my
beagleboard for months now, and it's worked reliably, except for one
situation.  since my laptop has no serial port, i'd purchased a
low-end USB-serial converter (with a prolific chipset), which failed
utterly.  i tried everything to debug my setup until someone else
suggested that the converter was at fault.

  i purchased a different converter and everything was fine.  so i'm
still curious about potential problems with minicom and u-boot.

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

        Linux Consulting, Training and Annoying Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================

             reply	other threads:[~2009-08-19  9:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-19  9:58 Robert P. J. Day [this message]
2009-08-19 10:16 ` [U-Boot] still ongoing problems using minicom to talk to u-boot? Wolfgang Denk
2009-08-19 10:42   ` Robert P. J. Day
2009-08-19 11:39     ` Wolfgang Denk
2009-08-19 11:54       ` vibi sreenivasan

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=alpine.LFD.2.00.0908190554330.8008@localhost \
    --to=rpjday@crashcourse.ca \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.