most likely, but as i'm explicitly not installing any documentation, i'm now poking around to see what insists on building that for no apparent reason. rday

It's not related to yp-docs at least. most likely some recipes that use docbook for their docs/man pages, no?

years ago, i asked about how to support a small set of closely-related targets using MACHINEOVERRIDES to define how to apply patches in a (somewhat) hierarchical

testing building qemuarm64 core-image-minimal from scratch, and noticed it fetching for docbook-xml and docbook-xsl stuff ... is there something that still needs docbook support? i'm about to take a

Hello Guys i have installed avahi-0.8 version using gatesgarth version, its compiled successfully but i am facing an issue with TriggeredBy: [[0;1;32m●[[0m avahi-daemon.socket, when i restart my

Hello John, It seems that your target is configured correctly. Since you have all the components you should and must have as SPI framework. Namely I was looking for /sys/bus (since you must have an

But there are NO udev files for the SPI devices defined in the DTSI file. On 2021-03-18 17:12, jchludzinski via lists.yoctoproject.org wrote:

That's with: root@arria10:~# lsmodModule Size Used byspi_altera 16384 0spidev 20480 0 On 2021-03-18 17:07, jchludzinski via lists.yoctoproject.org

root@arria10:~# find /sys/ -name

merged, thanks

merged thanks

merged. thanks

Applied. Thank you! :-)

I am guessing here.... But what do you have while executing the following command being in /sys as root? root@arm:/sys# find . -name spi* Zee _______ On Wed, Mar 17, 2021 at 5:41 PM jchludzinski

Thanks for input from you. Does this mean shown differences in directory tree is result, a mix of these all listed parameters? I am aware of these are two different distributions. I am aware of these

Thanks for helpful input. This matches my own observation. Tool-chain used in project requires additionally license.manifest file on its input. For some reason it also takes a look into files named

Hi All, This is the full report for yocto-3.3_M3.rc1: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high

Signed-off-by: Khem Raj <raj.khem@...> --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index 8eecdc5..db9961c

and meta-yocto was renamed to meta-poky in one of those changes at the request of the members and community.

OE allows you to build own distributions, so what you are looking at is two different distributions based on different different releases but using same build system ( OpenEmbedded ) over major