Vonter has quit [Read error: Connection reset by peer]
manuel1985 has quit [Ping timeout: 240 seconds]
rob_w has joined #yocto
camus1 has joined #yocto
camus has quit [Ping timeout: 258 seconds]
camus1 is now known as camus
zyga has joined #yocto
creich has joined #yocto
frieder has joined #yocto
Schlumpf has joined #yocto
goliath has joined #yocto
zpfvo has joined #yocto
tnovotny has joined #yocto
frieder has quit [Ping timeout: 246 seconds]
mckoan|away is now known as mckoan
<mckoan>
good morning
RobertBerger has quit [Quit: Leaving]
rber|res has joined #yocto
Schlumpf has quit [Quit: Client closed]
frieder has joined #yocto
zyga-mbp has joined #yocto
manuel1985 has joined #yocto
goliath has quit [Quit: SIGSEGV]
<qschulz>
mornin'
kayterina has joined #yocto
leon-anavi has joined #yocto
radek has joined #yocto
xmn has quit [Quit: ZZZzzz…]
Schlumpf has joined #yocto
Schlumpf has quit [Client Quit]
warthog9 has quit [Ping timeout: 258 seconds]
Schlumpf has joined #yocto
frieder has quit [Ping timeout: 258 seconds]
Schlumpf has quit [Quit: Client closed]
Schlumpf has joined #yocto
frieder has joined #yocto
zbr_ is now known as zibri
goliath has joined #yocto
<yates>
JPEW: thank you.
florian has joined #yocto
<yates>
mckoan, qschulz: good morning. couldn't sleep. still very early here in NC, USA
<qschulz>
yates: sorry to hear that
warthog9 has joined #yocto
rob_w_ has joined #yocto
rob_w has quit [Ping timeout: 252 seconds]
prabhakarlad has quit [Quit: Client closed]
prabhakarlad has joined #yocto
radek has quit [Quit: Leaving]
ndec_ is now known as ndec
LetoThe2nd has joined #yocto
jordemort has quit [Quit: Bridge terminating on SIGTERM]
shoragan[m] has quit [Quit: Bridge terminating on SIGTERM]
Andrei[m] has quit [Quit: Bridge terminating on SIGTERM]
kayterina[m] has quit [Quit: Bridge terminating on SIGTERM]
barath has quit [Quit: Bridge terminating on SIGTERM]
khem has quit [Quit: Bridge terminating on SIGTERM]
ejoerns[m] has quit [Quit: Bridge terminating on SIGTERM]
jwillikers[m] has quit [Quit: Bridge terminating on SIGTERM]
t_unix[m] has quit [Quit: Bridge terminating on SIGTERM]
SamuelDolt[m] has quit [Quit: Bridge terminating on SIGTERM]
Jari[m] has quit [Quit: Bridge terminating on SIGTERM]
WadeBerrier[m] has quit [Quit: Bridge terminating on SIGTERM]
lacouture[m] has quit [Quit: Bridge terminating on SIGTERM]
Saur[m] has quit [Quit: Bridge terminating on SIGTERM]
ndec[m] has quit [Quit: Bridge terminating on SIGTERM]
moto_timo[m] has quit [Quit: Bridge terminating on SIGTERM]
PascalBach[m] has quit [Quit: Bridge terminating on SIGTERM]
asus_986_gpu[m] has quit [Quit: Bridge terminating on SIGTERM]
Alban[m] has quit [Quit: Bridge terminating on SIGTERM]
christophs[m] has quit [Quit: Bridge terminating on SIGTERM]
AlessandroTaglia has quit [Quit: Bridge terminating on SIGTERM]
shoragan|m has quit [Quit: Bridge terminating on SIGTERM]
michaelo[m] has quit [Quit: Bridge terminating on SIGTERM]
fabatera[m] has quit [Quit: Bridge terminating on SIGTERM]
rodrjassoccom[m] has quit [Quit: Bridge terminating on SIGTERM]
nicolas[m]12 has quit [Quit: Bridge terminating on SIGTERM]
TrevorWoerner[m] has quit [Quit: Bridge terminating on SIGTERM]
xicopitz[m] has quit [Quit: Bridge terminating on SIGTERM]
TurtleCrazy[m] has quit [Quit: Bridge terminating on SIGTERM]
Pierre-jeanTexie has quit [Quit: Bridge terminating on SIGTERM]
jonesv[m] has quit [Quit: Bridge terminating on SIGTERM]
Spectrejan[m] has quit [Quit: Bridge terminating on SIGTERM]
JonasVautherin[m has quit [Quit: Bridge terminating on SIGTERM]
meck[m] has quit [Quit: Bridge terminating on SIGTERM]
janvermaete[m] has quit [Quit: Bridge terminating on SIGTERM]
timbert[m] has quit [Quit: Bridge terminating on SIGTERM]
behanw[m] has quit [Quit: Bridge terminating on SIGTERM]
SnowBeast[m] has quit [Quit: Bridge terminating on SIGTERM]
keepitsimplejim[ has quit [Quit: Bridge terminating on SIGTERM]
cody has quit [Quit: Bridge terminating on SIGTERM]
Emantor[m] has quit [Quit: Bridge terminating on SIGTERM]
alex88[m] has quit [Quit: Bridge terminating on SIGTERM]
dwagenk has quit [Quit: Bridge terminating on SIGTERM]
lexano[m] has quit [Quit: Bridge terminating on SIGTERM]
Andrei[m] has joined #yocto
meck[m] has joined #yocto
lexano[m] has joined #yocto
jordemort has joined #yocto
kayterina[m] has joined #yocto
cody has joined #yocto
shoragan[m] has joined #yocto
Jari[m] has joined #yocto
Pierre-jeanTexie has joined #yocto
Saur[m] has joined #yocto
khem has joined #yocto
ejoerns[m] has joined #yocto
Emantor[m] has joined #yocto
janvermaete[m] has joined #yocto
moto_timo[m] has joined #yocto
ndec[m] has joined #yocto
t_unix[m] has joined #yocto
WadeBerrier[m] has joined #yocto
jwillikers[m] has joined #yocto
TrevorWoerner[m] has joined #yocto
barath has joined #yocto
SamuelDolt[m] has joined #yocto
Alban[m] has joined #yocto
keepitsimplejim[ has joined #yocto
shoragan|m has joined #yocto
alex88[m] has joined #yocto
rodrjassoccom[m] has joined #yocto
xicopitz[m] has joined #yocto
AlessandroTaglia has joined #yocto
JonasVautherin[m has joined #yocto
jonesv[m] has joined #yocto
TurtleCrazy[m] has joined #yocto
michaelo[m] has joined #yocto
christophs[m] has joined #yocto
lacouture[m] has joined #yocto
Spectrejan[m] has joined #yocto
timbert[m] has joined #yocto
SnowBeast[m] has joined #yocto
fabatera[m] has joined #yocto
PascalBach[m] has joined #yocto
asus_986_gpu[m] has joined #yocto
behanw[m] has joined #yocto
nicolas[m]12 has joined #yocto
dwagenk has joined #yocto
Vonter_ has quit [Ping timeout: 255 seconds]
bps has joined #yocto
bps has joined #yocto
bps has quit [Changing host]
<dvorkindmitry>
rber|res, how can I find the recipe that gives a problem for SDK?
jwillikers has joined #yocto
jwillikers has quit [Remote host closed the connection]
Vonter has joined #yocto
jwillikers has joined #yocto
<vd>
hi all -- how can I add files to my data partition with wic?
<vd>
like IMAGE_BOOT_FILES but for data
<mckoan>
vd: wic defines partitions, if you want to add files into that is a normal recipe
<vd>
mckoan you're mixing the rootfs partitions (fed with --source rootfs) with arbitrary data partitions, but thanks
kayterina has quit [Remote host closed the connection]
florian_kc has joined #yocto
tgamblin has quit [Quit: Leaving]
tgamblin has joined #yocto
Schlumpf has quit [Quit: Client closed]
<override>
hey, Im trying to setup two partitions and tell uboot which one to boot the kernel from using a uboot env varaible or something. I need some direction as to how this can be done correctly in yocto world. Example recipes, overvall methodology examples welcome
dlan has quit [Remote host closed the connection]
<JPEW>
override: We tried a few different methods for that type of thing, but a u-boot boot script seems to be the most flexible
<vd>
override there's no yocto recommendation for this, it depends on your BSP layer. *I* would personally stay away from u-boot and move to barebox if the platform supports it. For this A/B rootfs scheme, a framework such as barebox bootchooser allows you to script which rootfs to boot from and inform the kernel about it
<qschulz>
libubootenv allows you to edit a U-Boot environment from userspace
<qschulz>
if that's what you're afte
<override>
the bsp which came with the boars is very u-boot centric
<JPEW>
override: It does require you to have a boot partition to put the script in, but after that you can put u-boot into "distro boot" mode and IIRC it will automatically pick up the boot script and run it
<override>
JPEW: vd: qschulz: Im also trying to understand how these partitions are setup to begin with
<override>
In a perfect world I want one of the partitions to copy the kenrnel image from mmc/usb and then just boot from that partition
dlan has joined #yocto
<JPEW>
override: Ya, I would look into u-boot boot scripts. You can basically make them do anything you would manually make u-boot do on the command line.
<override>
JPEW: so I can setup the partions usining u-boot boot scripts as well, or is that done else where
<JPEW>
override: I'm not sure what you mean by "setup the partitions"
<override>
JPEW: For the whole A/B rootfs to work, how would be setting up those two partitions to begin with?
<vd>
override this simpler is having a .wks file in your layer to define the 2 partitions for the wic image fstypes
<JPEW>
override: Ya, use wic to create the disk image
<vd>
just start with simple images with fixed size.
zyga has quit [Remote host closed the connection]
<override>
cool ok, thanks guys
<vd>
later, you may script resizing and all
zyga has joined #yocto
<override>
ill take a crack at it
<JPEW>
override: If it were me, I would make a wks file with 3 partitions: A boot partition with the u-boot script, and an A and B partition that (initially) both contain the same rootfs image
<qschulz>
BTW, I assume most sw upgrade software support this, so you might not need to reinvent the wheel
<qschulz>
swupdate does, probably others too
<override>
qschulz, swupdate would keep me from setting up the partitions and all??
<override>
is there a recipe or something for it that I can use to bring it over on my board?
<qschulz>
swupdate will take care of updating the A/B partition
<override>
thanks guys. ill be back with more questions later
roussinm has joined #yocto
Beginner42 has joined #yocto
Beginner42 has quit [Client Quit]
<override>
for distro conf files is there stuff that we are absolutely required to have? I just need it primarily to set INIT_MANAGER. Would I still need to set stuff like DISTRO_FEATURES PREMIRRORS etc?
camus has quit [Ping timeout: 255 seconds]
camus has joined #yocto
<vd>
your custom distro can be mostly empty, it doesn't really matter.
dtometzki has quit [Ping timeout: 268 seconds]
<override>
vd: in my local.conf can I put two distro names, one that came with the bso and one that my meta-layer has?
<qschulz>
override: what are you trying to achieve with this?
<override>
qschulz: just trying to setup systemd through distro rather than local.conf
dtometzki has joined #yocto
<qschulz>
why do you want to enable two distros at the same time?
<override>
so the distro I see right now in my local.conf came from the bsp. I would want all that to work ... So im not sure how I inculde the distro Im making for my own meta-layer in local.conf..
<qschulz>
override: you can include a distro configuration file from another one
sakoman has joined #yocto
<qschulz>
but you'll need to change the DISTRO in your local.conf and probably add the original name of the bsp distro to DISTROOVERRIDES if they use it in some recipes
<override>
dont those have a .inc extension ? the ones you can include
<qschulz>
not necessarily no
<override>
ok I can Include the bsp distro in my distro and then add my distro to local.conf
<qschulz>
yes
tnovotny has quit [Quit: Leaving]
<wyre>
is it safe to remove manually the tmp directory?
<wyre>
because apparently '-c cleanall' it's not removing it
Schlumpf has joined #yocto
<override>
qschulz: I was thinking about including the bsp distro in the distro for my meta-layer, and just not declare any disto name etc for my meta-layers distro. would this be very weird or is this usally how we built on top of distros from vendors/bsps?
<qschulz>
wyre: cleanall removes everything for one recipe
<wyre>
qschulz, even the images?
<qschulz>
wyre: it's a recipe
<qschulz>
you have package recipes and image recipes
<qschulz>
override: i'm not sure to understand your question
<qschulz>
the distro is up to the final user
<wyre>
qschulz, I'd like to clean the tmp/deploy/images/<machine>/ folder
<qschulz>
I think maybe there's a cleanold or something for image recipes, I don't remember exactly
<override>
qschulz: let me ask you this: Im including a distro conf that already has a distro name declated into my distro conf. Can I just let the name be, or do I have to use DISTROOVERRIDES ??
<override>
declared*
<qschulz>
the distroname has to be the one of the distro you just created (which includes the other one)
<qschulz>
if any of the recipes/subdirs/anything using OVERRIDES is using DISTROOVERRIDES (look for _<distroname> or subdirs named <distroname>, then you'll need to play with DISTROOVERRIDES)
goliath has quit [Quit: SIGSEGV]
xmn has joined #yocto
angolini has joined #yocto
camus1 has joined #yocto
camus has quit [Ping timeout: 268 seconds]
camus1 is now known as camus
frieder has quit [Remote host closed the connection]
Schlumpf has quit [Quit: Client closed]
<override>
where can I tell yocto to build raw disk images (literal, byte for byte) image rather than filesystem tarballs?
<jonesv[m]>
But I don't understand what I need to set to get what I need to output a video to HDMI (I'm hoping to get a framebuffer device, but I don't have much experience here)
Tokamak has quit [Ping timeout: 255 seconds]
LetoThe2nd has quit [Quit: Connection closed for inactivity]
<override>
JPEW: can we give image recipes command line args to set IMAGE_FSTYPES, or is that a bad idea?
<JPEW>
No, you would set it in local.conf or machine.conf
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
Guest8 has joined #yocto
<Guest8>
Trying to enable dmalloc c++ shared libraries in rocko. .bb looks correct (EXTRA_OECONF += "--enable-threads --enable-cxx --enable-shlib") but only 'c' versions of libraries created.
splendidsoccer has quit [Quit: Client closed]
yates_work has joined #yocto
<yates_work>
fray: are you available?
camus1 has joined #yocto
camus has quit [Read error: Connection reset by peer]
<Xagen>
is there anyone here that is well versed with toaster?
<JaMa>
git format-patch is the best format for patches, but it should also include Upstream-Status and Signed-off-by
<yates_work>
ok thanks JaMa
<vd>
JPEW since you're using whisk which uses multiconfigs to build different profiles, do you use the same generic (vanilla) image that you tweaks in the build multiconfig?
<JPEW>
More or less, yes
<vd>
I figure this might be the cleanest way, I have like 3 differents builds already, with 3 images where only the default root password and a few packages differ
<vd>
but I don't want to 'require vanilla-image.bb', it can be misleading
<vd>
I wanted to make sure appending a recipe from a multiconfig was something people do
tgamblin has quit [Quit: Leaving]
dvorkindmitry has quit [Ping timeout: 268 seconds]
dvorkindmitry has joined #yocto
ant__ has joined #yocto
<yates_work>
fray: i found that if i add --sysroot to the libs-y variable, it makes it work: libs-y += arch/csky/lib/ $(shell $(CC) $(KBUILD_CFLAGS) $(KCFLAGS) --sysroot=/edg/build-csky-toolchain-5.12-libgcc-10/tmp/work/qemucsky-poky-linux/linux-csky/5.12-r0/recipe-sysroot -print-libgcc-file-name)
<yates_work>
but i don't understand why this --sysroot option isn't being placed into the original KBUILD_CFLAGS