From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tabi Timur-B04825 <B04825@freescale.com>
Date: Sun, 15 Jul 2012 12:52:52 +0000
Subject: [U-Boot] [PATCH] fsl: board EEPROM has the CRC in the wrong
 location
In-Reply-To: <C5EFF1F960B6FC4C873CF9BD5FE250210791DCC8@039-SN2MPN1-013.039d.mgd.msft.net>
References: <1342129594-7861-1-git-send-email-timur@freescale.com>
	<9F5356FB-8CA2-44DE-9089-64ABD82CA733@freescale.com>
	<20120713043026.00DD82000B1@gemini.denx.de>
	<50001038.50303@freescale.com>
	<20120713212501.4C8132000F2@gemini.denx.de>
	<500096E0.9010406@freescale.com> <500098F6.8050702@freescale.com>
	<20120713230100.5E9C1200320@gemini.denx.de>
	<5000AB43.6090406@freescale.com>
	<C5EFF1F960B6FC4C873CF9BD5FE250210791DCC8@039-SN2MPN1-013.039d.mgd.msft.net>
Message-ID: <5002BD23.1030802@freescale.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Or Yoram-R56270 wrote:
> 1. Correct the v1 documentation to specify 23 MAC addresses and placing the CRC at 0xCC.
> 2. Create a new code and documentation for v2, specifying 31 MAC addresses and placing the CRC at 0xFC.

Both of these are unnecessary.  My patch fixes the code to match the spec 
*and* handles the CRC problem transparently.  It also doesn't do anything 
controversial that the current code doesn't already do.  Really, this is a 
non-issue.

-- 
Timur Tabi
Linux kernel developer at Freescale