From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] omap3: cm-t3517: define CONFIG_MACH_TYPE
Date: Wed, 9 Sep 2015 11:36:38 +0300 [thread overview]
Message-ID: <55EFEF96.3090106@compulab.co.il> (raw)
In-Reply-To: <1441787237-9195-1-git-send-email-lifshitz@compulab.co.il>
On 09/09/15 11:27, Dmitry Lifshitz wrote:
> Define CONFIG_MACH_TYPE to allow non DT Linux boot.
>
> Signed-off-by: Dmitry Lifshitz <lifshitz@compulab.co.il>
Acked-by: Igor Grinberg <grinberg@compulab.co.il>
> ---
> include/configs/cm_t3517.h | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/include/configs/cm_t3517.h b/include/configs/cm_t3517.h
> index fbc10dd..27c023c 100644
> --- a/include/configs/cm_t3517.h
> +++ b/include/configs/cm_t3517.h
> @@ -36,6 +36,8 @@
> #include <asm/arch/cpu.h> /* get chip and board defs */
> #include <asm/arch/omap.h>
>
> +#define CONFIG_MACH_TYPE MACH_TYPE_CM_T3517
> +
> /*
> * Display CPU and Board information
> */
>
--
Regards,
Igor.
next prev parent reply other threads:[~2015-09-09 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 8:27 [U-Boot] [PATCH] omap3: cm-t3517: define CONFIG_MACH_TYPE Dmitry Lifshitz
2015-09-09 8:36 ` Igor Grinberg [this message]
2015-09-12 12:52 ` [U-Boot] " Tom Rini
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=55EFEF96.3090106@compulab.co.il \
--to=grinberg@compulab.co.il \
--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