Andrew Johnson commented on a discussion on 
bsps/powerpc/qoriq/start/uboot_support.c: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1046#note_143513

 > + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 
 > PURPOSE
 > + * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
 > + * LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
 > + * CONSEQUENTIAL 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.
 > + */
 > +
 > +#include <stdint.h>
 > +
 > +#include <bsp.h>
 > +
 > +#if defined(HAS_UBOOT)

@sebhub Would you expect U-Boot on our MVME2500 boards to be providing a device 
tree to RTEMS? Can the QORIQ BSP look for and make use of a device tree if one 
is provided? Is there any RTEMS documentation on how that all works?

I would much prefer that we make use of a device tree if U-Boot can provide one 
and RTEMS can use it, but we didn't know anything about that when we started 
work on the BSP. Reading its environment variables was a solution we came up 
with to pass device configuration from U-Boot into the RTEMS image it loads 
from the network. If you have better suggestions we would sincerely appreciate 
your advice.

We want RTEMS to be able to reuse some of the configuration parameters that we 
have to set for U-Boot to load the OS image — mainly network settings, but 
passing a boot-line to our application would be useful too.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1046#note_143513
You're receiving this email because of your account on gitlab.rtems.org.


_______________________________________________
bugs mailing list
[email protected]
http://lists.rtems.org/mailman/listinfo/bugs

Reply via email to