<sef>
| % Total % Received % Xferd Average Speed Time Time Time Current
<sef>
| Dload Upload Total Spent Left Speed
<sef>
|
<sef>
| 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: gitlab.com
<sef>
| WARNING: exit code 6 from a shell command.
<sef>
ERROR: Task (/opt/trios-kirkstone/sources/meta-trio/recipes-frameworks/tensorflow-lite/tensorflow-lite_2.5.0.bb:do_unpack) failed with exit code '1'
<sef>
What could it be caused by?
leon-anavi has joined #yocto
<LetoThe2nd>
sef: probably the recipe is trying to download something in a stage that is not the fetch stage. which is a really bad practise (not cached and not reproducible), so the correct approach is to fix the recipe.
<sef>
tensorflow's "download_dependencies.sh" script is trying to download it. i guess i need to look at the patches or fixes in the repo where i got.
<LetoThe2nd>
sef: if a layer is compatible with kirkstone, it should be behaving properly.
odra_ has joined #yocto
<sef>
LetoThe2nd thank you
odra_ has quit [Remote host closed the connection]
odra_ has joined #yocto
odra_ has quit [Remote host closed the connection]
odra__ has joined #yocto
odra_ has joined #yocto
odra__ has quit [Read error: Connection reset by peer]
Schlumpf has quit [Quit: Ping timeout (120 seconds)]
kevinrowland has quit [Quit: Client closed]
mckoan is now known as mckoan|away
zpfvo has quit [Ping timeout: 250 seconds]
<xcm>
hello. i'm building my image (containing IMAGE_INSTALL:append="blah"), and then i have blah_git.bb: https://bpa.st/TAMQ . the `blah` binary ends up in the image, but the dependencies are not there. what could i be doing wrong here?
zpfvo has joined #yocto
<rburton>
if you need IMAGE_INSTALL:append then you should use RDEPENDS:${PN}
<rburton>
also if your recipe is blaa_0.0.0.bb then you don't need to set S, as the default is WORKDIR/PV-PN
<xcm>
rburton: ah i see, thanks a lot (for the versioning tip as well)! seems to be building the deps now
sef has quit [Ping timeout: 244 seconds]
sef has joined #yocto
alessioigor has joined #yocto
prabhakarlad has quit [Quit: Client closed]
Schlumpf has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
otavio has joined #yocto
sef has quit [Ping timeout: 244 seconds]
sef has joined #yocto
seninha has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
sef has quit [Ping timeout: 244 seconds]
sef has joined #yocto
sef has quit [Client Quit]
kscherer has joined #yocto
Schlumpf has quit [Quit: Client closed]
zpfvo has quit [Ping timeout: 248 seconds]
prabhakarlad has joined #yocto
zpfvo has joined #yocto
sef has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
sef has quit [Quit: Client closed]
kanavin has quit [Quit: Leaving]
Payam has joined #yocto
kanavin has joined #yocto
rob_w has quit [Quit: Leaving]
sakoman has joined #yocto
nucatus has joined #yocto
<nucatus>
Hello! some linux kernel related question here. Would be possible to communicate to a out-of-tree linux kernel module some parameters carried through the device tree? I know there is module_parameter macro that would allow to set LKM parameters using modprobe ... is there a similar one using the device tree?
vmeson has quit [Remote host closed the connection]
vmeson has joined #yocto
vmeson has quit [Quit: Konversation terminated!]
goliath has quit [Quit: SIGSEGV]
<rfs613>
nucatus: a kernel driver can read paramaters from device tree, regardless how it is compiled (built-in to kernel, or out-of-tree)
<qschulz>
rfs613: provided the module is probed via device tree matching I guess?
kovalevsky has joined #yocto
vmeson has joined #yocto
<rfs613>
qschulz: that's certainly the simplest, you can just use the normal functions for accessing it
<rfs613>
though I'm fairly sure you could scan the whole thing if you really wanted to.
<qschulz>
rfs613: now I remember Allwinner BSP looking all over the device tree for other nodes so yes, probably possible :)
<nucatus>
rfs613: is there an idiomatic/preferred way of doing that? Does the linux kernel provide a macro for that, similar to module_param?