In message <[EMAIL PROTECTED]> you wrote: > I'm new to working on low level code like u-boot. Something I don't > understand is why things like the Ethernet address are stored in > eeprom instead of flash. Is this something to do with how boards are
This may have h/w design reasons. For example, you may want to have things like serial number, MAC address and other similar settings stick with a device even when you change the CPU module; in such situations it's much easier to place a EEPROM somewhere in the device itself; with a I2C bus you need only 3 wires. If you try to use NOR flash in a similar configuration, you have to route the full data and address bus and some other signals, which is much more expensive. > manufactured? From a high level perspective it doesn't seem to matter > if eeprom or flash is used. Well, it does matter. Flash is much more reliable. Read for example doc/I2C_Edge_Conditions what can (and does!) happen to I2C attached EEPROM devices. And with flash, we can even store the data redun- dantly, so you have really good reliability. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] Making files is easy under the UNIX operating system. Therefore, users tend to create numerous files using large amounts of file space. It has been said that the only standard thing about all UNIX systems is the message-of-the-day telling users to clean up their files. -- System V.2 administrator's guide ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ U-Boot-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/u-boot-users
