Robert Schwebel wrote: > Hi, > > On Fri, Jun 20, 2008 at 09:59:03AM -0500, 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. > > I don't know what NXID and CCID is, but have you seen Wolfram's proposal > for sub-devicetrees? > > http://ozlabs.org/pipermail/linuxppc-dev/2008-June/058263.html
This doesn't apply. CCID and NXID are Freescale-custom layouts for data in an EEPROM. NXID replaces CCID. I suppose we could replace NXID with something FDT-based, like Wolfram's proposal, but for now my goal is clean up the code that supports the existing formats. > Our aim here is to put device tree sniplets into eeproms or flash areas; > we have several boards here that consist of > > - a module > - a base board > - maybe an extension board > > and having sub devicetrees would make it possible to simply put the > devicetree for each component into a piece of storage *on the > component*. So the bootloader and later Linux would be able to build the > whole tree from these sniplets. Sounds complicated and interesting. I might think about it some more later. -- Timur Tabi Linux Kernel Developer @ Freescale ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
