All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] mx6sl: Add initial support for mx6slevk board
Date: Sat, 06 Apr 2013 09:27:14 +0200	[thread overview]
Message-ID: <515FCE52.3070605@gmail.com> (raw)
In-Reply-To: <1365209739-5586-3-git-send-email-festevam@gmail.com>

Am 06.04.2013 02:55, schrieb Fabio Estevam:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> mx6slevk board is a development board from Freescale based on the mx6 solo-lite
> processor.
>
> For details about mx6slevk, please refer to:
> http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX6SLEVK&parentCode=i.MX6SL&fpsp=1
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---

> diff --git a/board/freescale/mx6slevk/imximage.cfg b/board/freescale/mx6slevk/imximage.cfg
> new file mode 100644
> index 0000000..df39a16
> --- /dev/null
> +++ b/board/freescale/mx6slevk/imximage.cfg
> @@ -0,0 +1,118 @@
> +/*
> + * Copyright (C) 2013 Freescale Semiconductor, Inc.
> + *
> + * This program is free software; you can redistribute it and/or
> + * modify it under the terms of the GNU General Public License as
> + * published by the Free Software Foundation; either version 2 of
> + * the License or (at your option) any later version.
> + *
> + * Refer docs/README.imxmage for more details about how-to configure
> + * and create imximage boot image
> + *
> + * The syntax is taken as close as possible with the kwbimage
> + */
> +
> +/* image version */
> +
> +IMAGE_VERSION 2
> +
> +/*
> + * Boot Device : one of
> + * spi, sd (the board has no nand neither onenand)
> + */
> +
> +BOOT_FROM	sd
> +
> +/*
> + * Device Configuration Data (DCD)
> + *
> + * Each entry must have the format:
> + * Addr-type           Address        Value
> + *
> + * where:
> + *	Addr-type register length (1,2 or 4 bytes)
> + *	Address	  absolute address of the register
> + *	value	  value to be stored in the register
> + */
> +DATA 4 0x020c4018 0x00260324
> +
> +DATA 4 0x020c4068 0xffffffff
> +DATA 4 0x020c406c 0xffffffff
> +DATA 4 0x020c4070 0xffffffff
> +DATA 4 0x020c4074 0xffffffff
> +DATA 4 0x020c4078 0xffffffff
> +DATA 4 0x020c407c 0xffffffff
> +DATA 4 0x020c4080 0xffffffff

Again this default stuff? ;)

Best regards

Dirk

  reply	other threads:[~2013-04-06  7:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-06  0:55 [U-Boot] [PATCH 1/3] iomux-v3: Place pad control definitions into common file Fabio Estevam
2013-04-06  0:55 ` [U-Boot] [PATCH 2/3] mx6: Add solo-lite variant support Fabio Estevam
2013-04-06  0:55 ` [U-Boot] [PATCH 3/3] mx6sl: Add initial support for mx6slevk board Fabio Estevam
2013-04-06  7:27   ` Dirk Behme [this message]
2013-04-06 12:47     ` Fabio Estevam
2013-04-06 13:52       ` Dirk Behme
2013-04-06 14:15         ` Fabio Estevam
2013-04-06 16:30           ` Dirk Behme
2013-04-06 16:40             ` Fabio Estevam
2013-04-06 16:48               ` Dirk Behme
2013-04-10  6:01               ` Stefano Babic
2013-04-17  8:48               ` Stefano Babic
2013-04-21 17:00                 ` Fabio Estevam
2013-04-22  7:51                   ` Stefano Babic
2013-04-09 18:20 ` [U-Boot] [PATCH 1/3] iomux-v3: Place pad control definitions into common file Otavio Salvador

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=515FCE52.3070605@gmail.com \
    --to=dirk.behme@gmail.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 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.