Chris Johns commented on a discussion on bsps/powerpc/include/bsp/ppcbug-nvram-net-env.h: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1322#note_153023 > + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS > + * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) > + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, > STRICT > + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY > + * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF > + * SUCH DAMAGE. > + */ > + > +/* > + * PPCBug RTEMS Network Environment Variables > + * > + * Set the environment variables based on the NVRAM data. The pattern > + * for scanning follows the parsing that was in EPICS Base's > + * `setBootConfigFromNVRAM.c`. The code was moved to RTEMS as part of > + * a clean up of EPICS code. > + */ I was thinking of adding the supported environment variables to the BSP once these MRs are merged. The only place I have provided a complete list is in the [RTEMS Support Planning](https://github.com/epics-base/epics-base/discussions/851#discussioncomment-16848778) issue Andrew created. In terms of what environment variables we support there is no LibBSD documentation and adding that to add this seciton is a large piece of work that is out of scope for this change. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1322#note_153023 You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/4-0h7210yo2w9yaqv1hejdxct7i-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
