I wrote the spec. This is what I wanted in there. I don't control what the SW population is able to handle. I prefer not to make a statement that all of sudden may become false based on a SW implementation event.
Gerald On Mon, Feb 9, 2015 at 8:03 PM, Josh Datko <[email protected]> wrote: > On Mon, 2015-02-09 at 20:08 -0500, Philip Polstra wrote: > > I remember populating this info for my XBee Cape, only to find that it > > is not used at all. I think it is still a good idea to have the info > > in there in case it is really used in the future. In theory it should > > be possible to have the cape configured without the need for a DTB > > file for each cape. > > The data in there is useful and I can think of some other useful data, > like a link to the elinux site. > > But if I put my manufacturer hat on, I want to know what's required and > what's recommended. For example, the CryptoCape doesn't populate the > week the board was made [1]. SparkFun uses it's own system AFIAK. > > I think that the EEPROM Spec, as written, doesn't match current > practice. Nice-to-haves are nice-to-have, but it would be nice if that > was indicated in the spec. ;) > > Josh > > [1] This is a result of my recommendation, so feel free to blame me, not > SparkFun on this one. > > > > > > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Gerald [email protected] http://beagleboard.org/ http://circuitco.com/support/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
