From: "Val Kondratenko" <valeriy.kondratenko@jci.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>,
"meta-freescale@lists.yoctoproject.org"
<meta-freescale@lists.yoctoproject.org>
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?
Date: Fri, 9 Jul 2021 19:22:44 +0000 [thread overview]
Message-ID: <BN6P132MB006816DD00714D82C23C07A2E1189@BN6P132MB0068.NAMP132.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAOMZO5APHLjiiqzchiZE1wndcNqRXxQ7X3Y0dhTHyj5LS0M5NA@mail.gmail.com>
As is, in the 5.12 upstream branch, RPM (specifically imx7D to M4) should just work?
Amount of code in this area seems minimal compared to meta-freescale 5.4 releases.
With most of the functionality that used to be in /drivers/rpmsg/imx_rpmsg.c no longer present.
Thanks in advance,
Val
-----Original Message-----
From: Fabio Estevam <festevam@gmail.com>
Sent: Friday, June 11, 2021 12:19 PM
To: Val Kondratenko <valeriy.kondratenko@jci.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>; meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?
Hi Val,
On Fri, Jun 11, 2021 at 12:12 PM Val Kondratenko <valeriy.kondratenko@jci.com> wrote:
>
> One other thing I see missing in 5.12, that was in freeescale 5.4, is the rpmsg (Remote Processor Messaging) functionality.
In mainline, this is handled by the drivers/remoteproc/imx_rproc.c driver.
Regards,
Fabio Estevam
next prev parent reply other threads:[~2021-07-09 19:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 12:34 Safe to upgrade to a Community BSP? Val Kondratenko
2021-06-10 19:43 ` [meta-freescale] " Otavio Salvador
2021-06-10 20:18 ` Val Kondratenko
2021-06-10 21:11 ` Fabio Estevam
2021-06-11 15:12 ` Val Kondratenko
2021-06-11 16:19 ` Fabio Estevam
2021-06-11 16:42 ` Val Kondratenko
2021-07-09 19:22 ` Val Kondratenko [this message]
2021-06-23 17:48 ` Val Kondratenko
2021-06-23 20:05 ` Fabio Estevam
[not found] ` <16878FD7EE6FE05F.27948@lists.yoctoproject.org>
2021-06-25 17:53 ` Val Kondratenko
2021-06-25 18:11 ` Fabio Estevam
2021-06-29 20:03 ` Val Kondratenko
2021-07-06 14:29 ` Val Kondratenko
[not found] ` <168BE6901ABD95ED.20408@lists.yoctoproject.org>
2021-06-25 18:28 ` Val Kondratenko
2021-07-09 19:08 ` Val Kondratenko
2021-06-10 20:14 ` Fabio Estevam
2021-06-10 20:21 ` Val Kondratenko
2021-07-07 11:48 ` Val Kondratenko
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=BN6P132MB006816DD00714D82C23C07A2E1189@BN6P132MB0068.NAMP132.PROD.OUTLOOK.COM \
--to=valeriy.kondratenko@jci.com \
--cc=festevam@gmail.com \
--cc=meta-freescale@lists.yoctoproject.org \
--cc=otavio.salvador@ossystems.com.br \
/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;
as well as URLs for NNTP newsgroup(s).