Adding board IDs to sys/contrib/octeon-sdk/cvmx-app-init.h

[Juli Mallett]

On Wed, Sep 7, 2011 at 12:37, Andrew Duane <aduane at juniper.net> wrote:
> I know this is a Cavium maintained file, there's even a comment inside that says:
>
>    /* Set aside a range for customer boards.  These numbers are managed
>     ** by Cavium.
>     */
>
> Is there a protocol for adding new board IDs? And, would it be a real problem if the board IDs were not between CVMX_BOARD_TYPE_CUST_PRIVATE_MIN and CVMX_BOARD_TYPE_CUST_PRIVATE_MAX? I'm trying to sort out some code additions to define our private boards, and they already have hardware IDs assigned and burned into them that are in the range of 1300 to 1600 or so.

Look at the ifdefs I added to that file to handle a couple of vendors
who went outside of those ranges or overlapped with other boards.
Just add an OCTEON_VENDOR_JUNIPER option and put your board-related
stuff behind an ifdef in the SDK and outside of it.

> I guess I could read the hardware IDs and add CVMX_BOARD_TYPE_CUST_PRIVATE_MIN as an offset, is that a reasonable approach?
>
> As a related question, is there a protocol for managing kernel configuration files that belong to a private platform?

I think probably not managing them in a FreeBSD.org tree makes the most sense :)