PobodysNerfect has quit [Ping timeout: 256 seconds]
silbe has joined #yocto
silbe has quit [Remote host closed the connection]
camus has quit [Remote host closed the connection]
camus has joined #yocto
Guest65 has joined #yocto
<Guest65>
hi
<Guest65>
I want to create recipe which build secondary kernel image which I want to use kdump kernel booting after primary kernel image crashing during kexec
<Guest65>
any pointer how I Can build both primary and secondary kernel image in yocto-2.5 ?
ptsneves has quit [Ping timeout: 256 seconds]
olani has joined #yocto
prabhakarlad has joined #yocto
yannd has joined #yocto
bps has joined #yocto
Guest65 has quit [Quit: Client closed]
amsobr has joined #yocto
phako[m] has quit [Remote host closed the connection]
alvaropg[m] has joined #yocto
Perflosopher has quit [Ping timeout: 250 seconds]
Thorn has joined #yocto
Perflosopher has joined #yocto
florian_kc has joined #yocto
bps has quit [Read error: Connection reset by peer]
florian_kc has quit [Ping timeout: 240 seconds]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
mvlad has joined #yocto
ptsneves has joined #yocto
florian_kc has joined #yocto
mckoan_ has joined #yocto
prabhakarlad has quit [Quit: Client closed]
Perflosopher has quit [Ping timeout: 256 seconds]
mckoan has quit [Ping timeout: 240 seconds]
Perflosopher has joined #yocto
bps has joined #yocto
bps has quit [Changing host]
bps has joined #yocto
Guest66 has joined #yocto
Guest66 has quit [Client Quit]
florian_kc has quit [Ping timeout: 256 seconds]
goliath has joined #yocto
seninha has joined #yocto
<rburton>
ok what joker put me in the 0915 slot at EOSS
seninha has quit [Remote host closed the connection]
seninha has joined #yocto
<LetoThe2nd>
rburton: you're supposed to calm people down after me enraging them at 900
beroset has joined #yocto
marka has quit [Ping timeout: 248 seconds]
TundraMan has joined #yocto
<LetoThe2nd>
JPEW: got an idea off hand why the doom demo fails with a dependency chain to libx11-xcb when trying to build for BeaglePlay?
<jclsn>
I am getting a devtool error on hardknott, which we are unfortunately stuck on. The result of the error is that a path is not assembled correctly and thus some files to be copies into oe-local-files can't be found. One of our colleagues found a workaround by removing http://ix.io/4xPA and copying the required files manually. Is there maybe a fix for this in later releases we could backport?
<JPEW>
Hmm... No. It's not using X, but Wayland/Weston instead
<JPEW>
LetoThe2nd: what's the error?
<LetoThe2nd>
JPEW: its just the dependency chain. now trying with lzdoom and x11 as a DISTRO_FEATURE.
<jclsn>
devtool seems to append too many subfolders to the path
bps has joined #yocto
bps has joined #yocto
zpfvo has joined #yocto
amitk has quit [Ping timeout: 268 seconds]
<mason>
I'm curious what the default cron is in poky. It appears to be ignoring /etc/cron.hourly, and while run-parts sees jobs as intended, run-parts is part of busybox and evidently cron is not.
<jclsn>
Also: I am having trouble to build the kernel in the workspace with the defconfig in our recipe. I need to do this to generate the compile_commands.json for clangd. Is there a way to copy the currently used defconfig over as .config to the workspace with devtool?
goliath has quit [Quit: SIGSEGV]
Thorn has quit [Ping timeout: 246 seconds]
sakoman has joined #yocto
xmn has joined #yocto
<jclsn>
You can generate a compile_commands.json in the work folder, but it doesn't work afterwards. You can't jump to any headers. How do you do that?
<JPEW>
So, when you start weston from the command line that way, you have to specify a tty manually; so try `weston --tty=7`
<JPEW>
But be aware; that allocates the TTY and I don't know how to unallocate it manually
<JPEW>
So you can't use --tty=7 again until you reboot
<LetoThe2nd>
funny, now that gave me that is is already in graphic mode. doom however still fails due to not initializing SDL
<JPEW>
But weston runs?
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
<LetoThe2nd>
seems to
<LetoThe2nd>
could it be because i went for lzdoom?
<JPEW>
I don't think so?
<LetoThe2nd>
the standard fails in Missing or unbuildable dependency chain was: ['core-image-doom', 'oe-doom-launcher', 'zdoom', 'gzdoom-native', 'libvpx-native']
<JPEW>
Ah
<JPEW>
Perhaps not as kirkstone compatible as initially though; I patched libvpx in master
<JPEW>
6aa414ea0 ("libvpx: Explicitly link with pthread support")
<LetoThe2nd>
ahaaa
<LetoThe2nd>
where did you patch that?
<JPEW>
meta-openembedded
nemik has quit [Ping timeout: 256 seconds]
user12346 has quit [Max SendQ exceeded]
<LetoThe2nd>
ok, seems I have to put that into an additional layer for me
Minvera2 has quit [Ping timeout: 250 seconds]
<LetoThe2nd>
thanks, will let you know then.
user12346 has joined #yocto
<JPEW>
The other option might be to make a kirkstone branch in oe-doom-demo and patch it in a bbappend
<LetoThe2nd>
yup
nemik has joined #yocto
PhoenixMage has quit [Ping timeout: 248 seconds]
seninha has joined #yocto
bps has quit [Ping timeout: 246 seconds]
bps has joined #yocto
bps has joined #yocto
bps has quit [Changing host]
user12346 has quit [Remote host closed the connection]
user12346 has joined #yocto
user12346 has quit [Max SendQ exceeded]
user12346 has joined #yocto
<s11c>
Hello. I am having trouble setting up a custom kernel config. I followed the instructions from the manual, and put my working .config file in my layer as defconfig. The problem is that when I build the kernel, it seems to change the config with some default values and I get a bunch of warnings about values not being valid and not included in the final config
<s11c>
I have tried just about everything I can find in the manual, but no luck. Is it not possible to just completely replace the .config file when using the yocto-linux recipe?
PhoenixMage has joined #yocto
<mason>
Oh, to answer my question from earlier, cronie, and there are bits of both cronie and busybox's cron mixed together brokenly.
<rburton>
you should file a bug about that, please
<rburton>
(or a patch but a bug would do)
<zeddii>
s11c: depends on how you created the defconfig, is it created with savedefconfig ? if so you need to set KCONFIG_MODE to be alldefconfig, but no matter what you use, the kernel configuration subsystem will change some values, and that has nothing to do with the fragments.
<mason>
rburton: kk, will gather some data and do that
<s11c>
zeddii: I have tried both ways. I tried using savedefconfig, and using KCONFIG_MODE="alldefconfig". I also tried just copying the .config file and not setting that, and also using KCONFIG_MODE="nodefconfig".
<s11c>
s/nodefconfig/allnoconfig/
<s11c>
I was looking for some magic that would tell it to not apply the defconfig from the recipe, but I can't find a way to do that
<zeddii>
the kernel's config system is always run, defconfig or not. so there's usually a few changes based on what it does or doesn't pick up as dependencies, etc.
<zeddii>
the defconfig won't clobber a .config in place, if found. (in the base kernel.bbclass), since all of the linux-yocto builds do their own configuration and generate a .config, nothing else is run from kernel.bbclass.
<s11c>
Ok. Is there a way to append to a target to replace the config once it has been generated? (In my bbappend I mean)
<zeddii>
you can just append to the configuration task in your bbappend, but if you are tweaking the .config directly, or copying something in. on the compile step, the kernel will re-run the configuration processing itself.
<s11c>
Ok. This seems wrong, but I guess I'm going to have to create a full custom kernel layer. The changes that are made change the processor type among other things, which means I can't use the build for my board. It seems like this should be possible, but I guess not
Thorn has joined #yocto
<zeddii>
you definitely shouldn't have to do that, there's nothing in either the merge_config or the kernel's processing that would change architecture or processor type, unless the defconfig isn't being picked up at all, and arch defaults are being used instead. if this is with public layers, I could try and reproduce it and offer better guidance.
user12346 has quit [Quit: Leaving]
<s11c>
I am working with an old pc-104 with an amd geode-lx800 chip. I created my own layer with a machine that is basically a duplicate of the generic-x86 (32 bit) machine. I have a distro and image file, but so far I haven't customized too much... Let me try to find a minimal set that can reproduce the problem
Minvera has joined #yocto
florian_kc has joined #yocto
alessioigor has quit [Quit: alessioigor]
jmk1 has joined #yocto
<s11c>
zedddii: Ok, I think I have something you can reproduce. I started with a fresh checkout of poky, mickledore branch. I set the machine in local.conf to genericx86, and did bitbake linux-yocto. Once that was done, I ran menuconfig and changed 1 value. In the processor type and features, I changed the processor type from pentium to 586. I created a layer.. if you want I can gzip that or something but it just had 1 recipe with a bbappend
<s11c>
for the kernel. I copied the .config I generated into a file called defconfig and then did a clean and build on linux-yocto. This time it gave a bunch of warnings, and the processor was back to pentium
<s11c>
For just the processor type, I can fix that using a fragment instead of the full config, but I have a lot of changes I need to make and some can't seem to be done using fragments... I really just want to drop in a working .config file
bps has quit [Ping timeout: 265 seconds]
Minvera has quit [Remote host closed the connection]
goliath has joined #yocto
<zeddii>
have you defined your own machine ?
<s11c>
Yeah, I did. For the test I didn't, as it wasn't needed to duplicate the problem
florian_kc has quit [Ping timeout: 250 seconds]
<zeddii>
for the test, if you don't have a new machine defined, the generic x86 definition will be picked up and used, then the defconfig applied as just another fragment. you can't clobber a built in BSP meta-data description like that. if I'm understanding what you tried.
Minvera has joined #yocto
<s11c>
Ah, ok, I understand. For the machine I defined I will check and see if it's also picking up a definition... I didn't start with a machine, I just added one as part of my troubleshooting. I'll go check that... it may be that it is just a clone of the genericx86 machine or somethine so that's where the defaults are coming from
florian_kc has joined #yocto
prabhakarlad has quit [Quit: Client closed]
PobodysNerfect_ has quit [Quit: Gone to sleep. ZZZzzz…]
mvlad has quit [Remote host closed the connection]
Minvera2 has joined #yocto
PobodysNerfect has joined #yocto
Minvera has quit [Ping timeout: 240 seconds]
Minvera2 has quit [Remote host closed the connection]
Minvera2 has joined #yocto
goliath has quit [Quit: SIGSEGV]
florian_kc has quit [Ping timeout: 256 seconds]
PobodysNerfect has quit [Quit: Gone to sleep. ZZZzzz…]
PobodysNerfect has joined #yocto
vladest has quit [Read error: Connection reset by peer]