We have a few recipes which only deploy files that go into the boot partition
and do not create packages to be installed into the rootfs. These recipes don't
need to run the usual packaging tasks so we can drop them to speed up the build
a little.
We also have a bunch of recipes that don't need the usual toolchain as they just
copy files or invoke native commands like `mkimage`. So to speed up the build a
little more we can set INHIBIT_DEFAULT_DEPS to avoid an unnecessary dependency
on the toolchain.
Signed-off-by: Paul Barker <pbarker@toganlabs.com>
If I am not mistaken, many desktops (kde/lxqt/xfce..) use udisks2 to ask for
devices which can be mounted. Without this patch the initial boot partition
can be mounted by a single click on folder displayed on desktop or file manager.
Why it is suggested to add this recipe to an image:
* It removes annoying icon in desktop/file manager.
* The initial boot partition is vfat. Unpriviledged users can modify
content. E.g by removing files accidently, images can be turned into
non-booting condition easily. And from security point of view, it is a
disaster.
FWIW: Have similar in all my BSPs vor very long time.
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
If rpi-basic-image is based on rpi-hwup-image, both deprecation warnings are
printed which may be confusing. Therefore let's just copy over the relevant bits
of rpi-hwup-image for now.
Signed-off-by: Paul Barker <pbarker@toganlabs.com>
As discussed on the issue tracker, it's confusing for meta-raspberrypi to have
its own set of image names filling the same jobs as the core images. Therefore
we are marking these images as deprecated and will be removing them in the
future. The recommended replacement images are as follows:
rpi-hwup-image -> core-image-minimal
rpi-basic-image -> core-image-base
The image 'rpi-test-image' will be kept and is not marked as deprecated, it is
still useful for testing. It it updated to be based on 'core-image-base'.
Signed-off-by: Paul Barker <pbarker@toganlabs.com>
* omxplayer has:
COMPATIBLE_MACHINE_rpi_aarch64 = null
so it cannot be inclued for raspberrypi3-64
* components used by this packagegroup are also restricted to ^rpi$ so
the packagegroup and the image using it cannot be built for anything else
* fixes couple errors when trying to build world with meta-raspberrypi included
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
BSPs should not be overriding the distro splash images, here we
reduce the priority of psplash-raspberrypi below 100 so the defaults
from distros can kick in.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
bcm2835 is an empty package because this recipe provides a static library.
Install on target only bcm2835-tests package in which files are statically
linked to that library.
Add forgotten GPIO packages: rpi-gpio and rpio.
Change-Id: I498d2a3948ad5faf963d492bc496d4725a79e136
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
Remove these files as the default ones work just OK.
Moreover, not having /run mounted as tmpfs, would break mounting root as
read only. This is done in the default fstab so use that one.
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
Instead of overriding the default psplash image, the raspberrypi image is added
as an additional image. It is then set as the default in the raspberrypi machine
config file so that other targets do not pick up our splash image.
Tested on raspberrpi and qemuarm: on raspberrypi I see to Raspberry Pi logo, on
qemuarm I see the Yocto Project logo.
Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
Dropped raspberrypi modifications to hosts and interfaces files as they are
unnecessary.
Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
Add a new basic image with ssh-server-dropbear IMAGE_FEATURE
This is to allow people without physical hardware attached to
the Pi such as monitor and keyboard to connect over the network.
[GITHUB #52]
Signed-off-by: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
