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: Tue, 6 Jul 2021 14:29:34 +0000 [thread overview]
Message-ID: <BN6P132MB00685A9A91E60A7BE80E01D4E11B9@BN6P132MB0068.NAMP132.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <BN6P132MB00687499DD73E997185BC044E1029@BN6P132MB0068.NAMP132.PROD.OUTLOOK.COM>
.. resending, back to this, still seeing the error below.
Does anyone have any ideas of why "Module.symvers" would not be present in my 5.12 build, and how to get it there (or at least avoid the error).
Thanks,
Val
-----Original Message-----
From: Val Kondratenko
Sent: Tuesday, June 29, 2021 4:03 PM
To: Fabio Estevam <festevam@gmail.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?
Trying to compile the new kernel (and applying our patches from 5.4/modified).
Getting this error:
DEBUG: Executing shell function do_shared_workdir
cp: cannot stat 'Module.symvers': No such file or directory
WARNING: exit code 1 from a shell command.
ERROR: Function failed: do_shared_workdir
That is coming from attached patch file in:
./meta-freescale/recipes-kernel/kernel-modules/kernel-module-imx-gpu-viv
Does anyone know what that could be (looks like some type of symbol file)?
Will the meta-freescale area be something that has to be modified for kernel 5.12?
Thanks in advance,
Val
-----Original Message-----
From: Fabio Estevam <festevam@gmail.com>
Sent: Friday, June 25, 2021 2:11 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?
On Fri, Jun 25, 2021 at 2:53 PM Val Kondratenko <valeriy.kondratenko@jci.com> wrote:
>
> Is the following a recommended upstream u-boot?
>
> u-boot-v2021.04 from
> https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsour
> ce.denx.de%2Fu-boot%2Fu-boot%2F&data=04%7C01%7Cvaleriy.kondratenko
> %40jci.com%7Cae9a307ad535470174e808d93804a3b9%7Ca1f1e2147ded45b681a19e
> 8ae3459641%7C0%7C1%7C637602414841277553%7CUnknown%7CTWFpbGZsb3d8eyJWIj
> oiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&am
> p;sdata=u7VdtzbmyNsIyJAk5wMd%2BM%2FohubZx6qe6fwKmUEWvjA%3D&reserve
> d=0
Yes, that's a good one.
U-Boot 2021.07 should be available on July, 5th.
> The cpuidle functionality would be in?
>
> arch/arm/mach-imx/mx7/psci-mx7.c
>
> From when/which release U-boot started support cpuidle?
>
> Is there any documentation on how to move the cpuidle functionality from kernel to u-boot?
> What is involved there?
The PSCI mechanism in U-Boot will take care of it. No extra action is required.
next prev parent reply other threads:[~2021-07-06 14:29 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
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 [this message]
[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=BN6P132MB00685A9A91E60A7BE80E01D4E11B9@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 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.