Fix "data truncated" warnings/errors when loading data for OE-Core:
* PROVIDES for recipe packagegroup-base is ~1452 characters
* LICENSE for recipe linux-firmware is ~1053 characters
(These aren't shown with SQLite, only with something like MariaDB where
column sizes are enforced.)
Signed-off-by
Allow updating multiple branches, and if no branches are specified,
update all branches that have a new "updates_enabled" flag field set to
True. This avoids the need to have a separate shell script which runs
update.py for each branch (and thus has hardcoded knowledge of each
active branch in the
Fix a greedy regex in the recipe detail view resulting in the git recipe
listing all bbappends named *_git.bbappend as its bbappends (quite a few
in the public instance).
Signed-off-by: Paul Eggleton
---
TODO| 1 -
layerindex/views.py | 2 +-
2 files changed, 1 insertion(+), 2 de
In order to try to avoid problems with leaking memory, context bleeding
from one layer to another, and lay the groundwork for supporting
updating all branches in one operation, split the updating of a single
layer out to its own internal script. This means that the tinfoil
instantiation and metadat
If you're moving a short description value from DESCRIPTION to SUMMARY
then part of that is setting DESCRIPTION to blank, however that wasn't
possible - the code was assuming that a null value meant "keep the
original value". Change the logic so that the value in the bulk change
object is always se
Refactor the update script to hopefully make it more robust, allow
multiple branches to be updated with one command, and fix a few other
issues.
The following changes since commit b80833e1c9d2e8d4bd15903810bc981dd3a9c19e:
TODO: drop some completed items (2016-05-30 15:28:20 +1200)
are availab
This mail was sent out by Recipe reporting system.
This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade at this time, they can fill
RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder
until newer upstream version w
On May 29, 2016 9:00 AM, "Paul Barker" wrote:
>
> PV is now set in each version of the linux-raspberrypi recipe instead of
in
> linux-raspberrypi.inc. This allows linux-raspberrypi.inc to be used in
custom
> kernel recipes in another layer which require a different PV value.
You can also use wea
I think we should remove it. But lets give a chance for folks to respond if
any one is using 3.18 still
On May 29, 2016 9:07 AM, "Paul Barker" wrote:
> The linux-raspberrypi v3.18 recipe does not build after commit
> 519c387e3b97ecc21ac1d7b4fc9197298f289a71 as it lacks the necessary dtb
> files.
The linux-raspberrypi v3.18 recipe does not build after commit
519c387e3b97ecc21ac1d7b4fc9197298f289a71 as it lacks the necessary dtb files.
Signed-off-by: Paul Barker
---
.../0001-dts-add-overlay-for-pitft22.patch | 110 -
recipes-kernel/linux/linux-raspberrypi_3.18.
We now need dtb files when booting via u-boot.
Signed-off-by: Paul Barker
---
classes/sdcard_image-rpi.bbclass | 40
1 file changed, 20 insertions(+), 20 deletions(-)
diff --git a/classes/sdcard_image-rpi.bbclass b/classes/sdcard_image-rpi.bbclass
index
The rpi-mkimage tools are no longer used. Recent Raspberry Pi firmware can
directly boot a Linux kernel image using device tree and mainline u-boot
supports Raspberry Pi without the use of these tools.
Signed-off-by: Paul Barker
---
recipes-bsp/rpi-mkimage/rpi-mkimage/License| 25 ---
The repository used by u-boot-rpi has not been updated since 2012. In the
meantime, mailine u-boot has gained Raspberry Pi support. All we need to do is
set UBOOT_MACHINE to an appropriate value in the machine config files.
Currently configs are only provided for raspberrypi and raspberrypi2. The
Recent versions of the Raspberry Pi firmware can directly handle kernel images
which use device tree. The modifications made by rpi-mkimage are no longer
needed.
Signed-off-by: Paul Barker
---
recipes-kernel/linux/linux-raspberrypi.inc | 18 --
1 file changed, 18 deletions(-)
di
Following discussion on the Raspberry Pi tools bug tracker it was found that
rpi-mkimage is no longer needed with recent firmware. It can therefore be
dropped from the layer completely.
Whilst looking into this I also found that the u-boot-rpi recipe in
meta-raspberrypi can now be replaced by dire
PV is now set in each version of the linux-raspberrypi recipe instead of in
linux-raspberrypi.inc. This allows linux-raspberrypi.inc to be used in custom
kernel recipes in another layer which require a different PV value.
Signed-off-by: Paul Barker
---
recipes-kernel/linux/linux-raspberrypi.inc
16 matches
Mail list logo
