From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] powerpc/eeprom: update MAX_NUM_PORTS to adapt non-256-bytes EEPROM
Date: Tue, 3 Sep 2013 10:29:02 -0700 [thread overview]
Message-ID: <52261C5E.50608@freescale.com> (raw)
In-Reply-To: <CAOZdJXXvMCvoVBncoanZeMjWFXc_SP8+9bcgF4O8kHYZLFXwKA@mail.gmail.com>
On 08/30/2013 06:56 AM, Timur Tabi wrote:
> On Fri, Aug 30, 2013 at 5:07 AM, Shengzhou Liu
> <Shengzhou.Liu@freescale.com> wrote:
>
>> #ifdef CONFIG_SYS_I2C_EEPROM_NXID
>> +/* some boards with non-256-bytes EEPROM have special define */
>> +/* for MAX_NUM_PORTS in board-specific file */
>> +#ifndef MAX_NUM_PORTS
>> #define MAX_NUM_PORTS 23
>> +#endif
>> #define NXID_VERSION 1
>> #endif
>
> I'll have to think about this. On one hand, this works. As long as
> the board-specific value of MAX_NUM_PORTS is valid, then it will work.
>
> On the other hand, it's fragile and violates the specification. An
> NXID v1 EEPROM has the CRC at offset 0xFC. I'm just not sure it
> really matters.
We need to verify the CRC is still valid.
>
> York, I'm okay with this patch if you are. You're the one maintaining
> this code now. Is there anyone left at Freescale who cares about the
> integrity of the EEPROM specification?
Some many boards pop up from different design groups. Unfortunately not
all came to us to review. It is often too late when we find the design
is different.
York
next prev parent reply other threads:[~2013-09-03 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 10:07 [U-Boot] [PATCH] powerpc/eeprom: update MAX_NUM_PORTS to adapt non-256-bytes EEPROM Shengzhou Liu
2013-08-30 13:56 ` Timur Tabi
2013-09-03 17:29 ` York Sun [this message]
2013-09-04 2:37 ` Liu Shengzhou-B36685
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=52261C5E.50608@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