public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] configs: ls1021atwr: Enable ID EEPROM for SD boot
Date: Wed, 14 Oct 2015 14:21:37 -0700	[thread overview]
Message-ID: <561EC761.2010504@freescale.com> (raw)
In-Reply-To: <1442994506-39691-1-git-send-email-yao.yuan@freescale.com>

On 09/23/2015 12:48 AM, Yuan Yao wrote:
> I2C1 can work on ls102xa rev2.0 SD boot, so add
> ID EEPROM for SD boot.
> 
> Signed-off-by: Yuan Yao <yao.yuan@freescale.com>
> ---
>  include/configs/ls1021atwr.h | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/include/configs/ls1021atwr.h b/include/configs/ls1021atwr.h
> index 7dcb719..59e704e 100644
> --- a/include/configs/ls1021atwr.h
> +++ b/include/configs/ls1021atwr.h
> @@ -278,7 +278,6 @@
>  #define CONFIG_SYS_I2C_MXC_I2C3		/* enable I2C bus 3 */
>  
>  /* EEPROM */
> -#ifndef CONFIG_SD_BOOT
>  #define CONFIG_ID_EEPROM
>  #define CONFIG_SYS_I2C_EEPROM_NXID
>  #define CONFIG_SYS_EEPROM_BUS_NUM		1
> @@ -286,7 +285,6 @@
>  #define CONFIG_SYS_I2C_EEPROM_ADDR_LEN		1
>  #define CONFIG_SYS_EEPROM_PAGE_WRITE_BITS	3
>  #define CONFIG_SYS_EEPROM_PAGE_WRITE_DELAY_MS	5
> -#endif
>  
>  /*
>   * MMC
> 

What would happen if you run the new u-boot image on earlier SoC? Do you need to
check SVR in function mac_read_from_eeprom()?

York

  reply	other threads:[~2015-10-14 21:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23  7:48 [U-Boot] [PATCH] configs: ls1021atwr: Enable ID EEPROM for SD boot Yuan Yao
2015-10-14 21:21 ` York Sun [this message]
2015-10-15  7:55   ` Yao Yuan
2015-10-15 16:40     ` York Sun
2015-10-15 19:37       ` Sinan Akman
2015-10-19  9:21         ` Yao Yuan
2015-10-19 11:14           ` Sinan Akman
2015-10-19 15:02             ` York Sun
2015-10-21  3:59               ` Yao Yuan
2015-10-21  5:37                 ` York Sun
2015-10-30 16:21 ` York Sun

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=561EC761.2010504@freescale.com \
    --to=yorksun@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