public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH v2] Update Freescale sys_eeprom.c to handle CCID formats
Date: Fri, 20 Jun 2008 09:45:57 -0700	[thread overview]
Message-ID: <485BDEC5.7010706@gmail.com> (raw)
In-Reply-To: <1213973943-22779-1-git-send-email-timur@freescale.com>

Hi Timur,

Timur Tabi wrote:
> Update the sys_eeprom.c file to handle both NXID and CCID EEPROM formats.  The
> NXID format replaces the older CCID format, but it's important to support both
> since most boards out there still use the CCID format.  This change is in
> preparation for using one file to handle both formats.  This will also unify
> EEPROM support for all Freescale 85xx and 86xx boards.
>
> Also update the 86xx board header files to use the standard CFG_I2C_EEPROM_ADDR
> instead of ID_EEPROM_ADDR.
>
> Signed-off-by: Timur Tabi <timur@freescale.com>
> ---
>
> This patch is the first in a series to clean up the MAC address determination
> in some of Freescale's board.  The ultimate goal is to get rid of
> CONFIG_ETHADDR and related macros in the board header files.
>
>   
So are you saying that the plan is to move much of the configuration 
information from NOR flash to I2C EEPROMs on Freescale evaluation 
boards?  I'm not suggesting that it's a good or bad idea, but just keep 
in mind that the main raison d'etre for these boards is to serve as 
starting points for customer designs, and I'm not sure the majority of 
customers would use things this way.

regards,
Ben

  reply	other threads:[~2008-06-20 16:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-20 14:59 [U-Boot-Users] [PATCH v2] Update Freescale sys_eeprom.c to handle CCID formats Timur Tabi
2008-06-20 16:45 ` Ben Warren [this message]
2008-06-20 18:16   ` Timur Tabi
2008-06-20 18:20     ` Ben Warren
2008-06-22 13:40 ` Robert Schwebel
2008-06-22 22:03   ` Timur Tabi
2008-06-23  6:35     ` Robert Schwebel
2008-06-24 21:04 ` Timur Tabi
2008-07-14 15:56   ` Timur Tabi

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=485BDEC5.7010706@gmail.com \
    --to=biggerbadderben@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox