From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: poky@yoctoproject.org
Subject: Re: [PATCH] README.hardware for mpc8315erdb incorrectly specified a null modem serial cable
Date: Fri, 30 Mar 2012 18:34:33 +0100 [thread overview]
Message-ID: <3081444.zUNYCddb1s@helios> (raw)
In-Reply-To: <4F75E5E3.9050407@mindchasers.com>
On Friday 30 March 2012 12:57:07 Bob Cochran wrote:
> I noticed this while beta testing 1.2. but patch is against master
> (latest commit: bcd4d14425cadc5bd6296f59f14733e8c39c49dd).
>
> Instructions specified a null modem. This isn't the case. A straight
> serial cable is required. I verified it with my own setup and
> Freescale's user manual.
>
>
> Signed-off-by: Robert Cochran<yocto@mindchasers.com>
>
> ---
> README.hardware | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/README.hardware b/README.hardware
> index f72da94..1e7df76 100644
> --- a/README.hardware
> +++ b/README.hardware
> @@ -241,8 +241,7 @@ Setup instructions
> You will need the following:
> * NFS root setup on your workstation
> * TFTP server installed on your workstation
> -* Null modem cable connected from your workstation to the first serial port
> - on the board
> +* Straight-thru 9-conductor serial cable (DB9, M/F) connected from your
> PC to UART1
> * Ethernet connected to the first ethernet port on the board
>
> --- Preparation ---
You're right - I've no idea how I got this wrong in the first place. Thanks!
Acked-by: Paul Eggleton <paul.eggleton@linux.intel.com>
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-03-30 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 16:57 [PATCH] README.hardware for mpc8315erdb incorrectly specified a null modem serial cable Bob Cochran
2012-03-30 17:34 ` Paul Eggleton [this message]
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=3081444.zUNYCddb1s@helios \
--to=paul.eggleton@linux.intel.com \
--cc=poky@yoctoproject.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 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.