From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Latest git not working for MPC8349EMDS
Date: Wed, 02 May 2007 12:56:23 -0500 [thread overview]
Message-ID: <4638D0C7.60803@freescale.com> (raw)
In-Reply-To: <4638D05A.9020701@ovro.caltech.edu>
David Hawkins wrote:
> But I'm not sure that would be correct for an MPC8349EMDS board.
> So his comment in J22 may refer to the ITX board, not the MDS.
> Check the MDS manual, and you'll figure it out.
Oh sorry. I don't know why I was thinking you had an ITX.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-05-02 17:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 20:12 [U-Boot-Users] Latest git not working for MPC8349EMDS Benedict, Michael
2007-05-01 20:33 ` David Hawkins
2007-05-01 21:12 ` Benedict, Michael
2007-05-01 21:24 ` Timur Tabi
2007-05-01 21:30 ` David Hawkins
2007-05-02 17:29 ` Benedict, Michael
2007-05-02 17:48 ` David Hawkins
2007-05-02 17:54 ` Timur Tabi
2007-05-02 17:48 ` Timur Tabi
2007-05-02 17:54 ` David Hawkins
2007-05-02 17:56 ` Timur Tabi [this message]
2007-05-02 18:10 ` Benedict, Michael
2007-05-02 18:32 ` David Hawkins
2007-05-02 18:33 ` Timur Tabi
2007-05-02 18:49 ` Benedict, Michael
2007-05-02 20:59 ` David Hawkins
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=4638D0C7.60803@freescale.com \
--to=timur@freescale.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