OK, let me try this: With other embedded OS's, the hardware specifics that are in the BSP are in the device trees in Linux. I assume the BSP's for OE Linux are rather simple?

OK, let's go with that. I've watched the "Live Coding with Yocto Project #1: download and first build" youtube video. Where is the BSP built in this procedure? wrote:

A board-support-package (BSP) is software that provides a layer of abstraction from the physical board specifics for the host embedded OS (e.g., VXworks). I believe the device tree files (*.dts, *dtsi

OE Linux uses device tree files (*.dts and *.dtsi files), so is there any need for a board-support-package?

I’m actually trying this on an RP4 running Raspbian.

$ git clone git://git.yoctoproject.org/poky.git $ cd ./poky $ git checkout yocto-3.4.2 $ cd .. $ source ./poky/oe-init-build-env $ cd ./build $ time bitbake core-image-minimal ... ERROR: OE-core's con

But obviously commented out.

There's this: #SDKMACHINE ?= "i686" ---John

I'm trying an experiment building yocto/OE on a Raspberry Pi 4 to host on the same RP4. Admittedly, a not practical platform for this purpose but it should work. I'm trying to target the ARM ISA for t

NEWBIE question! I tried building and I get: "Specified SDKMACHINE value is not valid" pi@raspberrypi ~/p/build> bitbake core-image-minimal /usr/lib/python3/dist-packages/html5lib/_trie/_base.py:3: De

When I trying using bitbake to build openembedded Linux kernel, it dies with these download failures: NOTE: Fetching uninative binary shim http://downloads.yoctoproject.org/releases/uninative/3.0/x86_

When I trying using bitbake to build openembedded Linux kernel, it dies with these download failures: NOTE: Fetching uninative binary shim http://downloads.yoctoproject.org/releases/uninative/3.0/x86_

What is the relationship between OpenBIOS and YOCTO? Between OpenBIOS and U-boot?

My problem is I have an 1553 chip (an avionic data bus) connected to the HPS master (an ARM processor) via an FPGA (soft) SPI controller. This is where the spi-altera.c comes in. It provides the drive

How is it possible to build a loadable module from spi-altera.c when it has no code for creating udev files (i.e., /dev/spidevXX); it has no: static int __init spidev_init(void) { int status; printk(K

Using 'make nconfig' I selected the following options: (Keep in mind I using an Altera/Intel Arria 10 SoC which uses DesignWare hard SPI controllers. BUT the SPI controllers I'm concerned with now are

But there are NO udev files for the SPI devices defined in the DTSI file.

That's with: root@arria10:~# lsmod Module Size Used by spi_altera 16384 0 spidev 20480 0

root@arria10:~# find /sys/ -name 'spi*' /sys/kernel/debug/clk/spi_m_clk /sys/kernel/debug/tracing/events/spi /sys/kernel/debug/tracing/events/spi/spi_controller_idle /sys/kernel/debug/tracing/events/s

In the YOCTO/Linux source tree there's drivers/spi/ which has all the source for SPI drivers. There's only 1 file, spidev.c, which has: static int __init spidev_init(void) { int status; /* Claim our 2