From: "Fabio Estevam" <festevam@gmail.com>
To: Neuber Sousa <neuberfran@gmail.com>
Cc: meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] RPmsg in pico-imx7d using mainline linux (5.6.xx) and Yocto dunfell
Date: Tue, 17 Aug 2021 12:09:41 -0300 [thread overview]
Message-ID: <CAOMZO5C0xtLy+uRLdwRo7fDVT1mmSo6yTR=nQj5xuK3XZ7F=jA@mail.gmail.com> (raw)
In-Reply-To: <CABWL1Pm2AY-ARQW273YZZqAaXKhffnMvxLWZq=SxDOXr8_aWmQ@mail.gmail.com>
Hi Neuber,
I think you forgot to hit reply-all.
On Mon, Aug 16, 2021 at 10:55 AM Neuber Sousa <neuberfran@gmail.com> wrote:
>
> Hi Fabio,
>
> In this video: https://mail.google.com/mail/u/0/?tab=rm&ogbl#all/FMfcgzGkZsrTzPBfwTMTnDdMWlJRQlCW
>
> at 23 minutes and 17 seconds, Diego Suero uses the following files:
>
> ../arch/arm/mach-imx/mu.c
> ../drivers/rpmsg/imx_rpmsg.c
> ../drivers/rpmsg/imx_rpmsg_tty.c
>
> What are the equivalent files (on mainline linux, one of them seems to be: ../drivers/remoteproc/imx_rproc.c)
> so that I can implement RPmsg on mainline linux/device tree correctly?
The mailbox driver is at drivers/mailbox/imx-mailbox.c in mainline.
>
> Or is the approach to mainline linux (RPmsg) in imx7d-pico different?
>
>
> i.e.:I haven't had any problems with dunfell using kernel 5.6.xx at the moment.
Sure, feel free to use it. It is just that you will not get any
support from the community using this version.
Personally, I haven't used the remoteproc driver in mainline, so I
can't help you.
prev parent reply other threads:[~2021-08-17 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 1:50 RPmsg in pico-imx7d using mainline linux (5.6.xx) and Yocto dunfell Neuber Sousa
2021-08-16 12:28 ` [meta-freescale] " Fabio Estevam
[not found] ` <CABWL1Pm2AY-ARQW273YZZqAaXKhffnMvxLWZq=SxDOXr8_aWmQ@mail.gmail.com>
2021-08-17 15:09 ` Fabio Estevam [this message]
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='CAOMZO5C0xtLy+uRLdwRo7fDVT1mmSo6yTR=nQj5xuK3XZ7F=jA@mail.gmail.com' \
--to=festevam@gmail.com \
--cc=meta-freescale@lists.yoctoproject.org \
--cc=neuberfran@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).