From: Andrei Kartashev <a.kartashev@yadro.com>
To: Nikhil V <nikhil.vu@zohocorp.com>, openbmc <openbmc@lists.ozlabs.org>
Subject: Re: [ERROR: Nothing RPROVIDES 'u-boot-default-env']
Date: Mon, 3 Jan 2022 14:10:09 +0300 [thread overview]
Message-ID: <ff7a3d7fc5ed91ab62b935421f779a6407e817fc.camel@yadro.com> (raw)
In-Reply-To: <17e1f659f9b.c8f061fb4115.9212316766481010802@zohocorp.com>
Hello,
It's hard to say what's wrong without knowing of what are you exactly
doing. Since there is no such platform as "at91" in OpenBMC, we don't
know what recipe do you use for u-boot.
Generally, u-boot recipe should include u-boot.inc:
> require recipes-bsp/u-boot/u-boot.inc
This include file provide u-boot-default-env recipe
https://github.com/openbmc/openbmc/blob/master/poky/meta/recipes-bsp/u-boot/u-boot.inc#L215
On Mon, 2022-01-03 at 15:34 +0530, Nikhil V wrote:
> Hi,
> I am trying to build image for openbmc on SAMA5D27-som1-ek1
> development board made by microchip(atmel). SAMA5D27 board has yocto
> support.
> I have added meta-atmel layer to openbmc, while building/compiling
> using " bitbake obmc-phosphor-image ", I am facing following error,
>
> [ERROR: Nothing RPROVIDES 'u-boot-default-env']
>
> I have tried by updating with following content but didnt get any
> result.
> PREFERRED_PROVIDER_u-boot = "u-boot-at91"
> PREFERRED_PROVIDER_virtual/bootloader = "u-boot-at91"
>
> Can you help me to find a solution.
>
>
> Thanks & Regards,
> Nikhil Muley
>
>
>
--
Best regards,
Andrei Kartashev
next prev parent reply other threads:[~2022-01-03 11:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 10:04 [ERROR: Nothing RPROVIDES 'u-boot-default-env'] Nikhil V
2022-01-03 11:10 ` Andrei Kartashev [this message]
2022-01-03 11:36 ` Nikhil V
2022-01-03 12:30 ` Andrei Kartashev
2022-01-03 13:15 ` Nikhil V
2022-01-05 11:10 ` Nikhil V
2022-01-05 17:01 ` Patrick Williams
2022-01-06 6:13 ` Nikhil V
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ff7a3d7fc5ed91ab62b935421f779a6407e817fc.camel@yadro.com \
--to=a.kartashev@yadro.com \
--cc=nikhil.vu@zohocorp.com \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.