From: "Jon Mason" <jdmason@kudzu.us>
To: Khasim Mohammed <Khasim.Mohammed@arm.com>
Cc: Diego Sueiro <Diego.Sueiro@arm.com>,
"meta-arm@lists.yoctoproject.org"
<meta-arm@lists.yoctoproject.org>
Subject: Re: [meta-arm] [PATCH 1/2] arm/scp-firmware : allow setting scp log level to INFO or WARN
Date: Wed, 24 Jun 2020 23:11:11 -0400 [thread overview]
Message-ID: <20200625031111.GA17463@kudzu.us> (raw)
In-Reply-To: <DB8PR08MB49699B2CDA2A7AD1225E3A4FFA950@DB8PR08MB4969.eurprd08.prod.outlook.com>
On Wed, Jun 24, 2020 at 06:52:05PM +0000, Khasim Mohammed wrote:
> Hi Jon,
>
> ________________________________________
> From: meta-arm@lists.yoctoproject.org <meta-arm@lists.yoctoproject.org> on behalf of Jon Mason via lists.yoctoproject.org <jdmason=kudzu.us@lists.yoctoproject.org>
> Sent: Thursday, June 25, 2020 12:10 AM
> To: Diego Sueiro
> Cc: meta-arm@lists.yoctoproject.org
> Subject: Re: [meta-arm] [PATCH 1/2] arm/scp-firmware : allow setting scp log level to INFO or WARN
>
> On Tue, Jun 23, 2020 at 12:05:43AM -0700, Diego Sueiro wrote:
> > On Mon, Jun 22, 2020 at 03:18 PM, Khasim Mohammed wrote:
> >
> > >
> > > SCP code has been updated with new logging framework. The patch
> > > is to allow setting of log level parameter to INFO or WARN.
> > >
> > > Change-Id: I20ec19a9aa1bdb7f59c067d2344c299c057a088b
> > > Issue-Id: PLATFORMS-3134
> > > Signed-off-by: Khasim Syed Mohammed <khasim.mohammed@arm.com>
> >
> > Reviewed-by: Diego Sueiro <diego.sueiro@arm.com>
>
> > Pulled into master.
>
> Can you please apply these three patches to dunfell branch as well ?
>
> https://lists.yoctoproject.org/g/meta-arm/topic/patch_2_2/75039153?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,75039153
> https://lists.yoctoproject.org/g/meta-arm/topic/patch_1_2_arm_scp_firmware/75039137?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,75039137
> https://lists.yoctoproject.org/g/meta-arm/topic/patch_arm_fiptool/75039113?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,75039113
Looks like there is a problem on dunfell. When compiling for n1sdp, I
get the following error:
ERROR: Nothing PROVIDES 'virtual/arm-none-eabi-gcc-native' (but /home/jdm/yocto/meta-arm/meta-arm/recipes-bsp/scp-firmware/scp-firmware_git.bb DEPENDS on or otherwise requires it). Close matches:
virtual/mesa-native
ERROR: Required build target 'core-image-sato' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-sato', 'virtual/control-processor-firmware', 'virtual/arm-none-eabi-gcc-native']
Can you confirm it compiles for you?
Thanks,
Jon
>
>
> Thanks
>
> Khasim
>
> > Thanks,
> > Jon
>
> >
> > > ---
> > > meta-arm/recipes-bsp/scp-firmware/scp-firmware.inc | 2 ++
> > > meta-arm/recipes-bsp/scp-firmware/scp-firmware_git.bb | 2 +-
> > > 2 files changed, 3 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/meta-arm/recipes-bsp/scp-firmware/scp-firmware.inc
> > > b/meta-arm/recipes-bsp/scp-firmware/scp-firmware.inc
> > > index 1873848..2db59d3 100644
> > > --- a/meta-arm/recipes-bsp/scp-firmware/scp-firmware.inc
> > > +++ b/meta-arm/recipes-bsp/scp-firmware/scp-firmware.inc
> > > @@ -6,6 +6,7 @@ SCP_BUILD_RELEASE ?= "1"
> > > SCP_COMPILE_VERBOSE ?= "0"
> > > SCP_PLATFORM ?= "invalid"
> > > SCP_COMPILER ?= "arm-none-eabi"
> > > +SCP_LOG_LEVEL ?= "WARN"
> > >
> > > DEPENDS += "virtual/arm-none-eabi-gcc-native"
> > >
> > > @@ -39,6 +40,7 @@ EXTRA_OEMAKE = "${SCP_COMP_STR} \
> > > BUILD_PATH='${B}' \
> > > PRODUCT='${SCP_PLATFORM}' \
> > > MODE='${SCP_BUILD_STR}' \
> > > + LOG_LEVEL='${SCP_LOG_LEVEL}' \
> > > CC='${SCP_COMPILER}-gcc' \
> > > AR='${SCP_COMPILER}-ar' \
> > > SIZE='${SCP_COMPILER}-size' \
> > > diff --git a/meta-arm/recipes-bsp/scp-firmware/scp-firmware_git.bb
> > > b/meta-arm/recipes-bsp/scp-firmware/scp-firmware_git.bb
> > > index 5ff5859..9cb8b64 100644
> > > --- a/meta-arm/recipes-bsp/scp-firmware/scp-firmware_git.bb
> > > +++ b/meta-arm/recipes-bsp/scp-firmware/scp-firmware_git.bb
> > > @@ -13,7 +13,7 @@ SRC_URI = "\
> > >
> > > git://github.com/ARM-software/CMSIS_5.git;protocol=https;name=cmsis;destsuffix=src/cmsis;lfs=0;nobranch=1
> > > \
> > > "
> > >
> > > -SRCREV_scp = "db19910aca6d1032eb0329e5fbb70a92b997f6f2"
> > > +SRCREV_scp = "fd7c83561a7d76c7681d5d017fb23aa3664c028c"
> > > SRCREV_cmsis = "refs/tags/5.2.0"
> > > SRCREV_FORMAT = "scp_cmsis"
> > >
> > > --
> > > 2.17.1
> > >
> > >
>
> >
>
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
next prev parent reply other threads:[~2020-06-25 3:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 14:17 [PATCH 1/2] arm/scp-firmware : allow setting scp log level to INFO or WARN Khasim Mohammed
2020-06-22 14:17 ` [PATCH 2/2] arm-bsp/scp-firmware: Build SCP MCP firmware for N1SDP Khasim Mohammed
2020-06-23 7:05 ` Diego Sueiro
2020-06-24 18:40 ` [meta-arm] " Jon Mason
2020-06-23 7:05 ` [PATCH 1/2] arm/scp-firmware : allow setting scp log level to INFO or WARN Diego Sueiro
2020-06-24 18:40 ` [meta-arm] " Jon Mason
2020-06-24 18:52 ` Khasim Mohammed
2020-06-25 3:11 ` Jon Mason [this message]
2020-06-25 3:51 ` Khasim Mohammed
2020-06-25 16:34 ` Jon Mason
2020-06-25 17:00 ` Khasim Mohammed
2020-06-25 19:34 ` Jon Mason
[not found] ` <161B8F8F11B0E6F1.591@lists.yoctoproject.org>
2020-06-24 18:55 ` Khasim Mohammed
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=20200625031111.GA17463@kudzu.us \
--to=jdmason@kudzu.us \
--cc=Diego.Sueiro@arm.com \
--cc=Khasim.Mohammed@arm.com \
--cc=meta-arm@lists.yoctoproject.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.