.
- Steve Pavao
Korg R&D
.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
the cm3 mentions the rpi3.
A colleague wonders if there are any differences that
someone was planning to eventually use that cm3 conf to enumerate, otherwise -
having a cm3 conf seems like unnecessary duplication.
Thanks again for your help!
- Steve Pavao
Korg R&D
> On May 1, 2018, at
for my purpose, and what is the
recommended syntax to achieve this conditional exclusion in my local.conf.
Thanks in advance for any ideas.
- Steve Pavao
Korg R&D
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/list
re
Question: How serious is this warning, and what should I do about it?
- Steve Pavao
Korg R&D
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
ailable
NOTE: Tasks Summary: Attempted 5203 tasks of which 5 didn't need to be rerun
and all succeeded.
Summary: There were 3 WARNING messages shown.
- Steve Pavao
Korg R&D
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Would you please add the bcm2710-rpi-cm3.dtb to the KERNEL_DEVICETREE listing
in raspberrypi3-64.conf in sumo branch? It’s missing.
- Steve Pavao
Korg R&D
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Hello -
I’m trying to build using a custom 64-bit kernel at head of sumo, but I get an
error. It seems that SRCPV cannot be resolved.Please send any ideas you
may have about how I may adapt my recipe to get it to work.
Normally, I use the default meta-raspberrypi kernel, but for this build
> On Jul 26, 2018, at 9:57 PM, ChenQi wrote:
>
> On 07/27/2018 12:56 AM, Steve Pavao wrote:
>> Hello -
>>
>> I’m trying to build using a custom 64-bit kernel at head of sumo, but I get
>> an error. It seems that SRCPV cannot be resolved.Please send any i
On Jul 26, 2018, at 12:56 PM, Steve Pavao wrote:
>
> I’m trying to build using a custom 64-bit kernel at head of sumo, but I get
> an error. It seems that SRCPV cannot be resolved.Please send any ideas
> you may have about how I may adapt my recipe to get it to work.
[sni
file listings to show that one of the builds contains kernel
modules (rpi-hwup-image) and the other does not (core-image-minimal).
Steve Pavao
Korg R&D
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Hello,
> On Aug 15, 2018, at 11:54 AM, Khem Raj wrote:
>
> On Tue, Aug 14, 2018 at 11:48 PM Steve Pavao <mailto:ste...@korgrd.com>> wrote:
>>
>> There seems to be a problem with the core-image-minimal bitbake for
>> raspberrypi3-64 target at head of sumo
Hello,
> On Aug 15, 2018, at 4:27 PM, Khem Raj wrote:
>
> On Wed, Aug 15, 2018 at 1:25 PM Steve Pavao wrote:
>> I would like to state my opinion though that to unconditionally warn the
>> user to use core-image-minimal instead of rpi-hwup-image (which definitely
>&
what I can do in my Yocto configuration so I can
rebake and not experience this problem?
Booting my system with the regular raspberrypi /linux kernel completes OK and
finishes with an X11 terminal on the HDMI.
- Steve Pavao
Korg R&D
--
___
y
way to avoid this
problem?
- Steve Pavao
Korg R&D
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 4
| ERROR: oe_runmake failed
| make os=EmbeddedLinuxAarch64 Daemon libdns_sd -C mDNSPosix
| make[1]: warning: jobserver unavailable: using -j1. Add '+'
IMAGE_INSTALL_append to get this far.
- Steve Pavao
Korg R&D
Build Configuration:
BB_VERSION= "1.34.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS= "aarch64-poky-linux"
MACHINE = "raspberry
nable mdns"
EXTRA_IMAGE_FEATURES ?= "debug-tweaks x11-base tools-debug tools-testapps
ssh-server-dropbear package-management"
- Steve Pavao
Korg R&D
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
console-latest.log and looking for
the highest kernel version I can observe from the recipes used. Is there a
better way to find this out at build time?
Knowing the kernel version would help me decide what version of a patch to
apply to go along with it.
Steve Pavao
Korg R&a
other layers such as meta or the BSP
layer?
Currently, I notice that architecture-level symbols are available to my custom
layer at compile time, such as __aarch64_ and __arm__, but not CPU tune
information, such as __ARM_ARCH_6__.
- Steve Pavao
Korg R&a
Hi Andre,
> On Mar 19, 2018, at 5:32 PM, Andre McCurdy wrote:
>
> On Mon, Mar 19, 2018 at 9:49 AM, Steve Pavao wrote:
>> What’s the recommended way to be able to propogate target-specific
>> compile-time CPU tune information to affect the build of a source file in my
witch causes libtool link to
fail due to missing libbz2.so. If I don’t specify the switch, the build
completes without errors.
It is important to be able to build poky linux with this switch to avoid
certain crash conditions as described in the ARM errata document.
Steve Pavao
Kor
lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "armv7a"
IMAGE_INSTALL_append += " vcgencmd lib32-glibc lib32-libgcc lib32-libstdc++
vcdbg rpi-setup \
“
I will post again when I have localized the build problem further.
> On Nov 4, 2019, at 11:11 AM, Adrian Bunk wrote:
>
> On Mon, Nov 04, 2019 at 10:48:57AM -0500, Steve Pavao wrote:
>>
>>> On Nov 3, 2019, at 1:25 PM, Adrian Bunk wrote:
>>>
>>> On Sun, Nov 03, 2019 at 05:56:45PM +, Andrei Gherzan wrote:
>
> On Nov 4, 2019, at 11:16 AM, Steve Pavao wrote:
>
>>
>> On Nov 4, 2019, at 11:11 AM, Adrian Bunk > <mailto:b...@stusta.de>> wrote:
>>
>> On Mon, Nov 04, 2019 at 10:48:57AM -0500, Steve Pavao wrote:
>>>
>>>> On Nov 3, 2
> On Nov 4, 2019, at 11:32 AM, Steve Pavao wrote:
>
>>
>> On Nov 4, 2019, at 11:16 AM, Steve Pavao > <mailto:ste...@korgrd.com>> wrote:
>>
>>>
>>> On Nov 4, 2019, at 11:11 AM, Adrian Bunk >> <mailto:b...@stusta.de>> wrote:
> On Nov 4, 2019, at 4:26 PM, Steve Pavao wrote:
>
>> On Nov 4, 2019, at 11:32 AM, Steve Pavao wrote:
>>>
>>> On Nov 4, 2019, at 11:16 AM, Steve Pavao wrote:
>>>>
>>>> On Nov 4, 2019, at 11:11 AM, Adrian Bunk wrote:
>>>>
25 matches
Mail list logo