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 jbda...@gmail.com wrote:
On
Gerald,
That makes sense. It sounds like, from the SRM's standpoint this data
is required whether or not software makes use of it.
Thanks for the response,
Josh
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google
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.
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
The SRM defines a very specific format for BeagleBone Black cape
EEPROMs[1]. AFAIK, the only fields that are actually required are the Board
Name and Version, which is used on boot to load the appropriate DTS file.
If this is the case can we change the other fields to optional?
There's a lot
