[PATCH] beaglebone capes: Added CBB-Relay cape dt overlay

GoogleGroups
1

Added Device Tree overlay for the CBB-Relay cape and fixed a copy and paste
error in a comment in /firmware/Makefile.

signed-off-by: Alexander Hiam <hiamalexander@gmail.com>

2

Thanks Alexander!

Just added this to the "bone50" patchset.

Regards,

3

Great, thanks Robert.

By the way, I’ve noticed that all the cape overlays these days have the ‘cape-’ prefix. Are you moving toward a standard naming convention? I would have done so on this one but the cape was already in production.

-Alex

4

I think at one time there was a standard. However with a 16 character
limit to the cape overlay name, it's hard to force everyone to burn 5
characters with the same prefix. So as long as it's reasonably
generic and descriptive, i'm fine with it. :wink:

Regards,

5

For example, Charles just noticed that a few capes violated the 16
character spec, so they would not load anyways..

https://github.com/RobertCNelson/linux-dev/commit/fe100ee424d5f1761eaad565114bbc3e9b42c3ff

So they are fixed now..

Regards,

6

Great, thanks Robert.

By the way, I've noticed that all the cape overlays these days have the
'cape-' prefix. Are you moving toward a standard naming convention? I would
have done so on this one but the cape was already in production.

I think at one time there was a standard. However with a 16 character
limit to the cape overlay name, it's hard to force everyone to burn 5
characters with the same prefix. So as long as it's reasonably
generic and descriptive, i'm fine with it. :wink:

For example, Charles just noticed that a few capes violated the 16
character spec, so they would not load anyways..

capes: Firmware: Update Replicape device tree overlay files Files · RobertCNelson/linux-dev@fe100ee · GitHub

So they are fixed now..

Is GitHub - beagleboard/kernel at 3.8 up-to-date?

7

Great, thanks Robert.

By the way, I’ve noticed that all the cape overlays these days have the
‘cape-’ prefix. Are you moving toward a standard naming convention? I would
have done so on this one but the cape was already in production.

I think at one time there was a standard. However with a 16 character
limit to the cape overlay name, it’s hard to force everyone to burn 5
characters with the same prefix. So as long as it’s reasonably
generic and descriptive, i’m fine with it. :wink:

For example, Charles just noticed that a few capes violated the 16
character spec, so they would not load anyways…

https://github.com/RobertCNelson/linux-dev/commit/fe100ee424d5f1761eaad565114bbc3e9b42c3ff

So they are fixed now…

Is https://github.com/beagleboard/kernel/tree/3.8 up-to-date?

It’s lagging a few of the recent commits, I’ll push to it tomorrow as my push scripts for that tree and the raw kernel tree are on my laptop at work.