On Thu, Apr 9, 2020, 12:52 PM Bruce Ashfield
wrote:
> On Thu, Apr 9, 2020 at 1:21 PM Sean McKay wrote:
> >
> > I don’t know offhand, but the kernel documentation seems relatively
> straightforward.
> >
> > I can start investigating in that direction and see how complex it looks
> like it’s
The simplest thing I've found is checking/comparing the BuildID that GCC embeds
in the ELF file after I force it to recompile. Eg:
$ file
tmp/work/qemux86_64-poky-linux/linux-yocto/5.2.28+gitAUTOINC+dd6019025c_992280855e-r0/linux-qemux86_64-standard-build/vmlinux
| egrep -o
On Thu, Apr 9, 2020 at 1:21 PM Sean McKay wrote:
>
> I don’t know offhand, but the kernel documentation seems relatively
> straightforward.
>
> I can start investigating in that direction and see how complex it looks like
> it’s going to be.
>
I can tweak linux-yocto in the direction of
I don't know offhand, but the kernel documentation seems relatively
straightforward.
I can start investigating in that direction and see how complex it looks like
it's going to be.
When you say that reproducible builds are turned on by default, is there a flag
somewhere that can be used to
On 4/9/20 11:42 AM, Sean McKay wrote:
Anyone have any thoughts or guidance on this?
It seems like a pretty major bug to me.
We’re willing to put the work in to fix it, and if it’s not something
the upstream community is interested in, I’ll just pick a solution for
us and go with it.
But
Anyone have any thoughts or guidance on this?
It seems like a pretty major bug to me.
We're willing to put the work in to fix it, and if it's not something the
upstream community is interested in, I'll just pick a solution for us and go
with it.
But if it's something that we'd like me to
Hi
Please give some information about your plafform.
Kernel release
u-boot release
architecture
ubifs or not
Michael
On Thu, Apr 9, 2020 at 4:25 PM Anders Montonen wrote:
>
> On 8 Apr 2020, at 14:59, JH wrote:
> >
> > I am running Yocto built Linux on an ARM device, it takes about more
> >
From: yocto@lists.yoctoproject.org On Behalf Of
akuster
Sent: Thursday, 9 April, 2020 9:58 AM
To: Jain, Sangeeta ; Richard Purdie
; yocto@lists.yoctoproject.org
Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
; Yeoh, Ee Peng ; Chan, Aaron
Chun Yew ; akuster...@gmail.com;
On 8 Apr 2020, at 14:59, JH wrote:
>
> I am running Yocto built Linux on an ARM device, it takes about more
> than 1 minutes to boot from NAND and kernel, any good strategy to
> reduce the ARM device booting time? I can think of cutting down
> unnecessary configures in kernel.
If you’re using
This fails in the ab.
https://errors.yoctoproject.org/Errors/Build/100954/
https://errors.yoctoproject.org/Errors/Details/401501/
On 4/1/20 7:27 PM, Aaron Chan wrote:
> Could someone please fix this simple piece?
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
Hi Rudolf,
I did some digging in imx-atf_1.0.bb and saw that it copies bl31-imx8mq.bin to
the imx-boot-tools folder in do_deploy().
In imx-boot_0.2.bb I can see that its do_compile is setup to run after
imx-atf's do_deploy:
>
> do_compile[depends] += " \
> virtual/bootloader:do_deploy \
> ${@'
On Thu, 2020-04-09 at 09:54 +0800, mohamad.noor.alim.hus...@intel.com wrote:
> From: Mohamad Noor Alim Hussin
>
> Using meta-intel with core-image-sato-(sdk)-ptest
> results in a hddimg size of more than 4 GB. Remove
> that image type from testing.
>
> hddimg is not built by default in dunfell
Hi Bruce,
On zeus, commit 20556f9b02:
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto/commit/arch/x86/kernel/cpu/mce/dev-mcelog.c?h=v5.2/standard/intel-x86=20556f9b022e6318ce8f48
used function "compat_ptr_ioctl" but in fact kernel of zeus has no such
function yet.
This caused a build
From: Arnd Bergmann
commit 2952db0fd51b0890f728df94ac563c21407f4f43 upstream
Many drivers have ioctl() handlers that are completely compatible between
32-bit and 64-bit architectures, except for the argument that is passed
down from user space and may have to be passed through compat_ptr()
in
14 matches
Mail list logo
