Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Naveen Saini" <naveen.kumar.saini@intel.com>
To: Amit Kucheria <amit.kucheria.ext@huawei.com>,
	"amit.kucheria@verdurent.com" <amit.kucheria@verdurent.com>,
	"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>,
	Wojciech Zmuda <wojciech.zmuda@huawei.com>,
	Andrei Gherzan <andrei.gherzan@huawei.com>
Subject: Re: [meta-zephyr][PATCHv2 1/5] zephyr-kernel: Clone mbedtls
Date: Wed, 9 Jun 2021 02:41:52 +0000	[thread overview]
Message-ID: <d7faaa13286f43c39f52da682adfbf3b@intel.com> (raw)
In-Reply-To: <21f4e4928aa1406c98c6d0ae974b5d9c@huawei.com>

Made few changes in this patch. Re-sent patchset including some additional patches.

Regards,
Naveen

> -----Original Message-----
> From: Amit Kucheria <amit.kucheria.ext@huawei.com>
> Sent: Tuesday, June 8, 2021 7:11 PM
> To: Saini, Naveen Kumar <naveen.kumar.saini@intel.com>;
> amit.kucheria@verdurent.com; yocto@lists.yoctoproject.org; Wojciech
> Zmuda <wojciech.zmuda@huawei.com>; Andrei Gherzan
> <andrei.gherzan@huawei.com>
> Subject: RE: [meta-zephyr][PATCHv2 1/5] zephyr-kernel: Clone mbedtls
> 
> Hi Naveen,
> 
> I'll take a look with the specific revision ID mentioned. I don't see a build
> failure here locally.
> 
> On a related note, since 2.6 is now released, should we just focus on getting
> all this working on 2.6 (assuming you'll move meta-zephyr to it soon)?
> 
> Regards,
> Amit
> 
> > -----Original Message-----
> > From: Saini, Naveen Kumar [mailto:naveen.kumar.saini@intel.com]
> > Sent: 08 June 2021 16:10
> > To: amit.kucheria@verdurent.com; yocto@lists.yoctoproject.org;
> > Wojciech Zmuda <wojciech.zmuda@huawei.com>; Andrei Gherzan
> > <andrei.gherzan@huawei.com>
> > Cc: Amit Kucheria <amit.kucheria.ext@huawei.com>
> > Subject: RE: [meta-zephyr][PATCHv2 1/5] zephyr-kernel: Clone mbedtls
> >
> > Build failing:
> >
> > Could not open 'poky/build-zephyr/tmp-newlib/work/armv7m-yocto-
> > eabi/zephyr-mqtt-publisher/2.5.0+gitAUTOINC+fe7c2efca8_c3bd2094f9-
> > r0/git/' (in 'osource "$(ZEPHYR_MBEDTLS_KCONFIG)"') (EISDIR: Is a
> > directory)
> >
> >
> >
> > To fix, can you try following revision for mbedtls.
> >     - name: mbedtls
> >       revision: 24d84ecff195fb15c889d9046e44e4804d626c67
> > https://github.com/zephyrproject-rtos/zephyr/blob/zephyr-
> > v2.5.0/west.yml#L94
> >
> > Regards,
> > Naveen
> >
> >
> >
> > > -----Original Message-----
> > > From: amit.kucheria@verdurent.com <amit.kucheria@verdurent.com>
> > > Sent: Monday, June 7, 2021 2:01 PM
> > > To: yocto@lists.yoctoproject.org; wojciech.zmuda@huawei.com;
> > > andrei.gherzan@huawei.com; Saini, Naveen Kumar
> > > <naveen.kumar.saini@intel.com>
> > > Cc: Amit Kucheria <amit.kucheria.ext@huawei.com>
> > > Subject: [meta-zephyr][PATCHv2 1/5] zephyr-kernel: Clone mbedtls
> > >
> > > From: Amit Kucheria <amit.kucheria.ext@huawei.com>
> > >
> > > MBed TLS is a library that implements cryptographic primitives and
> > > SSL/TLS and DTLS protocols that are needed in secure network
> > communications.
> > >
> > > Add it to the kernel include files to build and link against
> > > applications that need mbedtls.
> > >
> > > Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>
> > > ---
> > >  recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc    | 1 +
> > >  recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc | 1 +
> > >  recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc       | 1 +
> > >  3 files changed, 3 insertions(+)
> > >
> > > diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
> > > b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
> > > index 330fe59aebe5..c9acbbbc3645 100644
> > > --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
> > > +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
> > > @@ -28,6 +28,7 @@ ZEPHYR_MODULES = ""
> > >  ZEPHYR_MODULES_append_arm = "\;${S}/modules/cmsis"
> > >  ZEPHYR_MODULES_append_nordic = "\;${S}/modules/hal/nordic"
> > >  ZEPHYR_MODULES_append_stm32 = "\;${S}/modules/hal/stm32"
> > > +ZEPHYR_MODULES_append_mbedtls = "\;${S}/modules/lib/mbedtls"
> > >  ZEPHYR_MODULES_append_openamp = "\;${S}/modules/lib/open-
> > > amp\;${S}/modules/hal/libmetal"
> > >
> > >  EXTRA_OECMAKE_append = " -
> DZEPHYR_MODULES=${ZEPHYR_MODULES}"
> > > diff --git
> > > a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc
> > > b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc
> > > index 5d66f0f3cb5b..3aeb3bf6fc3f 100644
> > > --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc
> > > +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc
> > > @@ -6,6 +6,7 @@ SRCREV_stm32 =
> > > "cc8731dba4fd9c57d7fe8ea6149828b89c2bd635"
> > >  SRCREV_open-amp = "de1b85a13032a2de1d8b6695ae5f800b613e739d"
> > >  SRCREV_libmetal = "9d4ee2c3cfd5f49861939447990f3b7d7bf9bf94"
> > >  SRCREV_tinycrypt = "3e9a49d2672ec01435ffbf0d788db6d95ef28de0"
> > > +SRCREV_mbedtls = "5765cb7f75a9973ae9232d438e361a9d7bbc49e7"
> > >
> > >  PV = "2.5.0+git${SRCPV}"
> > >
> > > diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
> > > b/recipes- kernel/zephyr-kernel/zephyr-kernel-src.inc
> > > index 1d06d916a1e0..069fa561667c 100644
> > > --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
> > > +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
> > > @@ -13,6 +13,7 @@ SRC_URI = "\
> > >      git://github.com/zephyrproject-
> > > rtos/cmsis.git;protocol=https;destsuffix=git/modules/cmsis;name=cmsis
> \
> > >      git://github.com/zephyrproject-
> > > rtos/hal_nordic.git;protocol=https;destsuffix=git/modules/hal/nordic
> > > ;n
> > > ame=
> > > nordic \
> > >      git://github.com/zephyrproject-
> > > rtos/hal_stm32.git;protocol=https;destsuffix=git/modules/hal/stm32;n
> > > am
> > > e=
> > > stm32 \
> > > +
> > > + git://github.com/zephyrproject-rtos/mbedtls.git;protocol=https;des
> > > + ts uf fix=git/modules/lib/mbedtls;name=mbedtls \
> > >      git://github.com/zephyrproject-rtos/open-
> > > amp.git;protocol=https;destsuffix=git/modules/lib/open-
> amp;name=open
> > > -
> > > amp \
> > >      git://github.com/zephyrproject-
> > > rtos/libmetal.git;protocol=https;destsuffix=git/modules/hal/libmetal
> > > ;n
> > > ame=l
> > > ibmetal \
> > >      git://github.com/zephyrproject-
> > > rtos/tinycrypt.git;protocol=https;destsuffix=git/modules/crypto/tiny
> > > cr
> > > ypt;na
> > > me=tinycrypt \
> > > --
> > > 2.25.1


  parent reply	other threads:[~2021-06-09  2:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07  6:00 [meta-zephyr][PATCHv2 0/5] zephyr-kernel: Clone mbedtls amit.kucheria
2021-06-07  6:00 ` [meta-zephyr][PATCHv2 1/5] " amit.kucheria
2021-06-08 10:36   ` Naveen Saini
2021-06-08 10:39   ` Naveen Saini
     [not found]     ` <21f4e4928aa1406c98c6d0ae974b5d9c@huawei.com>
2021-06-09  2:41       ` Naveen Saini [this message]
2021-06-07  6:00 ` [meta-zephyr][PATCHv2 2/5] zephyr-echo-client: Add recipe for echo client amit.kucheria
2021-06-07  6:00 ` [meta-zephyr][PATCHv2 3/5] zephyr-http-client: Add recipe for http client amit.kucheria
2021-06-07  6:00 ` [meta-zephyr][PATCHv2 4/5] zephyr-websocket-client: Add recipe for websocket client amit.kucheria
2021-06-07  6:00 ` [meta-zephyr][PATCHv2 5/5] zephyr-mqtt-publisher: Add recipe for mqtt publisher amit.kucheria

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=d7faaa13286f43c39f52da682adfbf3b@intel.com \
    --to=naveen.kumar.saini@intel.com \
    --cc=amit.kucheria.ext@huawei.com \
    --cc=amit.kucheria@verdurent.com \
    --cc=andrei.gherzan@huawei.com \
    --cc=wojciech.zmuda@huawei.com \
    --cc=yocto@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox