All of lore.kernel.org
 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 11:20:49 -0700	[thread overview]
Message-ID: <485BF501.4070702@gmail.com> (raw)
In-Reply-To: <485BF3F3.4040104@freescale.com>

Timur Tabi wrote:
> Ben Warren wrote:
>
>   
>> 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? 
>>     
>
> No.  The plan is to better support does boards that *do* have MAC addresses in
> EEPROM.
>
> (Actually, I have no idea what the board designers are planning on doing in the
> future.  I just know what doesn't work today).
>
> One of the problems is that the CRC value in the EEPROM is not programmed during
> manufacturing, but the current version of the code will refuse to read MAC
> addresses if the CRC doesn't match.  So out of the box, the BSPs never use the
> EEPROM for anything.  The user has to rewrite the EEPROM.
>
>   
Oh.  OK.
>> 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.
>>     
>
> True, but it would be nice if the code worked properly. :-)
>
>   
That's for sure.  Thanks for the clarification.

Ben

  reply	other threads:[~2008-06-20 18:20 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
2008-06-20 18:16   ` Timur Tabi
2008-06-20 18:20     ` Ben Warren [this message]
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=485BF501.4070702@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 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.