On Fri, 2021-11-05 at 15:02 -0700, chuck kamas via
lists.yoctoproject.org wrote:
> Well it turns out that following the Perf recipe was not only a good
> idea, but absolutely necessary. The perf recipe copies the code out of
> the work-shared kernel directory into the perf build directory. This
Well it turns out that following the Perf recipe was not only a good
idea, but absolutely necessary. The perf recipe copies the code out of
the work-shared kernel directory into the perf build directory. This
avoids the error when bitbake thinks that the kernel code is not needed
anymore and
On Tue, Oct 12, 2021 at 12:33 AM chuck kamas via
lists.yoctoproject.org
wrote:
>
> Thanks for the quick reply. I looked at the perf recipe, and its quite
> involved. Is there a simpler recipie to use as a template? Perhaps one of
> these?
>
My intent was just to show how you'd get the source
Thanks for the quick reply. I looked at the perf recipe, and its quite
involved. Is there a simpler recipie to use as a template? Perhaps one
of these?
meta-openembedded/meta-oe/recipes-kernel/bpftool/bpftool.bb
meta-openembedded/meta-oe/recipes-kernel/spidev-test/spidev-test.bb
On Mon, Oct 11, 2021 at 6:16 PM chuck kamas via lists.yoctoproject.org
wrote:
>
> Hi all,
>
>
> I've googled most of the day, but to no avail. How does one compile and
> add to the image the daemon usbipd? Is there a bitbake file already for
> this? The code is part of the kernel found in the
Hi all,
I've googled most of the day, but to no avail. How does one compile and
add to the image the daemon usbipd? Is there a bitbake file already for
this? The code is part of the kernel found in the kernel tree:
KERNEL_SRC_PATH/tools/usb/usbip/src
and is invoked from the
