in commit 01b162388e
with commit message:
rpi-base: Drop old dtbo names
pi3-disable-bt is renamed to disable-bt and pi3-miniuart-bt is renamed
to miniuart-bt in 2014, now with 5.4 these are not recognised anymore
and miniuart-bt and disable-bt are already part of RPI_KERNEL_DEVICETREE_OVERLAYS
Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
The dependencies to the meta-openembedded layers are handled through
dynamic layers so there is no need to advertise this in the
documentation. Especially that the layer configuration doesn't set that
either.
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
matrix.org doesn't allow guest logins which is required by the shield.
Use a custom one to avoid a confusing badge warning.
Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
The mailing list infrastructure at Yocto project changed (for a good
while now) but we still reference the old address/links. Update them
accordingly.
Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
* Remove CI badges - I plan to move to github CI soon and they are broken
* anyway. So I might as well look into them when I migrate the CI.
* Update maintainer email.
* Drop temporary the sponsor logo - it breaks documentation builds in
Read The Docs. I'll check it out when I revamp the docs.
* Update the matrix channel.
Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
balena.io has been sponsoring the project with a build server for a
while now. It's only fair for us to mention this somewhere in our
README.
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
Corrects README.md to indicate that the new generated image extension is
.wic.bz2 rather than sdimg as previously stated.
Signed-off-by: Brandon Verkamp <jadelclemens@gmail.com>
The kas tool provides an easy mechanism to setup bitbake based projects.
As explained in [1] the key features provided by kas are:
- clone and checkout bitbake layers
- create default bitbake settings (machine, arch, ...)
- launch minimal build environment, reducing risk of host contamination
- initiate bitbake build process
So, let's create a minimal example in this layer to build an image with a
small effort. This seems interesting for new users of the meta-raspberrypi.
For example:
$: sudo pip3 install kas
$: mkdir rpi
$: cd rpi
$: git clone https://github.com/agherzan/meta-raspberrypi.git
$: kas build meta-raspberrypi/kas-poky-rpi.yml
and that's all !
To adjust the construction with specific options (I2C, SPI, ...), simply add
a section as follows:
local_conf_header:
rpi-specific: |
ENABLE_I2C = "1"
RPI_EXTRA_CONFIG = "dtoverlay=pi3-disable-bt"
To configure the machine, the user have to update the 'machine' variable.
And the same for the 'distro'.
[1] - https://kas.readthedocs.io/en/1.0/userguide.html
Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
* As we now use GitHub for development we should point users at this repo.
* Layer documentation is now published on Read the Docs.
Signed-off-by: Paul Barker <pbarker@toganlabs.com>
The top-level README document has got pretty unwieldy and so we need to
switch to add some more structure to our documentation. The first step
is to split out sub-sections of the README document into separate files
in a new 'docs' directory.
Whilst splitting up the README, we can also take the opportunity to tidy
things up and fix a couple of typos.
Signed-off-by: Paul Barker <pbarker@toganlabs.com>
