Re: [yocto] Remove libjpeg.so (default built even in core-image-minimal) from the rootfs when build yocto

[Petter Mabäcker]

 

My guess would be that the package name to exclude is libjpeg-turbo
. But it seems to provide jpeg-tools as well, so that can be good to
have in mind when elaborating with excluding this package. 

BR Petter


2018-01-16 07:46 skrev Nguyễn Thanh Vũ: 

> I know that I need to use
PACKAGE_EXCLUDE, but I have no idea what is the package name of libjpeg
... Any clue? 
> 
> On Tue, Jan 16, 2018 at 1:40 PM, Petter Mabäcker
 wrote:
> 
>> 2018-01-16 05:28 skrev Nguyễn Thanh Vũ:

>> 
>>> I have statically linked the libjpeg of my own to the exe file,
so I do not need the libjpeg.so default built in the /lib of rootfs. How
can I modify or specify in the local.conf file so that I can remove that
component? It takes quite a lot of space. 
>>> 
>>> Thank you.
>> 
>> Hi
Nguyễn, 
>> 
>> If you want (and no dependencies dissallow it), you can
remove the entire package providing libjpeg.so from being installed with
PACKAGE_EXCLUDE
(http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-PACKAGE_EXCLUDE
[2]). 
>> 
>> If that`s not working you can for example use
ROOTFS_POSTPROCESS_COMMAND
(http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-ROOTFS_POSTPROCESS_COMMAND
[3]). However that will require more work then just update a line in
local.conf. 
>> 
>> If you want to try it out you can simply append the
image recipe in a custom layer with below. 
>> 
>>
my_postprocess_function() {
>> rm -f
${IMAGE_ROOTFS}/path/to/libjpeg.so
>> }
>> ROOTFS_POSTPROCESS_COMMAND +=
"my_postprocess_function; "
>> 
>> BR Petter 
>> 
>> Petter Mabäcker
>>

>> Technux 
>> www.technux.se [1]



Links:
--
[1] http://www.technux.se
[2]
http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-PACKAGE_EXCLUDE
[3]
http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-ROOTFS_POSTPROCESS_COMMAND
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Remove libjpeg.so (default built even in core-image-minimal) from the rootfs when build yocto

[Petter Mabäcker]

 

2018-01-16 05:28 skrev Nguyễn Thanh Vũ: 

> I have statically linked
the libjpeg of my own to the exe file, so I do not need the libjpeg.so
default built in the /lib of rootfs. How can I modify or specify in the
local.conf file so that I can remove that component? It takes quite a
lot of space. 
> 
> Thank you.

Hi Nguyễn, 

If you want (and no
dependencies dissallow it), you can remove the entire package providing
libjpeg.so from being installed with PACKAGE_EXCLUDE
(http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-PACKAGE_EXCLUDE).


If that`s not working you can for example use
ROOTFS_POSTPROCESS_COMMAND
(http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-ROOTFS_POSTPROCESS_COMMAND).
However that will require more work then just update a line in
local.conf. 

If you want to try it out you can simply append the image
recipe in a custom layer with below. 

 my_postprocess_function() {
 rm
-f ${IMAGE_ROOTFS}/path/to/libjpeg.so
 }
 ROOTFS_POSTPROCESS_COMMAND +=
"my_postprocess_function; "

BR Petter 

Petter Mabäcker

Technux

www.technux.se
 -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] What is the procedure for creating a board support package?

[Petter Mabäcker]

 

2018-01-09 19:38 skrev Peter Spierenburg: 

> I'm trying to follow
the instructions at: 
> 
>
http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html#creating-a-new-bsp-layer-using-the-yocto-bsp-script
[1] 
> 
> I followed the prompts exactly as specified (although the SMP
support prompt did not appear), and I chose the default 4.12 kernel
(presumably the guide is slightly out of date). 
> 
> I included the
generated bsp in bblayers.conf as indicated. 
> 
> I invoked: 
> 
>
bitbake core-image-minimal
> However, the resulting build was intel
based, and not arm as one might expect since I asked for ARM when
prompted by the yocto-bsp script.Is there a more hands-on document that
I could be following? 
> 
> Peter.
> 
> This communication, including
any attached documentation, is intended only for the person or entity to
which it is addressed, and may contain confidential, personal, and/or
privileged information. Any unauthorized disclosure, copying, or taking
action on the contents is strictly prohibited. If you have received this
message in error, please contact us immediately so we may correct our
records. Please then delete or destroy the original transmission and any
subsequent reply. Thank you.

Hi Peter, 

Have you set MACHINE = "myarm"
in conf/local.conf in your project? That is required in order to enable
full usage of your new bsp. If not it will by default be set to qemux86.


Also note that you can type arm instead of qemu when doing it for the
real target ($ ./yocto-bsp create myarm arm) 

BR Petter 

Petter
Mabäcker

Technux 
www.technux.se



Links:
--
[1]
http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html#creating-a-new-bsp-layer-using-the-yocto-bsp-script
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Upgrading Yocto Project Version - To Rocko

[Petter Mabäcker]

 

Hi Vincent, 

When you are talking about database, are you talking
about specific data from your generated project (such as the sstate
cache) or are you talking about data in your current poky folder? If you
are talking about project specific data I would recommend you create a
new project and build from scratch when doing such a large upgrade (Fido
--> Rocko), since a lot of stuffs have changed. For example
bblayers.conf looks different (meta-yocto renamed to meta-poky) and so
on. But if you have cusomizations done for fido you of course need
ensure that these changes are manually exported to the new Rocko based
project (for example point out custom layers in bblayers.conf and
MACHINE in local.conf after creating your new project). 

If you are
afraid of wiping git changes, and you already have an existing poky git
clone you can just fetch the data (git fetch) then checkout the wanted
branch, tag or revision. 

BR Petter 

2018-01-09 14:35 skrev Kok,
Vincent Chin Keong: 

> How if I want to remain my database from
previous version? How can I export them?
> 
> Warmest regards, 
>
Vincent Kok 
> 
> Sent from my iPad 
> 
> On Jan 9, 2018, at 20:45,
Alexander Kanavin  wrote:
> 
>> On
01/09/2018 01:55 PM, Kok, Vincent Chin Keong wrote:
>> 
>>> I was
wondering, how can I upgrade to Yocto version 2.4 (Rocko)? Do I just
remove the previous poky folder I downloaded and re-download a newer
version of poky and checkout the branch and tags?
>> 
>> The easiest is
to perform a clean clone of the poky repo, and check out the tag you
want.
>> 
>> Alex
 -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-chip][PATCH] linux: remove usage of deprecated linux-dtb.inc

[Petter Mabäcker]

Signed-off-by: Petter Mabäcker 
---
 recipes-kernel/linux/linux-chip_git.bb | 1 -
 1 file changed, 1 deletion(-)

diff --git a/recipes-kernel/linux/linux-chip_git.bb 
b/recipes-kernel/linux/linux-chip_git.bb
index 38df4ad..955d6e7 100644
--- a/recipes-kernel/linux/linux-chip_git.bb
+++ b/recipes-kernel/linux/linux-chip_git.bb
@@ -6,7 +6,6 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
 COMPATIBLE_MACHINE = "chip"
 
 inherit kernel
-require recipes-kernel/linux/linux-dtb.inc
 
 LINUX_VERSION ?= "4.3.0"
 PV = "${LINUX_VERSION}+git${SRCPV}"
-- 
2.14.2

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-chip][RFC PATCH 3/3] chip: Add chip-u-boot-scr recipe and flash script

[Petter Mabäcker]

 

2017-06-19 16:40 skrev Trevor Woerner: 

> On Mon, Jun 19, 2017 at
7:22 AM, Drew Moseley  wrote:
> 
>>> On Jun 19,
2017, at 1:48 AM, Trevor Woerner  wrote: 
>>> 
>>>>
If you have a serial console connected to +your board, you will see the
progress and a message on the console will indicate when +the flashing
is completed.
>>> hmmm, never saw this. I have a console connected, the
moment the script started, on the console I got: U-Boot SPL 2016.01 (Jun
19 2017 - 00:32:19) DRAM: 512 MiB CPU: 100800Hz, AXI/AHB/APB: 3/2/2
Trying to boot from which looks right, the date+time are good.
>> Did
you see the proper serial output after using a smaller image?
> 
> Yes.
With a smaller image (~90MB) the flash update worked. Maybe
> another
improvement for a v2 would be for the script to look at the
> size of
/full/path/to/UBI_IMAGE and issue a warning/error if it's too
> big?
>

> I think the wording of what to expect on the host and over the
serial
> console could use some updating. Not to mention you say: "the
status
> LED on the CHIP board will flash 30 times per second..." which
doesn't
> seem to be the case, it looks more like the LED is toggled
every 2
> seconds (??), in any case, it's a lot slower than 30/sec.

I
also had the same experience as Trevor, that the led seems to flash
every 2 seconds. Also the code indicate that 2 x 1 sec sleep is used in
this area, so please go through the above description when it comes to
led experience during flashing. Another minor comment is that I believe
you should update the UBI_IMAGE example in README to use the "default"
meta-chip hwup image (chip-hwup-image-chip.ubi). 

BR Petter 

Petter
Mabäcker

Technux 
www.technux.se
 -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-chip][RFC PATCH 0/3] Initial attempt at flashing instructions.

[Petter Mabäcker]

 

2017-06-16 23:15 skrev drew.mose...@mender.io: 

> From: Drew
Moseley 
> 
> This set of patches adds the
native tools and target components needed to
> reflash the CHIP boards.
Additionally a shell script is added to the deploy
> directory showing
how to kick off a flash update. It's not ideal as I've
> hardcoded a max
size for the UBI image into the script and didn't see much
> of an
alternative. It does function though.
> 
> Drew
> 
> The following
changes since commit 0079e6ac10fc371d6f527270c23b887561f717aa:
> 
>
chip: Append to MACHINE_EXTRA_RRECOMMENDS rather than overwriting
(2017-06-15 13:37:19 +0100)
> 
> are available in the git repository
at:
> 
> g...@github.com:drewmoseley/meta-chip.git
flashing-instructions
> 
> for you to fetch changes up to
195a92fc1faa49495d1a2b6cda0134f07ce72189:
> 
> chip: Add chip-u-boot-scr
recipe and flash script (2017-06-15 11:27:06 -0400)
> 
>

> Drew
Moseley (3):
> u-boot-chip: Deploy the sunxi-spl-with-ecc.bin file.
>
chip: Build sunxi-tools-native.
> chip: Add chip-u-boot-scr recipe and
flash script
> 
> README | 26 -
> conf/layer.conf | 3 ++
>
conf/machine/chip.conf | 3 +-
>
recipes-bsp/chip-u-boot-scr/chip-u-boot-scr.bb | 70
+
>
recipes-bsp/chip-u-boot-scr/files/boot.cmd.full | 32 +++
>
recipes-bsp/chip-u-boot-scr/files/boot.cmd.in | 43 +++
>
recipes-bsp/u-boot/u-boot-chip_git.bb | 7 +++
> 7 files changed, 182
insertions(+), 2 deletions(-)
> create mode 100644
recipes-bsp/chip-u-boot-scr/chip-u-boot-scr.bb
> create mode 100644
recipes-bsp/chip-u-boot-scr/files/boot.cmd.full
> create mode 100644
recipes-bsp/chip-u-boot-scr/files/boot.cmd.in
> 
> Drew Moseley (3):
>
u-boot-chip: Deploy the sunxi-spl-with-ecc.bin file.
> chip: Build
sunxi-tools-native.
> chip: Add chip-u-boot-scr recipe and flash
script
> 
> README | 26 -
> conf/layer.conf | 3 ++
>
conf/machine/chip.conf | 3 +-
>
recipes-bsp/chip-u-boot-scr/chip-u-boot-scr.bb | 70
+
>
recipes-bsp/chip-u-boot-scr/files/boot.cmd.full | 32 +++
>
recipes-bsp/chip-u-boot-scr/files/boot.cmd.in | 43 +++
>
recipes-bsp/u-boot/u-boot-chip_git.bb | 7 +++
> 7 files changed, 182
insertions(+), 2 deletions(-)
> create mode 100644
recipes-bsp/chip-u-boot-scr/chip-u-boot-scr.bb
> create mode 100644
recipes-bsp/chip-u-boot-scr/files/boot.cmd.full
> create mode 100644
recipes-bsp/chip-u-boot-scr/files/boot.cmd.in
> 
> -- 
> 2.7.4

Hi Drew,


First of all, great work. The flashing mechanism have been sort of a
headache for many. Even if like you say there are some limitations etc
with this proposal, it works and it's easy to use. Also since no other
major concern have been provided by other reviewers, I think you should
fix the comments received and then send it as non-RFC patch. Also check
with Andrei if he want to have this as a PR in github as well. 

BR
Petter 

Petter Mabäcker

Technux 
www.technux.se
 -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH v2] pi-blaster: update to include proper rpi3 support

[Petter Mabäcker]

Update to latest available revision, in order to include proper rpi3
support as well as latest fixes.

LIC_FILES_CHKSUM for the license text in README.md is changed to handle
fixes of whitespace and newlines in the license text, introduced by the
pi-blaster commit: '0e1a1df Cleaning up the README'.

Signed-off-by: Petter Mabäcker 
---
 .../files/remove-initscript-lsb-dependency.patch   | 37 --
 recipes-devtools/pi-blaster/pi-blaster.inc |  2 +-
 recipes-devtools/pi-blaster/pi-blaster_git.bb  |  2 +-
 3 files changed, 30 insertions(+), 11 deletions(-)

diff --git 
a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch 
b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
index 7ea9a3b..c8afe60 100644
--- a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
+++ b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
@@ -1,13 +1,28 @@
-Remove dependencies on LSB functions
+From 1338f98a279616f4e5e9ea30a25d1dfa0c7df5d6 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petter=20Mab=C3=A4cker?= 
+Date: Sun, 4 Jun 2017 12:22:40 +0200
+Subject: [PATCH] Remove dependencies on LSB functions
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+See this as a rebase of the previous 'Remove dependencies on LSB
+functions patch' with only minor modifications from the original version,
+based on the work done by Alex Lennon  in
+'25fd817 pi-blaster: Added recipe'.
 
 Upstream-Status: Inappropriate [configuration]
 
-Signed-off-by: Alex Lennon 
+Signed-off-by: Petter Mabäcker 
+---
+ debian/pi-blaster.init | 38 +++---
+ 1 file changed, 7 insertions(+), 31 deletions(-)
 
-diff -ur git.org/pi-blaster.boot.sh git/pi-blaster.boot.sh
 git.org/pi-blaster.boot.sh 2014-05-20 14:49:44.378582168 +0100
-+++ git/pi-blaster.boot.sh 2014-05-20 14:51:08.330582386 +0100
-@@ -28,12 +28,12 @@
+diff --git a/debian/pi-blaster.init b/debian/pi-blaster.init
+index b142d70..01a686c 100644
+--- a/debian/pi-blaster.init
 b/debian/pi-blaster.init
+@@ -28,12 +28,12 @@ SCRIPTNAME=/etc/init.d/$NAME
  [ -r /etc/default/$NAME ] && . /etc/default/$NAME
  
  # Load the VERBOSE setting and other rcS variables
@@ -22,7 +37,7 @@ diff -ur git.org/pi-blaster.boot.sh git/pi-blaster.boot.sh
  
  #
  # Function that starts the daemon/service
-@@ -77,48 +77,23 @@
+@@ -77,48 +77,24 @@ do_stop()
  
  case "$1" in
start)
@@ -52,6 +67,7 @@ diff -ur git.org/pi-blaster.boot.sh git/pi-blaster.boot.sh
# 'force-reload' alias
#
 -  log_daemon_msg "Restarting $DESC" "$NAME"
++  echo "Restarting $DESC" "$NAME"
do_stop
 -  case "$?" in
 -0|1)
@@ -67,11 +83,14 @@ diff -ur git.org/pi-blaster.boot.sh git/pi-blaster.boot.sh
 -  log_end_msg 1
 -  ;;
 -  esac
-+  do_start
++do_start
;;
*)
 -  echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2
-+  echo "Usage: $SCRIPTNAME {start|stop|restart}" >&2
++  echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload}" >&2
exit 3
;;
  esac
+-- 
+1.9.1
+
diff --git a/recipes-devtools/pi-blaster/pi-blaster.inc 
b/recipes-devtools/pi-blaster/pi-blaster.inc
index a3beccc..a548957 100644
--- a/recipes-devtools/pi-blaster/pi-blaster.inc
+++ b/recipes-devtools/pi-blaster/pi-blaster.inc
@@ -2,7 +2,7 @@ DESCRIPTION = "This project enables PWM on the GPIO pins you 
request of a Raspbe
 HOMEPAGE = "https://github.com/sarfata/pi-blaster/";
 SECTION = "devel/libs"
 LICENSE = "MIT"
-LIC_FILES_CHKSUM = 
"file://README.md;beginline=157;endline=170;md5=f20832f31126609af5a7bf2340014540"
+LIC_FILES_CHKSUM = 
"file://README.md;beginline=212;endline=239;md5=a012868ef5f83b9f257af253d7cb07a3"
 
 SRC_URI = "git://github.com/sarfata/pi-blaster \
file://remove-initscript-lsb-dependency.patch \
diff --git a/recipes-devtools/pi-blaster/pi-blaster_git.bb 
b/recipes-devtools/pi-blaster/pi-blaster_git.bb
index 263852b..ac812ab 100644
--- a/recipes-devtools/pi-blaster/pi-blaster_git.bb
+++ b/recipes-devtools/pi-blaster/pi-blaster_git.bb
@@ -1,3 +1,3 @@
 require pi-blaster.inc
 
-SRCREV = "ec5e1b4c6191d8f9a538497dbbb86f9cf0de7016"
+SRCREV = "9f45eb23a8a3b2d1c08d08a6d68f206fe91ecf4c"
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] pi-blaster: update to include proper rpi3 support

[Petter Mabäcker]

 

2017-06-08 11:53 skrev Andrei Gherzan: 

> On Thu, Jun 8, 2017 at
5:22 AM, Khem Raj  wrote:
> 
>> On Wed, Jun 7, 2017
at 9:09 PM, Petter Mabäcker  wrote:
>> > 2017-06-08
00:54 skrev Khem Raj:
>> >
>> >
>> > On Wed, Jun 7, 2017 at 2:17 PM
Petter Mabäcker  wrote:
>> >>
>> >> Update to latest
available revision, in order to include proper rpi3
>> >> support as
well as latest fixes.
>> >>
>> >> Signed-off-by: Petter Mabäcker

>> >> ---
>> >>
.../files/remove-initscript-lsb-dependency.patch | 37
>> >>
--
>> >> recipes-devtools/pi-blaster/pi-blaster.inc
| 2 +-
>> >> recipes-devtools/pi-blaster/pi-blaster_git.bb [1] | 2 +-
>>
>> 3 files changed, 30 insertions(+), 11 deletions(-)
>> >>
>> >> diff
--git
>> >>
a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
>>
>>
b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
>>
>> index 7ea9a3b..c8afe60 100644
>> >> ---
>> >>
a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
>>
>> +++
>> >>
b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
>>
>> @@ -1,13 +1,28 @@
>> >> -Remove dependencies on LSB functions
>> >>
+From 1338f98a279616f4e5e9ea30a25d1dfa0c7df5d6 Mon Sep 17 00:00:00
2001
>> >> +From: =?UTF-8?q?Petter=20Mab=C3=A4cker?=

>> >> +Date: Sun, 4 Jun 2017 12:22:40 +0200
>> >>
+Subject: [PATCH] Remove dependencies on LSB functions
>> >>
+MIME-Version: 1.0
>> >> +Content-Type: text/plain; charset=UTF-8
>> >>
+Content-Transfer-Encoding: 8bit
>> >> +
>> >> +See this as a rebase of
the previous 'Remove dependencies on LSB
>> >> +functions patch' with
only minor modifications from the original version,
>> >> +based on the
work done by Alex Lennon  in
>> >>
+'25fd817 pi-blaster: Added recipe'.
>> >>
>> >> Upstream-Status:
Inappropriate [configuration]
>> >>
>> >> -Signed-off-by: Alex Lennon

>> >> +Signed-off-by: Petter Mabäcker

>> >> +---
>> >> + debian/pi-blaster.init | 38
+++---
>> >> + 1 file changed, 7
insertions(+), 31 deletions(-)
>> >>
>> >> -diff -ur
git.org/pi-blaster.boot.sh [2] git/pi-blaster.boot.sh [3]
>> >> 
git.org/pi-blaster.boot.sh [2] 2014-05-20 14:49:44.378582168 +0100
>> >>
-+++ git/pi-blaster.boot.sh [3] 2014-05-20 14:51:08.330582386 +0100
>>
>> -@@ -28,12 +28,12 @@
>> >> +diff --git a/debian/pi-blaster.init
b/debian/pi-blaster.init
>> >> +index b142d70..01a686c 100644
>> >> +---
a/debian/pi-blaster.init
>> >>  b/debian/pi-blaster.init
>> >> +@@
-28,12 +28,12 @@ SCRIPTNAME=/etc/init.d/$NAME
>> >> [ -r
/etc/default/$NAME ] && . /etc/default/$NAME
>> >>
>> >> # Load the
VERBOSE setting and other rcS variables
>> >> @@ -22,7 +37,7 @@ diff -ur
git.org/pi-blaster.boot.sh [2]
>> >> git/pi-blaster.boot.sh [3]
>> >>
>>
>> #
>> >> # Function that starts the daemon/service
>> >> -@@ -77,48
+77,23 @@
>> >> +@@ -77,48 +77,24 @@ do_stop()
>> >>
>> >> case "$1"
in
>> >> start)
>> >> @@ -52,6 +67,7 @@ diff -ur
git.org/pi-blaster.boot.sh [2]
>> >> git/pi-blaster.boot.sh [3]
>> >> #
'force-reload' alias
>> >> #
>> >> - log_daemon_msg "Restarting $DESC"
"$NAME"
>> >> ++ echo "Restarting $DESC" "$NAME"
>> >> do_stop
>> >> -
case "$?" in
>> >> - 0|1)
>> >> @@ -67,11 +83,14 @@ diff -ur
git.org/pi-blaster.boot.sh [2]
>> >> git/pi-blaster.boot.sh [3]
>> >> -
log_end_msg 1
>> >> - ;;
>> >> - esac
>> >> -+ do_start
>> >> ++
do_start
>> >> ;;
>> >> *)
>> >> - echo "Usage: $SCRIPTNAME
{start|stop|status|restart|force-reload}"
>> >> >&2
>> >> -+ echo
"Usage: $SCRIPTNAME {start|stop|restart}" >&2
>> >> ++ echo "Usage:
$SCRIPTNAME {start|stop|restart|force-reload}" >&2
>> >> exit 3
>> >>
;;
>> >> esac
>> >> +--
>> >> +1.9.1
>> >> +
&g

Re: [yocto] [meta-raspberrypi][PATCH] pi-blaster: update to include proper rpi3 support

[Petter Mabäcker]

 

2017-06-08 00:54 skrev Khem Raj: 

> On Wed, Jun 7, 2017 at 2:17 PM
Petter Mabäcker  wrote: 
> 
>> Update to latest
available revision, in order to include proper rpi3
>> support as well
as latest fixes.
>> 
>> Signed-off-by: Petter Mabäcker

>> ---
>>
.../files/remove-initscript-lsb-dependency.patch | 37
--
>> recipes-devtools/pi-blaster/pi-blaster.inc | 2
+-
>> recipes-devtools/pi-blaster/pi-blaster_git.bb [1] | 2 +-
>> 3
files changed, 30 insertions(+), 11 deletions(-)
>> 
>> diff --git
a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
>>
index 7ea9a3b..c8afe60 100644
>> ---
a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
>>
+++
b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
>>
@@ -1,13 +1,28 @@
>> -Remove dependencies on LSB functions
>> +From
1338f98a279616f4e5e9ea30a25d1dfa0c7df5d6 Mon Sep 17 00:00:00 2001
>>
+From: =?UTF-8?q?Petter=20Mab=C3=A4cker?= 
>> +Date:
Sun, 4 Jun 2017 12:22:40 +0200
>> +Subject: [PATCH] Remove dependencies
on LSB functions
>> +MIME-Version: 1.0
>> +Content-Type: text/plain;
charset=UTF-8
>> +Content-Transfer-Encoding: 8bit
>> +
>> +See this as a
rebase of the previous 'Remove dependencies on LSB
>> +functions patch'
with only minor modifications from the original version,
>> +based on
the work done by Alex Lennon  in
>>
+'25fd817 pi-blaster: Added recipe'.
>> 
>> Upstream-Status:
Inappropriate [configuration]
>> 
>> -Signed-off-by: Alex Lennon

>> +Signed-off-by: Petter Mabäcker

>> +---
>> + debian/pi-blaster.init | 38
+++---
>> + 1 file changed, 7
insertions(+), 31 deletions(-)
>> 
>> -diff -ur
git.org/pi-blaster.boot.sh [2] git/pi-blaster.boot.sh [3]
>> 
git.org/pi-blaster.boot.sh [2] 2014-05-20 14:49:44.378582168 +0100
>>
-+++ git/pi-blaster.boot.sh [3] 2014-05-20 14:51:08.330582386 +0100
>>
-@@ -28,12 +28,12 @@
>> +diff --git a/debian/pi-blaster.init
b/debian/pi-blaster.init
>> +index b142d70..01a686c 100644
>> +---
a/debian/pi-blaster.init
>>  b/debian/pi-blaster.init
>> +@@ -28,12
+28,12 @@ SCRIPTNAME=/etc/init.d/$NAME
>> [ -r /etc/default/$NAME ] && .
/etc/default/$NAME
>> 
>> # Load the VERBOSE setting and other rcS
variables
>> @@ -22,7 +37,7 @@ diff -ur git.org/pi-blaster.boot.sh [2]
git/pi-blaster.boot.sh [3]
>> 
>> #
>> # Function that starts the
daemon/service
>> -@@ -77,48 +77,23 @@
>> +@@ -77,48 +77,24 @@
do_stop()
>> 
>> case "$1" in
>> start)
>> @@ -52,6 +67,7 @@ diff -ur
git.org/pi-blaster.boot.sh [2] git/pi-blaster.boot.sh [3]
>> #
'force-reload' alias
>> #
>> - log_daemon_msg "Restarting $DESC"
"$NAME"
>> ++ echo "Restarting $DESC" "$NAME"
>> do_stop
>> - case "$?"
in
>> - 0|1)
>> @@ -67,11 +83,14 @@ diff -ur git.org/pi-blaster.boot.sh
[2] git/pi-blaster.boot.sh [3]
>> - log_end_msg 1
>> - ;;
>> - esac
>>
-+ do_start
>> ++ do_start
>> ;;
>> *)
>> - echo "Usage: $SCRIPTNAME
{start|stop|status|restart|force-reload}" >&2
>> -+ echo "Usage:
$SCRIPTNAME {start|stop|restart}" >&2
>> ++ echo "Usage: $SCRIPTNAME
{start|stop|restart|force-reload}" >&2
>> exit 3
>> ;;
>> esac
>> +--
>>
+1.9.1
>> +
>> diff --git a/recipes-devtools/pi-blaster/pi-blaster.inc
b/recipes-devtools/pi-blaster/pi-blaster.inc
>> index a3beccc..a548957
100644
>> --- a/recipes-devtools/pi-blaster/pi-blaster.inc
>> +++
b/recipes-devtools/pi-blaster/pi-blaster.inc
>> @@ -2,7 +2,7 @@
DESCRIPTION = "This project enables PWM on the GPIO pins you request of
a Raspbe
>> HOMEPAGE = "https://github.com/sarfata/pi-blaster/ [4]"
>>
SECTION = "devel/libs"
>> LICENSE = "MIT"
>> -LIC_FILES_CHKSUM =
"file://README.md;beginline=157;endline=170;md5=f20832f31126609af5a7bf2340014540"
>>
+LIC_FILES_CHKSUM =
"file://README.md;beginline=212;endline=239;md5=a012868ef5f83b9f257af253d7cb07a3"
>

> What changed here ?

The license is added in the end of the
README.md so in this case some additional description + modifications
earlier in the README.md caused the license text to move place. When it
comes to the license text I could only find changes in whitespace and
newlines. They seems to have been caused by the pi-blaster commit:
'0e1a1df

[yocto] [meta-raspberrypi][PATCH] pi-blaster: update to include proper rpi3 support

[Petter Mabäcker]

Update to latest available revision, in order to include proper rpi3
support as well as latest fixes.

Signed-off-by: Petter Mabäcker 
---
 .../files/remove-initscript-lsb-dependency.patch   | 37 --
 recipes-devtools/pi-blaster/pi-blaster.inc |  2 +-
 recipes-devtools/pi-blaster/pi-blaster_git.bb  |  2 +-
 3 files changed, 30 insertions(+), 11 deletions(-)

diff --git 
a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch 
b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
index 7ea9a3b..c8afe60 100644
--- a/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
+++ b/recipes-devtools/pi-blaster/files/remove-initscript-lsb-dependency.patch
@@ -1,13 +1,28 @@
-Remove dependencies on LSB functions
+From 1338f98a279616f4e5e9ea30a25d1dfa0c7df5d6 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petter=20Mab=C3=A4cker?= 
+Date: Sun, 4 Jun 2017 12:22:40 +0200
+Subject: [PATCH] Remove dependencies on LSB functions
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+See this as a rebase of the previous 'Remove dependencies on LSB
+functions patch' with only minor modifications from the original version,
+based on the work done by Alex Lennon  in
+'25fd817 pi-blaster: Added recipe'.
 
 Upstream-Status: Inappropriate [configuration]
 
-Signed-off-by: Alex Lennon 
+Signed-off-by: Petter Mabäcker 
+---
+ debian/pi-blaster.init | 38 +++---
+ 1 file changed, 7 insertions(+), 31 deletions(-)
 
-diff -ur git.org/pi-blaster.boot.sh git/pi-blaster.boot.sh
 git.org/pi-blaster.boot.sh 2014-05-20 14:49:44.378582168 +0100
-+++ git/pi-blaster.boot.sh 2014-05-20 14:51:08.330582386 +0100
-@@ -28,12 +28,12 @@
+diff --git a/debian/pi-blaster.init b/debian/pi-blaster.init
+index b142d70..01a686c 100644
+--- a/debian/pi-blaster.init
 b/debian/pi-blaster.init
+@@ -28,12 +28,12 @@ SCRIPTNAME=/etc/init.d/$NAME
  [ -r /etc/default/$NAME ] && . /etc/default/$NAME
  
  # Load the VERBOSE setting and other rcS variables
@@ -22,7 +37,7 @@ diff -ur git.org/pi-blaster.boot.sh git/pi-blaster.boot.sh
  
  #
  # Function that starts the daemon/service
-@@ -77,48 +77,23 @@
+@@ -77,48 +77,24 @@ do_stop()
  
  case "$1" in
start)
@@ -52,6 +67,7 @@ diff -ur git.org/pi-blaster.boot.sh git/pi-blaster.boot.sh
# 'force-reload' alias
#
 -  log_daemon_msg "Restarting $DESC" "$NAME"
++  echo "Restarting $DESC" "$NAME"
do_stop
 -  case "$?" in
 -0|1)
@@ -67,11 +83,14 @@ diff -ur git.org/pi-blaster.boot.sh git/pi-blaster.boot.sh
 -  log_end_msg 1
 -  ;;
 -  esac
-+  do_start
++do_start
;;
*)
 -  echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2
-+  echo "Usage: $SCRIPTNAME {start|stop|restart}" >&2
++  echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload}" >&2
exit 3
;;
  esac
+-- 
+1.9.1
+
diff --git a/recipes-devtools/pi-blaster/pi-blaster.inc 
b/recipes-devtools/pi-blaster/pi-blaster.inc
index a3beccc..a548957 100644
--- a/recipes-devtools/pi-blaster/pi-blaster.inc
+++ b/recipes-devtools/pi-blaster/pi-blaster.inc
@@ -2,7 +2,7 @@ DESCRIPTION = "This project enables PWM on the GPIO pins you 
request of a Raspbe
 HOMEPAGE = "https://github.com/sarfata/pi-blaster/";
 SECTION = "devel/libs"
 LICENSE = "MIT"
-LIC_FILES_CHKSUM = 
"file://README.md;beginline=157;endline=170;md5=f20832f31126609af5a7bf2340014540"
+LIC_FILES_CHKSUM = 
"file://README.md;beginline=212;endline=239;md5=a012868ef5f83b9f257af253d7cb07a3"
 
 SRC_URI = "git://github.com/sarfata/pi-blaster \
file://remove-initscript-lsb-dependency.patch \
diff --git a/recipes-devtools/pi-blaster/pi-blaster_git.bb 
b/recipes-devtools/pi-blaster/pi-blaster_git.bb
index 263852b..ac812ab 100644
--- a/recipes-devtools/pi-blaster/pi-blaster_git.bb
+++ b/recipes-devtools/pi-blaster/pi-blaster_git.bb
@@ -1,3 +1,3 @@
 require pi-blaster.inc
 
-SRCREV = "ec5e1b4c6191d8f9a538497dbbb86f9cf0de7016"
+SRCREV = "9f45eb23a8a3b2d1c08d08a6d68f206fe91ecf4c"
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] (no subject)

[Petter Mabäcker]

 

Hi, 

After a quick look, it seems like the problem is related to
the Upgrade to Qt 5.8 that was done in pyro. 

commit: 333949a Upgrade
to Qt 5.8 (in meta-qt5) 

The above mentioned commit causes
'./dynamic-layers/qt5-layer/recipes-qt/qt5/qtbase/0014-Add-IMX-GPU-support.patch'
(in meta-freescale) to fail. So this patch needs to be updated to match
the Qt 5.8 changes (that affects qmake.conf). 

BR Petter 

Petter
Mabäcker

Technux 
www.technux.se

2017-05-30 07:19
skrev Андрей Кононов: 

> i'm trying to build
> bitbake
fsl-image-multimedia-full -k
> using PYRO repository and my image
include QT5 library, but get error. The same configuration on MORTY
builded without errors 
> 
> Parsing recipes: 100%
||
Time: 0:19:36
> Parsing of 2258 .bb files complete (0 cached, 2258
parsed). 3050 targets, 506 skipped, 0 masked, 0 errors.
> NOTE:
Resolving any missing task queue dependencies 
> 
> Build
Configuration:
> BB_VERSION = "1.34.0"
> BUILD_SYS = "x86_64-linux"
>
NATIVELSBSTRING = "linuxmint-18.1"
> TARGET_SYS =
"arm-poky-linux-gnueabi"
> MACHINE = "imx6qpsabreauto"
> DISTRO =
"poky"
> DISTRO_VERSION = "2.3"
> TUNE_FEATURES = "arm armv7a vfp thumb
neon callconvention-hard cortexa9"
> TARGET_FPU = "hard"
> meta 
>
meta-poky = "HEAD:31389f8b0088a8a83aa5e50f11359b39934e4640"
> meta-oe 
>
meta-gnome 
> meta-multimedia =
"HEAD:5e82995148a2844c6f483ae5ddd1438d87ea9fb7"
> meta-freescale =
"HEAD:a65d13c315db447adda68b47faeb4c0afd0655b8"
>
meta-freescale-3rdparty =
"HEAD:1f37698ac62945b6531a316ec1232af23cc6c050"
> meta-freescale-distro
= "HEAD:cd5c7a2539f40004f74126e9fdf08254fd9a6390"
> meta-qt5 =
"master:6605c48f3a900da26425ef31d83eb1c95d551531"
> meta-ruby 
>
meta-networking 
> meta-python 
> meta-filesystems =
"HEAD:5e82995148a2844c6f483ae5ddd1438d87ea9fb7" 
> 
> Initialising
tasks: 100%
|#|
Time: 0:02:40
> NOTE: Executing SetScene Tasks
> NOTE: Executing
RunQueue Tasks
> ERROR: qtbase-5.8.0+gitAUTOINC+49dc9aa409-r0 do_patch:
Command Error: 'quilt --quiltrc
/media/barsuk/ext4.720/pyro/rootfs.systemd.qp/tmp/work/cortexa9hf-neon-mx6qdl-poky-linux-gnueabi/qtbase/5.8.0+gitAUTOINC+49dc9aa409-r0/recipe-sysroot-native/etc/quiltrc
push' exited with 0 Output:
> Applying patch
0014-Add-IMX-GPU-support.patch
> patching file
mkspecs/linux-oe-g++/qmake.conf
> Hunk #1 FAILED at 39.
> 1 out of 1
hunk FAILED -- rejects in file mkspecs/linux-oe-g++/qmake.conf
> Patch
0014-Add-IMX-GPU-support.patch does not apply (enforce with -f)
> ERROR:
qtbase-5.8.0+gitAUTOINC+49dc9aa409-r0 do_patch: Function failed:
patch_do_patch
> ERROR: Logfile of failure stored in:
/media/barsuk/ext4.720/pyro/rootfs.systemd.qp/tmp/work/cortexa9hf-neon-mx6qdl-poky-linux-gnueabi/qtbase/5.8.0+gitAUTOINC+49dc9aa409-r0/temp/log.do_patch.8895
>
ERROR: Task
(/media/barsuk/ext4.720/pyro/sources/meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_patch)
failed with exit code '1'
> WARNING: ttf-arphic-uming-20080216-r6
do_populate_lic: ttf-arphic-uming: No generic license file exists for:
Arphic-Public-License in any provider
> NOTE: Tasks Summary: Attempted
5116 tasks of which 6 didn't need to be rerun and 1 failed. 
> 
>
Summary: 1 task failed:
>
/media/barsuk/ext4.720/pyro/sources/meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_patch
>
Summary: There were 2 WARNING messages shown.
> Summary: There were 2
ERROR messages shown, returning a non-zero exit code. 
> 
> -- 
> Андрей
Кононов
 -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to install dbg package and not its dependencies?

[Petter Mabäcker]

 

Hi, 

If the problem is the footprint, then you can add below line
in the libexample recipe: 

INHIBIT_PACKAGE_DEBUG_SPLIT = "1" 

This
will prevent the build system from adding any debug info in the
libexample-dbg package. 

BR Petter 

[1] -
http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-INHIBIT_PACKAGE_DEBUG_SPLIT


Petter Mabäcker

Technux

www.technux.se

2017-05-30 04:17 skrev Ngọc Thi
Huỳnh: 

> I have both app-example-DBG & app-example in IMAGE_INSTALL
and the result is app-example-dbg & app-example & libexample-dbg &
libexample are included in the final image. 
> 
> Huỳnh Ngọc Thi
> 
>
-so61pi 
> 
> On Mon, May 29, 2017 at 9:58 PM, Leonardo Sandoval
 wrote:
> 
>> On Sun,
2017-05-28 at 17:23 +0700, Ngọc Thi Huỳnh wrote:
>> > Hi everyone,
>>
>
>> >
>> > Let's say I have app-example package which depends on
libexample.
>> >
>> > When I add app-example-dbg to IMAGE_INSTALL,
libexample-dbg package is
>> > automatically included in the final image
which makes the image size
>> > become bigger.
>> >
>> what about
installing the non-dbg ones?
>> 
>>> 
>> > In this case, is there a way
to prevent libexample-dbg from being
>> > installed?
>> >
>> >
>> >
Thanks,
>> >
>> > Thi Huynh
>> > > --
>> >
___
>> > yocto mailing
list
>> > yocto@yoctoproject.org
>> >
https://lists.yoctoproject.org/listinfo/yocto [1]
 

Links:
--
[1]
https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi-base.bbclass: remove version hack

[Petter Mabäcker]

 

2016-12-13 06:39 skrev Petter Mabäcker: 

> 2016-12-13 00:55 skrev
Andreas Müller: 
> 
>> On Mon, Dec 12, 2016 at 11:33 PM, Petter Mabäcker
 wrote:
>> 
>>> 2016-12-12 06:21 skrev Khem Raj: On
Thu, Dec 8, 2016 at 2:40 AM, Andreas Müller
 wrote: * no more required (version > 3.17
| > 4.3.x | > 4.4.5) * causes error with rt kernel I think this is ok to
apply now. Signed-off-by: Andreas Müller 
--- classes/linux-raspberrypi-base.bbclass | 15 --- 1 file
changed, 15 deletions(-) diff --git
a/classes/linux-raspberrypi-base.bbclass
b/classes/linux-raspberrypi-base.bbclass index 3a6e33d..dc2330a 100644
--- a/classes/linux-raspberrypi-base.bbclass +++
b/classes/linux-raspberrypi-base.bbclass @@ -14,21 +14,6 @@ def
get_dts(d, ver=None): from the kernel staging ''' ver =
get_kernelversion_file(staging_dir) - if ver is not None: - min_ver =
ver.split('.', 3) - else: - return dts - - # Always turn off device tree
support for kernel's < 3.18 - try: - if int(min_ver[0]) >= 4: - if
(int(min_ver[1]) < 4) or (int(min_ver[1]) == 4 and int(min_ver[2]) < 6):
- dts = ' '.join([(re.sub(r'(.*).dtbo$', r'1-overlay.dtb', x)) for x in
dts.split()]) - elif int(min_ver[1]) < 18: - dts = "" - except
IndexError: - min_ver = None - return dts -- 2.7.4 --
___ yocto mailing list
yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[1]
>> 
>>> I think you should go even one step further and revert the
entire commit merging this obsolete functionality: "git revert
4a4373c02d3d8355a2e5faa10af61450e5b093d8" .
>> BR Petter 
>> 
>> To be
honest: I have forked meta-raspberrypi and don't use it any
>> more.
Just wanted to be a good boy. So maybe you want to send the
>> revert
here?
>> 
>> Andreas
>> 
>>> 
> 
> Oh I see. Sure, I can send something
up. 
> 
> Petter Mabäcker
> 
> Technux 
>
www.technux.se

This wasn't as easy that I first thought. I totally
forgot about that Device Tree Overlays are assumed to be suffixed by
'-overlay.dtb' (4.1.x) or by '.dtbo' (4.4.9+). So it's not possible to
just revert the commit and handle some simple conflicts..

Andrei: I
think you can go ahead and merge this patch when fully verified. Then I
instead will see if I can do some cleanup in a later step. But at least
this patch simplifies things and solves the rt-issue.

BR Petter



Links:
--
[1] https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi-base.bbclass: remove version hack

[Petter Mabäcker]

 

2016-12-13 00:55 skrev Andreas Müller: 

> On Mon, Dec 12, 2016 at
11:33 PM, Petter Mabäcker  wrote:
> 
>> 2016-12-12
06:21 skrev Khem Raj: On Thu, Dec 8, 2016 at 2:40 AM, Andreas Müller
 wrote: * no more required (version > 3.17
| > 4.3.x | > 4.4.5) * causes error with rt kernel I think this is ok to
apply now. Signed-off-by: Andreas Müller 
--- classes/linux-raspberrypi-base.bbclass | 15 --- 1 file
changed, 15 deletions(-) diff --git
a/classes/linux-raspberrypi-base.bbclass
b/classes/linux-raspberrypi-base.bbclass index 3a6e33d..dc2330a 100644
--- a/classes/linux-raspberrypi-base.bbclass +++
b/classes/linux-raspberrypi-base.bbclass @@ -14,21 +14,6 @@ def
get_dts(d, ver=None): from the kernel staging ''' ver =
get_kernelversion_file(staging_dir) - if ver is not None: - min_ver =
ver.split('.', 3) - else: - return dts - - # Always turn off device tree
support for kernel's < 3.18 - try: - if int(min_ver[0]) >= 4: - if
(int(min_ver[1]) < 4) or (int(min_ver[1]) == 4 and int(min_ver[2]) < 6):
- dts = ' '.join([(re.sub(r'(.*).dtbo$', r'1-overlay.dtb', x)) for x in
dts.split()]) - elif int(min_ver[1]) < 18: - dts = "" - except
IndexError: - min_ver = None - return dts -- 2.7.4 --
___ yocto mailing list
yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[1]
> 
>> I think you should go even one step further and revert the
entire commit merging this obsolete functionality: "git revert
4a4373c02d3d8355a2e5faa10af61450e5b093d8" .
> BR Petter 
> 
> To be
honest: I have forked meta-raspberrypi and don't use it any
> more. Just
wanted to be a good boy. So maybe you want to send the
> revert here?
>

> Andreas
> 
>> 

Oh I see. Sure, I can send something up. 

Petter
Mabäcker

Technux 
www.technux.se



Links:
--
[1] https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi-base.bbclass: remove version hack

[Petter Mabäcker]

 

2016-12-12 06:21 skrev Khem Raj: 

> On Thu, Dec 8, 2016 at 2:40 AM,
Andreas Müller
>  wrote:
> 
>> * no more
required (version > 3.17 | > 4.3.x | > 4.4.5) * causes error with rt
kernel
> 
> I think this is ok to apply now.
> 
>> Signed-off-by:
Andreas Müller  ---
classes/linux-raspberrypi-base.bbclass | 15 --- 1 file
changed, 15 deletions(-) diff --git
a/classes/linux-raspberrypi-base.bbclass
b/classes/linux-raspberrypi-base.bbclass index 3a6e33d..dc2330a 100644
--- a/classes/linux-raspberrypi-base.bbclass +++
b/classes/linux-raspberrypi-base.bbclass @@ -14,21 +14,6 @@ def
get_dts(d, ver=None): from the kernel staging ''' ver =
get_kernelversion_file(staging_dir) - if ver is not None: - min_ver =
ver.split('.', 3) - else: - return dts - - # Always turn off device tree
support for kernel's < 3.18 - try: - if int(min_ver[0]) >= 4: - if
(int(min_ver[1]) < 4) or (int(min_ver[1]) == 4 and int(min_ver[2]) < 6):
- dts = ' '.join([(re.sub(r'(.*).dtbo$', r'1-overlay.dtb', x)) for x in
dts.split()]) - elif int(min_ver[1]) < 18: - dts = "" - except
IndexError: - min_ver = None - return dts -- 2.7.4 --
___ yocto mailing list
yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[1]

I think you should go even one step further and revert the entire
commit merging this obsolete functionality: "git revert
4a4373c02d3d8355a2e5faa10af61450e5b093d8" . 

BR Petter


Links:
--
[1] https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to build a simple kernel modul

[Petter Mabäcker]

 

2016-05-09 17:06 skrev s.jar...@esa-grimma.de: 

> Hej, 
> 
> I want
to build a recipe for a simple GPIO Module. I found no tutorial at the
documentation. What is the comon way to build a simple kernel module? 
>

> The Makefile looks like: 
> # 
> obj-m += ledmodule.o 
> 
>
SRC := $(shell pwd) 
> 
> all: modules 
> 
> modules: 
> $(MAKE) -C
$(KERNEL_SRC) M=$(SRC) modules 
> 
> modules_install: 
> $(MAKE) -C
$(KERNEL_SRC) M=$(SRC) modules_install 
> 
> clean: 
> rm -rf *.o *.ko
*.mod.c 
> # 
> The recipe contains: 
> # 
> SUMMARY =
"ledmodule" 
> SECTION = "" 
> LICENSE = "CLOSED" 
> 
> inherit module

> 
> SRC_URI = "file://ledmodule.c [1] 
> file://Makefile [2] 
> " 
> S
= "${WORKDIR}/ledmodule-0.1" 
> # 
> 
> Regards
> 
> Stefan
Jaritz
> Entwickler
> 
>

> ESA
Elektroschaltanlagen Grimma GmbH
> Broner Ring 30
> 04668 Grimma
>
Telefon: +49 3437 9211 176
> Telefax: +49 3437 9211 26
> E-Mail:
s.jar...@esa-grimma.de
> Internet: www.esa-grimma.de
> 
>
Geschäftsführer:
> Dipl.-Ing. Jörg Gaitzsch
> Jörg Reinker
> 
> Sitz der
Gesellschaft: Grimma
> Ust.-ID: DE 141784437
> Amtsgericht: Leipzig, HRB
5159
> Steuernummer: 238/108/00755
> 
> Diese E-Mail enthält
vertrauliche und/oder rechtlich geschützte Informationen. 
> Wenn Sie
nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten

> haben, informieren Sie bitte sofort den Absender und löschen Sie
diese 
> Nachricht. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail 
> ist nicht gestattet.
> 
> This e-mail may
contain confidential and/or privileged information. If you are 
> not
the intended recipient (or have received this e-mail in error) please 
>
notify the sender immediately and destroy this e-mail. Any unauthorized

> copying, disclosure or distribution of the material in this e-mail is
strictly 
> forbidden.

Hi, 

There are actually some guides for this,
see lab4
in:
https://www.yoctoproject.org/sites/default/files/kernel-lab-2.1_0.pdf


But to simply build a module using bitbake, you can just do: 

$
bitbake ledmodule 

then you will find your recipe and the module in the
./tmp/work/ structure (assuming you are not inheriting 'rm_work' in
local.conf...). 

if you just want to compile it, you can run: 

$
bitbake ledmodule -c compile 

BR Petter 

Petter Mabäcker

Technux

www.technux.se
 

Links:
--
[1]
file://sek4_ledmodule.c/
[2] file://Makefile/
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] sdcard_image-rpi.bbclass: Fix do_image_rpi_sdimg tashhash mismatch

[Petter Mabäcker]

 

2016-04-29 03:57 skrev Jonathan Liu: 

> IMAGE_CMD_rpi-sdimg() uses
the IMAGEDATESTAMP variable, so the taskhash
> of the function keeps
changing. This results in a taskhash mismatch
> error.
> 
> Fix this by
excluding the IMAGEDATESTAMP variable from the checksum.
> 
> Change-Id:
Ie6f30ad29e279d5312ec655ac4a3bf246c8a04de
> Signed-off-by: Jonathan Liu

> ---
> classes/sdcard_image-rpi.bbclass | 1 +
> 1
file changed, 1 insertion(+)
> 
> diff --git
a/classes/sdcard_image-rpi.bbclass b/classes/sdcard_image-rpi.bbclass
>
index 1b055bd..989d77a 100644
> --- a/classes/sdcard_image-rpi.bbclass
>
+++ b/classes/sdcard_image-rpi.bbclass
> @@ -67,6 +67,7 @@ SDIMG =
"${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.rpi-sdimg"
> FATPAYLOAD ?=
""
> 
> IMAGEDATESTAMP = "${@time.strftime('%Y.%m.%d',time.gmtime())}"
>
+IMAGE_CMD_rpi-sdimg[vardepsexclude] = "IMAGEDATESTAMP"
> 
>
IMAGE_CMD_rpi-sdimg () {
> 
> -- 
> 2.8.0

Hi Andrei, 

Any plans for
merging this patch soon? I have been using it in my tree for quite some
time and the fix seems reasonable and solves the annoying taskhash
problem when creating the image. 

BR Petter 

Petter Mabäcker

Technux

www.technux.se
 -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH v2 3/5] rpi-base.inc: Add overlay for rpi-ft5406

[Petter Mabäcker]

 

2016-04-14 00:04 skrev Trevor Woerner: 

> On Wed 2016-03-30 @
04:35:47 PM, Petter Mabäcker wrote:
> 
>> rpi-ft5406 is an enabler for
Official Raspberry Pi 7 inch touchscreen support.
> 
> I have an
official raspberry pi 7" touchscreen and it's not obvious to me how
> I
would go about enabling it in my config. If I had one of the others I
would
> simply add:
> 
> MACHINE_FEATURES += "pitft pitft22"
> 
> or
>

> MACHINE_FEATURES += "pitft pitft28r"
> 
> to my conf/local.conf, but
what do I do for the official touchscreen?
> 
> Also, by trial and error
I've discovered that my touchscreen comes up as
> /dev/fb0 and not
/dev/fb1. But the xorg config for touchscreen support assumes
>
/dev/fb1. Am I doing something wrong in my build or can anyone think of
a
> reason why my screen would be /dev/fb0 instead of /dev/fb1?
> 
> By
the way
> 
> MACHINE_FEATURES += "pitft pitft22"
> 
> seems to work for
me if I use /dev/fb0, but I'm not sure if that's a fluke?
> 
> Best
regards,
> Trevor

Hi Trevor, 

Actually it's very simple for the
Official rpi touchscreen. 

1. Ensure that you DON'T have pitft support
enabled when using this touchscreen! (PiTFT uses /dev/fb1, which isn't
the case for the official toucscreen). 

2. Build for example
'core-image-sato' 

3. Add: 

echo "dtoverlay=rpi-ft5406" >>
/path/to/sdcard/boot/config.txt 

...and you are done. 

Like stated in
the commit msg this is just an enabler for being able to configure
rpi-ft5406. When I have time I will send the complete solution for this,
perhaps a good idea is to do like a MACHINE_FEATURES as well, to make it
look similar to the PiTFT's usage? 

BR Petter 

Petter
Mabäcker

Technux 
www.technux.se
 -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 1/1] README: Mention all the supported machines

[Petter Mabäcker]

On 04/04/2016 07:54 PM, Andrei Gherzan wrote:

Signed-off-by: Andrei Gherzan 
---
  README | 5 -
  1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/README b/README
index 536926b..542b135 100644
--- a/README
+++ b/README
@@ -73,7 +73,10 @@ revision: HEAD
  a. source poky/oe-init-build-env rpi-build
  b. Add needed layer to bblayers.conf:
  - meta-raspberrypi
-c. Set MACHINE to "raspberrypi"/"raspberrypi2" in local.conf
+c. Set MACHINE in local.conf to one of the supported boards:
+- raspberrypi
+- raspberrypi2
+- raspberrypi3
  d. bitbake rpi-hwup-image
  e. dd to a SD card the generated sdimg file (use xzcat if rpi-sdimg.xz is 
used)
  f. Boot your RPI.
Good, this is a tiny but important change! Should we also mention 
raspberrypi0? Currently it just includes raspberrypi.conf and the the 
raspberrypi0 MACHINEOVERRIDE isn't used for anything, but still it is a 
defined MACHINE. What do you think?


BR Petter
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] Adding more screens / PiTFT support.

[Petter Mabäcker]

 

2016-04-04 15:17 skrev GUEYTAT Julien: 

> Hi, 
> 
> I would like to
add PiTFT support to the meta-raspberry layer. Or at least I would like
to add it in my own BSP layer. 
> 
> I read that Peter were playing with
that recently. Could you please give me some hints to do so? 
> 
> I
have at least two more screens to integrate. 
> 
> If someone could
point me to an example of a BSP based on meta-raspberrypi that would be
awesome. 
> 
> Thanks in advance, 
> 
> Best Regards 
> 
> JULIEN
GUEYTAT 
> 
> INGÉNIEUR INFORMATIQUE 
> 
> 1027, avenue du Docteur
Julien Lefebre BP27 
> 
> 06271 Villeneuve-Loubet Cedex 
> 
> Fixe : +33
(0) 492 024 545
> Mob : +33(0) 617 980 383
> Fax : +33(0) 492 024 546
>
Email : j.guey...@cdssoft.studiel.fr 
> 
> www : www.studiel.fr [1] 
>

> PPENSEZ ENVIRONNEMENT, IMPRIMEZ SEULEMENT SI NÉCESSAIRE

Hi Julien,


After some discussions with the community, we decided that the
official meta-raspberrypi pitft support should be added using
MACHINE_FEATURES. If you look in README for meta-raspberrypi there are
some basic description about how to enable support: 

For a already
supported pitft model (pitft22 is supported and 28r is on it's way
https://lists.yoctoproject.org/pipermail/yocto/2016-March/029284.html),
you can just add below MACHINE_FEATURES to local.conf:


MACHINE_FEATURES += "pitft pitft22" 

In order to add support for
additional models you can use
https://lists.yoctoproject.org/pipermail/yocto/2016-March/029284.html as
a reference.
 Basically what you need are to: 

* add the overlay for
the screen 

* Add dtoverlay option with wanted default arguments in
rpi-config_git.bb 

* Add a default calibration (if needed) 

Assuming
an overlay exists for your model, it shouldn't be so tricky to fix the
rest.. 

BR Petter 

Petter Mabäcker

Technux

www.technux.se
 

Links:
--
[1]
http://www.studiel.fr/
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH v2 3/5] rpi-base.inc: Add overlay for rpi-ft5406

[Petter Mabäcker]

rpi-ft5406 is an enabler for Official Raspberry Pi 7 inch
touchscreen support.

Signed-off-by: Petter Mabäcker 
---
 conf/machine/include/rpi-base.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index f70e952..34eb774 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -35,6 +35,7 @@ KERNEL_DEVICETREE ?= " \
 overlays/pitft22-overlay.dtb \
 overlays/pitft28-resistive-overlay.dtb \
 overlays/pps-gpio-overlay.dtb \
+overlays/rpi-ft5406-overlay.dtb \
 overlays/w1-gpio-overlay.dtb \
 overlays/w1-gpio-pullup-overlay.dtb \
 "
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH v2 5/5] linux-raspberrypi: Drop support for 3.14

[Petter Mabäcker]

General policy is to support three kernel versions; latest stable + two
longterm versions. These are currently 4.4, 4.1, and 3.18.

Signed-off-by: Petter Mabäcker 
---
 .../0001-ASoC-Add-BCM2708-fixes.patch  | 263 -
 ...ng-lock-from-atomic-context-in-i2c-driver.patch | 235 --
 recipes-kernel/linux/linux-raspberrypi_3.14.bb |  11 -
 3 files changed, 509 deletions(-)
 delete mode 100644 
recipes-kernel/linux/linux-raspberrypi-3.14/0001-ASoC-Add-BCM2708-fixes.patch
 delete mode 100644 
recipes-kernel/linux/linux-raspberrypi-3.14/0002-Fix-grabbing-lock-from-atomic-context-in-i2c-driver.patch
 delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.14.bb

diff --git 
a/recipes-kernel/linux/linux-raspberrypi-3.14/0001-ASoC-Add-BCM2708-fixes.patch 
b/recipes-kernel/linux/linux-raspberrypi-3.14/0001-ASoC-Add-BCM2708-fixes.patch
deleted file mode 100644
index 26c71b8..000
--- 
a/recipes-kernel/linux/linux-raspberrypi-3.14/0001-ASoC-Add-BCM2708-fixes.patch
+++ /dev/null
@@ -1,263 +0,0 @@
-From e73a69601c65103b0e032e6093af0f00a1e1af3a Mon Sep 17 00:00:00 2001
-From: Florian Meier 
-Date: Fri, 22 Nov 2013 14:33:38 +0100
-Subject: [PATCH 1/2] ASoC: Add BCM2708 fixes
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-(cherry-pick remaining parts of
-730cb8a1216f9da3d097072cd9bb06e0db348172)
-
-bcm2708-i2s: Update bclk_ratio to more correct values
-
-Move GPIO setup to hw_params.
-
-This is used to stop the I2S driver from breaking
-the GPIO setup for other uses of the PCM interface
-
-Configure GPIOs for I2S based on revision/card settings
-
-With RPi model B+, assignment of the I2S GPIO pins has changed.
-This patch uses the board revision to auto-detect the GPIOs used
-for I2S. It also allows sound card drivers to set the GPIOs that
-should be used. This is especially important with the Compute
-Module.
-
-bcm2708-i2s: Avoid leak from iomap when accessing gpio
-
-bcm2708: Eliminate i2s debugfs directory error
-
-Qualify the two regmap ranges uses by bcm2708-i2s ('-i2s' and '-clk')
-to avoid the name clash when registering debugfs entries.
-
-Upstream-Status: Pending
-
-Signed-off-by: Petter Mabäcker 
-
-Conflicts:
-   sound/soc/bcm/Kconfig
-   sound/soc/bcm/Makefile
-   sound/soc/bcm/bcm2708-i2s.c

- sound/soc/bcm/bcm2708-i2s.c | 82 -
- sound/soc/bcm/bcm2708-i2s.h | 35 +++
- 2 files changed, 102 insertions(+), 15 deletions(-)
- create mode 100644 sound/soc/bcm/bcm2708-i2s.h
-
-diff --git a/sound/soc/bcm/bcm2708-i2s.c b/sound/soc/bcm/bcm2708-i2s.c
-index 9976571..3fcb740 100644
 a/sound/soc/bcm/bcm2708-i2s.c
-+++ b/sound/soc/bcm/bcm2708-i2s.c
-@@ -31,6 +31,8 @@
-  * General Public License for more details.
-  */
- 
-+#include "bcm2708-i2s.h"
-+
- #include 
- #include 
- #include 
-@@ -38,6 +40,7 @@
- #include 
- #include 
- #include 
-+#include 
- 
- #include 
- #include 
-@@ -46,6 +49,8 @@
- #include 
- #include 
- 
-+#include 
-+
- /* Clock registers */
- #define BCM2708_CLK_PCMCTL_REG  0x00
- #define BCM2708_CLK_PCMDIV_REG  0x04
-@@ -163,6 +168,9 @@ static const unsigned int 
bcm2708_clk_freq[BCM2708_CLK_SRC_HDMI+1] = {
- #define BCM2708_DMA_DREQ_PCM_TX   2
- #define BCM2708_DMA_DREQ_PCM_RX   3
- 
-+/* I2S pin configuration */
-+static int bcm2708_i2s_gpio=BCM2708_I2S_GPIO_AUTO;
-+
- /* General device struct */
- struct bcm2708_i2s_dev {
-   struct device   *dev;
-@@ -174,6 +182,12 @@ struct bcm2708_i2s_dev {
-   struct regmap *clk_regmap;
- };
- 
-+void bcm2708_i2s_set_gpio(int gpio) {
-+  bcm2708_i2s_gpio=gpio;
-+}
-+EXPORT_SYMBOL(bcm2708_i2s_set_gpio);
-+
-+
- static void bcm2708_i2s_start_clock(struct bcm2708_i2s_dev *dev)
- {
-   /* Start the clock if in master mode */
-@@ -306,6 +320,25 @@ static int bcm2708_i2s_set_dai_bclk_ratio(struct 
snd_soc_dai *dai,
- }
- 
- 
-+static int bcm2708_i2s_set_function(unsigned offset, int function)
-+{
-+  #define GPIOFSEL(x)  (0x00+(x)*4)
-+  void __iomem *gpio = __io_address(GPIO_BASE);
-+  unsigned alt = function <= 3 ? function + 4: function == 4 ? 3 : 2;
-+  unsigned gpiodir;
-+  unsigned gpio_bank = offset / 10;
-+  unsigned gpio_field_offset = (offset - 10 * gpio_bank) * 3;
-+
-+  if (offset >= BCM2708_NR_GPIOS)
-+  return -EINVAL;
-+
-+  gpiodir = readl(gpio + GPIOFSEL(gpio_bank));
-+  gpiodir &= ~(7 << gpio_field_offset);
-+  gpiodir |= alt << gpio_field_offset;
-+  writel(gpiodir, gpio + GPIOFSEL(gpio_bank));
-+  return 0;
-+}
-+
- static void bcm2708_i2s_setup_gpio(void)
- {
-   /*
-@@ -314,20 +347,37 @@ static void bcm2708_i2s_setup_gpio(void)
-* TODO Better way would be to handle
-* this in the device tree!
-*/
--#define INP_GPIO(g) *(gpio+((g)/10)) &= ~(7<<(((g)%10)*3

[yocto] [meta-raspberrypi][PATCH v2 1/5] pitft: Add support for pitft28r

[Petter Mabäcker]

The support for PiTFT 28 inch resistive touchscreen is optional
and can be enabled by adding below in local.conf:

MACHINE_FEATURES += "pitft pitft28r"

While at it also fix a minor typo in README.

Signed-off-by: Petter Mabäcker 
---
 README  | 3 ++-
 conf/machine/include/rpi-base.inc   | 1 +
 recipes-bsp/bootfiles/rpi-config_git.bb | 6 ++
 .../xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/98-pitft.conf  | 5 +
 .../xserver-xf86-config/rpi/xorg.conf.d/99-calibration.conf | 6 ++
 .../xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf  | 5 -
 recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend  | 6 --
 recipes-kernel/linux/linux-raspberrypi.inc  | 2 ++
 8 files changed, 26 insertions(+), 8 deletions(-)
 create mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/98-pitft.conf
 create mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-calibration.conf
 delete mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf

diff --git a/README b/README
index 536926b..3a7735c 100644
--- a/README
+++ b/README
@@ -204,7 +204,7 @@ kernels.
 NOTE: KERNEL_DEVICETREE is default enabled for kernel >= 3.18 and always 
disabled for
   older kernel versions.
 
-3.L. Eenable SPI bus
+3.L. Enable SPI bus
 
 When using device tree kernels, set this variable to enable the SPI bus
 ENABLE_SPI_BUS = "1"
@@ -232,6 +232,7 @@ the modelname should be added as a MACHINE_FEATURES in 
local.conf like below:
 
 List of currently supported models:
 - pitft22
+- pitft28r
 
 
 4. Extra apps
diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index 792150e..a9e8053 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -33,6 +33,7 @@ KERNEL_DEVICETREE ?= " \
 overlays/iqaudio-dacplus-overlay.dtb \
 overlays/lirc-rpi-overlay.dtb \
 overlays/pitft22-overlay.dtb \
+overlays/pitft28-resistive-overlay.dtb \
 overlays/pps-gpio-overlay.dtb \
 overlays/w1-gpio-overlay.dtb \
 overlays/w1-gpio-pullup-overlay.dtb \
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index 4d41723..2941982 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -17,6 +17,7 @@ PR = "r4"
 
 PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
 PITFT22="${@bb.utils.contains("MACHINE_FEATURES", "pitft22", "1", "0", d)}"
+PITFT28r="${@bb.utils.contains("MACHINE_FEATURES", "pitft28r", "1", "0", d)}"
 
 inherit deploy
 
@@ -90,6 +91,11 @@ do_deploy() {
 echo "# Enable PITFT22 display" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtoverlay=pitft22,rotate=270,speed=3200,txbuflen=32768" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 fi
+
+if [ "${PITFT28r}" = "1" ]; then
+echo "# Enable PITFT28r display" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo 
"dtoverlay=pitft28-resistive,rotate=90,speed=3200,txbuflen=32768" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+fi
 }
 
 addtask deploy before do_package after do_install
diff --git 
a/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/98-pitft.conf
 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/98-pitft.conf
new file mode 100644
index 000..0d2b36b
--- /dev/null
+++ 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/98-pitft.conf
@@ -0,0 +1,5 @@
+Section "Device"
+Identifier "Adafruit PiTFT"
+Driver "fbdev"
+Option "fbdev" "/dev/fb1"
+EndSection
diff --git 
a/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-calibration.conf
 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-calibration.conf
new file mode 100644
index 000..f8b578c
--- /dev/null
+++ 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-calibration.conf
@@ -0,0 +1,6 @@
+Section "InputClass"
+Identifier  "calibration"
+MatchProduct"stmpe-ts"
+Option  "Calibration"   "3800 200 200 3800"
+Option  "SwapAxes"  "1"
+EndSection
diff --git 
a/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
deleted file mode 100644
index 0d2

[yocto] [meta-raspberrypi][PATCH v2 4/5] .gitignore: Ignore some additional files

[Petter Mabäcker]

Signed-off-by: Petter Mabäcker 
---
 .gitignore | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/.gitignore b/.gitignore
index f235765..bd5616a 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,5 @@
 build*
 *~
 .*.swp
+*.orig
+*.rej
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH v2 0/5] Various upgrade/fixes from Technux

[Petter Mabäcker]

Various fixes from Technux, with focus on PiTFT28 resistive support and
Official Raspberry Pi 7 inch touchscreen enablers.

Petter Mabäcker (5):
  pitft: Add support for pitft28r
  rpi-base.inc: Remove deprecated MACHINE_FEATURES
  rpi-base.inc: Add overlay for rpi-ft5406
  .gitignore: Ignore some additional files
  linux-raspberrypi: Drop support for 3.14

 .gitignore |   2 +
 README |   3 +-
 conf/machine/include/rpi-base.inc  |   4 +-
 recipes-bsp/bootfiles/rpi-config_git.bb|   6 +
 .../rpi/xorg.conf.d/98-pitft.conf  |   5 +
 .../rpi/xorg.conf.d/99-calibration.conf|   6 +
 .../rpi/xorg.conf.d/99-pitft.conf  |   5 -
 .../xorg-xserver/xserver-xf86-config_0.1.bbappend  |   6 +-
 .../0001-ASoC-Add-BCM2708-fixes.patch  | 263 -
 ...ng-lock-from-atomic-context-in-i2c-driver.patch | 235 --
 recipes-kernel/linux/linux-raspberrypi.inc |   2 +
 recipes-kernel/linux/linux-raspberrypi_3.14.bb |  11 -
 12 files changed, 30 insertions(+), 518 deletions(-)
 create mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/98-pitft.conf
 create mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-calibration.conf
 delete mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
 delete mode 100644 
recipes-kernel/linux/linux-raspberrypi-3.14/0001-ASoC-Add-BCM2708-fixes.patch
 delete mode 100644 
recipes-kernel/linux/linux-raspberrypi-3.14/0002-Fix-grabbing-lock-from-atomic-context-in-i2c-driver.patch
 delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.14.bb

-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH v2 2/5] rpi-base.inc: Remove deprecated MACHINE_FEATURES

[Petter Mabäcker]

Signed-off-by: Petter Mabäcker 
---
 conf/machine/include/rpi-base.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index a9e8053..f70e952 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -40,7 +40,7 @@ KERNEL_DEVICETREE ?= " \
 "
 KERNEL_IMAGETYPE ?= "Image"
 
-MACHINE_FEATURES += "kernel26 apm usbhost keyboard vfat ext2 screen 
touchscreen alsa bluetooth wifi sdio"
+MACHINE_FEATURES += "apm usbhost keyboard vfat ext2 screen touchscreen alsa 
bluetooth wifi sdio"
 
 # Raspberry Pi has no hardware clock
 MACHINE_FEATURES_BACKFILL_CONSIDERED = "rtc"
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 1/4] pitft: Add support for pitft28r

[Petter Mabäcker]

On 03/29/2016 05:59 PM, Khem Raj wrote:

On Mar 29, 2016, at 8:04 AM, Petter Mabäcker  wrote:

The support for PiTFT 28 inch resistive touchscreen is optional
and can be enabled by adding below in local.conf:

MACHINE_FEATURES += "pitft pitft28r”


will this work with all kernel recipes available in layer ?
It works on 3.18+. I just realized that 3.14 support was not removed 
when we took in 4.4 (so it will not work on that kernel). Since the 
general policy we have is to support three kernel versions; latest 
stable (4.4) + two longterm (4.1 and 3.18), I can send up a commit that 
removes 3.14 support in 'master' within this series.


Thanks for your help to pointing this out!

BR Petter




Signed-off-by: Petter Mabäcker 
---
README  | 1 +
conf/machine/include/rpi-base.inc   | 1 +
recipes-bsp/bootfiles/rpi-config_git.bb | 6 ++
.../xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/98-pitft.conf  | 5 +
.../xserver-xf86-config/rpi/xorg.conf.d/99-calibration.conf | 6 ++
.../xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf  | 5 -
recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend  | 6 --
recipes-kernel/linux/linux-raspberrypi.inc  | 2 ++
8 files changed, 25 insertions(+), 7 deletions(-)
create mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/98-pitft.conf
create mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-calibration.conf
delete mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf

diff --git a/README b/README
index 536926b..54b1ac3 100644
--- a/README
+++ b/README
@@ -232,6 +232,7 @@ the modelname should be added as a MACHINE_FEATURES in 
local.conf like below:

List of currently supported models:
 - pitft22
+- pitft28r


4. Extra apps
diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index 792150e..a9e8053 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -33,6 +33,7 @@ KERNEL_DEVICETREE ?= " \
 overlays/iqaudio-dacplus-overlay.dtb \
 overlays/lirc-rpi-overlay.dtb \
 overlays/pitft22-overlay.dtb \
+overlays/pitft28-resistive-overlay.dtb \
 overlays/pps-gpio-overlay.dtb \
 overlays/w1-gpio-overlay.dtb \
 overlays/w1-gpio-pullup-overlay.dtb \
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index 4d41723..2941982 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -17,6 +17,7 @@ PR = "r4"

PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
PITFT22="${@bb.utils.contains("MACHINE_FEATURES", "pitft22", "1", "0", d)}"
+PITFT28r="${@bb.utils.contains("MACHINE_FEATURES", "pitft28r", "1", "0", d)}"

inherit deploy

@@ -90,6 +91,11 @@ do_deploy() {
 echo "# Enable PITFT22 display" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtoverlay=pitft22,rotate=270,speed=3200,txbuflen=32768" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 fi
+
+if [ "${PITFT28r}" = "1" ]; then
+echo "# Enable PITFT28r display" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtoverlay=pitft28-resistive,rotate=90,speed=3200,txbuflen=32768" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+fi
}

addtask deploy before do_package after do_install
diff --git 
a/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/98-pitft.conf
 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/98-pitft.conf
new file mode 100644
index 000..0d2b36b
--- /dev/null
+++ 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/98-pitft.conf
@@ -0,0 +1,5 @@
+Section "Device"
+Identifier "Adafruit PiTFT"
+Driver "fbdev"
+Option "fbdev" "/dev/fb1"
+EndSection
diff --git 
a/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-calibration.conf
 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-calibration.conf
new file mode 100644
index 000..f8b578c
--- /dev/null
+++ 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-calibration.conf
@@ -0,0 +1,6 @@
+Section "InputClass"
+Identifier  "calibration"
+MatchProduct"stmpe-ts"
+Option  "Calibration"   "3800 200 200 3800"
+Option  "SwapAxes"  "1"
+EndSection
diff --git 
a/recipes-graphics/xorg-xserver/xser

[yocto] [meta-raspberrypi][PATCH 1/4] pitft: Add support for pitft28r

[Petter Mabäcker]

The support for PiTFT 28 inch resistive touchscreen is optional
and can be enabled by adding below in local.conf:

MACHINE_FEATURES += "pitft pitft28r"

Signed-off-by: Petter Mabäcker 
---
 README  | 1 +
 conf/machine/include/rpi-base.inc   | 1 +
 recipes-bsp/bootfiles/rpi-config_git.bb | 6 ++
 .../xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/98-pitft.conf  | 5 +
 .../xserver-xf86-config/rpi/xorg.conf.d/99-calibration.conf | 6 ++
 .../xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf  | 5 -
 recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend  | 6 --
 recipes-kernel/linux/linux-raspberrypi.inc  | 2 ++
 8 files changed, 25 insertions(+), 7 deletions(-)
 create mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/98-pitft.conf
 create mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-calibration.conf
 delete mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf

diff --git a/README b/README
index 536926b..54b1ac3 100644
--- a/README
+++ b/README
@@ -232,6 +232,7 @@ the modelname should be added as a MACHINE_FEATURES in 
local.conf like below:
 
 List of currently supported models:
 - pitft22
+- pitft28r
 
 
 4. Extra apps
diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index 792150e..a9e8053 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -33,6 +33,7 @@ KERNEL_DEVICETREE ?= " \
 overlays/iqaudio-dacplus-overlay.dtb \
 overlays/lirc-rpi-overlay.dtb \
 overlays/pitft22-overlay.dtb \
+overlays/pitft28-resistive-overlay.dtb \
 overlays/pps-gpio-overlay.dtb \
 overlays/w1-gpio-overlay.dtb \
 overlays/w1-gpio-pullup-overlay.dtb \
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index 4d41723..2941982 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -17,6 +17,7 @@ PR = "r4"
 
 PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
 PITFT22="${@bb.utils.contains("MACHINE_FEATURES", "pitft22", "1", "0", d)}"
+PITFT28r="${@bb.utils.contains("MACHINE_FEATURES", "pitft28r", "1", "0", d)}"
 
 inherit deploy
 
@@ -90,6 +91,11 @@ do_deploy() {
 echo "# Enable PITFT22 display" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtoverlay=pitft22,rotate=270,speed=3200,txbuflen=32768" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 fi
+
+if [ "${PITFT28r}" = "1" ]; then
+echo "# Enable PITFT28r display" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo 
"dtoverlay=pitft28-resistive,rotate=90,speed=3200,txbuflen=32768" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+fi
 }
 
 addtask deploy before do_package after do_install
diff --git 
a/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/98-pitft.conf
 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/98-pitft.conf
new file mode 100644
index 000..0d2b36b
--- /dev/null
+++ 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/98-pitft.conf
@@ -0,0 +1,5 @@
+Section "Device"
+Identifier "Adafruit PiTFT"
+Driver "fbdev"
+Option "fbdev" "/dev/fb1"
+EndSection
diff --git 
a/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-calibration.conf
 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-calibration.conf
new file mode 100644
index 000..f8b578c
--- /dev/null
+++ 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-calibration.conf
@@ -0,0 +1,6 @@
+Section "InputClass"
+Identifier  "calibration"
+MatchProduct"stmpe-ts"
+Option  "Calibration"   "3800 200 200 3800"
+Option  "SwapAxes"  "1"
+EndSection
diff --git 
a/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
deleted file mode 100644
index 0d2b36b..000
--- 
a/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
+++ /dev/null
@@ -1,5 +0,0 @@
-Section "Device"
-Identifier "Adafruit PiTFT"
-Driver "fbdev"
-Option "fbdev" "/dev/fb1"
-EndSection
diff --git a/recipes-graphics/xorg-xserver/xserver-xf86-config

[yocto] [meta-raspberrypi][PATCH 4/4] .gitignore: Ignore some additional files

[Petter Mabäcker]

Signed-off-by: Petter Mabäcker 
---
 .gitignore | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/.gitignore b/.gitignore
index f235765..bd5616a 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,5 @@
 build*
 *~
 .*.swp
+*.orig
+*.rej
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 3/4] rpi-base.inc: Add overlay for rpi-ft5406

[Petter Mabäcker]

rpi-ft5406 is an enabler for Official Raspberry Pi 7 inch
touchscreen support.

Signed-off-by: Petter Mabäcker 
---
 conf/machine/include/rpi-base.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index f70e952..34eb774 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -35,6 +35,7 @@ KERNEL_DEVICETREE ?= " \
 overlays/pitft22-overlay.dtb \
 overlays/pitft28-resistive-overlay.dtb \
 overlays/pps-gpio-overlay.dtb \
+overlays/rpi-ft5406-overlay.dtb \
 overlays/w1-gpio-overlay.dtb \
 overlays/w1-gpio-pullup-overlay.dtb \
 "
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 2/4] rpi-base.inc: Remove deprecated MACHINE_FEATURES

[Petter Mabäcker]

Signed-off-by: Petter Mabäcker 
---
 conf/machine/include/rpi-base.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index a9e8053..f70e952 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -40,7 +40,7 @@ KERNEL_DEVICETREE ?= " \
 "
 KERNEL_IMAGETYPE ?= "Image"
 
-MACHINE_FEATURES += "kernel26 apm usbhost keyboard vfat ext2 screen 
touchscreen alsa bluetooth wifi sdio"
+MACHINE_FEATURES += "apm usbhost keyboard vfat ext2 screen touchscreen alsa 
bluetooth wifi sdio"
 
 # Raspberry Pi has no hardware clock
 MACHINE_FEATURES_BACKFILL_CONSIDERED = "rtc"
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 0/4] Various upgrade/fixes from Technux

[Petter Mabäcker]

Various fixes from Technux, with focus on PiTFT28 resistive support and
Official Raspberry Pi 7 inch touchscreen enablers.

Petter Mabäcker (4):
  pitft: Add support for pitft28r
  rpi-base.inc: Remove deprecated MACHINE_FEATURES
  rpi-base.inc: Add overlay for rpi-ft5406
  .gitignore: Ignore some additional files

 .gitignore  | 2 ++
 README  | 1 +
 conf/machine/include/rpi-base.inc   | 4 +++-
 recipes-bsp/bootfiles/rpi-config_git.bb | 6 ++
 .../xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/98-pitft.conf  | 5 +
 .../xserver-xf86-config/rpi/xorg.conf.d/99-calibration.conf | 6 ++
 .../xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf  | 5 -
 recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend  | 6 --
 recipes-kernel/linux/linux-raspberrypi.inc  | 2 ++
 9 files changed, 29 insertions(+), 8 deletions(-)
 create mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/98-pitft.conf
 create mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-calibration.conf
 delete mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf

-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH v3 6/6] pitft: Add PiTFT22 support

[Petter Mabäcker]

 

2016-03-02 00:50 skrev Andrei Gherzan: 

> On Sun, Feb 28, 2016 at
02:46:13PM +0100, Petter Mabäcker wrote:
> 
>> - Add support to build
overlays for PiTFT22 in the kernel. - Setup a basic configuration for
the driver The PiTFT22 support is optional and can be enabled by adding
below in local.conf: MACHINE_FEATURES += "pitft pitft22" [Support #70]
Signed-off-by: Petter Mabäcker  --- README | 9 ++
conf/machine/include/rpi-base.inc | 1 +
recipes-bsp/bootfiles/rpi-config_git.bb | 7 ++
...dts-add-overlay-for-pitft22-in-linux-3.18.patch | 110
+ .../0001-dts-add-overlay-for-pitft22.patch | 110
+ recipes-kernel/linux/linux-raspberrypi_3.18.bb | 5
+- recipes-kernel/linux/linux-raspberrypi_4.1.bb | 4 +- 7 files changed,
243 insertions(+), 3 deletions(-) create mode 100644
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
create mode 100644
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22.patch
diff --git a/README b/README index 6a6c398..4114ccc 100644 --- a/README
+++ b/README @@ -170,6 +170,15 @@ MACHINE_FEATURES += "pitft" NOTE: To
get this working the overlay for the PiTFT model must be build, added
and specified as well (dtoverlay= in config.txt) +Below is a
list of currently supported PiTFT models in meta-raspberrypi, +the
modelname should be added as a MACHINE_FEATURES in local.conf like
below: + + - MACHINE_FEATURES += "pitft " + +List of
currently supported models +--- +pitft22
+ 2.L. Images === * rpi-hwup-image diff --git
a/conf/machine/include/rpi-base.inc b/conf/machine/include/rpi-base.inc
index c8f6cd6..27f09ad 100644 --- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc @@ -31,6 +31,7 @@
KERNEL_DEVICETREE ?= " overlays/iqaudio-dac-overlay.dtb
overlays/iqaudio-dacplus-overlay.dtb overlays/lirc-rpi-overlay.dtb +
overlays/pitft22-overlay.dtb overlays/pps-gpio-overlay.dtb
overlays/w1-gpio-overlay.dtb overlays/w1-gpio-pullup-overlay.dtb diff
--git a/recipes-bsp/bootfiles/rpi-config_git.bb
b/recipes-bsp/bootfiles/rpi-config_git.bb index 236a359..631ff42 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb +++
b/recipes-bsp/bootfiles/rpi-config_git.bb @@ -16,6 +16,7 @@ S =
"${WORKDIR}/git" PR = "r4"
PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
+PITFT22="${@bb.utils.contains("MACHINE_FEATURES", "pitft22", "1", "0",
d)}" inherit deploy @@ -80,6 +81,12 @@ do_deploy() { echo
"dtparam=i2c1=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt echo
"dtparam=i2c_arm=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt fi + +
# PiTFT22 display support + if [ "${PITFT22}" = "1" ]; then + echo "#
Enable PITFT22 display" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt +
echo "dtoverlay=pitft22,rotate=270,speed=3200,txbuflen=32768"
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt + fi } addtask deploy before
do_package after do_install diff --git
a/recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
b/recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
new file mode 100644 index 000..fa73599 --- /dev/null +++
b/recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
@@ -0,0 +1,110 @@ +From 2f44861e2a2d651a9aa62a75343a032fee33e93b Mon
Sep 17 00:00:00 2001 +From: =?UTF-8?q?Petter=20Mab=C3=A4cker?=
 +Date: Fri, 8 Jan 2016 09:02:44 +0100 +Subject:
[PATCH] dts: add overlay for pitft22 in linux 3.18 +MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding:
8bit + +Upstream-Status: Pending + +Add the pitft22 overlay from
adafruit Adafruit-Pi-Kernel-o-Matic repo:
+https://github.com/adafruit/Adafruit-Pi-Kernel-o-Matic [1] +
+Signed-off-by: Petter Mabäcker  +--- +
arch/arm/boot/dts/overlays/Makefile | 1 + +
arch/arm/boot/dts/overlays/pitft22-overlay.dts | 69
++ + 2 files changed, 70 insertions(+) + create
mode 100755 arch/arm/boot/dts/overlays/pitft22-overlay.dts + +diff --git
a/arch/arm/boot/dts/overlays/Makefile
b/arch/arm/boot/dts/overlays/Makefile +index c766616..1eaaf81 100644
+--- a/arch/arm/boot/dts/overlays/Makefile 
b/arch/arm/boot/dts/overlays/Makefile +@@ -27,6 +27,7 @@
dtb-$(RPI_DT_OVERLAYS) += mcp2515-can0-overlay.dtb +
dtb-$(RPI_DT_OVERLAYS) += mmc-overlay.dtb + dtb-$(RPI_DT_OVERLAYS) +=
mz61581-overlay.dtb + dtb-$(RPI_DT_OVERLAYS) += piscreen-overlay.dtb
++dtb-$(RPI_DT_OVERLAYS) += pitft22-overlay.dtb + dtb-$(RPI_DT_OVERLAYS)
+= pitft28-resistive-overlay.dtb + dtb-$(RPI_DT_OVERLAYS) +=
pps-gpio-overlay.dtb + dtb-$(RPI_DT_OVERLAYS) += rpi-dac-overlay.dtb
+diff --git a/arch/arm/boot/dts/overlays/pi

[yocto] [meta-raspberrypi][PATCH v3 6/6] pitft: Add PiTFT22 support

[Petter Mabäcker]

- Add support to build overlays for PiTFT22 in the kernel.
- Setup a basic configuration for the driver

The PiTFT22 support is optional and can be enabled by adding below in
local.conf:

MACHINE_FEATURES += "pitft pitft22"

[Support #70]

Signed-off-by: Petter Mabäcker 
---
 README |   9 ++
 conf/machine/include/rpi-base.inc  |   1 +
 recipes-bsp/bootfiles/rpi-config_git.bb|   7 ++
 ...dts-add-overlay-for-pitft22-in-linux-3.18.patch | 110 +
 .../0001-dts-add-overlay-for-pitft22.patch | 110 +
 recipes-kernel/linux/linux-raspberrypi_3.18.bb |   5 +-
 recipes-kernel/linux/linux-raspberrypi_4.1.bb  |   4 +-
 7 files changed, 243 insertions(+), 3 deletions(-)
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22.patch

diff --git a/README b/README
index 6a6c398..4114ccc 100644
--- a/README
+++ b/README
@@ -170,6 +170,15 @@ MACHINE_FEATURES += "pitft"
 NOTE: To get this working the overlay for the PiTFT model must be build,
   added and specified as well (dtoverlay= in config.txt)
 
+Below is a list of currently supported PiTFT models in meta-raspberrypi,
+the modelname should be added as a MACHINE_FEATURES in local.conf like below:
+
+   - MACHINE_FEATURES += "pitft "
+
+List of currently supported models
+---
+pitft22
+
 2.L. Images
 ===
 * rpi-hwup-image
diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index c8f6cd6..27f09ad 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -31,6 +31,7 @@ KERNEL_DEVICETREE ?= " \
 overlays/iqaudio-dac-overlay.dtb \
 overlays/iqaudio-dacplus-overlay.dtb \
 overlays/lirc-rpi-overlay.dtb \
+overlays/pitft22-overlay.dtb \
 overlays/pps-gpio-overlay.dtb \
 overlays/w1-gpio-overlay.dtb \
 overlays/w1-gpio-pullup-overlay.dtb \
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index 236a359..631ff42 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -16,6 +16,7 @@ S = "${WORKDIR}/git"
 PR = "r4"
 
 PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
+PITFT22="${@bb.utils.contains("MACHINE_FEATURES", "pitft22", "1", "0", d)}"
 
 inherit deploy
 
@@ -80,6 +81,12 @@ do_deploy() {
 echo "dtparam=i2c1=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=i2c_arm=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 fi
+
+# PiTFT22 display support
+if [ "${PITFT22}" = "1" ]; then
+echo "# Enable PITFT22 display" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtoverlay=pitft22,rotate=270,speed=3200,txbuflen=32768" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+fi
 }
 
 addtask deploy before do_package after do_install
diff --git 
a/recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
 
b/recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
new file mode 100644
index 000..fa73599
--- /dev/null
+++ 
b/recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
@@ -0,0 +1,110 @@
+From 2f44861e2a2d651a9aa62a75343a032fee33e93b Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petter=20Mab=C3=A4cker?= 
+Date: Fri, 8 Jan 2016 09:02:44 +0100
+Subject: [PATCH] dts: add overlay for pitft22 in linux 3.18
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Upstream-Status: Pending
+
+Add the pitft22 overlay from adafruit Adafruit-Pi-Kernel-o-Matic repo:
+https://github.com/adafruit/Adafruit-Pi-Kernel-o-Matic
+
+Signed-off-by: Petter Mabäcker 
+---
+ arch/arm/boot/dts/overlays/Makefile|  1 +
+ arch/arm/boot/dts/overlays/pitft22-overlay.dts | 69 ++
+ 2 files changed, 70 insertions(+)
+ create mode 100755 arch/arm/boot/dts/overlays/pitft22-overlay.dts
+
+diff --git a/arch/arm/boot/dts/overlays/Makefile 
b/arch/arm/boot/dts/overlays/Makefile
+index c766616..1eaaf81 100644
+--- a/arch/arm/boot/dts/overlays/Makefile
 b/arch/arm/boot/dts/overlays/Makefile
+@@ -27,6 +27,7 @@ dtb-$(RPI_DT_OVERLAYS) += mcp2515-can0-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += mmc-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += mz61581-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += piscreen-overlay.dtb
++dtb-$(RPI_DT_OVERLAYS) += pitft22-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += pitft28-resistive-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS)

[yocto] [meta-raspberrypi][PATCH v3 4/6] rpi-base.inc: Allow MACHINE_FEATURES appends

[Petter Mabäcker]

Ensure that it's possible to add MACHINE_FEATURES from places that will
be executed before rpi-base.inc (like e.g. local.conf), without having
them overrided.

Signed-off-by: Petter Mabäcker 
---
 conf/machine/include/rpi-base.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index e097702..c8f6cd6 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -37,7 +37,7 @@ KERNEL_DEVICETREE ?= " \
 "
 KERNEL_IMAGETYPE ?= "Image"
 
-MACHINE_FEATURES = "kernel26 apm usbhost keyboard vfat ext2 screen touchscreen 
alsa bluetooth wifi sdio"
+MACHINE_FEATURES += "kernel26 apm usbhost keyboard vfat ext2 screen 
touchscreen alsa bluetooth wifi sdio"
 
 # Raspberry Pi has no hardware clock
 MACHINE_FEATURES_BACKFILL_CONSIDERED = "rtc"
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH v3 5/6] pitft: Add basic support for PiTFT

[Petter Mabäcker]

Add basic support for PiTFT display by using device-trees.

In order get it working below configurations must be active in
local.conf:

MACHINE_FEATURES += "pitft"
 - This will enable SPI bus and i2c device-trees, it will also setup
   framebuffer for console and x server on PiTFT.

[Support #70]

Signed-off-by: Petter Mabäcker 
---
 README | 29 --
 recipes-bsp/bootfiles/rpi-config_git.bb|  6 +++--
 .../rpi/xorg.conf.d/99-pitft.conf  |  5 
 .../xorg-xserver/xserver-xf86-config_0.1.bbappend  | 11 ++--
 recipes-kernel/linux/linux-raspberrypi.inc |  6 -
 5 files changed, 44 insertions(+), 13 deletions(-)
 create mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf

diff --git a/README b/README
index 8ef4e7a..6a6c398 100644
--- a/README
+++ b/README
@@ -22,10 +22,11 @@ Contents:
 2.H. Optional - Enable kgdb over console support
 2.I. Optional - Enable SPI bus
 2.J. Optional - Enable I2C
-2.K. Images
-2.L. Boot to U-Boot
-2.M. Image with Initramfs
-2.N. Device tree support
+2.K. Optional - Enable PiTFT support
+2.L. Images
+2.M. Boot to U-Boot
+2.N. Image with Initramfs
+2.O. Device tree support
 3. Extra apps
 3.A. omxplayer
 4. Source code and mirrors
@@ -157,7 +158,19 @@ ENABLE_SPI_BUS = "1"
 When using device tree kernels, set this variable to enable I2C
 ENABLE_I2C = "1"
 
-2.K. Images
+2.K. Optional - Enable PiTFT support
+
+Basic support for using PiTFT screens can be enabled by adding
+below in local.conf:
+
+MACHINE_FEATURES += "pitft"
+  - This will enable SPI bus and i2c device-trees, it will also setup
+framebuffer for console and x server on PiTFT.
+
+NOTE: To get this working the overlay for the PiTFT model must be build,
+  added and specified as well (dtoverlay= in config.txt)
+
+2.L. Images
 ===
 * rpi-hwup-image
 Hardware up image
@@ -167,7 +180,7 @@ ENABLE_I2C = "1"
 Image based on rpi-basic-image which includes most of the packages in this
 layer and some media samples.
 
-2.L. Boot to U-Boot
+2.M. Boot to U-Boot
 ===
 To have u-boot load kernel image, set in your local.conf
 KERNEL_IMAGETYPE = "uImage"
@@ -175,7 +188,7 @@ KERNEL_IMAGETYPE = "uImage"
 This will make kernel.img be u-boot image which will load uImage.
 By default, kernel.img is the actual kernel image (ex. Image).
 
-2.M. Image with Initramfs
+2.N. Image with Initramfs
 =
 To build an initramfs image :
 * Set this 3 kernel variables (in linux-raspberrypi.inc for example)
@@ -188,7 +201,7 @@ To build an initramfs image :
 * Set the meta-rasberrypi variable (in raspberrypi.conf for example)
 - KERNEL_INITRAMFS = "-initramfs"
 
-2.N. Device tree support
+2.O. Device tree support
 =
 Device tree for RPi is only supported when using linux-raspberrypi 3.18+
 kernels.
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index ccb9b7f..236a359 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -15,6 +15,8 @@ S = "${WORKDIR}/git"
 
 PR = "r4"
 
+PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
+
 inherit deploy
 
 do_deploy() {
@@ -68,12 +70,12 @@ do_deploy() {
 fi
 
 # SPI bus support
-if [ -n "${ENABLE_SPI_BUS}" ]; then
+if [ -n "${ENABLE_SPI_BUS}" ] || [ "${PITFT}" = "1" ]; then
 echo "# Enable SPI bus" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=spi=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 fi
 
-if [ -n "${ENABLE_I2C}" ]; then
+if [ -n "${ENABLE_I2C}" ] || [ "${PITFT}" = "1" ]; then
 echo "# Enable I2C" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=i2c1=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=i2c_arm=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
diff --git 
a/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
new file mode 100644
index 000..0d2b36b
--- /dev/null
+++ 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
@@ -0,0 +1,5 @@
+Section "Device"
+Identifier "Adafruit PiTFT"
+Driver "fbdev"
+Option "fbdev" "/dev/fb1"
+EndSection
diff --git a/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend 
b/recipes-graphics/xorg-xser

[yocto] [meta-raspberrypi][PATCH v3 0/6] Various upgrade/fixes from Technux

[Petter Mabäcker]

Various fixes from Technux, with focus on PiTFT support.

Petter Mabäcker (6):
  README: Add SPI bus chapter to content
  .gitignore: Ignore .swp files
  rpi-config: I2C support
  rpi-base.inc: Allow MACHINE_FEATURES appends
  pitft: Add basic support for PiTFT
  pitft: Add PiTFT22 support

 .gitignore |   1 +
 README |  55 ---
 conf/machine/include/rpi-base.inc  |   3 +-
 recipes-bsp/bootfiles/rpi-config_git.bb|  17 +++-
 .../rpi/xorg.conf.d/99-pitft.conf  |   5 +
 .../xorg-xserver/xserver-xf86-config_0.1.bbappend  |  11 ++-
 recipes-kernel/linux/linux-raspberrypi.inc |   6 +-
 ...dts-add-overlay-for-pitft22-in-linux-3.18.patch | 110 +
 .../0001-dts-add-overlay-for-pitft22.patch | 110 +
 recipes-kernel/linux/linux-raspberrypi_3.18.bb |   5 +-
 recipes-kernel/linux/linux-raspberrypi_4.1.bb  |   4 +-
 11 files changed, 306 insertions(+), 21 deletions(-)
 create mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22.patch

-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH v3 3/6] rpi-config: I2C support

[Petter Mabäcker]

With newer kernels (>=3.18) that supports device-trees I2C
should be enabled with device-trees.

This is now support by adding:
ENABLE_I2C = "1"
in local.conf

This will enable the dtparams:
i2c1
i2c_arm

Signed-off-by: Petter Mabäcker 
---
 README  | 21 +
 recipes-bsp/bootfiles/rpi-config_git.bb |  6 ++
 2 files changed, 19 insertions(+), 8 deletions(-)

diff --git a/README b/README
index a168692..8ef4e7a 100644
--- a/README
+++ b/README
@@ -21,10 +21,11 @@ Contents:
 2.G. Optional - Enable offline compositing support
 2.H. Optional - Enable kgdb over console support
 2.I. Optional - Enable SPI bus
-2.J. Images
-2.K. Boot to U-Boot
-2.L. Image with Initramfs
-2.M. Device tree support
+2.J. Optional - Enable I2C
+2.K. Images
+2.L. Boot to U-Boot
+2.M. Image with Initramfs
+2.N. Device tree support
 3. Extra apps
 3.A. omxplayer
 4. Source code and mirrors
@@ -151,8 +152,12 @@ ENABLE_KGDB = "1"
 When using device tree kernels, set this variable to enable the SPI bus
 ENABLE_SPI_BUS = "1"
 
+2.J. Optional - Enable I2C
+==
+When using device tree kernels, set this variable to enable I2C
+ENABLE_I2C = "1"
 
-2.J. Images
+2.K. Images
 ===
 * rpi-hwup-image
 Hardware up image
@@ -162,7 +167,7 @@ ENABLE_SPI_BUS = "1"
 Image based on rpi-basic-image which includes most of the packages in this
 layer and some media samples.
 
-2.K. Boot to U-Boot
+2.L. Boot to U-Boot
 ===
 To have u-boot load kernel image, set in your local.conf
 KERNEL_IMAGETYPE = "uImage"
@@ -170,7 +175,7 @@ KERNEL_IMAGETYPE = "uImage"
 This will make kernel.img be u-boot image which will load uImage.
 By default, kernel.img is the actual kernel image (ex. Image).
 
-2.L. Image with Initramfs
+2.M. Image with Initramfs
 =
 To build an initramfs image :
 * Set this 3 kernel variables (in linux-raspberrypi.inc for example)
@@ -183,7 +188,7 @@ To build an initramfs image :
 * Set the meta-rasberrypi variable (in raspberrypi.conf for example)
 - KERNEL_INITRAMFS = "-initramfs"
 
-2.M. Device tree support
+2.N. Device tree support
 =
 Device tree for RPi is only supported when using linux-raspberrypi 3.18+
 kernels.
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index aa11b25..ccb9b7f 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -72,6 +72,12 @@ do_deploy() {
 echo "# Enable SPI bus" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=spi=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 fi
+
+if [ -n "${ENABLE_I2C}" ]; then
+echo "# Enable I2C" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtparam=i2c1=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtparam=i2c_arm=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+fi
 }
 
 addtask deploy before do_package after do_install
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH v3 1/6] README: Add SPI bus chapter to content

[Petter Mabäcker]

The optional SPI bus chapter was missing in the content list.

While at it also place it together with the other "optional" chapters,
instead of in the end.

Signed-off-by: Petter Mabäcker 
---
 README | 28 +++-
 1 file changed, 15 insertions(+), 13 deletions(-)

diff --git a/README b/README
index 16ac1cb..a168692 100644
--- a/README
+++ b/README
@@ -20,10 +20,11 @@ Contents:
 2.F. Optional - Video camera support with V4L2 drivers
 2.G. Optional - Enable offline compositing support
 2.H. Optional - Enable kgdb over console support
-2.I. Images
-2.J. Boot to U-Boot
-2.K. Image with Initramfs
-2.L. Device tree support
+2.I. Optional - Enable SPI bus
+2.J. Images
+2.K. Boot to U-Boot
+2.L. Image with Initramfs
+2.M. Device tree support
 3. Extra apps
 3.A. omxplayer
 4. Source code and mirrors
@@ -145,7 +146,13 @@ To add the kdbg over console (kgdboc) parameter to the 
kernel command line,
 set this variable in local.conf:
 ENABLE_KGDB = "1"
 
-2.I. Images
+2.I. Optional - Enable SPI bus
+==
+When using device tree kernels, set this variable to enable the SPI bus
+ENABLE_SPI_BUS = "1"
+
+
+2.J. Images
 ===
 * rpi-hwup-image
 Hardware up image
@@ -155,7 +162,7 @@ ENABLE_KGDB = "1"
 Image based on rpi-basic-image which includes most of the packages in this
 layer and some media samples.
 
-2.J. Boot to U-Boot
+2.K. Boot to U-Boot
 ===
 To have u-boot load kernel image, set in your local.conf
 KERNEL_IMAGETYPE = "uImage"
@@ -163,7 +170,7 @@ KERNEL_IMAGETYPE = "uImage"
 This will make kernel.img be u-boot image which will load uImage.
 By default, kernel.img is the actual kernel image (ex. Image).
 
-2.K. Image with Initramfs
+2.L. Image with Initramfs
 =
 To build an initramfs image :
 * Set this 3 kernel variables (in linux-raspberrypi.inc for example)
@@ -176,7 +183,7 @@ To build an initramfs image :
 * Set the meta-rasberrypi variable (in raspberrypi.conf for example)
 - KERNEL_INITRAMFS = "-initramfs"
 
-2.L. Device tree support
+2.M. Device tree support
 =
 Device tree for RPi is only supported when using linux-raspberrypi 3.18+
 kernels.
@@ -189,11 +196,6 @@ kernels.
 NOTE: KERNEL_DEVICETREE is default enabled for kernel >= 3.18 and always 
disabled for
   older kernel versions.
 
-2.M. Optional - enable SPI bus
-==
-When using device tree kernels, set this variable to enable the SPI bus
-ENABLE_SPI_BUS = "1"
-
 3. Extra apps
 =
 
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH v3 2/6] .gitignore: Ignore .swp files

[Petter Mabäcker]

Signed-off-by: Petter Mabäcker 
---
 .gitignore | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.gitignore b/.gitignore
index 1677b58..f235765 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,2 +1,3 @@
 build*
 *~
+.*.swp
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH v2 3/7] linux-raspberrypi: Update 4.1 recipe to 4.1.15

[Petter Mabäcker]

 

2016-02-28 12:02 skrev Andrei Gherzan: 

> On Sun, Feb 28, 2016 at
11:51:58AM +0100, Andrei Gherzan wrote:
> 
>> On Sun, Feb 28, 2016 at
08:56:33AM +0100, Petter Mabäcker wrote: 
>> 
>>> 2016-01-14 17:40 skrev
Petter Mab?cker: [Support #69] Signed-off-by: Petter Mab?cker
<[1]pet...@technux.se> --- recipes-kernel/linux/linux-raspberrypi_4.1.bb
| 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git
a/recipes-kernel/linux/linux-raspberrypi_4.1.bb b/recipes-kernel/linu
x/linux-raspberrypi_4.1.bb index 3a3cf40..cae459a 100644 ---
a/recipes-kernel/linux/linux-raspberrypi_4.1.bb +++
b/recipes-kernel/linux/linux-raspberrypi_4.1.bb @@ -1,6 +1,6 @@
-LINUX_VERSION ?= "4.1.10" +LINUX_VERSION ?= "4.1.15" -SRCREV =
"b74df9228c27f55361c065bc5dbfba88861cc771" +SRCREV =
"02a8ee530e32b08e5df44f10e24d5fd82bb960e3" SRC_URI =
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.1.y "
require linux-raspberrypi.inc Hi Andrei, This commit can be skipped,
since Khem have done an even newer update of the 4.1 kernel (4.1.10 -->
4.1.17) in the large series of commits from yesterday
(https://lists.yoctoproject.org/pipermail/yocto/2016-February/028754.ht
[1] ml). Do you want me to send an updated version of this series of
commit without it or not? BR Petter References 1.
mailto:pet...@technux.se
>> Thanks Peter. No need to bother. I'll keep
in mind not to pull this patch.
> 
> Petter,
> 
> Actually I do have a
request. Could you please send the v2 again (or a v3)
> cause even if
they are on the ml archive I don't have it in my mailbox (this
> kinda
worries me). Sorry for this and thank you in advance.
> 
> --
> Andrei
Gherzan

I will send up a v3 with the kernel bump commit removed (and
also a fix for a minor typo in the README..). 

BR Petter 

Petter
Mabäcker

Technux 
www.technux.se



Links:
--
[1]
https://lists.yoctoproject.org/pipermail/yocto/2016-February/028754.ht
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH V2] linux-raspberry.inc: add initramfs support

[Petter Mabäcker]

 

5 

Petter Mabäcker

Technux

www.technux.se

2016-02-10 11:26 skrev Stéphane
Cerveau: 

> append initramfs creation to install RPi bootloader
trailer
> 
> Signed-off-by: Stéphane Cerveau 
> ---
>
recipes-kernel/linux/linux-raspberrypi.inc | 9 +
> 1 file
changed, 9 insertions(+)
> 
> diff --git
a/recipes-kernel/linux/linux-raspberrypi.inc
b/recipes-kernel/linux/linux-raspberrypi.inc
> index 70e8bfe..74dbf19
100644
> --- a/recipes-kernel/linux/linux-raspberrypi.inc
> +++
b/recipes-kernel/linux/linux-raspberrypi.inc
> @@ -64,4 +64,13 @@
do_rpiboot_mkimage() {
> fi
> fi
> }
> +do_bundle_initramfs_append() {
>
+ if test "x${KERNEL_IMAGETYPE}" != "xuImage" ; then
> + if test -n
"${KERNEL_DEVICETREE}"; then
> + # Add RPi bootloader trailer to kernel
image to enable DeviceTree support
> +
${STAGING_DIR_NATIVE}/usr/lib/rpi-mkimage/mkknlimg --dtok
${KERNEL_OUTPUT}.initramfs ${KERNEL_OUTPUT}.initramfs
> + fi
> + fi
>
+}
> +
> addtask rpiboot_mkimage before do_install after do_compile
> --

> 2.1.4

Hi, 

You should change the path to mkknlimg to use:
${STAGING_LIBEXECDIR_NATIVE}/mkknlimg 

See the discussion about this
in:
https://lists.yoctoproject.org/pipermail/yocto/2016-February/028769.html


BR Petter -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH v2 3/7] linux-raspberrypi: Update 4.1 recipe to 4.1.15

[Petter Mabäcker]

 

2016-01-14 17:40 skrev Petter Mabäcker: 

> [Support #69]
> 
>
Signed-off-by: Petter Mabäcker 
> ---
>
recipes-kernel/linux/linux-raspberrypi_4.1.bb | 4 ++--
> 1 file changed,
2 insertions(+), 2 deletions(-)
> 
> diff --git
a/recipes-kernel/linux/linux-raspberrypi_4.1.bb
b/recipes-kernel/linux/linux-raspberrypi_4.1.bb
> index 3a3cf40..cae459a
100644
> --- a/recipes-kernel/linux/linux-raspberrypi_4.1.bb
> +++
b/recipes-kernel/linux/linux-raspberrypi_4.1.bb
> @@ -1,6 +1,6 @@
>
-LINUX_VERSION ?= "4.1.10"
> +LINUX_VERSION ?= "4.1.15"
> 
> -SRCREV =
"b74df9228c27f55361c065bc5dbfba88861cc771"
> +SRCREV =
"02a8ee530e32b08e5df44f10e24d5fd82bb960e3"
> SRC_URI =
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.1.y"
>

> require linux-raspberrypi.inc

Hi Andrei, 

This commit can be
skipped, since Khem have done an even newer update of the 4.1 kernel
(4.1.10 --> 4.1.17) in the large series of commits from yesterday
(https://lists.yoctoproject.org/pipermail/yocto/2016-February/028754.html).
Do you want me to send an updated version of this series of commit
without it or not? 

BR Petter -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi: fix path to mkknlimg

[Petter Mabäcker]

 

2016-02-27 13:25 skrev Jonathan Liu: 

> On 27 February 2016 at
23:21, Andrei Gherzan  wrote:
> 
>> On Sat, Feb 27,
2016 at 08:03:10AM +1100, Jonathan Liu wrote: 
>> 
>>> On 27 February
2016 at 06:55, Andrei Gherzan  wrote: 
>>> 
>>>> On
Fri, Feb 26, 2016 at 07:04:28PM +0100, Andrei Gherzan wrote: 
>>>>

>>>>> -- Andrei Gherzan On Fri, Feb 26, 2016 at 6:48 PM, Petter
Mabäcker <[1]pet...@technux.se> wrote: 2016-02-26 18:14 skrev Andrei
Gherzan: On Fri, Feb 26, 2016 at 08:26:57PM +1100, Jonathan Liu wrote:
The path had libexecdir hardcoded so it was no longer correct when
libexecdir was changed in meta/conf/bitbake.conf from ${libdir}/${BPN}
to ${prefix_native}/libexec for nativesdk recipes. Fixes "No such file
or directory" error when executing do_rpiboot_mkimage. Signed-off-by:
Jonathan Liu <[2]net...@gmail.com> ---
recipes-kernel/linux/linux-raspberrypi.inc | 2 +- 1 file changed, 1
insertion(+), 1 deletion(-) diff --git
a/recipes-kernel/linux/linux-raspberrypi.inc
b/recipes-kernel/linux/linux-raspberrypi.inc index 70e8bfe..8c7c46c
100644 --- a/recipes-kernel/linux/linux-raspberrypi.inc +++
b/recipes-kernel/linux/linux-raspberrypi.inc @@ -60,7 +60,7 @@
do_rpiboot_mkimage() { if test "x${KERNEL_IMAGETYPE}" != "xuImage" ;
then if test -n "${KERNEL_DEVICETREE}"; then # Add RPi bootloader
trailer to kernel image to enable DeviceTree support -
${STAGING_DIR_NATIVE}/usr/lib/rpi-mkimage/mkknlimg --dtok
${KERNEL_OUTPUT} ${KERNEL_OUTPUT} +
${STAGING_LIBEXECDIR_NATIVE}/mkknlimg --dtok ${KERNEL_OUTPUT}
${KERNEL_OUTPUT} fi fi } -- 2.7.1 Back alive. testing this. -- Andrei
Gherzan Hi, I think we should use the older patchset from Maciej
Borzecki (that solves this and some other minor stuffs) instead. It also
keeps the rpi-mkimage structure:
[3]https://lists.yoctoproject.org/pipermail/yocto/2016-February/028271
[1]. html BR Petter Very good catch Petter. I'll test that PR.
>>>>
Merged the patch set sent by Maciej. Which covers this patch too.
Thanks, -- Andrei Gherzan
>>> Note that Maciej's patch doesn't really
preserve the path on older branches like you expect. On master branch:
${libexecdir}/rpi-mkimage expands to /usr/libexec/rpi-mkimage On daisy
branch: ${libexecdir}/rpi-mkimage expands to
/usr/lib/rpi-mkimage/rpi-mkimage
>> This is a very good catch. But for
now this patch is not in daisy it is only in master which is supposed to
work with poky master. I do understand your concern. And I think it is
the same thing on jethro too. So you propose relying on
STAGING_LIBEXECDIR_NATIVE and let it append or not BPN? -- Andrei
Gherzan
> 
> I propose my patch instead which has the following behavior
and goes
> along with the libexecdir change rather than trying to go
against it.
> 
> My patch has the following paths for mkknlimg.
> 
>
daisy:
> [...]/sysroots/x86_64-linux/usr/lib/rpi-mkimage/mkknlimg
>
which matches the previous hardcoded path before the patch so the path
>
doesn't change with the patch for older branches
> 
> master:
>
[...]/sysroots/x86_64-linux/usr/libexec/mkknlimg
> 
> You can then do
something similar for U-Boot.

Ah, nice. I agree that this difference
from the other solutions for this problem, gives an additional value and
should be merged. I can see that this info is described in the commit
message for the new commits, good =) 

BR Petter 

> Regards, Jonathan



Links:
--
[1]
https://lists.yoctoproject.org/pipermail/yocto/2016-February/028271
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi: fix path to mkknlimg

[Petter Mabäcker]

 

2016-02-26 18:14 skrev Andrei Gherzan: 

> On Fri, Feb 26, 2016 at
08:26:57PM +1100, Jonathan Liu wrote:
> 
>> The path had libexecdir
hardcoded so it was no longer correct when libexecdir was changed in
meta/conf/bitbake.conf from ${libdir}/${BPN} to ${prefix_native}/libexec
for nativesdk recipes. Fixes "No such file or directory" error when
executing do_rpiboot_mkimage. Signed-off-by: Jonathan Liu
 --- recipes-kernel/linux/linux-raspberrypi.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-) diff --git
a/recipes-kernel/linux/linux-raspberrypi.inc
b/recipes-kernel/linux/linux-raspberrypi.inc index 70e8bfe..8c7c46c
100644 --- a/recipes-kernel/linux/linux-raspberrypi.inc +++
b/recipes-kernel/linux/linux-raspberrypi.inc @@ -60,7 +60,7 @@
do_rpiboot_mkimage() { if test "x${KERNEL_IMAGETYPE}" != "xuImage" ;
then if test -n "${KERNEL_DEVICETREE}"; then # Add RPi bootloader
trailer to kernel image to enable DeviceTree support -
${STAGING_DIR_NATIVE}/usr/lib/rpi-mkimage/mkknlimg --dtok
${KERNEL_OUTPUT} ${KERNEL_OUTPUT} +
${STAGING_LIBEXECDIR_NATIVE}/mkknlimg --dtok ${KERNEL_OUTPUT}
${KERNEL_OUTPUT} fi fi } -- 2.7.1
> 
> Back alive. testing this.
> 
> --

> Andrei Gherzan

Hi,

I think we should use the older patchset from
_Maciej Borzecki _ (that solves this and some other minor stuffs)
instead. It also keeps the rpi-mkimage
structure:

https://lists.yoctoproject.org/pipermail/yocto/2016-February/028271.html

BR
Petter -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH v2 7/7] pitft: Add PiTFT22 support

[Petter Mabäcker]

- Add support to build overlays for PiTFT22 in the kernel.
- Setup a basic configuration for the driver

The PiTFT22 support is optional and can be enabled by adding below in
local.conf:

MACHINE_FEATURES += "pitft pitft22"

[Support #70]

Signed-off-by: Petter Mabäcker 
---
 README |   9 ++
 conf/machine/include/rpi-base.inc  |   1 +
 recipes-bsp/bootfiles/rpi-config_git.bb|   7 ++
 ...dts-add-overlay-for-pitft22-in-linux-3.18.patch | 110 +
 .../0001-dts-add-overlay-for-pitft22.patch | 110 +
 recipes-kernel/linux/linux-raspberrypi_3.18.bb |   5 +-
 recipes-kernel/linux/linux-raspberrypi_4.1.bb  |   4 +-
 7 files changed, 243 insertions(+), 3 deletions(-)
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22.patch

diff --git a/README b/README
index 6a6c398..f5b155f 100644
--- a/README
+++ b/README
@@ -170,6 +170,15 @@ MACHINE_FEATURES += "pitft"
 NOTE: To get this working the overlay for the PiTFT model must be build,
   added and specified as well (dtoverlay= in config.txt)
 
+Below is a list of currently supported PiTFT models in meta-raspberrypi,
+the modelname should be added as a MACHINE_FEATURES in local.conf like below:
+
+   - MACHINE_FEATURES .= "pitft "
+
+List of currently supported models
+---
+pitft22
+
 2.L. Images
 ===
 * rpi-hwup-image
diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index c8f6cd6..27f09ad 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -31,6 +31,7 @@ KERNEL_DEVICETREE ?= " \
 overlays/iqaudio-dac-overlay.dtb \
 overlays/iqaudio-dacplus-overlay.dtb \
 overlays/lirc-rpi-overlay.dtb \
+overlays/pitft22-overlay.dtb \
 overlays/pps-gpio-overlay.dtb \
 overlays/w1-gpio-overlay.dtb \
 overlays/w1-gpio-pullup-overlay.dtb \
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index 236a359..631ff42 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -16,6 +16,7 @@ S = "${WORKDIR}/git"
 PR = "r4"
 
 PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
+PITFT22="${@bb.utils.contains("MACHINE_FEATURES", "pitft22", "1", "0", d)}"
 
 inherit deploy
 
@@ -80,6 +81,12 @@ do_deploy() {
 echo "dtparam=i2c1=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=i2c_arm=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 fi
+
+# PiTFT22 display support
+if [ "${PITFT22}" = "1" ]; then
+echo "# Enable PITFT22 display" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtoverlay=pitft22,rotate=270,speed=3200,txbuflen=32768" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+fi
 }
 
 addtask deploy before do_package after do_install
diff --git 
a/recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
 
b/recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
new file mode 100644
index 000..fa73599
--- /dev/null
+++ 
b/recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
@@ -0,0 +1,110 @@
+From 2f44861e2a2d651a9aa62a75343a032fee33e93b Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petter=20Mab=C3=A4cker?= 
+Date: Fri, 8 Jan 2016 09:02:44 +0100
+Subject: [PATCH] dts: add overlay for pitft22 in linux 3.18
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Upstream-Status: Pending
+
+Add the pitft22 overlay from adafruit Adafruit-Pi-Kernel-o-Matic repo:
+https://github.com/adafruit/Adafruit-Pi-Kernel-o-Matic
+
+Signed-off-by: Petter Mabäcker 
+---
+ arch/arm/boot/dts/overlays/Makefile|  1 +
+ arch/arm/boot/dts/overlays/pitft22-overlay.dts | 69 ++
+ 2 files changed, 70 insertions(+)
+ create mode 100755 arch/arm/boot/dts/overlays/pitft22-overlay.dts
+
+diff --git a/arch/arm/boot/dts/overlays/Makefile 
b/arch/arm/boot/dts/overlays/Makefile
+index c766616..1eaaf81 100644
+--- a/arch/arm/boot/dts/overlays/Makefile
 b/arch/arm/boot/dts/overlays/Makefile
+@@ -27,6 +27,7 @@ dtb-$(RPI_DT_OVERLAYS) += mcp2515-can0-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += mmc-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += mz61581-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += piscreen-overlay.dtb
++dtb-$(RPI_DT_OVERLAYS) += pitft22-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += pitft28-resistive-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS)

[yocto] [meta-raspberrypi][PATCH v2 0/7] Various upgrade/fixes from Technux

[Petter Mabäcker]

Various fixes from Technux, with focus on PiTFT support.

Major changes from v1 is that after feedback, MACHINE_FEATURES is used to
enable/disable pitft support instead of MACHINEOVERRIDES.

Petter Mabäcker (7):
  README: Add SPI bus chapter to content
  .gitignore: Ignore .swp files
  linux-raspberrypi: Update 4.1 recipe to 4.1.15
  rpi-config: I2C support
  rpi-base.inc: Allow MACHINE_FEATURES appends
  pitft: Add basic support for PiTFT
  pitft: Add PiTFT22 support

 .gitignore |   1 +
 README |  55 ---
 conf/machine/include/rpi-base.inc  |   3 +-
 recipes-bsp/bootfiles/rpi-config_git.bb|  17 +++-
 .../rpi/xorg.conf.d/99-pitft.conf  |   5 +
 .../xorg-xserver/xserver-xf86-config_0.1.bbappend  |  11 ++-
 recipes-kernel/linux/linux-raspberrypi.inc |   6 +-
 ...dts-add-overlay-for-pitft22-in-linux-3.18.patch | 110 +
 .../0001-dts-add-overlay-for-pitft22.patch | 110 +
 recipes-kernel/linux/linux-raspberrypi_3.18.bb |   5 +-
 recipes-kernel/linux/linux-raspberrypi_4.1.bb  |   8 +-
 11 files changed, 308 insertions(+), 23 deletions(-)
 create mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22.patch

-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH v2 6/7] pitft: Add basic support for PiTFT

[Petter Mabäcker]

Add basic support for PiTFT display by using device-trees.

In order get it working below configurations must be active in
local.conf:

MACHINE_FEATURES += "pitft"
 - This will enable SPI bus and i2c device-trees, it will also setup
   framebuffer for console and x server on PiTFT.

[Support #70]

Signed-off-by: Petter Mabäcker 
---
 README | 29 --
 recipes-bsp/bootfiles/rpi-config_git.bb|  6 +++--
 .../rpi/xorg.conf.d/99-pitft.conf  |  5 
 .../xorg-xserver/xserver-xf86-config_0.1.bbappend  | 11 ++--
 recipes-kernel/linux/linux-raspberrypi.inc |  6 -
 5 files changed, 44 insertions(+), 13 deletions(-)
 create mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf

diff --git a/README b/README
index 8ef4e7a..6a6c398 100644
--- a/README
+++ b/README
@@ -22,10 +22,11 @@ Contents:
 2.H. Optional - Enable kgdb over console support
 2.I. Optional - Enable SPI bus
 2.J. Optional - Enable I2C
-2.K. Images
-2.L. Boot to U-Boot
-2.M. Image with Initramfs
-2.N. Device tree support
+2.K. Optional - Enable PiTFT support
+2.L. Images
+2.M. Boot to U-Boot
+2.N. Image with Initramfs
+2.O. Device tree support
 3. Extra apps
 3.A. omxplayer
 4. Source code and mirrors
@@ -157,7 +158,19 @@ ENABLE_SPI_BUS = "1"
 When using device tree kernels, set this variable to enable I2C
 ENABLE_I2C = "1"
 
-2.K. Images
+2.K. Optional - Enable PiTFT support
+
+Basic support for using PiTFT screens can be enabled by adding
+below in local.conf:
+
+MACHINE_FEATURES += "pitft"
+  - This will enable SPI bus and i2c device-trees, it will also setup
+framebuffer for console and x server on PiTFT.
+
+NOTE: To get this working the overlay for the PiTFT model must be build,
+  added and specified as well (dtoverlay= in config.txt)
+
+2.L. Images
 ===
 * rpi-hwup-image
 Hardware up image
@@ -167,7 +180,7 @@ ENABLE_I2C = "1"
 Image based on rpi-basic-image which includes most of the packages in this
 layer and some media samples.
 
-2.L. Boot to U-Boot
+2.M. Boot to U-Boot
 ===
 To have u-boot load kernel image, set in your local.conf
 KERNEL_IMAGETYPE = "uImage"
@@ -175,7 +188,7 @@ KERNEL_IMAGETYPE = "uImage"
 This will make kernel.img be u-boot image which will load uImage.
 By default, kernel.img is the actual kernel image (ex. Image).
 
-2.M. Image with Initramfs
+2.N. Image with Initramfs
 =
 To build an initramfs image :
 * Set this 3 kernel variables (in linux-raspberrypi.inc for example)
@@ -188,7 +201,7 @@ To build an initramfs image :
 * Set the meta-rasberrypi variable (in raspberrypi.conf for example)
 - KERNEL_INITRAMFS = "-initramfs"
 
-2.N. Device tree support
+2.O. Device tree support
 =
 Device tree for RPi is only supported when using linux-raspberrypi 3.18+
 kernels.
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index ccb9b7f..236a359 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -15,6 +15,8 @@ S = "${WORKDIR}/git"
 
 PR = "r4"
 
+PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
+
 inherit deploy
 
 do_deploy() {
@@ -68,12 +70,12 @@ do_deploy() {
 fi
 
 # SPI bus support
-if [ -n "${ENABLE_SPI_BUS}" ]; then
+if [ -n "${ENABLE_SPI_BUS}" ] || [ "${PITFT}" = "1" ]; then
 echo "# Enable SPI bus" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=spi=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 fi
 
-if [ -n "${ENABLE_I2C}" ]; then
+if [ -n "${ENABLE_I2C}" ] || [ "${PITFT}" = "1" ]; then
 echo "# Enable I2C" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=i2c1=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=i2c_arm=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
diff --git 
a/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
new file mode 100644
index 000..0d2b36b
--- /dev/null
+++ 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
@@ -0,0 +1,5 @@
+Section "Device"
+Identifier "Adafruit PiTFT"
+Driver "fbdev"
+Option "fbdev" "/dev/fb1"
+EndSection
diff --git a/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend 
b/recipes-graphics/xorg-xser

[yocto] [meta-raspberrypi][PATCH v2 2/7] .gitignore: Ignore .swp files

[Petter Mabäcker]

Signed-off-by: Petter Mabäcker 
---
 .gitignore | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.gitignore b/.gitignore
index 1677b58..f235765 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,2 +1,3 @@
 build*
 *~
+.*.swp
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH v2 4/7] rpi-config: I2C support

[Petter Mabäcker]

With newer kernels (>=3.18) that supports device-trees I2C
should be enabled with device-trees.

This is now support by adding:
ENABLE_I2C = "1"
in local.conf

This will enable the dtparams:
i2c1
i2c_arm

Signed-off-by: Petter Mabäcker 
---
 README  | 21 +
 recipes-bsp/bootfiles/rpi-config_git.bb |  6 ++
 2 files changed, 19 insertions(+), 8 deletions(-)

diff --git a/README b/README
index a168692..8ef4e7a 100644
--- a/README
+++ b/README
@@ -21,10 +21,11 @@ Contents:
 2.G. Optional - Enable offline compositing support
 2.H. Optional - Enable kgdb over console support
 2.I. Optional - Enable SPI bus
-2.J. Images
-2.K. Boot to U-Boot
-2.L. Image with Initramfs
-2.M. Device tree support
+2.J. Optional - Enable I2C
+2.K. Images
+2.L. Boot to U-Boot
+2.M. Image with Initramfs
+2.N. Device tree support
 3. Extra apps
 3.A. omxplayer
 4. Source code and mirrors
@@ -151,8 +152,12 @@ ENABLE_KGDB = "1"
 When using device tree kernels, set this variable to enable the SPI bus
 ENABLE_SPI_BUS = "1"
 
+2.J. Optional - Enable I2C
+==
+When using device tree kernels, set this variable to enable I2C
+ENABLE_I2C = "1"
 
-2.J. Images
+2.K. Images
 ===
 * rpi-hwup-image
 Hardware up image
@@ -162,7 +167,7 @@ ENABLE_SPI_BUS = "1"
 Image based on rpi-basic-image which includes most of the packages in this
 layer and some media samples.
 
-2.K. Boot to U-Boot
+2.L. Boot to U-Boot
 ===
 To have u-boot load kernel image, set in your local.conf
 KERNEL_IMAGETYPE = "uImage"
@@ -170,7 +175,7 @@ KERNEL_IMAGETYPE = "uImage"
 This will make kernel.img be u-boot image which will load uImage.
 By default, kernel.img is the actual kernel image (ex. Image).
 
-2.L. Image with Initramfs
+2.M. Image with Initramfs
 =
 To build an initramfs image :
 * Set this 3 kernel variables (in linux-raspberrypi.inc for example)
@@ -183,7 +188,7 @@ To build an initramfs image :
 * Set the meta-rasberrypi variable (in raspberrypi.conf for example)
 - KERNEL_INITRAMFS = "-initramfs"
 
-2.M. Device tree support
+2.N. Device tree support
 =
 Device tree for RPi is only supported when using linux-raspberrypi 3.18+
 kernels.
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index aa11b25..ccb9b7f 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -72,6 +72,12 @@ do_deploy() {
 echo "# Enable SPI bus" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=spi=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 fi
+
+if [ -n "${ENABLE_I2C}" ]; then
+echo "# Enable I2C" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtparam=i2c1=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtparam=i2c_arm=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+fi
 }
 
 addtask deploy before do_package after do_install
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH v2 1/7] README: Add SPI bus chapter to content

[Petter Mabäcker]

The optional SPI bus chapter was missing in the content list.

While at it also place it together with the other "optional" chapters,
instead of in the end.

Signed-off-by: Petter Mabäcker 
---
 README | 28 +++-
 1 file changed, 15 insertions(+), 13 deletions(-)

diff --git a/README b/README
index 16ac1cb..a168692 100644
--- a/README
+++ b/README
@@ -20,10 +20,11 @@ Contents:
 2.F. Optional - Video camera support with V4L2 drivers
 2.G. Optional - Enable offline compositing support
 2.H. Optional - Enable kgdb over console support
-2.I. Images
-2.J. Boot to U-Boot
-2.K. Image with Initramfs
-2.L. Device tree support
+2.I. Optional - Enable SPI bus
+2.J. Images
+2.K. Boot to U-Boot
+2.L. Image with Initramfs
+2.M. Device tree support
 3. Extra apps
 3.A. omxplayer
 4. Source code and mirrors
@@ -145,7 +146,13 @@ To add the kdbg over console (kgdboc) parameter to the 
kernel command line,
 set this variable in local.conf:
 ENABLE_KGDB = "1"
 
-2.I. Images
+2.I. Optional - Enable SPI bus
+==
+When using device tree kernels, set this variable to enable the SPI bus
+ENABLE_SPI_BUS = "1"
+
+
+2.J. Images
 ===
 * rpi-hwup-image
 Hardware up image
@@ -155,7 +162,7 @@ ENABLE_KGDB = "1"
 Image based on rpi-basic-image which includes most of the packages in this
 layer and some media samples.
 
-2.J. Boot to U-Boot
+2.K. Boot to U-Boot
 ===
 To have u-boot load kernel image, set in your local.conf
 KERNEL_IMAGETYPE = "uImage"
@@ -163,7 +170,7 @@ KERNEL_IMAGETYPE = "uImage"
 This will make kernel.img be u-boot image which will load uImage.
 By default, kernel.img is the actual kernel image (ex. Image).
 
-2.K. Image with Initramfs
+2.L. Image with Initramfs
 =
 To build an initramfs image :
 * Set this 3 kernel variables (in linux-raspberrypi.inc for example)
@@ -176,7 +183,7 @@ To build an initramfs image :
 * Set the meta-rasberrypi variable (in raspberrypi.conf for example)
 - KERNEL_INITRAMFS = "-initramfs"
 
-2.L. Device tree support
+2.M. Device tree support
 =
 Device tree for RPi is only supported when using linux-raspberrypi 3.18+
 kernels.
@@ -189,11 +196,6 @@ kernels.
 NOTE: KERNEL_DEVICETREE is default enabled for kernel >= 3.18 and always 
disabled for
   older kernel versions.
 
-2.M. Optional - enable SPI bus
-==
-When using device tree kernels, set this variable to enable the SPI bus
-ENABLE_SPI_BUS = "1"
-
 3. Extra apps
 =
 
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH v2 5/7] rpi-base.inc: Allow MACHINE_FEATURES appends

[Petter Mabäcker]

Ensure that it's possible to add MACHINE_FEATURES from places that will
be executed before rpi-base.inc (like e.g. local.conf), without having
them overrided.

Signed-off-by: Petter Mabäcker 
---
 conf/machine/include/rpi-base.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index e097702..c8f6cd6 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -37,7 +37,7 @@ KERNEL_DEVICETREE ?= " \
 "
 KERNEL_IMAGETYPE ?= "Image"
 
-MACHINE_FEATURES = "kernel26 apm usbhost keyboard vfat ext2 screen touchscreen 
alsa bluetooth wifi sdio"
+MACHINE_FEATURES += "kernel26 apm usbhost keyboard vfat ext2 screen 
touchscreen alsa bluetooth wifi sdio"
 
 # Raspberry Pi has no hardware clock
 MACHINE_FEATURES_BACKFILL_CONSIDERED = "rtc"
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH v2 3/7] linux-raspberrypi: Update 4.1 recipe to 4.1.15

[Petter Mabäcker]

[Support #69]

Signed-off-by: Petter Mabäcker 
---
 recipes-kernel/linux/linux-raspberrypi_4.1.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-kernel/linux/linux-raspberrypi_4.1.bb 
b/recipes-kernel/linux/linux-raspberrypi_4.1.bb
index 3a3cf40..cae459a 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.1.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.1.bb
@@ -1,6 +1,6 @@
-LINUX_VERSION ?= "4.1.10"
+LINUX_VERSION ?= "4.1.15"
 
-SRCREV = "b74df9228c27f55361c065bc5dbfba88861cc771"
+SRCREV = "02a8ee530e32b08e5df44f10e24d5fd82bb960e3"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.1.y"
 
 require linux-raspberrypi.inc
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 4/5] pitft: Add basic support for PiTFT

[Petter Mabäcker]

 

2016-01-12 09:45 skrev Khem Raj: 

> On Mon, Jan 11, 2016 at 10:51
PM, Petter Mabäcker  wrote:
> 
>> 2016-01-11 21:32
skrev Andrei Gherzan: On Mon, Jan 11, 2016 at 09:55:43AM -0800, Khem Raj
wrote: On Jan 11, 2016, at 8:49 AM, Petter Mabäcker 
wrote: Add basic support for PiTFT display by using device-trees. In
order get it working below configurations must be active in local.conf:
MACHINEOVERRIDES .= ":pitft" Using MACHINE_FEATURES will be more
appropriate term. Effects are same. Indeed. I support MACHINE_FEATURE
usage here. I agree that the term MACHINE_FEATURES is better. However
since MACHINE_FEATURES isn't included in the OVERRIDES variable I will
not be able to use the task pre/appends that was the reason I used
MACHINEOVERRIDES in the first place. The reason I want to use overrides
in this case is since I think it makes the code easier to read and
understand for the user (in this particular case at least). I can of
course change to just using variables (like in many other optional
features in meta-raspberrypi) or change to MACHINE_FEATURES. But I'm not
sure how I can solve for example the below part in a effective and nice
way:
> 
> it really doesnt need to have override, you can enquire
>
MACHINE_FEATURES in python or shell.

Yes, I'm aware of that I can use
it that way. It was just my personal opinion that the code looks better
with overrides in this particular case. On the other hand I can agree
that the end-user will be more comfortable with using MACHINE_FEATURES
instead of MACHINEOVERRIDES. Also since both you and Andrei push for
MACHINE_FEATURES I will bend for your will =) 

Start using
MACHINE_FEATURES from local.conf when using meta-raspberrypi will
require a minor change i rpi-base.inc as well, since it otherwise will
override MACHINE_FEATURES added in local.conf. I will send up a fix for
that in v2 of this series as well. 

Thanks for your feedback. 

BR
Petter 

>> xserver-xf86-config_0.1.bbappend FILESEXTRAPATHS_prepend :=
"${THISDIR}/${PN}:" SRC_URI_append_rpi = "
file://xorg.conf.d/10-evdev.conf [1] " SRC_URI_append_pitft = "
file://xorg.conf.d/99-pitft.conf [2] " < My change
do_install_append_rpi () { install -d
${D}/${sysconfdir}/X11/xorg.conf.d/ install -m 0644
${WORKDIR}/xorg.conf.d/* ${D}/${sysconfdir}/X11/xorg.conf.d/ }
FILES_${PN}_rpi += "${sysconfdir}/X11/xorg.conf
${sysconfdir}/X11/xorg.conf.d/*" --- end
--- But if you have any good suggestions about how
to solve this, please enlighten me =) BR Petter -- Andrei Gherzan



Links:
--
[1] file://xorg.conf.d/10-evdev.conf
[2]
file://xorg.conf.d/99-pitft.conf
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 4/5] pitft: Add basic support for PiTFT

[Petter Mabäcker]

 

2016-01-11 21:32 skrev Andrei Gherzan: 

> On Mon, Jan 11, 2016 at
09:55:43AM -0800, Khem Raj wrote:
> 
>>> On Jan 11, 2016, at 8:49 AM,
Petter Mabäcker  wrote: Add basic support for PiTFT
display by using device-trees. In order get it working below
configurations must be active in local.conf: MACHINEOVERRIDES .=
":pitft"
>> Using MACHINE_FEATURES will be more appropriate term.
Effects are same.
> 
> Indeed. I support MACHINE_FEATURE usage here.

I
agree that the term MACHINE_FEATURES is better. However since
MACHINE_FEATURES isn't included in the OVERRIDES variable I will not be
able to use the task pre/appends that was the reason I used
MACHINEOVERRIDES in the first place. The reason I want to use overrides
in this case is since I think it makes the code easier to read and
understand for the user (in this particular case at least). I can of
course change to just using variables (like in many other optional
features in meta-raspberrypi) or change to MACHINE_FEATURES. But I'm not
sure how I can solve for example the below part in a effective and nice
way: 

xserver-xf86-config_0.1.bbappend 

FILESEXTRAPATHS_prepend :=
"${THISDIR}/${PN}:"

SRC_URI_append_rpi = "
file://xorg.conf.d/10-evdev.conf "
SRC_URI_append_pitft = "
file://xorg.conf.d/99-pitft.conf " < My
change

do_install_append_rpi () {
 install -d
${D}/${sysconfdir}/X11/xorg.conf.d/
 install -m 0644
${WORKDIR}/xorg.conf.d/*
${D}/${sysconfdir}/X11/xorg.conf.d/
}

FILES_${PN}_rpi +=
"${sysconfdir}/X11/xorg.conf
${sysconfdir}/X11/xorg.conf.d/*"
--- end
--- 

But if you have any good suggestions about how
to solve this, please enlighten me =) 

BR Petter 

> -- Andrei Gherzan

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 0/5] Various upgrade/fixes from Technux

[Petter Mabäcker]

 

Just realized that I missed one minor patch that fixes some typo in
the README.. Will add that one in a v2 of this serie. 

BR Petter


Petter Mabäcker

Technux

www.technux.se

2016-01-11 17:49 skrev Petter
Mabäcker: 

> Various fixes from Technux, with focus on PiTFT support.
>

> Petter Mabäcker (5):
> .gitignore: Ignore .swp files
>
linux-raspberrypi: Update 4.1 recipe to 4.1.15
> rpi-config: I2C
support
> pitft: Add basic support for PiTFT
> pitft: Add PiTFT22
support
> 
> .gitignore | 1 +
> README | 43 ++--
>
conf/machine/include/rpi-base.inc | 1 +
>
recipes-bsp/bootfiles/rpi-config_git.bb | 26 +
>
.../rpi/xorg.conf.d/99-pitft.conf | 5 +
>
.../xorg-xserver/xserver-xf86-config_0.1.bbappend | 1 +
>
recipes-kernel/linux/linux-raspberrypi.inc | 1 +
>
...dts-add-overlay-for-pitft22-in-linux-3.18.patch | 110
+
> .../0001-dts-add-overlay-for-pitft22.patch | 110
+
> recipes-kernel/linux/linux-raspberrypi_3.18.bb |
5 +-
> recipes-kernel/linux/linux-raspberrypi_4.1.bb | 8 +-
> 11 files
changed, 298 insertions(+), 13 deletions(-)
> create mode 100644
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
>
create mode 100644
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
>
create mode 100644
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22.patch

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 4/5] pitft: Add basic support for PiTFT

[Petter Mabäcker]

Add basic support for PiTFT display by using device-trees.

In order get it working below configurations must be active in
local.conf:

MACHINEOVERRIDES .= ":pitft"
 - This will enable SPI bus and i2c device-trees, it will also setup
   framebuffer for console and x server on PiTFT.

[Support #70]

Signed-off-by: Petter Mabäcker 
---
 README | 29 --
 recipes-bsp/bootfiles/rpi-config_git.bb| 14 +++
 .../rpi/xorg.conf.d/99-pitft.conf  |  5 
 .../xorg-xserver/xserver-xf86-config_0.1.bbappend  |  1 +
 recipes-kernel/linux/linux-raspberrypi.inc |  1 +
 5 files changed, 42 insertions(+), 8 deletions(-)
 create mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf

diff --git a/README b/README
index 8ef4e7a..791038f 100644
--- a/README
+++ b/README
@@ -22,10 +22,11 @@ Contents:
 2.H. Optional - Enable kgdb over console support
 2.I. Optional - Enable SPI bus
 2.J. Optional - Enable I2C
-2.K. Images
-2.L. Boot to U-Boot
-2.M. Image with Initramfs
-2.N. Device tree support
+2.K. Optional - Enable PiTFT support
+2.L. Images
+2.M. Boot to U-Boot
+2.N. Image with Initramfs
+2.O. Device tree support
 3. Extra apps
 3.A. omxplayer
 4. Source code and mirrors
@@ -157,7 +158,19 @@ ENABLE_SPI_BUS = "1"
 When using device tree kernels, set this variable to enable I2C
 ENABLE_I2C = "1"
 
-2.K. Images
+2.K. Optional - Enable PiTFT support
+
+Basic support for using PiTFT screens can be enabled by adding
+below in local.conf:
+
+MACHINEOVERRIDES .= ":pitft"
+  - This will enable SPI bus and i2c device-trees, it will also setup
+framebuffer for console and x server on PiTFT.
+
+NOTE: To get this working the overlay for the PiTFT model must be build,
+  added and specified as well (dtoverlay= in config.txt)
+
+2.L. Images
 ===
 * rpi-hwup-image
 Hardware up image
@@ -167,7 +180,7 @@ ENABLE_I2C = "1"
 Image based on rpi-basic-image which includes most of the packages in this
 layer and some media samples.
 
-2.L. Boot to U-Boot
+2.M. Boot to U-Boot
 ===
 To have u-boot load kernel image, set in your local.conf
 KERNEL_IMAGETYPE = "uImage"
@@ -175,7 +188,7 @@ KERNEL_IMAGETYPE = "uImage"
 This will make kernel.img be u-boot image which will load uImage.
 By default, kernel.img is the actual kernel image (ex. Image).
 
-2.M. Image with Initramfs
+2.N. Image with Initramfs
 =
 To build an initramfs image :
 * Set this 3 kernel variables (in linux-raspberrypi.inc for example)
@@ -188,7 +201,7 @@ To build an initramfs image :
 * Set the meta-rasberrypi variable (in raspberrypi.conf for example)
 - KERNEL_INITRAMFS = "-initramfs"
 
-2.N. Device tree support
+2.O. Device tree support
 =
 Device tree for RPi is only supported when using linux-raspberrypi 3.18+
 kernels.
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index ccb9b7f..9f20352 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -80,6 +80,20 @@ do_deploy() {
 fi
 }
 
+do_deploy_append_pitft() {
+# Add SPI BUS and I2C support if needed
+if [ -z "${ENABLE_SPI_BUS}" ]; then
+echo "# Enable SPI bus" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtparam=spi=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+fi
+
+if [ -z "${ENABLE_I2C}" ]; then
+echo "# Enable I2C" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtparam=i2c1=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtparam=i2c_arm=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+fi
+}
+
 addtask deploy before do_package after do_install
 do_deploy[dirs] += "${DEPLOYDIR}/bcm2835-bootfiles"
 
diff --git 
a/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
new file mode 100644
index 000..0d2b36b
--- /dev/null
+++ 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
@@ -0,0 +1,5 @@
+Section "Device"
+Identifier "Adafruit PiTFT"
+Driver "fbdev"
+Option "fbdev" "/dev/fb1"
+EndSection
diff --git a/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend 
b/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
index 2cf40f8..db8e4c1 100644
--- a/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
+++ b/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
@@ -1,6 +1,7 @@
 FILESEXTRAPATHS_pr

[yocto] [meta-raspberrypi][PATCH 5/5] pitft: Add PiTFT22 support

[Petter Mabäcker]

- Add support to build overlays for PiTFT22 in the kernel.
- Setup a basic configuration for the driver

The PiTFT22 support is optional and can be enabled by adding below in
local.conf:

MACHINEOVERRIDES .= ":pitft:pitft22"

[Support #70]

Signed-off-by: Petter Mabäcker 
---
 README |   9 ++
 conf/machine/include/rpi-base.inc  |   1 +
 recipes-bsp/bootfiles/rpi-config_git.bb|   6 ++
 ...dts-add-overlay-for-pitft22-in-linux-3.18.patch | 110 +
 .../0001-dts-add-overlay-for-pitft22.patch | 110 +
 recipes-kernel/linux/linux-raspberrypi_3.18.bb |   5 +-
 recipes-kernel/linux/linux-raspberrypi_4.1.bb  |   4 +-
 7 files changed, 242 insertions(+), 3 deletions(-)
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22.patch

diff --git a/README b/README
index 791038f..d08d925 100644
--- a/README
+++ b/README
@@ -170,6 +170,15 @@ MACHINEOVERRIDES .= ":pitft"
 NOTE: To get this working the overlay for the PiTFT model must be build,
   added and specified as well (dtoverlay= in config.txt)
 
+Below is a list of currently supported PiTFT models in meta-raspberrypi,
+the modelname should be appended with MACHINEOVERRIDES in local.conf like 
below:
+
+   - MACHINEOVERRIDES .= ":pitft:"
+
+List of currently supported models
+---
+pitft22
+
 2.L. Images
 ===
 * rpi-hwup-image
diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index e097702..44cc7de 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -31,6 +31,7 @@ KERNEL_DEVICETREE ?= " \
 overlays/iqaudio-dac-overlay.dtb \
 overlays/iqaudio-dacplus-overlay.dtb \
 overlays/lirc-rpi-overlay.dtb \
+overlays/pitft22-overlay.dtb \
 overlays/pps-gpio-overlay.dtb \
 overlays/w1-gpio-overlay.dtb \
 overlays/w1-gpio-pullup-overlay.dtb \
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index 9f20352..5d1539f 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -94,6 +94,12 @@ do_deploy_append_pitft() {
 fi
 }
 
+do_deploy_append_pitft22() {
+# Add support for PiTFT22 display
+echo "# Enable PITFT22 display" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtoverlay=pitft22,rotate=270,speed=3200,txbuflen=32768" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+}
+
 addtask deploy before do_package after do_install
 do_deploy[dirs] += "${DEPLOYDIR}/bcm2835-bootfiles"
 
diff --git 
a/recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
 
b/recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
new file mode 100644
index 000..fa73599
--- /dev/null
+++ 
b/recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
@@ -0,0 +1,110 @@
+From 2f44861e2a2d651a9aa62a75343a032fee33e93b Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petter=20Mab=C3=A4cker?= 
+Date: Fri, 8 Jan 2016 09:02:44 +0100
+Subject: [PATCH] dts: add overlay for pitft22 in linux 3.18
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Upstream-Status: Pending
+
+Add the pitft22 overlay from adafruit Adafruit-Pi-Kernel-o-Matic repo:
+https://github.com/adafruit/Adafruit-Pi-Kernel-o-Matic
+
+Signed-off-by: Petter Mabäcker 
+---
+ arch/arm/boot/dts/overlays/Makefile|  1 +
+ arch/arm/boot/dts/overlays/pitft22-overlay.dts | 69 ++
+ 2 files changed, 70 insertions(+)
+ create mode 100755 arch/arm/boot/dts/overlays/pitft22-overlay.dts
+
+diff --git a/arch/arm/boot/dts/overlays/Makefile 
b/arch/arm/boot/dts/overlays/Makefile
+index c766616..1eaaf81 100644
+--- a/arch/arm/boot/dts/overlays/Makefile
 b/arch/arm/boot/dts/overlays/Makefile
+@@ -27,6 +27,7 @@ dtb-$(RPI_DT_OVERLAYS) += mcp2515-can0-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += mmc-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += mz61581-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += piscreen-overlay.dtb
++dtb-$(RPI_DT_OVERLAYS) += pitft22-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += pitft28-resistive-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += pps-gpio-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += rpi-dac-overlay.dtb
+diff --git a/arch/arm/boot/dts/overlays/pitft22-overlay.dts 
b/arch/arm/boot/dts/overlays/pitft22-overlay.dts
+new file mode 100755
+index 000..894ba22
+--- /dev/null
 b/arch/arm/boot/dts/overlays/pitft22-overlay.dts
+@@ -0,0 +1,69 @@
++/*
++ * Device Tree overlay for pitft by Adafruit
++ *
++ */
++
++/dts-v1/;
++/plugin/;
++
++/ {
++compatible = "brcm,bcm2835", &quo

[yocto] [meta-raspberrypi][PATCH 2/5] linux-raspberrypi: Update 4.1 recipe to 4.1.15

[Petter Mabäcker]

[Support #69]

Signed-off-by: Petter Mabäcker 
---
 recipes-kernel/linux/linux-raspberrypi_4.1.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-kernel/linux/linux-raspberrypi_4.1.bb 
b/recipes-kernel/linux/linux-raspberrypi_4.1.bb
index 3a3cf40..cae459a 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.1.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.1.bb
@@ -1,6 +1,6 @@
-LINUX_VERSION ?= "4.1.10"
+LINUX_VERSION ?= "4.1.15"
 
-SRCREV = "b74df9228c27f55361c065bc5dbfba88861cc771"
+SRCREV = "02a8ee530e32b08e5df44f10e24d5fd82bb960e3"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.1.y"
 
 require linux-raspberrypi.inc
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 1/5] .gitignore: Ignore .swp files

[Petter Mabäcker]

Signed-off-by: Petter Mabäcker 
---
 .gitignore | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.gitignore b/.gitignore
index 1677b58..f235765 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,2 +1,3 @@
 build*
 *~
+.*.swp
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 3/5] rpi-config: I2C support

[Petter Mabäcker]

With newer kernels (>=3.18) that supports device-trees I2C
should be enabled with device-trees.

This is now support by adding:
ENABLE_I2C = "1"
in local.conf

This will enable the dtparams:
i2c1
i2c_arm

Signed-off-by: Petter Mabäcker 
---
 README  | 21 +
 recipes-bsp/bootfiles/rpi-config_git.bb |  6 ++
 2 files changed, 19 insertions(+), 8 deletions(-)

diff --git a/README b/README
index a168692..8ef4e7a 100644
--- a/README
+++ b/README
@@ -21,10 +21,11 @@ Contents:
 2.G. Optional - Enable offline compositing support
 2.H. Optional - Enable kgdb over console support
 2.I. Optional - Enable SPI bus
-2.J. Images
-2.K. Boot to U-Boot
-2.L. Image with Initramfs
-2.M. Device tree support
+2.J. Optional - Enable I2C
+2.K. Images
+2.L. Boot to U-Boot
+2.M. Image with Initramfs
+2.N. Device tree support
 3. Extra apps
 3.A. omxplayer
 4. Source code and mirrors
@@ -151,8 +152,12 @@ ENABLE_KGDB = "1"
 When using device tree kernels, set this variable to enable the SPI bus
 ENABLE_SPI_BUS = "1"
 
+2.J. Optional - Enable I2C
+==
+When using device tree kernels, set this variable to enable I2C
+ENABLE_I2C = "1"
 
-2.J. Images
+2.K. Images
 ===
 * rpi-hwup-image
 Hardware up image
@@ -162,7 +167,7 @@ ENABLE_SPI_BUS = "1"
 Image based on rpi-basic-image which includes most of the packages in this
 layer and some media samples.
 
-2.K. Boot to U-Boot
+2.L. Boot to U-Boot
 ===
 To have u-boot load kernel image, set in your local.conf
 KERNEL_IMAGETYPE = "uImage"
@@ -170,7 +175,7 @@ KERNEL_IMAGETYPE = "uImage"
 This will make kernel.img be u-boot image which will load uImage.
 By default, kernel.img is the actual kernel image (ex. Image).
 
-2.L. Image with Initramfs
+2.M. Image with Initramfs
 =
 To build an initramfs image :
 * Set this 3 kernel variables (in linux-raspberrypi.inc for example)
@@ -183,7 +188,7 @@ To build an initramfs image :
 * Set the meta-rasberrypi variable (in raspberrypi.conf for example)
 - KERNEL_INITRAMFS = "-initramfs"
 
-2.M. Device tree support
+2.N. Device tree support
 =
 Device tree for RPi is only supported when using linux-raspberrypi 3.18+
 kernels.
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index aa11b25..ccb9b7f 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -72,6 +72,12 @@ do_deploy() {
 echo "# Enable SPI bus" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=spi=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 fi
+
+if [ -n "${ENABLE_I2C}" ]; then
+echo "# Enable I2C" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtparam=i2c1=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtparam=i2c_arm=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+fi
 }
 
 addtask deploy before do_package after do_install
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 0/5] Various upgrade/fixes from Technux

[Petter Mabäcker]

Various fixes from Technux, with focus on PiTFT support.

Petter Mabäcker (5):
  .gitignore: Ignore .swp files
  linux-raspberrypi: Update 4.1 recipe to 4.1.15
  rpi-config: I2C support
  pitft: Add basic support for PiTFT
  pitft: Add PiTFT22 support

 .gitignore |   1 +
 README |  43 ++--
 conf/machine/include/rpi-base.inc  |   1 +
 recipes-bsp/bootfiles/rpi-config_git.bb|  26 +
 .../rpi/xorg.conf.d/99-pitft.conf  |   5 +
 .../xorg-xserver/xserver-xf86-config_0.1.bbappend  |   1 +
 recipes-kernel/linux/linux-raspberrypi.inc |   1 +
 ...dts-add-overlay-for-pitft22-in-linux-3.18.patch | 110 +
 .../0001-dts-add-overlay-for-pitft22.patch | 110 +
 recipes-kernel/linux/linux-raspberrypi_3.18.bb |   5 +-
 recipes-kernel/linux/linux-raspberrypi_4.1.bb  |   8 +-
 11 files changed, 298 insertions(+), 13 deletions(-)
 create mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22.patch

-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Can any one please tell the what is the exact difference between DEPENDS and RDEPENDS

[Petter Mabäcker]

 

2015-10-08 06:37 skrev Vivek Per: 

> Hi, 
> Can any one please tell
the what is the exact difference between DEPENDS and RDEPENDS . I am not
able to get it . How these variables are exactly parsed. 
> 
> -regards

> vivek

Hi, 

I guess you already have read through the manual about
the variables?


http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-RDEPENDS


http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-DEPENDS


The overall description of the differences are (please someone
correct me if you find my answer incorrect) that DEPENDS specifics
build-time dependencies (e.i. other recipe files) so you should be
guaranteed that all packages listed in the DEPENDS has been built and
installed in the sysroot before your new package starts its configure
task. 

RDEPENDS on the other hand, is a run-time dependency so instead
of other recipe files RDEPENDS lists packages that should have been
installed in order to correctly run your package on target. 

All this
is explained more in detail in the manual (see above links). Also keep
in mind that DEPENDS works with recipes and RDEPENDS with packages
(which isn't necessary the same). Debug the PACKAGES for a specific
variable
(http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-PACKAGES)
in order to get a clue about what packages a recipe will generate. 

If
you still have a hard to understanding the differences my suggestion is
that you starts playing around a bit with them. Create a project and add
some DEPENDS and RDEPENDS to a recipe(s), build the affected packages
and investigate if they have been built in the expected order. This can
for example be verified by tracking the build output or by looking
through the cooker logs tmp/log/cooker/*. 

BR Petter 

Petter
Mabäcker

Technux 
www.technux.se
 -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 1/1] pi-blaster: Bump SRCREV

[Petter Mabäcker]

Update to latest revision in order to get rid of the integration patch
'0001-handle-install-data-hook-when-cross-compile.patch' that has been
submitted upstream.

Changes since cd318cd63031a30249a4c08435b97263fa76d7b7:
  bce7c1b Merge pull request #45 from Technux/dev/technux
  74510ff Display an error message if unable to open mbox
  53197ca handle install-data-hook when cross compile

Signed-off-by: Petter Mabäcker 
---
 ...ndle-install-data-hook-when-cross-compile.patch | 54 --
 recipes-devtools/pi-blaster/pi-blaster.inc |  1 -
 recipes-devtools/pi-blaster/pi-blaster_git.bb  |  2 +-
 3 files changed, 1 insertion(+), 56 deletions(-)
 delete mode 100644 
recipes-devtools/pi-blaster/files/0001-handle-install-data-hook-when-cross-compile.patch

diff --git 
a/recipes-devtools/pi-blaster/files/0001-handle-install-data-hook-when-cross-compile.patch
 
b/recipes-devtools/pi-blaster/files/0001-handle-install-data-hook-when-cross-compile.patch
deleted file mode 100644
index 2f2a7f4..000
--- 
a/recipes-devtools/pi-blaster/files/0001-handle-install-data-hook-when-cross-compile.patch
+++ /dev/null
@@ -1,54 +0,0 @@
-From 28e4bc3216f8845cf278f0fbc6b2c30eebcc35aa Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Petter=20Mab=C3=A4cker?= 
-Date: Sun, 7 Jun 2015 17:17:01 +0200
-Subject: [PATCH] handle install-data-hook when cross compile
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-Avoid doing 'install-data-hook' when cross compiling since it isn't
-suitable to update rc.d or run the service when cross
-compiling.
-
-Upstream-Status: Pending
-
-Signed-off-by: Petter Mabäcker 

- Makefile.am  | 4 +++-
- configure.ac | 1 +
- 2 files changed, 4 insertions(+), 1 deletion(-)
-
-diff --git a/Makefile.am b/Makefile.am
-index 6693d46..935288f 100644
 a/Makefile.am
-+++ b/Makefile.am
-@@ -13,6 +13,7 @@ else
- init_ddir = $(sysconfdir)/init.d
- init_d_SCRIPTS = pi-blaster.boot.sh
- 
-+if !CROSS_COMPILING
- install-data-hook:
-   update-rc.d pi-blaster.boot.sh defaults
-   $(init_ddir)/pi-blaster.boot.sh start
-@@ -20,4 +21,5 @@ install-data-hook:
- uninstall-hook:
-   update-rc.d pi-blaster.boot.sh remove
-   killall pi-blaster
--endif
-+endif # !CROSS_COMPILING
-+endif # !HAVE_SYSTEMD
-diff --git a/configure.ac b/configure.ac
-index 5d0c1fa..aaf4465 100644
 a/configure.ac
-+++ b/configure.ac
-@@ -23,6 +23,7 @@ if test "x$with_systemdsystemunitdir" != xno; then
-  AC_SUBST([systemdsystemunitdir], [$with_systemdsystemunitdir])
- fi
- AM_CONDITIONAL(HAVE_SYSTEMD, [test -n "$with_systemdsystemunitdir" -a 
"x$with_systemdsystemunitdir" != xno ])
-+AM_CONDITIONAL(CROSS_COMPILING, [test x"$cross_compiling" = x"yes" ])
- 
- # Checks for programs.
- AC_PROG_CC
--- 
-1.9.1
-
diff --git a/recipes-devtools/pi-blaster/pi-blaster.inc 
b/recipes-devtools/pi-blaster/pi-blaster.inc
index 1f4cc2f..a3beccc 100644
--- a/recipes-devtools/pi-blaster/pi-blaster.inc
+++ b/recipes-devtools/pi-blaster/pi-blaster.inc
@@ -6,7 +6,6 @@ LIC_FILES_CHKSUM = 
"file://README.md;beginline=157;endline=170;md5=f20832f311266
 
 SRC_URI = "git://github.com/sarfata/pi-blaster \
file://remove-initscript-lsb-dependency.patch \
-   file://0001-handle-install-data-hook-when-cross-compile.patch \
 "
 
 S = "${WORKDIR}/git"
diff --git a/recipes-devtools/pi-blaster/pi-blaster_git.bb 
b/recipes-devtools/pi-blaster/pi-blaster_git.bb
index 3ae7c49..01a55ca 100644
--- a/recipes-devtools/pi-blaster/pi-blaster_git.bb
+++ b/recipes-devtools/pi-blaster/pi-blaster_git.bb
@@ -1,3 +1,3 @@
 require pi-blaster.inc
 
-SRCREV = "cd318cd63031a30249a4c08435b97263fa76d7b7"
+SRCREV = "bce7c1b4c53b0dd12665e46bdebd3b7cb0987e3d"
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 0/1] pi-blaster: Bump SRCREV

[Petter Mabäcker]

The following changes since commit 17dad9328b100beda1cf870c9075e509b5cbfa90:

  README: Add extra iformation on creating/sending patches using git 
(2015-08-10 23:37:14 +0200)

are available in the git repository at:

  
https://github.com/Technux/meta-raspberrypi/commit/f2a71b6959484f9a6d4c60bb28b7b47b13f57607

Petter Mabäcker (1):
  pi-blaster: Bump SRCREV

 ...ndle-install-data-hook-when-cross-compile.patch | 54 --
 recipes-devtools/pi-blaster/pi-blaster.inc |  1 -
 recipes-devtools/pi-blaster/pi-blaster_git.bb  |  2 +-
 3 files changed, 1 insertion(+), 56 deletions(-)
 delete mode 100644 
recipes-devtools/pi-blaster/files/0001-handle-install-data-hook-when-cross-compile.patch

-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 2/2] linux-raspberrypi: build audio driver into kernel

[Petter Mabäcker]

 

2015-08-17 11:23 skrev Alex J Lennon: 

> On 17/08/2015 09:11,
Petter Mabäcker wrote:
> 
>> 2015-08-17 09:57 skrev Andrei Gherzan: 
>>

>>> Hello, On Tuesday, August 11, 2015, Petter Mabäcker
mailto:pet...@technux.se>> wrote: 2015-08-11 19:04
skrev Alex J Lennon: Signed-off-by: Alex J Lennon
 ---
recipes-kernel/linux/linux-raspberrypi.inc | 4  1 file changed, 4
insertions(+) diff --git a/recipes-kernel/linux/linux-raspberrypi.inc
b/recipes-kernel/linux/linux-raspberrypi.inc index e38d905..8024412
100644 --- a/recipes-kernel/linux/linux-raspberrypi.inc +++
b/recipes-kernel/linux/linux-raspberrypi.inc @@ -6,6 +6,10 @@ SECTION =
"kernel" LICENSE = "GPLv2" LIC_FILES_CHKSUM =
"file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7" +SRC_URI += " +
file://build-in-audio.cfg [1] + " This one didn't make it. -- Andrei
Gherzan -- -- Andrei Gherzan
>> Think you got the wrong receiver =) I
notified Alex about this some days ago, Alex can you send up a v2 for
this?
> 
> The build-in-audio.cfg patch was just for testing of fragment
support.
> It's understood that we're not going to have this build into
the kernel
> by default, although I do still need to find some words to
add to the
> README on audio routing setup and so forth.
> 
> I started
testing a build with master over the weekend and it built OK.
> Just
need to find some time to run up a couple of kernels and will
> resubmit
the v2 patch with Petter's enhanced commit message.
> 
> I don't have an
RPiv1 around at the moment but I will probably double
> check the kernel
does still actually build for RPiv1 machine
> 
> Cheers,
> 
> Alex
> 
>>
BR, Petter

Hi Alex, Any news for the v2 changeset? Would be awesome to
get the 4.x integrated soon. 

BR Petter 

Links:
--
[1]
file://build-in-audio.cfg
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 2/2] linux-raspberrypi: build audio driver into kernel

[Petter Mabäcker]

 

2015-08-17 09:57 skrev Andrei Gherzan: 

> Hello,
> 
> On Tuesday,
August 11, 2015, Petter Mabäcker  wrote: 
> 
>>
2015-08-11 19:04 skrev Alex J Lennon: 
>> 
>>> Signed-off-by: Alex J
Lennon 
>>> ---
>>>
recipes-kernel/linux/linux-raspberrypi.inc | 4 
>>> 1 file changed,
4 insertions(+)
>>> 
>>> diff --git
a/recipes-kernel/linux/linux-raspberrypi.inc
b/recipes-kernel/linux/linux-raspberrypi.inc
>>> index e38d905..8024412
100644
>>> --- a/recipes-kernel/linux/linux-raspberrypi.inc
>>> +++
b/recipes-kernel/linux/linux-raspberrypi.inc
>>> @@ -6,6 +6,10 @@
SECTION = "kernel"
>>> LICENSE = "GPLv2"
>>> LIC_FILES_CHKSUM =
"file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
>>> 
>>> +SRC_URI
+= " 
>>> + file://build-in-audio.cfg 
>>> + "
> 
> This one didn't make
it. 
> 
> -- 
> Andrei Gherzan 
> 
> -- 
> 
> -- Andrei Gherzan

Think
you got the wrong receiver =) I notified Alex about this some days ago,
Alex can you send up a v2 for this? 

BR, Petter -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][fido][PATCH 0/4] Backport of various fixes

[Petter Mabäcker]

Backport of various fixes and important updates (backward compatible) from
meta-raspberrypi:master to meta-raspberrypi:fido

The following changes since commit b896a7da70dd7a16ba7ffd664f7747cb37e1d142:

  .gitignore: Ignore some stuff (2015-03-12 22:20:51 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib petmab/rpi_fido_fixes
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=petmab/rpi_fido_fixes

Andrei Gherzan (1):
  rpi-default-providers: Let users overwrite the default providers

Khem Raj (1):
  userland: Fix POSIX compliance expectation

Petter Mabäcker (1):
  linux-raspberrypi: Update 3.18 branch to 3.18.11

Thomas Perrot (1):
  If SERIAL_CONSOLE is already define by another layer, this value may
not be good.

 conf/machine/include/rpi-base.inc  |  2 +-
 conf/machine/include/rpi-default-providers.inc |  8 ++---
 .../userland/0001-Use-newer-POSIX-macro.patch  | 35 ++
 recipes-graphics/userland/userland_git.bb  |  1 +
 recipes-kernel/linux/linux-raspberrypi_3.18.bb |  8 ++---
 5 files changed, 44 insertions(+), 10 deletions(-)
 create mode 100644 
recipes-graphics/userland/userland/0001-Use-newer-POSIX-macro.patch

-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][fido][PATCH 3/4] userland: Fix POSIX compliance expectation

[Petter Mabäcker]

From: Khem Raj 

We have errors like below with glibc 2.22+

net_sockets_common.c:139:20: error: storage size of 'hints' isn't known
struct addrinfo hints, *info, *p;
^

newer glibc has now fixed the definitions of getaddrinfo and ilk to be
enabled with correct posix version.

Signed-off-by: Khem Raj 

(cherry picked from commit f188f3d756f59fb4dc64cc1a64263c2251f76ae5)
Signed-off-by: Petter Mabäcker 
---
 .../userland/0001-Use-newer-POSIX-macro.patch  | 35 ++
 recipes-graphics/userland/userland_git.bb  |  1 +
 2 files changed, 36 insertions(+)
 create mode 100644 
recipes-graphics/userland/userland/0001-Use-newer-POSIX-macro.patch

diff --git 
a/recipes-graphics/userland/userland/0001-Use-newer-POSIX-macro.patch 
b/recipes-graphics/userland/userland/0001-Use-newer-POSIX-macro.patch
new file mode 100644
index 000..2a092c2
--- /dev/null
+++ b/recipes-graphics/userland/userland/0001-Use-newer-POSIX-macro.patch
@@ -0,0 +1,35 @@
+From 12f7718bb0e08e2c06825c7ab7541b3c5bfe74c1 Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Sun, 9 Aug 2015 08:55:05 -0700
+Subject: [PATCH] Use newer POSIX macro
+
+Define _POSIX_C_SOURCE such that it demands correct
+posix interfaces, netdb.h declares interfaces such as
+getaddrinfo if __USE_POSIX, i.e. POSIX.1:1990 or later.
+However, these interfaces were new in the 2001 edition of POSIX
+therefore ask for Extension from POSIX.1:2001 since we use addrinfo
+structure here.
+
+Signed-off-by: Khem Raj 
+---
+Upstream-Status: Submitted
+
+ containers/CMakeLists.txt | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/containers/CMakeLists.txt b/containers/CMakeLists.txt
+index a29a885..5570038 100644
+--- a/containers/CMakeLists.txt
 b/containers/CMakeLists.txt
+@@ -13,7 +13,7 @@ add_definitions(-DDL_PATH_PREFIX="${VMCS_PLUGIN_DIR}/")
+ 
+ SET( GCC_COMPILER_FLAGS -Wall -g -O2 -Wstrict-prototypes -Wmissing-prototypes 
-Wmissing-declarations -Wcast-qual -Wwrite-strings -Wundef )
+ SET( GCC_COMPILER_FLAGS ${GCC_COMPILER_FLAGS} -Wextra 
)#-Wno-missing-field-initializers )
+-SET( GCC_COMPILER_FLAGS ${GCC_COMPILER_FLAGS} -std=c99 
-D_POSIX_C_SOURCE=199309L )
++SET( GCC_COMPILER_FLAGS ${GCC_COMPILER_FLAGS} -std=c99 
-D_POSIX_C_SOURCE=200112L )
+ SET( GCC_COMPILER_FLAGS ${GCC_COMPILER_FLAGS} -Wno-missing-field-initializers 
)
+ SET( GCC_COMPILER_FLAGS ${GCC_COMPILER_FLAGS} -Wno-unused-value )
+ 
+-- 
+2.1.4
+
diff --git a/recipes-graphics/userland/userland_git.bb 
b/recipes-graphics/userland/userland_git.bb
index 729c42a..861029d 100644
--- a/recipes-graphics/userland/userland_git.bb
+++ b/recipes-graphics/userland/userland_git.bb
@@ -16,6 +16,7 @@ SRCFORK = "raspberrypi"
 SRCREV = "3b81b91c18ff19f97033e146a9f3262ca631f0e9"
 
 SRC_URI = 
"git://github.com/${SRCFORK}/userland.git;protocol=git;branch=${SRCBRANCH} \
+   file://0001-Use-newer-POSIX-macro.patch \
   "
 S = "${WORKDIR}/git"
 
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][fido][PATCH 1/4] linux-raspberrypi: Update 3.18 branch to 3.18.11

[Petter Mabäcker]

Update linux-raspberrypi_3.18 to latest version.
Remove sl030raspberrypii2ckernel.patch since it will not apply anymore
and its content seems to be obsolite in later kernel versions.

[Support #56]

Change-Id: I91e57f4e65d9c1c9d12014f5d11b0acd950e2d1d
Signed-off-by: Petter Mabäcker 
Signed-off-by: Andrei Gherzan 

(cherry picked from commit c9f29df249b80ab488e4ea6eddc01a6522a28c09)
Signed-off-by: Petter Mabäcker 
---
 recipes-kernel/linux/linux-raspberrypi_3.18.bb | 8 +++-
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/recipes-kernel/linux/linux-raspberrypi_3.18.bb 
b/recipes-kernel/linux/linux-raspberrypi_3.18.bb
index 921e702..6d8b155 100644
--- a/recipes-kernel/linux/linux-raspberrypi_3.18.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_3.18.bb
@@ -1,8 +1,6 @@
-LINUX_VERSION ?= "3.18.5"
+LINUX_VERSION ?= "3.18.11"
 
-SRCREV = "a6cf3c99bc89e2c010c2f78fbf9e3ed478ccfd46"
-SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.18.y \
-   file://sl030raspberrypii2ckernel.patch \
-  "
+SRCREV = "d64fa8121fca9883d6fb14ca06d2abf66496195e"
+SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.18.y"
 
 require linux-raspberrypi.inc
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][fido][PATCH 4/4] rpi-default-providers: Let users overwrite the default providers

[Petter Mabäcker]

From: Andrei Gherzan 

[Feature #65]

Signed-off-by: Andrei Gherzan 
Signed-off-by: Pierre FICHEUX 

(cherry picked from commit ade923f17d242f9a043b1714deb584929a2ffe8e)
Signed-off-by: Petter Mabäcker 
---
 conf/machine/include/rpi-default-providers.inc | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/conf/machine/include/rpi-default-providers.inc 
b/conf/machine/include/rpi-default-providers.inc
index ee3a3ac..cabbd43 100644
--- a/conf/machine/include/rpi-default-providers.inc
+++ b/conf/machine/include/rpi-default-providers.inc
@@ -1,10 +1,10 @@
 # RaspberryPi BSP default providers
 
-PREFERRED_PROVIDER_virtual/kernel = "linux-raspberrypi"
-PREFERRED_PROVIDER_u-boot = "u-boot-rpi"
-PREFERRED_PROVIDER_virtual/xserver = "xserver-xorg"
+PREFERRED_PROVIDER_virtual/kernel ?= "linux-raspberrypi"
+PREFERRED_PROVIDER_u-boot ?= "u-boot-rpi"
+PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xorg"
 PREFERRED_PROVIDER_virtual/egl ?= "userland"
 PREFERRED_PROVIDER_virtual/libgles2 ?= "userland"
 PREFERRED_PROVIDER_virtual/libgl ?= "mesa-gl"
 PREFERRED_PROVIDER_virtual/mesa ?= "mesa-gl"
-PREFERRED_PROVIDER_jpeg = "jpeg"
+PREFERRED_PROVIDER_jpeg ?= "jpeg"
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][fido][PATCH 2/4] If SERIAL_CONSOLE is already define by another layer, this value may not be good.

[Petter Mabäcker]

From: Thomas Perrot 

Signed-off-by: Thomas Perrot 

(cherry picked from commit c8532df1c2e4812b3520d32ed49be943bea2edd9)
Signed-off-by: Petter Mabäcker 
---
 conf/machine/include/rpi-base.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index a26803a..1dda207 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -7,7 +7,7 @@ include conf/machine/include/soc-family.inc
 
 IMAGE_FSTYPES ?= "tar.bz2 ext3 rpi-sdimg"
 
-SERIAL_CONSOLE ?= "115200 ttyAMA0"
+SERIAL_CONSOLE = "115200 ttyAMA0"
 
 XSERVER = " \
 xserver-xorg \
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 1/2] linux-raspberrypi: support configuration fragments

[Petter Mabäcker]

 

2015-08-12 10:28 skrev Alex J Lennon: 

> On 12/08/2015 09:08,
Petter Mabäcker wrote:
> 
>> 2015-08-11 21:20 skrev Alex J Lennon: 
>>

>>> On 11/08/2015 19:54, Petter Mabäcker wrote: 
>>> 
>>>> 2015-08-11
19:04 skrev Alex J Lennon: 
>>>> 
>>>>> - remove placeholder defconfig
and custom copying logic - use KBUILD_DEFCONFIG for default in-tree
configurations instead - do not replace all Yocto configured settings in
do_configure_prepen see:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7474 [1]
Signed-off-by: Alex J Lennon mailto:ajlen...@dynamicdevices.co.uk>
<mailto:ajlen...@dynamicdevices.co.uk
<mailto:ajlen...@dynamicdevices.co.uk>>> ---
recipes-kernel/linux/linux-raspberrypi.inc | 15 ---
recipes-kernel/linux/linux-raspberrypi/defconfig | 1 -
recipes-kernel/linux/linux.inc | 6 +++--- 3 files changed, 7
insertions(+), 15 deletions(-) delete mode 100644
recipes-kernel/linux/linux-raspberrypi/defconfig diff --git
a/recipes-kernel/linux/linux-raspberrypi.inc
b/recipes-kernel/linux/linux-raspberrypi.inc index 7e36408..e38d905
100644 --- a/recipes-kernel/linux/linux-raspberrypi.inc +++
b/recipes-kernel/linux/linux-raspberrypi.inc @@ -6,17 +6,14 @@ SECTION =
"kernel" LICENSE = "GPLv2" LIC_FILES_CHKSUM =
"file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7" -SRC_URI += " -
file://defconfig - " - COMPATIBLE_MACHINE = "raspberrypi" PV =
"${LINUX_VERSION}+git${SRCREV}" -# NOTE: For now we pull in the default
config from the RPi kernel GIT tree. -KERNEL_DEFCONFIG_raspberrypi ?=
"bcmrpi_defconfig" -KERNEL_DEFCONFIG_raspberrypi2 ?= "bcm2709_defconfig"
+KMACHINE ?= "${MACHINE}" +KCONFIG_MODE = "--alldefconfig"
+KBUILD_DEFCONFIG_raspberrypi ?= "bcmrpi_defconfig"
+KBUILD_DEFCONFIG_raspberrypi2 ?= "bcm2709_defconfig" # CMDLINE for
raspberrypi CMDLINE = "dwc_otg.lpm_enable=0 console=ttyAMA0,115200
kgdboc=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait" @@
-38,10 +35,6 @@ python __anonymous () { d.setVar("DEPENDS", depends) }
-do_kernel_configme_prepend() { - install -m 0644
${S}/arch/${ARCH}/configs/${KERNEL_DEFCONFIG} ${WORKDIR}/defconfig ||
die "No default configuration for ${MACHINE} / ${KERNEL_DEFCONFIG}
available." -} - do_install_prepend() { install -d ${D}/lib/firmware }
diff --git a/recipes-kernel/linux/linux-raspberrypi/defconfig
b/recipes-kernel/linux/linux-raspberrypi/defconfig deleted file mode
100644 index ecbf32c..000 ---
a/recipes-kernel/linux/linux-raspberrypi/defconfig +++ /dev/null @@ -1
+0,0 @@ -# Dummy file to get through do_kernel_configme. diff --git
a/recipes-kernel/linux/linux.inc b/recipes-kernel/linux/linux.inc index
fae78b7..103512b 100644 --- a/recipes-kernel/linux/linux.inc +++
b/recipes-kernel/linux/linux.inc @@ -33,8 +33,7 @@
kernel_configure_variable() { } do_configure_prepend() { - # Clean
.config - echo "" > ${B}/.config + mv -f ${B}/.config
${B}/.config.patched CONF_SED_SCRIPT="" # oabi / eabi support @@ -109,7
+108,8 @@ do_configure_prepend() { # Keep this the last line # Remove
all modified configs and add the rest to .config - sed -e
"${CONF_SED_SCRIPT}" < '${WORKDIR}/defconfig' >> '${B}/.config' + sed -e
"${CONF_SED_SCRIPT}" < '${B}/.config.patched' >> '${B}/.config' + rm -f
${B}/.config.patched yes '' | oe_runmake oldconfig } -- 1.9.1
>>>> Nice,
some small comments only. Please write a short summary of the feature
(kernel-yocto: allow in-tree defconfig) but keep the bugzilla as a
reference for further info. Always good to have some background
found
>>> This is seems a significant core change so I wanted to make
sure these individual changes were as easily searchable as possible in
case any problems arise in future. Can you provide an example of what
you are suggesting for the commit msg?
>> Perhaps something like: Start
using the "in-tree defconfig" solution provided in poky[0]. To specify
an "in-tree" defconfig file, edit the recipe that builds your kernel so
that it has the following command form: KBUILD_DEFCONFIG_KMACHINE ?=
defconfig_file You need to append the variable with KMACHINE and then
supply the path to your "in-tree" defconfig file. In order to achieve
this in meta-raspberrypi will need to: - start using
KBUILD_DEFCONFIG_KMACHINE - Remove placeholder defconfig and custom
copying logic. - Avoid replacing all Yocto project configured settings
in do_configure_prepend. For more background regarding this migration
read the bugzilla bug info[1]. [0] -
http://www.yoctoproject.org/docs/1.8/kernel-dev/kernel-dev.html#using-an-in-tree-defconfig-file
[2] [1] - https://bugzilla.yoctoproject.org/show_bug.cgi?id=7474 [1]
>

> Very compreh

Re: [yocto] [meta-raspberrypi][PATCH 1/2] linux-raspberrypi: support configuration fragments

[Petter Mabäcker]

 

2015-08-11 21:20 skrev Alex J Lennon: 

> On 11/08/2015 19:54,
Petter Mabäcker wrote:
> 
>> 2015-08-11 19:04 skrev Alex J Lennon: 
>>

>>> - remove placeholder defconfig and custom copying logic - use
KBUILD_DEFCONFIG for default in-tree configurations instead - do not
replace all Yocto configured settings in do_configure_prepen see:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7474 [1]
Signed-off-by: Alex J Lennon mailto:ajlen...@dynamicdevices.co.uk>> ---
recipes-kernel/linux/linux-raspberrypi.inc | 15 ---
recipes-kernel/linux/linux-raspberrypi/defconfig | 1 -
recipes-kernel/linux/linux.inc | 6 +++--- 3 files changed, 7
insertions(+), 15 deletions(-) delete mode 100644
recipes-kernel/linux/linux-raspberrypi/defconfig diff --git
a/recipes-kernel/linux/linux-raspberrypi.inc
b/recipes-kernel/linux/linux-raspberrypi.inc index 7e36408..e38d905
100644 --- a/recipes-kernel/linux/linux-raspberrypi.inc +++
b/recipes-kernel/linux/linux-raspberrypi.inc @@ -6,17 +6,14 @@ SECTION =
"kernel" LICENSE = "GPLv2" LIC_FILES_CHKSUM =
"file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7" -SRC_URI += " -
file://defconfig - " - COMPATIBLE_MACHINE = "raspberrypi" PV =
"${LINUX_VERSION}+git${SRCREV}" -# NOTE: For now we pull in the default
config from the RPi kernel GIT tree. -KERNEL_DEFCONFIG_raspberrypi ?=
"bcmrpi_defconfig" -KERNEL_DEFCONFIG_raspberrypi2 ?= "bcm2709_defconfig"
+KMACHINE ?= "${MACHINE}" +KCONFIG_MODE = "--alldefconfig"
+KBUILD_DEFCONFIG_raspberrypi ?= "bcmrpi_defconfig"
+KBUILD_DEFCONFIG_raspberrypi2 ?= "bcm2709_defconfig" # CMDLINE for
raspberrypi CMDLINE = "dwc_otg.lpm_enable=0 console=ttyAMA0,115200
kgdboc=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait" @@
-38,10 +35,6 @@ python __anonymous () { d.setVar("DEPENDS", depends) }
-do_kernel_configme_prepend() { - install -m 0644
${S}/arch/${ARCH}/configs/${KERNEL_DEFCONFIG} ${WORKDIR}/defconfig ||
die "No default configuration for ${MACHINE} / ${KERNEL_DEFCONFIG}
available." -} - do_install_prepend() { install -d ${D}/lib/firmware }
diff --git a/recipes-kernel/linux/linux-raspberrypi/defconfig
b/recipes-kernel/linux/linux-raspberrypi/defconfig deleted file mode
100644 index ecbf32c..000 ---
a/recipes-kernel/linux/linux-raspberrypi/defconfig +++ /dev/null @@ -1
+0,0 @@ -# Dummy file to get through do_kernel_configme. diff --git
a/recipes-kernel/linux/linux.inc b/recipes-kernel/linux/linux.inc index
fae78b7..103512b 100644 --- a/recipes-kernel/linux/linux.inc +++
b/recipes-kernel/linux/linux.inc @@ -33,8 +33,7 @@
kernel_configure_variable() { } do_configure_prepend() { - # Clean
.config - echo "" > ${B}/.config + mv -f ${B}/.config
${B}/.config.patched CONF_SED_SCRIPT="" # oabi / eabi support @@ -109,7
+108,8 @@ do_configure_prepend() { # Keep this the last line # Remove
all modified configs and add the rest to .config - sed -e
"${CONF_SED_SCRIPT}" < '${WORKDIR}/defconfig' >> '${B}/.config' + sed -e
"${CONF_SED_SCRIPT}" < '${B}/.config.patched' >> '${B}/.config' + rm -f
${B}/.config.patched yes '' | oe_runmake oldconfig } -- 1.9.1
>> Nice,
some small comments only. Please write a short summary of the feature
(kernel-yocto: allow in-tree defconfig) but keep the bugzilla as a
reference for further info. Always good to have some background found
>

> This is seems a significant core change so I wanted to make sure
these
> individual changes were as easily searchable as possible in case
any
> problems arise in future. Can you provide an example of what you
are
> suggesting for the commit msg?

Perhaps something like:

Start
using the "in-tree defconfig" solution provided in poky[0]. To specify
an "in-tree" defconfig file, edit the recipe that builds your kernel so
that it has the following command form:

 KBUILD_DEFCONFIG_KMACHINE ?=
defconfig_file

You need to append the variable with KMACHINE and then
supply the path to your "in-tree" defconfig file. 

In order to achieve
this in meta-raspberrypi will need to:

- start using
KBUILD_DEFCONFIG_KMACHINE
- Remove placeholder defconfig and custom
copying logic.
- Avoid replacing all Yocto project configured settings
in do_configure_prepend.

For more background regarding this migration
read the bugzilla bug info[1].

[0] -
http://www.yoctoproject.org/docs/1.8/kernel-dev/kernel-dev.html#using-an-in-tree-defconfig-file
[1]
- https://bugzilla.yoctoproject.org/show_bug.cgi?id=7474

>> directly
in the commit msg itself. Have you tested it using both poky:master and
poky:fido?
> 
> Rpi2 fido 3.18.16 with/without sound patch, 4.1.3
with/without sound patch.
> 
> BR,
> 
> Alex

Ok, since there has been
som

Re: [yocto] [meta-raspberrypi][PATCH 1/2] linux-raspberrypi: support configuration fragments

[Petter Mabäcker]

 

2015-08-11 19:04 skrev Alex J Lennon: 

> - remove placeholder
defconfig and custom copying logic
> - use KBUILD_DEFCONFIG for default
in-tree configurations instead
> - do not replace all Yocto configured
settings in do_configure_prepen
> 
> see:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7474 [1]
> 
>
Signed-off-by: Alex J Lennon 
> ---
>
recipes-kernel/linux/linux-raspberrypi.inc | 15 ---
>
recipes-kernel/linux/linux-raspberrypi/defconfig | 1 -
>
recipes-kernel/linux/linux.inc | 6 +++---
> 3 files changed, 7
insertions(+), 15 deletions(-)
> delete mode 100644
recipes-kernel/linux/linux-raspberrypi/defconfig
> 
> diff --git
a/recipes-kernel/linux/linux-raspberrypi.inc
b/recipes-kernel/linux/linux-raspberrypi.inc
> index 7e36408..e38d905
100644
> --- a/recipes-kernel/linux/linux-raspberrypi.inc
> +++
b/recipes-kernel/linux/linux-raspberrypi.inc
> @@ -6,17 +6,14 @@ SECTION
= "kernel"
> LICENSE = "GPLv2"
> LIC_FILES_CHKSUM =
"file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
> 
> -SRC_URI += "

> - file://defconfig 
> - "
> -
> COMPATIBLE_MACHINE = "raspberrypi"
>

> PV = "${LINUX_VERSION}+git${SRCREV}"
> 
> -# NOTE: For now we pull in
the default config from the RPi kernel GIT tree.
>
-KERNEL_DEFCONFIG_raspberrypi ?= "bcmrpi_defconfig"
>
-KERNEL_DEFCONFIG_raspberrypi2 ?= "bcm2709_defconfig"
> +KMACHINE ?=
"${MACHINE}"
> +KCONFIG_MODE = "--alldefconfig"
>
+KBUILD_DEFCONFIG_raspberrypi ?= "bcmrpi_defconfig"
>
+KBUILD_DEFCONFIG_raspberrypi2 ?= "bcm2709_defconfig"
> 
> # CMDLINE for
raspberrypi
> CMDLINE = "dwc_otg.lpm_enable=0 console=ttyAMA0,115200
kgdboc=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait"
> @@
-38,10 +35,6 @@ python __anonymous () {
> d.setVar("DEPENDS", depends)
>
}
> 
> -do_kernel_configme_prepend() {
> - install -m 0644
${S}/arch/${ARCH}/configs/${KERNEL_DEFCONFIG} ${WORKDIR}/defconfig ||
die "No default configuration for ${MACHINE} / ${KERNEL_DEFCONFIG}
available."
> -}
> -
> do_install_prepend() {
> install -d
${D}/lib/firmware
> }
> diff --git
a/recipes-kernel/linux/linux-raspberrypi/defconfig
b/recipes-kernel/linux/linux-raspberrypi/defconfig
> deleted file mode
100644
> index ecbf32c..000
> ---
a/recipes-kernel/linux/linux-raspberrypi/defconfig
> +++ /dev/null
> @@
-1 +0,0 @@
> -# Dummy file to get through do_kernel_configme.
> diff
--git a/recipes-kernel/linux/linux.inc
b/recipes-kernel/linux/linux.inc
> index fae78b7..103512b 100644
> ---
a/recipes-kernel/linux/linux.inc
> +++
b/recipes-kernel/linux/linux.inc
> @@ -33,8 +33,7 @@
kernel_configure_variable() {
> }
> 
> do_configure_prepend() {
> - #
Clean .config
> - echo "" > ${B}/.config
> + mv -f ${B}/.config
${B}/.config.patched
> CONF_SED_SCRIPT=""
> 
> # oabi / eabi support
>
@@ -109,7 +108,8 @@ do_configure_prepend() {
> 
> # Keep this the last
line
> # Remove all modified configs and add the rest to .config
> - sed
-e "${CONF_SED_SCRIPT}" < '${WORKDIR}/defconfig' >> '${B}/.config'
> +
sed -e "${CONF_SED_SCRIPT}" < '${B}/.config.patched' >> '${B}/.config'
>
+ rm -f ${B}/.config.patched
> 
> yes '' | oe_runmake oldconfig
> }
> --

> 1.9.1

Nice, some small comments only. Please write a short summary
of the feature (kernel-yocto: allow in-tree defconfig) but keep the
bugzilla as a reference for further info. Always good to have some
background found directly in the commit msg itself. Have you tested it
using both poky:master and poky:fido? 

BR, Petter 

Petter
Mabäcker

Technux 
www.technux.se



Links:
--
[1]
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7474
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 2/2] linux-raspberrypi: build audio driver into kernel

[Petter Mabäcker]

 

2015-08-11 19:04 skrev Alex J Lennon: 

> Signed-off-by: Alex J
Lennon 
> ---
>
recipes-kernel/linux/linux-raspberrypi.inc | 4 
> 1 file changed, 4
insertions(+)
> 
> diff --git
a/recipes-kernel/linux/linux-raspberrypi.inc
b/recipes-kernel/linux/linux-raspberrypi.inc
> index e38d905..8024412
100644
> --- a/recipes-kernel/linux/linux-raspberrypi.inc
> +++
b/recipes-kernel/linux/linux-raspberrypi.inc
> @@ -6,6 +6,10 @@ SECTION
= "kernel"
> LICENSE = "GPLv2"
> LIC_FILES_CHKSUM =
"file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
> 
> +SRC_URI += "

> + file://build-in-audio.cfg [1] 
> + "
> +
> COMPATIBLE_MACHINE =
"raspberrypi"
> 
> PV = "${LINUX_VERSION}+git${SRCREV}"
> -- 
>
1.9.1

It seems like the file build-in-audio.cfg is missing from the
changeset? 

/Petter 

Petter Mabäcker

Technux

www.technux.se
 

Links:
--
[1]
file://build-in-audio.cfg
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 1/2] linux-raspberrypi: Update kernel to 3.18.16

[Petter Mabäcker]

 

2015-08-11 15:10 skrev Alex J Lennon: 

> On 11/08/2015 11:34,
Petter Mabäcker wrote: 
> 
>> 2015-08-11 11:03 skrev Alex Lennon: 
>>

>>> On Tuesday, August 11, 2015, Petter Mabäcker 
wrote:
>>> 
>>>> 2015-08-11 10:31 skrev Alex J Lennon: 
>>>> 
>>>>> On
11/08/2015 08:58, Petter Mabäcker wrote:
>>>>> 
>>>>>> 2015-08-10 13:08
skrev Alex J Lennon: 
>>>>>> 
>>>>>>> This requires some changes to
KERNEL_DEVICETREE as the dtb layout has changed to support overlays.
This change also makes us ready to support kernel 4.x series
Signed-off-by: Alex J Lennon mailto:ajlen...@dynamicdevices.co.uk>> ---
conf/machine/include/rpi-base.inc | 22 ++
recipes-kernel/linux/linux-raspberrypi_3.18.bb [1] | 9 +++-- 2 files
changed, 17 insertions(+), 14 deletions(-) diff --git
a/conf/machine/include/rpi-base.inc b/conf/machine/include/rpi-base.inc
index 1dda207..8caa5ba 100644 --- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc @@ -23,18 +23,16 @@
KERNEL_DEVICETREE ?= " bcm2708-rpi-b-plus.dtb bcm2709-rpi-2-b.dtb -
ds1307-rtc-overlay.dtb - hifiberry-amp-overlay.dtb -
hifiberry-dac-overlay.dtb - hifiberry-dacplus-overlay.dtb -
hifiberry-digi-overlay.dtb - iqaudio-dac-overlay.dtb -
iqaudio-dacplus-overlay.dtb - lirc-rpi-overlay.dtb -
pcf8523-rtc-overlay.dtb - pps-gpio-overlay.dtb - w1-gpio-overlay.dtb -
w1-gpio-pullup-overlay.dtb + overlays/hifiberry-amp-overlay.dtb +
overlays/hifiberry-dac-overlay.dtb +
overlays/hifiberry-dacplus-overlay.dtb +
overlays/hifiberry-digi-overlay.dtb + overlays/iqaudio-dac-overlay.dtb +
overlays/iqaudio-dacplus-overlay.dtb + overlays/lirc-rpi-overlay.dtb +
overlays/pps-gpio-overlay.dtb + overlays/w1-gpio-overlay.dtb +
overlays/w1-gpio-pullup-overlay.dtb " KERNEL_IMAGETYPE ?= "Image" diff
--git a/recipes-kernel/linux/linux-raspberrypi_3.18.bb [1]
b/recipes-kernel/linux/linux-raspberrypi_3.18.bb [1] index
6d8b155..18c2020 100644 ---
a/recipes-kernel/linux/linux-raspberrypi_3.18.bb [1] +++
b/recipes-kernel/linux/linux-raspberrypi_3.18.bb [1] @@ -1,6 +1,11 @@
-LINUX_VERSION ?= "3.18.11" +LINUX_VERSION ?= "3.18.16" -SRCREV =
"d64fa8121fca9883d6fb14ca06d2abf66496195e" +SRCREV =
"1bb18c8f721ef674a447f3622273f2e2de7a205c" SRC_URI = "git://
[2]github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.18.y [3]"
require linux-raspberrypi.inc + +# Create missing out of tree 'overlays'
directory prior to install step +do_compile_append() { + mkdir -p
${B}/arch/arm/boot/dts/overlays +} -- 1.9.1
>>>>>> Hi Alex, At least I
get problems during compile step with above change (I'm building for
rpi2). So are your sure '${B}/arch/arm/boot/dts/overlays' isn't needed
during compile? I tried with changing above from append to
> 
>>>>>>
prepand instead and then it worked fine for me (when building 3.18
kernel). (from log.do_compile, complete log can be found at:
http://www.technux.se/logs/log.do_compile.4398.fail [4] ) KSYM
.tmp_kallsyms1.o KSYM .tmp_kallsyms2.o LD vmlinux SORTEX vmlinux SYSMAP
System.map OBJCOPY arch/arm/boot/Image Kernel: arch/arm/boot/Image is
ready NOTE: make -j 4 bcm2708-rpi-b.dtb DTC
arch/arm/boot/dts/bcm2708-rpi-b.dtb NOTE: make -j 4
bcm2708-rpi-b-plus.dtb DTC arch/arm/boot/dts/bcm2708-rpi-b-plus.dtb
NOTE: make -j 4 bcm2709-rpi-2-b.dtb DTC
arch/arm/boot/dts/bcm2709-rpi-2-b.dtb NOTE: make -j 4
overlays/hifiberry-amp-overlay.dtb DTC
arch/arm/boot/dts/overlays/hifiberry-amp-overlay.dtb cc1: fatal error:
opening output file
arch/arm/boot/dts/overlays/.hifiberry-amp-overlay.dtb.dts.tmp: No such
file or directory compilation terminated. make[3]: ***
[arch/arm/boot/dts/overlays/hifiberry-amp-overlay.dtb] Error 1 make[2]:
*** [overlays/hifiberry-amp-overlay.dtb] Error 2 make[1]: *** [sub-make]
Error 2 make: *** [__sub-make] Error 2 ERROR: oe_runmake failed ERROR:
Function failed: do_compile (log file is located at
/home/epetmab/programming/yocto/alex_test_sstate/tmp/work/raspberrypi2-poky-linux-gnueabi/linux-raspberrypi/3.18.16+git1bb18c8f721ef674a447f3622273f2e2de7a205c-r0/temp/log.do_compile.4398)
BR, Petter
>>>>> 
>>>>> Hi Petter,
>>>>> 
>>>>> Thanks for testing that
out. That is indeed exactly what I was seeing
>>>>> before I added the
directory creation.
>>>>> 
>>>>> I did do the following test for both
3.18.x and 4.1.3 kernels (rpi2)
>>>>> 
>>>>> bitbake -f -c cleansstate
virtual/kernel
>>>>> bitbake -f virtual/kernel
>>>>> 
>>>>> I've just
re-run that again here and it works for me as-is. I thought
>>>>>
cleansstate was causing me to build from scratch so I'

Re: [yocto] [meta-raspberrypi][PATCH v2 1/2] linux-raspberrypi: Update kernel to 3.18.16

[Petter Mabäcker]

 

2015-08-11 14:30 skrev Alex J Lennon: 

> This requires some changes
to KERNEL_DEVICETREE as the dtb
> layout has changed to support
overlays. This change also
> makes us ready to support kernel 4.x
series
> 
> Signed-off-by: Alex J Lennon

> ---
>
conf/machine/include/rpi-base.inc | 22 ++
>
recipes-kernel/linux/linux-raspberrypi_3.18.bb | 9 +++--
> 2 files
changed, 17 insertions(+), 14 deletions(-)
> 
> diff --git
a/conf/machine/include/rpi-base.inc
b/conf/machine/include/rpi-base.inc
> index 1dda207..8caa5ba 100644
>
--- a/conf/machine/include/rpi-base.inc
> +++
b/conf/machine/include/rpi-base.inc
> @@ -23,18 +23,16 @@
KERNEL_DEVICETREE ?= " 
> bcm2708-rpi-b-plus.dtb 
> bcm2709-rpi-2-b.dtb

> 
> - ds1307-rtc-overlay.dtb 
> - hifiberry-amp-overlay.dtb 
> -
hifiberry-dac-overlay.dtb 
> - hifiberry-dacplus-overlay.dtb 
> -
hifiberry-digi-overlay.dtb 
> - iqaudio-dac-overlay.dtb 
> -
iqaudio-dacplus-overlay.dtb 
> - lirc-rpi-overlay.dtb 
> -
pcf8523-rtc-overlay.dtb 
> - pps-gpio-overlay.dtb 
> -
w1-gpio-overlay.dtb 
> - w1-gpio-pullup-overlay.dtb 
> +
overlays/hifiberry-amp-overlay.dtb 
> +
overlays/hifiberry-dac-overlay.dtb 
> +
overlays/hifiberry-dacplus-overlay.dtb 
> +
overlays/hifiberry-digi-overlay.dtb 
> +
overlays/iqaudio-dac-overlay.dtb 
> +
overlays/iqaudio-dacplus-overlay.dtb 
> + overlays/lirc-rpi-overlay.dtb

> + overlays/pps-gpio-overlay.dtb 
> + overlays/w1-gpio-overlay.dtb 
>
+ overlays/w1-gpio-pullup-overlay.dtb 
> "
> KERNEL_IMAGETYPE ?=
"Image"
> 
> diff --git a/recipes-kernel/linux/linux-raspberrypi_3.18.bb
b/recipes-kernel/linux/linux-raspberrypi_3.18.bb
> index
6d8b155..a1fe6b4 100644
> ---
a/recipes-kernel/linux/linux-raspberrypi_3.18.bb
> +++
b/recipes-kernel/linux/linux-raspberrypi_3.18.bb
> @@ -1,6 +1,11 @@
>
-LINUX_VERSION ?= "3.18.11"
> +LINUX_VERSION ?= "3.18.16"
> 
> -SRCREV =
"d64fa8121fca9883d6fb14ca06d2abf66496195e"
> +SRCREV =
"1bb18c8f721ef674a447f3622273f2e2de7a205c"
> SRC_URI =
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.18.y"
>

> require linux-raspberrypi.inc
> +
> +# Create missing out of tree
'overlays' directory prior to install step
> +do_compile_prepend() {
> +
mkdir -p ${B}/arch/arm/boot/dts/overlays
> +}
> -- 
> 1.9.1

One very
minor comment, update the comment ".. prior to install step" to
something like ".. prior to compile step instead" :) Perhaps Andrei can
fix that during merge, since at least I see no need for a v3 for
this :) 

BR Petter -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 1/2] linux-raspberrypi: Update kernel to 3.18.16

[Petter Mabäcker]

 

2015-08-11 11:03 skrev Alex Lennon: 

> On Tuesday, August 11, 2015,
Petter Mabäcker  wrote:
> 
>> 2015-08-11 10:31 skrev
Alex J Lennon: 
>> 
>>> On 11/08/2015 08:58, Petter Mabäcker wrote:
>>>

>>>> 2015-08-10 13:08 skrev Alex J Lennon: 
>>>> 
>>>>> This requires
some changes to KERNEL_DEVICETREE as the dtb layout has changed to
support overlays. This change also makes us ready to support kernel 4.x
series Signed-off-by: Alex J Lennon mailto:ajlen...@dynamicdevices.co.uk>> ---
conf/machine/include/rpi-base.inc | 22 ++
recipes-kernel/linux/linux-raspberrypi_3.18.bb [1] | 9 +++-- 2 files
changed, 17 insertions(+), 14 deletions(-) diff --git
a/conf/machine/include/rpi-base.inc b/conf/machine/include/rpi-base.inc
index 1dda207..8caa5ba 100644 --- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc @@ -23,18 +23,16 @@
KERNEL_DEVICETREE ?= " bcm2708-rpi-b-plus.dtb bcm2709-rpi-2-b.dtb -
ds1307-rtc-overlay.dtb - hifiberry-amp-overlay.dtb -
hifiberry-dac-overlay.dtb - hifiberry-dacplus-overlay.dtb -
hifiberry-digi-overlay.dtb - iqaudio-dac-overlay.dtb -
iqaudio-dacplus-overlay.dtb - lirc-rpi-overlay.dtb -
pcf8523-rtc-overlay.dtb - pps-gpio-overlay.dtb - w1-gpio-overlay.dtb -
w1-gpio-pullup-overlay.dtb + overlays/hifiberry-amp-overlay.dtb +
overlays/hifiberry-dac-overlay.dtb +
overlays/hifiberry-dacplus-overlay.dtb +
overlays/hifiberry-digi-overlay.dtb + overlays/iqaudio-dac-overlay.dtb +
overlays/iqaudio-dacplus-overlay.dtb + overlays/lirc-rpi-overlay.dtb +
overlays/pps-gpio-overlay.dtb + overlays/w1-gpio-overlay.dtb +
overlays/w1-gpio-pullup-overlay.dtb " KERNEL_IMAGETYPE ?= "Image" diff
--git a/recipes-kernel/linux/linux-raspberrypi_3.18.bb [1]
b/recipes-kernel/linux/linux-raspberrypi_3.18.bb [1] index
6d8b155..18c2020 100644 ---
a/recipes-kernel/linux/linux-raspberrypi_3.18.bb [1] +++
b/recipes-kernel/linux/linux-raspberrypi_3.18.bb [1] @@ -1,6 +1,11 @@
-LINUX_VERSION ?= "3.18.11" +LINUX_VERSION ?= "3.18.16" -SRCREV =
"d64fa8121fca9883d6fb14ca06d2abf66496195e" +SRCREV =
"1bb18c8f721ef674a447f3622273f2e2de7a205c" SRC_URI =
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.18.y
[2]" require linux-raspberrypi.inc + +# Create missing out of tree
'overlays' directory prior to install step +do_compile_append() { +
mkdir -p ${B}/arch/arm/boot/dts/overlays +} -- 1.9.1
>>>> Hi Alex, At
least I get problems during compile step with above change (I'm building
for rpi2). So are your sure '${B}/arch/arm/boot/dts/overlays' isn't
needed during compile? I tried with changing above from append to
prepand instead and then it worked fine for me (when building 3.18
kernel). (from log.do_compile, complete log can be found at:
http://www.technux.se/logs/log.do_compile.4398.fail [3] ) KSYM
.tmp_kallsyms1.o KSYM .tmp_kallsyms2.o LD vmlinux SORTEX vmlinux SYSMAP
System.map OBJCOPY arch/arm/boot/Image Kernel: arch/arm/boot/Image is
ready NOTE: make -j 4 bcm2708-rpi-b.dtb DTC
arch/arm/boot/dts/bcm2708-rpi-b.dtb NOTE: make -j 4
bcm2708-rpi-b-plus.dtb DTC arch/arm/boot/dts/bcm2708-rpi-b-plus.dtb
NOTE: make -j 4 bcm2709-rpi-2-b.dtb DTC
arch/arm/boot/dts/bcm2709-rpi-2-b.dtb NOTE: make -j 4
overlays/hifiberry-amp-overlay.dtb DTC
arch/arm/boot/dts/overlays/hifiberry-amp-overlay.dtb cc1: fatal error:
opening output file
arch/arm/boot/dts/overlays/.hifiberry-amp-overlay.dtb.dts.tmp: No such
file or directory compilation terminated. make[3]: ***
[arch/arm/boot/dts/overlays/hifiberry-amp-overlay.dtb] Error 1 make[2]:
*** [overlays/hifiberry-amp-overlay.dtb] Error 2 make[1]: *** [sub-make]
Error 2 make: *** [__sub-make] Error 2 ERROR: oe_runmake failed ERROR:
Function failed: do_compile (log file is located at
/home/epetmab/programming/yocto/alex_test_sstate/tmp/work/raspberrypi2-poky-linux-gnueabi/linux-raspberrypi/3.18.16+git1bb18c8f721ef674a447f3622273f2e2de7a205c-r0/temp/log.do_compile.4398)
BR, Petter
>>> 
>>> Hi Petter,
>>> 
>>> Thanks for testing that out.
That is indeed exactly what I was seeing
>>> before I added the
directory creation.
>>> 
>>> I did do the following test for both 3.18.x
and 4.1.3 kernels (rpi2)
>>> 
>>> bitbake -f -c cleansstate
virtual/kernel
>>> bitbake -f virtual/kernel
>>> 
>>> I've just re-run
that again here and it works for me as-is. I thought
>>> cleansstate was
causing me to build from scratch so I'm unclear as to
>>> why I'm not
seeing the problem...
>>> 
>>> NB. I'd also add that for preference I'd
like to see the kernel build
>>> Makefile patched with whatever is in
4.1 to create that needed overlays
>>> directory but I've had a look and
can't spot it.
>>

Re: [yocto] [meta-raspberrypi][PATCH 1/2] linux-raspberrypi: Update kernel to 3.18.16

[Petter Mabäcker]

 

2015-08-11 10:31 skrev Alex J Lennon: 

> On 11/08/2015 08:58,
Petter Mabäcker wrote:
> 
>> 2015-08-10 13:08 skrev Alex J Lennon: 
>>

>>> This requires some changes to KERNEL_DEVICETREE as the dtb layout
has changed to support overlays. This change also makes us ready to
support kernel 4.x series Signed-off-by: Alex J Lennon
mailto:ajlen...@dynamicdevices.co.uk>>
--- conf/machine/include/rpi-base.inc | 22 ++
recipes-kernel/linux/linux-raspberrypi_3.18.bb | 9 +++-- 2 files
changed, 17 insertions(+), 14 deletions(-) diff --git
a/conf/machine/include/rpi-base.inc b/conf/machine/include/rpi-base.inc
index 1dda207..8caa5ba 100644 --- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc @@ -23,18 +23,16 @@
KERNEL_DEVICETREE ?= " bcm2708-rpi-b-plus.dtb bcm2709-rpi-2-b.dtb -
ds1307-rtc-overlay.dtb - hifiberry-amp-overlay.dtb -
hifiberry-dac-overlay.dtb - hifiberry-dacplus-overlay.dtb -
hifiberry-digi-overlay.dtb - iqaudio-dac-overlay.dtb -
iqaudio-dacplus-overlay.dtb - lirc-rpi-overlay.dtb -
pcf8523-rtc-overlay.dtb - pps-gpio-overlay.dtb - w1-gpio-overlay.dtb -
w1-gpio-pullup-overlay.dtb + overlays/hifiberry-amp-overlay.dtb +
overlays/hifiberry-dac-overlay.dtb +
overlays/hifiberry-dacplus-overlay.dtb +
overlays/hifiberry-digi-overlay.dtb + overlays/iqaudio-dac-overlay.dtb +
overlays/iqaudio-dacplus-overlay.dtb + overlays/lirc-rpi-overlay.dtb +
overlays/pps-gpio-overlay.dtb + overlays/w1-gpio-overlay.dtb +
overlays/w1-gpio-pullup-overlay.dtb " KERNEL_IMAGETYPE ?= "Image" diff
--git a/recipes-kernel/linux/linux-raspberrypi_3.18.bb
b/recipes-kernel/linux/linux-raspberrypi_3.18.bb index 6d8b155..18c2020
100644 --- a/recipes-kernel/linux/linux-raspberrypi_3.18.bb +++
b/recipes-kernel/linux/linux-raspberrypi_3.18.bb @@ -1,6 +1,11 @@
-LINUX_VERSION ?= "3.18.11" +LINUX_VERSION ?= "3.18.16" -SRCREV =
"d64fa8121fca9883d6fb14ca06d2abf66496195e" +SRCREV =
"1bb18c8f721ef674a447f3622273f2e2de7a205c" SRC_URI =
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.18.y"
require linux-raspberrypi.inc + +# Create missing out of tree 'overlays'
directory prior to install step +do_compile_append() { + mkdir -p
${B}/arch/arm/boot/dts/overlays +} -- 1.9.1
>> Hi Alex, At least I get
problems during compile step with above change (I'm building for rpi2).
So are your sure '${B}/arch/arm/boot/dts/overlays' isn't needed during
compile? I tried with changing above from append to prepand instead and
then it worked fine for me (when building 3.18 kernel). (from
log.do_compile, complete log can be found at:
http://www.technux.se/logs/log.do_compile.4398.fail [1] ) KSYM
.tmp_kallsyms1.o KSYM .tmp_kallsyms2.o LD vmlinux SORTEX vmlinux SYSMAP
System.map OBJCOPY arch/arm/boot/Image Kernel: arch/arm/boot/Image is
ready NOTE: make -j 4 bcm2708-rpi-b.dtb DTC
arch/arm/boot/dts/bcm2708-rpi-b.dtb NOTE: make -j 4
bcm2708-rpi-b-plus.dtb DTC arch/arm/boot/dts/bcm2708-rpi-b-plus.dtb
NOTE: make -j 4 bcm2709-rpi-2-b.dtb DTC
arch/arm/boot/dts/bcm2709-rpi-2-b.dtb NOTE: make -j 4
overlays/hifiberry-amp-overlay.dtb DTC
arch/arm/boot/dts/overlays/hifiberry-amp-overlay.dtb cc1: fatal error:
opening output file
arch/arm/boot/dts/overlays/.hifiberry-amp-overlay.dtb.dts.tmp: No such
file or directory compilation terminated. make[3]: ***
[arch/arm/boot/dts/overlays/hifiberry-amp-overlay.dtb] Error 1 make[2]:
*** [overlays/hifiberry-amp-overlay.dtb] Error 2 make[1]: *** [sub-make]
Error 2 make: *** [__sub-make] Error 2 ERROR: oe_runmake failed ERROR:
Function failed: do_compile (log file is located at
/home/epetmab/programming/yocto/alex_test_sstate/tmp/work/raspberrypi2-poky-linux-gnueabi/linux-raspberrypi/3.18.16+git1bb18c8f721ef674a447f3622273f2e2de7a205c-r0/temp/log.do_compile.4398)
BR, Petter
> 
> Hi Petter,
> 
> Thanks for testing that out. That is
indeed exactly what I was seeing
> before I added the directory
creation.
> 
> I did do the following test for both 3.18.x and 4.1.3
kernels (rpi2)
> 
> bitbake -f -c cleansstate virtual/kernel
> bitbake
-f virtual/kernel
> 
> I've just re-run that again here and it works for
me as-is. I thought
> cleansstate was causing me to build from scratch
so I'm unclear as to
> why I'm not seeing the problem...
> 
> NB. I'd
also add that for preference I'd like to see the kernel build
> Makefile
patched with whatever is in 4.1 to create that needed overlays
>
directory but I've had a look and can't spot it.
> 
> Cheers,
> 
>
Alex

Hmm Ok, might be some "pebcak" from my side, since I was using an
old sstate, but according to my history I did 'cleanall' before I got
the problem. But will re-try this on a completely new build without any
old savings (it will take some time to test however..). What struck me
was 

Re: [yocto] [meta-raspberrypi][PATCH 1/2] linux-raspberrypi: Update kernel to 3.18.16

[Petter Mabäcker]

 

2015-08-10 13:08 skrev Alex J Lennon: 

> This requires some changes
to KERNEL_DEVICETREE as the dtb
> layout has changed to support
overlays. This change also
> makes us ready to support kernel 4.x
series
> 
> Signed-off-by: Alex J Lennon

> ---
>
conf/machine/include/rpi-base.inc | 22 ++
>
recipes-kernel/linux/linux-raspberrypi_3.18.bb | 9 +++--
> 2 files
changed, 17 insertions(+), 14 deletions(-)
> 
> diff --git
a/conf/machine/include/rpi-base.inc
b/conf/machine/include/rpi-base.inc
> index 1dda207..8caa5ba 100644
>
--- a/conf/machine/include/rpi-base.inc
> +++
b/conf/machine/include/rpi-base.inc
> @@ -23,18 +23,16 @@
KERNEL_DEVICETREE ?= " 
> bcm2708-rpi-b-plus.dtb 
> bcm2709-rpi-2-b.dtb

> 
> - ds1307-rtc-overlay.dtb 
> - hifiberry-amp-overlay.dtb 
> -
hifiberry-dac-overlay.dtb 
> - hifiberry-dacplus-overlay.dtb 
> -
hifiberry-digi-overlay.dtb 
> - iqaudio-dac-overlay.dtb 
> -
iqaudio-dacplus-overlay.dtb 
> - lirc-rpi-overlay.dtb 
> -
pcf8523-rtc-overlay.dtb 
> - pps-gpio-overlay.dtb 
> -
w1-gpio-overlay.dtb 
> - w1-gpio-pullup-overlay.dtb 
> +
overlays/hifiberry-amp-overlay.dtb 
> +
overlays/hifiberry-dac-overlay.dtb 
> +
overlays/hifiberry-dacplus-overlay.dtb 
> +
overlays/hifiberry-digi-overlay.dtb 
> +
overlays/iqaudio-dac-overlay.dtb 
> +
overlays/iqaudio-dacplus-overlay.dtb 
> + overlays/lirc-rpi-overlay.dtb

> + overlays/pps-gpio-overlay.dtb 
> + overlays/w1-gpio-overlay.dtb 
>
+ overlays/w1-gpio-pullup-overlay.dtb 
> "
> KERNEL_IMAGETYPE ?=
"Image"
> 
> diff --git a/recipes-kernel/linux/linux-raspberrypi_3.18.bb
b/recipes-kernel/linux/linux-raspberrypi_3.18.bb
> index
6d8b155..18c2020 100644
> ---
a/recipes-kernel/linux/linux-raspberrypi_3.18.bb
> +++
b/recipes-kernel/linux/linux-raspberrypi_3.18.bb
> @@ -1,6 +1,11 @@
>
-LINUX_VERSION ?= "3.18.11"
> +LINUX_VERSION ?= "3.18.16"
> 
> -SRCREV =
"d64fa8121fca9883d6fb14ca06d2abf66496195e"
> +SRCREV =
"1bb18c8f721ef674a447f3622273f2e2de7a205c"
> SRC_URI =
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.18.y"
>

> require linux-raspberrypi.inc
> +
> +# Create missing out of tree
'overlays' directory prior to install step
> +do_compile_append() {
> +
mkdir -p ${B}/arch/arm/boot/dts/overlays
> +}
> -- 
> 1.9.1

Hi Alex,


At least I get problems during compile step with above change (I'm
building for rpi2). So are your sure '${B}/arch/arm/boot/dts/overlays'
isn't needed during compile? I tried with changing above from append to
prepand instead and then it worked fine for me (when building 3.18
kernel). 

(from log.do_compile, complete log can be found at:
http://www.technux.se/logs/log.do_compile.4398.fail ) 

 KSYM
.tmp_kallsyms1.o
 KSYM .tmp_kallsyms2.o
 LD vmlinux
 SORTEX vmlinux

SYSMAP System.map
 OBJCOPY arch/arm/boot/Image
 Kernel:
arch/arm/boot/Image is ready
NOTE: make -j 4 bcm2708-rpi-b.dtb
 DTC
arch/arm/boot/dts/bcm2708-rpi-b.dtb
NOTE: make -j 4
bcm2708-rpi-b-plus.dtb
 DTC
arch/arm/boot/dts/bcm2708-rpi-b-plus.dtb
NOTE: make -j 4
bcm2709-rpi-2-b.dtb
 DTC arch/arm/boot/dts/bcm2709-rpi-2-b.dtb
NOTE:
make -j 4 overlays/hifiberry-amp-overlay.dtb
 DTC
arch/arm/boot/dts/overlays/hifiberry-amp-overlay.dtb
cc1: fatal error:
opening output file
arch/arm/boot/dts/overlays/.hifiberry-amp-overlay.dtb.dts.tmp: No such
file or directory
compilation terminated.
make[3]: ***
[arch/arm/boot/dts/overlays/hifiberry-amp-overlay.dtb] Error 1
make[2]:
*** [overlays/hifiberry-amp-overlay.dtb] Error 2
make[1]: *** [sub-make]
Error 2
make: *** [__sub-make] Error 2
ERROR: oe_runmake failed
ERROR:
Function failed: do_compile (log file is located at
/home/epetmab/programming/yocto/alex_test_sstate/tmp/work/raspberrypi2-poky-linux-gnueabi/linux-raspberrypi/3.18.16+git1bb18c8f721ef674a447f3622273f2e2de7a205c-r0/temp/log.do_compile.4398)

BR,
Petter -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 0/5] Add support for 4.1 kernel with vc4 DRM/KMS driver

[Petter Mabäcker]

 

2015-08-04 18:07 skrev Javier Martinez Canillas: 

> Hello Petter,
>

> Thanks a lot for your feedback.
> 
> On 08/04/2015 11:16 AM, Petter
Mabäcker wrote:
> 
>> On 07/30/2015 10:34 AM, Javier Martinez Canillas
wrote: 
>> 
>>> Hello Andrei, This series adds support for Eric Anholt's
v4.1 kernel, that has support for the vc4 DRM/KMS driver. Which is the
new open source graphics driver stack for the Raspberry Pi to be used
instead of the userland driver. We are using it in the Tizen port to
RPI2 [0] and are trying to push all the patches back to the tizen-distro
and meta-raspberrypi OE layers so I'm posting these patches to get your
feedback. The v4.1 kernel is under heavy development so is a
work-in-progress and should not be used in production. That's why a
default preference of -1 is set and the kernel only is enabled if the
"vc4-gfx" feature is added to the DISTRO_FEATURES variable. But even
when it's still a development kernel, having the recipe in the
meta-raspberrypi will allow people to test it. The patches are for:
Patch 1/5 makes optional to add the kgdboc kernel command line parameter
Patch 2/5 allows to set the mask_gpu_interrupt0 option in config.txt
Patch 3/5 changes the partition layout to add more space for boot files
Patch 4/5 adds a recipe for the 4.1 and some patches to make it stable
Patch 5/5 switchs the default providers according to the gfx stack used
One problem I found is that the latest RPI kernels changed the path for
the DT overlays after commit 739c586c8757 ("BCM270X_DT: Move the
overlays into a subdirectory, adding the README") [1] so the kernel
fails to build with the default KERNEL_DEVICETREE. I tried to change
get_dts() function logic to take this into account but found that it
would had been a more intrusive change and KERNEL_DEVICETREE will have
to be changed anyways once the recipes for the other kernels are updated
to the latest HEAD so for now I just define the following on local.conf
to make it build:
>> As long as we bump SRCREV for 3.18 kernel as well,
I see no problem. Since then the KERNEL_DEVICETREE default value can
look the same in all situations (both 3.18 and 4.x can handle the new
structure and we get no compatibility issues) and for older kernels
(3.12 and 3.14) it doesn't matter since they don't have native device
tree support and will turn device tree support off by default.
> 
> Yes,
that's what I meant when I said that the problem will be solved once
>
all the recipes for DT enabled kernels are updated to the latest
branch
> HEAD. But I didn't want to do that in this series since I
wanted the
> changes to be as less intrusive as possible.

Ok, sounds
reasonable. Alex found some problems when bumping 3.18 to latest but
when that is solved he can push the 3.18 bumping and prepare the
KERNEL_DEVICETREE variable with the new subdir for overlays. 

>>
KERNEL_DEVICETREE = " bcm2708-rpi-b.dtb bcm2708-rpi-b-plus.dtb
bcm2709-rpi-2-b.dtb overlays/hifiberry-amp-overlay.dtb
overlays/hifiberry-dac-overlay.dtb
overlays/hifiberry-dacplus-overlay.dtb
overlays/hifiberry-digi-overlay.dtb overlays/iqaudio-dac-overlay.dtb
overlays/iqaudio-dacplus-overlay.dtb overlays/lirc-rpi-overlay.dtb
overlays/pps-gpio-overlay.dtb overlays/w1-gpio-overlay.dtb
overlays/w1-gpio-pullup-overlay.dtb " [0]:
http://blogs.s-osg.org/tizen-rpi2-now-supporting-3d-acceleration/ [1]
[1]: https://github.com/raspberrypi/linux/commit/739c586c8757 [2] Best
regards, --- Javier Martinez Canillas Open Source Group Samsung Research
America Derek Foreman (4): rpi-config: Allow to mask GPU irqs
sdcard_image-rpi.bbclass: Allocate more space for boot partition
linux-raspberrypi: Add a 4.1 linux kernel with vc4 support
rpi-default-providers: Switch providers according to used gfx stack
Mauro Carvalho Chehab (1): linux-raspberrypi.inc: Make kgdboc kernel
param optional README | 38 +-- classes/sdcard_image-rpi.bbclass | 6
+- conf/machine/include/rpi-default-providers.inc | 8 +-
conf/machine/include/rpi-default-versions.inc | 2 +-
recipes-bsp/bootfiles/rpi-config_git.bb | 6 ++
recipes-kernel/linux/linux-raspberrypi.inc | 5 +-
..._defconfig-Enable-config-options-for-vc4-.patch | 48 +
...-ARM-dts-Fix-i2c-for-bcm2709-RPI2-B-board.patch | 85 +++
.../0003-drm-vc4-Use-the-fbdev_cma-helpers.patch | 115
+ .../0004-drm-vc4-Allow-vblank-to-be-disabled.patch
| 26 + .../0005-drm-vc4-Disable-KMS-operations.patch | 95
+ recipes-kernel/linux/linux-raspberrypi_4.1.bb | 16 +++
12 files changed, 433 insertions(+), 17 deletions(-) create mode 100644
recipes-kernel/linux/linux-raspberrypi/0001-ARM-bcm2709_defconfig-Enable-config-options-for-vc4-.patch
create mode 100644
recipes-kernel/linux/linux-raspberrypi/0002-ARM-dts-Fix-i2c-for-bcm2709-RPI2-B-board.patch
create mode 100644
recipes-kernel/linux/linux-raspberrypi/0003-drm-vc4-Use-the

Re: [yocto] [meta-raspberrypi][PATCH 0/5] Add support for 4.1 kernel with vc4 DRM/KMS driver

[Petter Mabäcker]

On 07/30/2015 10:34 AM, Javier Martinez Canillas wrote:

Hello Andrei,

This series adds support for Eric Anholt's v4.1 kernel, that has support
for the vc4 DRM/KMS driver. Which is the new open source graphics driver
stack for the Raspberry Pi to be used instead of the userland driver.

We are using it in the Tizen port to RPI2 [0] and are trying to push all
the patches back to the tizen-distro and meta-raspberrypi OE layers so
I'm posting these patches to get your feedback.

The v4.1 kernel is under heavy development so is a work-in-progress and
should not be used in production. That's why a default preference of -1
is set and the kernel only is enabled if the "vc4-gfx" feature is added
to the DISTRO_FEATURES variable.

But even when it's still a development kernel, having the recipe in the
meta-raspberrypi will allow people to test it. The patches are for:

Patch 1/5 makes optional to add the kgdboc kernel command line parameter

Patch 2/5 allows to set the mask_gpu_interrupt0 option in config.txt

Patch 3/5 changes the partition layout to add more space for boot files

Patch 4/5 adds a recipe for the 4.1 and some patches to make it stable

Patch 5/5 switchs the default providers according to the gfx stack used

One problem I found is that the latest RPI kernels changed the path for
the DT overlays after commit 739c586c8757 ("BCM270X_DT: Move the overlays
into a subdirectory, adding the README") [1] so the kernel fails to build
with the default KERNEL_DEVICETREE. I tried to change get_dts() function
logic to take this into account but found that it would had been a more
intrusive change and KERNEL_DEVICETREE will have to be changed anyways
once the recipes for the other kernels are updated to the latest HEAD so
for now I just define the following on local.conf to make it build:
As long as we bump SRCREV for 3.18 kernel as well, I see no problem. 
Since then the KERNEL_DEVICETREE default value can look the same in all 
situations (both 3.18 and 4.x can handle the new structure and we get no 
compatibility issues) and for older kernels (3.12 and 3.14) it doesn't 
matter since they don't have native device tree support and will turn 
device tree support off by default.




KERNEL_DEVICETREE = " \
 bcm2708-rpi-b.dtb \
 bcm2708-rpi-b-plus.dtb \
 bcm2709-rpi-2-b.dtb \
 \
 overlays/hifiberry-amp-overlay.dtb \
 overlays/hifiberry-dac-overlay.dtb \
 overlays/hifiberry-dacplus-overlay.dtb \
 overlays/hifiberry-digi-overlay.dtb \
 overlays/iqaudio-dac-overlay.dtb \
 overlays/iqaudio-dacplus-overlay.dtb \
 overlays/lirc-rpi-overlay.dtb \
 overlays/pps-gpio-overlay.dtb \
 overlays/w1-gpio-overlay.dtb \
 overlays/w1-gpio-pullup-overlay.dtb \
 "

[0]: http://blogs.s-osg.org/tizen-rpi2-now-supporting-3d-acceleration/
[1]: https://github.com/raspberrypi/linux/commit/739c586c8757

Best regards,
---
Javier Martinez Canillas
Open Source Group
Samsung Research America


Derek Foreman (4):
   rpi-config: Allow to mask GPU irqs
   sdcard_image-rpi.bbclass: Allocate more space for boot partition
   linux-raspberrypi: Add a 4.1 linux kernel with vc4 support
   rpi-default-providers: Switch providers according to used gfx stack

Mauro Carvalho Chehab (1):
   linux-raspberrypi.inc: Make kgdboc kernel param optional

  README |  38 +--
  classes/sdcard_image-rpi.bbclass   |   6 +-
  conf/machine/include/rpi-default-providers.inc |   8 +-
  conf/machine/include/rpi-default-versions.inc  |   2 +-
  recipes-bsp/bootfiles/rpi-config_git.bb|   6 ++
  recipes-kernel/linux/linux-raspberrypi.inc |   5 +-
  ..._defconfig-Enable-config-options-for-vc4-.patch |  48 +
  ...-ARM-dts-Fix-i2c-for-bcm2709-RPI2-B-board.patch |  85 +++
  .../0003-drm-vc4-Use-the-fbdev_cma-helpers.patch   | 115 +
  .../0004-drm-vc4-Allow-vblank-to-be-disabled.patch |  26 +
  .../0005-drm-vc4-Disable-KMS-operations.patch  |  95 +
  recipes-kernel/linux/linux-raspberrypi_4.1.bb  |  16 +++
  12 files changed, 433 insertions(+), 17 deletions(-)
  create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-ARM-bcm2709_defconfig-Enable-config-options-for-vc4-.patch
  create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0002-ARM-dts-Fix-i2c-for-bcm2709-RPI2-B-board.patch
  create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0003-drm-vc4-Use-the-fbdev_cma-helpers.patch
  create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0004-drm-vc4-Allow-vblank-to-be-disabled.patch
  create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0005-drm-vc4-Disable-KMS-operations.patch
  create mode 100644 recipes-kernel/linux/linux-raspberrypi_4.1.bb



Nice and interesting changes, but you really should sync this with Alex 
Lennon as well since he currently are working with integrating 4.1 into 
meta-raspberrypi. An other opinion is that you should

Re: [yocto] [meta-raspberrypi] Adding an additional device tree overlay in the SDCard

[Petter Mabäcker]

Hi,

BR,
Petter

On 08/01/2015 03:22 AM, Herve Jourdain wrote:


Hi Petter,

Thanks for your answers.

At some point, I’ve set it in the disto.conf – it works there – but 
for maintenance reasons I’d love to be able to keep it “localized” 
with the kernel .bbappend – since it clearly depends on the kernel.


For now, I’ve just patched the sdcard_image-rpi.bbclass, to take the 
existing ${KERNEL_IMAGE}*.dtb in the ${DEPLOY_DIR_DIRECTORY}, split 
them in overlay and non-overlay, and then do the processing like it’s 
done now.


It does work in my case, and I can provide the patch if it’s deemed of 
interest. But I’m not sure whether or not there can be some side 
effects – looks like rather safe, but more opinions are definitely 
needed on that.


Feel free to either send a RFC patch to the mailinglist or start by 
sending it for early feedback to me, Andrei and Alex.


Regarding the kernel, yes I’m using the 3.18 that is supported by the 
meta-raspberry layer. As I mentioned in another thread, with more 
recent kernels, the RaspberryPi overlay layers were added in a 
separate directory, so in addition to a patch to build the newer 
kernel, the sdcard_image-rpi.bbclass will also have to be modified to 
get the files in the proper directory, when we switch to those newer 
kernels.


I remember that thread. We are currently working with integrating 4.x 
into meta-raspberrypi you can follow Alex work at 
http://redmine.gherzan.com/issues/62. One problem is however how to 
handle support for both 3.x and 4.x with the current KERNEL_DEVICETREE 
solution in combination with the changed overlay directories.


Best regards,

Herve

*From:*Petter Mabäcker [mailto:pet...@technux.se]
*Sent:* vendredi 31 juillet 2015 15:29
*To:* Herve Jourdain ; 
franc...@concept-embarque.fr; Andrei Gherzan 

*Cc:* yocto@yoctoproject.org
*Subject:* Re: [yocto] [meta-raspberrypi] Adding an additional device 
tree overlay in the SDCard


Hi Herve,

See inline answers.

BR,
Petter

On 07/30/2015 05:27 AM, Herve Jourdain wrote:

Hello,

I’m trying to add a specific .dts file to the raspberrypi.

Therefore, in my own layer, I have made a
linux-raspberrypi_3.%.bbappend, that applies a patch to the
arch/arm/boot/dts makefile to add my own layer, and a new rule
that copies my specific .dts file to the kernel source directory.

And, initially, I had also defined KERNEL_DEVICETREE +=
“myown-overlay.dtb” in there.

It definitely compiles well, installation process is smooth, I get
the Image-myown-overlay.dtb in tmp/deploy/raspberrypi2.

BUT when I flash my SDCard, it does NOT appear in the “overlays”
directory of the DOS partition!

If I add it manually, everything works fine, so I know my overlay
has been correctly generated and is working.

What I discovered is that, the sdcard_image_rpi class takes the
list of .dtb to be considered from split_overlays(), which is
defined in linux-raspberrypi-base class.

And split_overlays() basically  gets the value of
KERNEL_DEVICETREE (dts = d.getVar("KERNEL_DEVICETREE", True)).

But when I set KERNEL_DEVICETREE in
linux-raspberrypi_3.%.bbappend, it seems the additional value it
defines is NOT taken into account when linux-raspberry-class
evaluates the value of KERNEL_DEVICETREE.

I’ve checked in the create_image.rpi-sdimg script created, it does
not appear in DTS nor DT_OVERLAYS.

But when I define KERNEL_DEVICETREE in my distro.conf, THEN it is
taken into account…

My goal would be to add that overlay by NOT modifying distro.conf
(distros are not necessarily RaspberryPi centric) nor in the
raspberry machine files (or local.conf).

This leads me to several questions:

#1 Is there a specific reason why my addition to KERNEL_DEVICETREE
gets lost when creating the image? I mean, is it normal, or are
there some steps I missed there?

Yes, in the current solution KERNEL_DEVICETREE is needed in both the 
kernel recipe and image creation context. When appending 
KERNEL_DEVICETREE in linux-raspberrypi_3.%.bbappend your new overlay 
will only be visible within the linux-raspberrypi scope and NOT within 
the image class.



#2 Is there a way that I could achieve adding my .dtb overlay in
the sdcard image only from my linux kernel bbappend?


If I remember the code correct within the kernel scope we are only 
interesting if device tree should be used. At least in theory 
(assuming you are using a >= 3.18 kernel since then KERNEL_DEVICETREE 
will bve set by default) you should be able to skip the 
KERNEL_DEVICETREE += code in linux-raspberrypi_3.%.bbappend (since it 
will be set any way and the overlays themselves isn't really used in 
here..) then append the KERNEL_DEVICETREE within the image scope. If 
you don't want to put this into the layer.conf or similiar in your own 
layer I guess it should work to "prepend" for example the 
IMAGE_

Re: [yocto] [meta-raspberrypi] Adding an additional device tree overlay in the SDCard

[Petter Mabäcker]

Hi Herve,

See inline answers.

BR,
Petter

On 07/30/2015 05:27 AM, Herve Jourdain wrote:


Hello,

I’m trying to add a specific .dts file to the raspberrypi.

Therefore, in my own layer, I have made a 
linux-raspberrypi_3.%.bbappend, that applies a patch to the 
arch/arm/boot/dts makefile to add my own layer, and a new rule that 
copies my specific .dts file to the kernel source directory.


And, initially, I had also defined KERNEL_DEVICETREE += 
“myown-overlay.dtb” in there.


It definitely compiles well, installation process is smooth, I get the 
Image-myown-overlay.dtb in tmp/deploy/raspberrypi2.


BUT when I flash my SDCard, it does NOT appear in the “overlays” 
directory of the DOS partition!


If I add it manually, everything works fine, so I know my overlay has 
been correctly generated and is working.


What I discovered is that, the sdcard_image_rpi class takes the list 
of .dtb to be considered from split_overlays(), which is defined in 
linux-raspberrypi-base class.


And split_overlays() basically  gets the value of KERNEL_DEVICETREE 
(dts = d.getVar("KERNEL_DEVICETREE", True)).


But when I set KERNEL_DEVICETREE in linux-raspberrypi_3.%.bbappend, it 
seems the additional value it defines is NOT taken into account when 
linux-raspberry-class evaluates the value of KERNEL_DEVICETREE.


I’ve checked in the create_image.rpi-sdimg script created, it does not 
appear in DTS nor DT_OVERLAYS.


But when I define KERNEL_DEVICETREE in my distro.conf, THEN it is 
taken into account…


My goal would be to add that overlay by NOT modifying distro.conf 
(distros are not necessarily RaspberryPi centric) nor in the raspberry 
machine files (or local.conf).


This leads me to several questions:

#1 Is there a specific reason why my addition to KERNEL_DEVICETREE 
gets lost when creating the image? I mean, is it normal, or are there 
some steps I missed there?


Yes, in the current solution KERNEL_DEVICETREE is needed in both the 
kernel recipe and image creation context. When appending 
KERNEL_DEVICETREE in linux-raspberrypi_3.%.bbappend your new overlay 
will only be visible within the linux-raspberrypi scope and NOT within 
the image class.


#2 Is there a way that I could achieve adding my .dtb overlay in the 
sdcard image only from my linux kernel bbappend?




If I remember the code correct within the kernel scope we are only 
interesting if device tree should be used. At least in theory (assuming 
you are using a >= 3.18 kernel since then KERNEL_DEVICETREE will bve set 
by default) you should be able to skip the KERNEL_DEVICETREE += code in 
linux-raspberrypi_3.%.bbappend (since it will be set any way and the 
overlays themselves isn't really used in here..) then append the 
KERNEL_DEVICETREE within the image scope. If you don't want to put this 
into the layer.conf or similiar in your own layer I guess it should work 
to "prepend" for example the IMAGE_CMD. But in the current solution I 
guess local.conf, layer.conf (in your own layer) or rpi-base.inc (in 
meta-raspberrypi) is the easiest options..


#3 On a more general note, wouldn’t it be simpler (better?) to just 
add all the .dtb that are found in the deploy/images/ directory to the 
DOS partition of the SDCard? After all, the .dtb need to be compiled 
from a .dts, so all the .dtb that appear in deploy/images are “legit”.




That might perhaps be a better solution. Have you tried it out? Andrei 
or Francois might have some comments about this?


Herve





-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 0/1] packagegroup-rpi-test: Add pi-blaster

[Petter Mabäcker]

The following changes since commit 7457bf182c8fd550ec877ecd786a3edd16e65495:

  wiringpi: Bump SRCREV (2015-07-19 14:53:27 +0200)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib petmab/rpi_minor_fix
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=petmab/rpi_minor_fix

Petter Mabäcker (1):
  packagegroup-rpi-test: Add pi-blaster

 recipes-core/packagegroups/packagegroup-rpi-test.bb | 1 +
 1 file changed, 1 insertion(+)

-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 1/1] packagegroup-rpi-test: Add pi-blaster

[Petter Mabäcker]

Ensure that pi-blaster is built and included by default when building
'rpi-test-image'.

Signed-off-by: Petter Mabäcker 
---
 recipes-core/packagegroups/packagegroup-rpi-test.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/recipes-core/packagegroups/packagegroup-rpi-test.bb 
b/recipes-core/packagegroups/packagegroup-rpi-test.bb
index e16e79e..d8d311f 100644
--- a/recipes-core/packagegroups/packagegroup-rpi-test.bb
+++ b/recipes-core/packagegroups/packagegroup-rpi-test.bb
@@ -10,6 +10,7 @@ RDEPENDS_${PN} = "\
 wiringpi \
 rpio \
 rpi-gpio \
+pi-blaster \
 "
 
 RRECOMMENDS_${PN} = "\
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 2/2] wiringpi: Bump SRCREV

[Petter Mabäcker]

Update wiringpi to latest revision. Due to a refactoring of the build
procedure in wiringpi the integration patch 'makefile-install.patch'
didn't apply anymore. While migrating that patch it was simplified and
generated using 'git format-patch' instead, to make it easier to maintain
the patch in the future.

[Support #60]

Signed-off-by: Petter Mabäcker 
---
 .../0001-Add-initial-cross-compile-support.patch   | 429 +
 .../wiringPi/files/Makefiles-install.patch | 202 --
 recipes-devtools/wiringPi/wiringpi_git.bb  |  10 +-
 3 files changed, 435 insertions(+), 206 deletions(-)
 create mode 100644 
recipes-devtools/wiringPi/files/0001-Add-initial-cross-compile-support.patch
 delete mode 100644 recipes-devtools/wiringPi/files/Makefiles-install.patch

diff --git 
a/recipes-devtools/wiringPi/files/0001-Add-initial-cross-compile-support.patch 
b/recipes-devtools/wiringPi/files/0001-Add-initial-cross-compile-support.patch
new file mode 100644
index 000..c5ba270
--- /dev/null
+++ 
b/recipes-devtools/wiringPi/files/0001-Add-initial-cross-compile-support.patch
@@ -0,0 +1,429 @@
+From b0d82bc7cc90db41aa4f7012bbe3009f0b8ab11d Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petter=20Mab=C3=A4cker?= 
+Date: Sat, 18 Jul 2015 23:20:05 +0200
+Subject: [PATCH] Add initial cross compile support
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Upstream-Status: Pending
+
+Signed-off-by: Petter Mabäcker 
+---
+ devLib/Makefile | 58 +
+ examples/Gertboard/Makefile | 22 ++---
+ examples/Makefile   | 19 +--
+ examples/PiFace/Makefile| 22 ++---
+ examples/PiGlow/Makefile|  4 ++--
+ examples/q2w/Makefile   |  5 ++--
+ gpio/Makefile   | 31 +---
+ wiringPi/Makefile   | 56 ---
+ 8 files changed, 124 insertions(+), 93 deletions(-)
+
+diff --git a/devLib/Makefile b/devLib/Makefile
+index d62b532..c7c7884 100644
+--- a/devLib/Makefile
 b/devLib/Makefile
+@@ -22,18 +22,22 @@
+ 
#
+ 
+ VERSION=$(shell cat ../VERSION)
+-DESTDIR=/usr
+-PREFIX=/local
++DESTDIR?=/usr
++PREFIX?=/local
+ 
+-STATIC=libwiringPiDev.a
+-DYNAMIC=libwiringPiDev.so.$(VERSION)
++INCLUDE_DIR?=$(DESTDIR)$(PREFIX)/include
++LIB_DIR?=$(DESTDIR)$(PREFIX)/lib
+ 
+-#DEBUG= -g -O0
+-DEBUG = -O2
+-CC= gcc
+-INCLUDE   = -I.
+-DEFS  = -D_GNU_SOURCE
+-CFLAGS= $(DEBUG) $(DEFS) -Wformat=2 -Wall -Winline $(INCLUDE) -pipe 
-fPIC
++BASE_NAME=libwiringPiDev
++STATIC=$(BASE_NAME).a
++DYNAMIC=$(BASE_NAME).so.$(VERSION)
++
++#DEBUG?= -g -O0
++DEBUG ?= -O2
++CC?= gcc
++INCLUDE   ?= -I.
++DEFS  ?= -D_GNU_SOURCE
++CFLAGS?= $(DEBUG) $(DEFS) -Wformat=2 -Wall -Winline $(INCLUDE) -pipe 
-fPIC
+ 
+ LIBS=
+ 
+@@ -60,16 +64,16 @@ $(STATIC): $(OBJ)
+ 
+ $(DYNAMIC):   $(OBJ)
+   @echo "[Link (Dynamic)]"
+-  @$(CC) -shared -Wl,-soname,libwiringPiDev.so -o 
libwiringPiDev.so.$(VERSION) -lpthread $(OBJ)
++  @$(CC) -shared -Wl,-soname,$(BASE_NAME).so.$(DYN_VERS_MAJ) -o 
$(BASE_NAME).so -lpthread $(OBJ)
+ 
+ .c.o:
+   @echo [Compile] $<
+-  @$(CC) -c $(CFLAGS) $< -o $@
++  @$(CC) -c $(CFLAGS) -fPIC $< -o $@
+ 
+ .PHONY:   clean
+ clean:
+   @echo "[Clean]"
+-  @rm -f $(OBJ) $(OBJ_I2C) *~ core tags Makefile.bak libwiringPiDev.*
++  @rm -f $(OBJ) $(OBJ_I2C) *~ core tags Makefile.bak $(BASE_NAME).so* 
$(BASE_NAME).a
+ 
+ .PHONY:   tags
+ tags: $(SRC)
+@@ -80,22 +84,22 @@ tags:  $(SRC)
+ .PHONY:   install
+ install:  $(DYNAMIC)
+   @echo "[Install Headers]"
+-  @install -m 0755 -d 
$(DESTDIR)$(PREFIX)/include
+-  @install -m 0644 $(HEADERS) 
$(DESTDIR)$(PREFIX)/include
++  @install -m 0755 -d 
$(INCLUDE_DIR)
++  @install -m 0644 $(HEADERS) 
$(INCLUDE_DIR)
+   @echo "[Install Dynamic Lib]"
+-  @install -m 0755 -d 
$(DESTDIR)$(PREFIX)/lib
+-  @install -m 0755 libwiringPiDev.so.$(VERSION)   
$(DESTDIR)$(PREFIX)/lib/libwiringPiDev.so.$(VERSION)
+-  @ln -sf $(DESTDIR)$(PREFIX)/lib/libwiringPiDev.so.$(VERSION)
$(DESTDIR)/lib/libwiringPiDev.so
+-  @ldconfig
++  @install -m 0755 -d 
$(LIB_DIR)
++  @install -m 0755 $(BASE_NAME).so$(LIB_DIR)/$(DYNAMIC)
++  @ln -sf $(DYNAMIC)  $(LIB_DIR)/$(BASE_NAME).so
++  @ln -sf $(DYNAMIC)  
$(LIB_DIR)/$(BASE_NAME).so.$(DYN_VERS_MAJ)
+ 
+ .PHONY:   install-static
+ install-static: 

[yocto] [meta-raspberrypi][PATCH 1/2] omxplayer: Bump SRCREV

[Petter Mabäcker]

[Support #60]

Signed-off-by: Petter Mabäcker 
---
 recipes-multimedia/omxplayer/omxplayer_git.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-multimedia/omxplayer/omxplayer_git.bb 
b/recipes-multimedia/omxplayer/omxplayer_git.bb
index c71a743..f4839a9 100644
--- a/recipes-multimedia/omxplayer/omxplayer_git.bb
+++ b/recipes-multimedia/omxplayer/omxplayer_git.bb
@@ -8,9 +8,9 @@ LICENSE = "GPLv2"
 LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
 
 DEPENDS = "libpcre libav virtual/egl boost freetype dbus openssl samba libssh"
-PR = "r3"
+PR = "r4"
 
-SRCREV = "18f051d64d9c837edbf718bc4935204583cfa030"
+SRCREV = "4d8ffd13153bfef2966671cb4fb484afeaf792a8"
 SRC_URI = 
"git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master \
file://0001-Remove-Makefile.include-which-includes-hardcoded.patch \

file://0002-Libraries-and-headers-from-ffmpeg-are-installed-in-u.patch \
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 0/2] More package updates

[Petter Mabäcker]

The following changes since commit c8532df1c2e4812b3520d32ed49be943bea2edd9:

  If SERIAL_CONSOLE is already define by another layer, this value may not be 
good. (2015-06-05 16:38:14 +0200)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib petmab/rpi_redmine_60_more_updates
  
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=petmab/rpi_redmine_60_more_updates

Petter Mabäcker (2):
  omxplayer: Bump SRCREV
  wiringpi: Bump SRCREV

 .../0001-Add-initial-cross-compile-support.patch   | 429 +
 .../wiringPi/files/Makefiles-install.patch | 202 --
 recipes-devtools/wiringPi/wiringpi_git.bb  |  10 +-
 recipes-multimedia/omxplayer/omxplayer_git.bb  |   4 +-
 4 files changed, 437 insertions(+), 208 deletions(-)
 create mode 100644 
recipes-devtools/wiringPi/files/0001-Add-initial-cross-compile-support.patch
 delete mode 100644 recipes-devtools/wiringPi/files/Makefiles-install.patch

-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 0/6] Update packages

[Petter Mabäcker]

See http://redmine.gherzan.com/issues/60 for additional info.

The following changes since commit c8532df1c2e4812b3520d32ed49be943bea2edd9:

  If SERIAL_CONSOLE is already define by another layer, this value may not be 
good. (2015-06-05 16:38:14 +0200)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib petmab/rpi_redmine_60_03
  
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=petmab/rpi_redmine_60_03

Petter Mabäcker (6):
  bcm: Bump SRCREV
  rpi-mkimage: Bump SRCREV
  bcm2835: update version to 1.44
  pi-blaster: bump to latest version
  rpi-gpio: update version to 0.5.11
  userland: bump SRCREV

 recipes-bsp/common/firmware.inc|  4 +-
 recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb |  2 +-
 .../bcm2835/{bcm2835_1.38.bb => bcm2835_1.44.bb}   |  4 +-
 ...ndle-install-data-hook-when-cross-compile.patch | 54 +++
 .../files/enable-autotools-support.patch   | 77 --
 recipes-devtools/pi-blaster/pi-blaster.inc |  4 +-
 recipes-devtools/pi-blaster/pi-blaster_git.bb  |  2 +-
 .../{rpi-gpio_0.5.9.bb => rpi-gpio_0.5.11.bb}  |  4 +-
 recipes-graphics/userland/userland_git.bb  |  4 +-
 9 files changed, 66 insertions(+), 89 deletions(-)
 rename recipes-devtools/bcm2835/{bcm2835_1.38.bb => bcm2835_1.44.bb} (88%)
 create mode 100644 
recipes-devtools/pi-blaster/files/0001-handle-install-data-hook-when-cross-compile.patch
 delete mode 100644 
recipes-devtools/pi-blaster/files/enable-autotools-support.patch
 rename recipes-devtools/python/{rpi-gpio_0.5.9.bb => rpi-gpio_0.5.11.bb} (76%)

-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 5/6] rpi-gpio: update version to 0.5.11

[Petter Mabäcker]

[Support #60]

Signed-off-by: Petter Mabäcker 
---
 recipes-devtools/python/{rpi-gpio_0.5.9.bb => rpi-gpio_0.5.11.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename recipes-devtools/python/{rpi-gpio_0.5.9.bb => rpi-gpio_0.5.11.bb} (76%)

diff --git a/recipes-devtools/python/rpi-gpio_0.5.9.bb 
b/recipes-devtools/python/rpi-gpio_0.5.11.bb
similarity index 76%
rename from recipes-devtools/python/rpi-gpio_0.5.9.bb
rename to recipes-devtools/python/rpi-gpio_0.5.11.bb
index 9394fd8..bca31cc 100644
--- a/recipes-devtools/python/rpi-gpio_0.5.9.bb
+++ b/recipes-devtools/python/rpi-gpio_0.5.11.bb
@@ -15,5 +15,5 @@ inherit distutils
 
 COMPATIBLE_MACHINE = "raspberrypi"
 
-SRC_URI[md5sum] = "54ea6ef33502d43e3a89713593315e5a"
-SRC_URI[sha256sum] = 
"167fab1861093677af69db135ce815729dd4fbfb8f8e2eb830eab6324bc89152"
+SRC_URI[md5sum] = "9dc3dab6ce2b7ccb833a866efb392821"
+SRC_URI[sha256sum] = 
"8d6f02da7f90e24512ad80ee4ccf34ef33687c88c47326f100cf7ac4d7ae4bf3"
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 2/6] rpi-mkimage: Bump SRCREV

[Petter Mabäcker]

Update to latest version of rpi-mkimg

[Support #60]

Signed-off-by: Petter Mabäcker 
---
 recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb 
b/recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb
index 1778275..ffd1818 100644
--- a/recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb
+++ b/recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb
@@ -5,7 +5,7 @@ SECTION = "bootloader"
 
 DEPENDS = "python"
 
-SRCREV = "b9d7a8ac626e377577aa6900da5c5a965cafb66c"
+SRCREV = "d4b397f3a1e60ea45660eafb9209bcb97453c456"
 SRC_URI = " \
 git://github.com/raspberrypi/tools.git;branch=master;protocol=git \
 file://License \
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 6/6] userland: bump SRCREV

[Petter Mabäcker]

Update to latest version of userland for rpi.

[Support #60]

Signed-off-by: Petter Mabäcker 
---
 recipes-graphics/userland/userland_git.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-graphics/userland/userland_git.bb 
b/recipes-graphics/userland/userland_git.bb
index 729c42a..dfb6701 100644
--- a/recipes-graphics/userland/userland_git.bb
+++ b/recipes-graphics/userland/userland_git.bb
@@ -5,7 +5,7 @@ vcos, openmaxil, vchiq_arm, bcm_host, WFC, OpenVG."
 LICENSE = "Broadcom"
 LIC_FILES_CHKSUM = "file://LICENCE;md5=957f6640d5e2d2acfce73a36a56cb32f"
 
-PR = "r4"
+PR = "r5"
 
 PROVIDES = "virtual/libgles2 \
 virtual/egl"
@@ -13,7 +13,7 @@ COMPATIBLE_MACHINE = "raspberrypi"
 
 SRCBRANCH = "master"
 SRCFORK = "raspberrypi"
-SRCREV = "3b81b91c18ff19f97033e146a9f3262ca631f0e9"
+SRCREV = "c2f27fb8e581f8e5af83bf28422553ade8f7a7c8"
 
 SRC_URI = 
"git://github.com/${SRCFORK}/userland.git;protocol=git;branch=${SRCBRANCH} \
   "
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 3/6] bcm2835: update version to 1.44

[Petter Mabäcker]

[Support #60]

Signed-off-by: Petter Mabäcker 
---
 recipes-devtools/bcm2835/{bcm2835_1.38.bb => bcm2835_1.44.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename recipes-devtools/bcm2835/{bcm2835_1.38.bb => bcm2835_1.44.bb} (88%)

diff --git a/recipes-devtools/bcm2835/bcm2835_1.38.bb 
b/recipes-devtools/bcm2835/bcm2835_1.44.bb
similarity index 88%
rename from recipes-devtools/bcm2835/bcm2835_1.38.bb
rename to recipes-devtools/bcm2835/bcm2835_1.44.bb
index 316d7b5..a0d349d 100644
--- a/recipes-devtools/bcm2835/bcm2835_1.38.bb
+++ b/recipes-devtools/bcm2835/bcm2835_1.44.bb
@@ -12,8 +12,8 @@ COMPATIBLE_MACHINE = "raspberrypi"
 
 SRC_URI = "http://www.airspayce.com/mikem/bcm2835/bcm2835-${PV}.tar.gz";
 
-SRC_URI[md5sum] = "22d431f7402b9c7f93baef348a459cb1"
-SRC_URI[sha256sum] = 
"90c993559ea273ae2e0587f6b815f7c80f19f47ee7f8aa7799b883f975196dbe"
+SRC_URI[md5sum] = "a974af22a2fa2c0b131becd55c4b31c0"
+SRC_URI[sha256sum] = 
"608b60bf95ff909a027155303090b71643f333116584d4a2c3b8f6edbf49c612"
 
 inherit autotools
 
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 4/6] pi-blaster: bump to latest version

[Petter Mabäcker]

Removed 'enable-autotools-support.patch' since it is included in latest
upstream. Also fix a cross compiling issue.

[Support #60]

Signed-off-by: Petter Mabäcker 
---
 ...ndle-install-data-hook-when-cross-compile.patch | 54 +++
 .../files/enable-autotools-support.patch   | 77 --
 recipes-devtools/pi-blaster/pi-blaster.inc |  4 +-
 recipes-devtools/pi-blaster/pi-blaster_git.bb  |  2 +-
 4 files changed, 57 insertions(+), 80 deletions(-)
 create mode 100644 
recipes-devtools/pi-blaster/files/0001-handle-install-data-hook-when-cross-compile.patch
 delete mode 100644 
recipes-devtools/pi-blaster/files/enable-autotools-support.patch

diff --git 
a/recipes-devtools/pi-blaster/files/0001-handle-install-data-hook-when-cross-compile.patch
 
b/recipes-devtools/pi-blaster/files/0001-handle-install-data-hook-when-cross-compile.patch
new file mode 100644
index 000..2f2a7f4
--- /dev/null
+++ 
b/recipes-devtools/pi-blaster/files/0001-handle-install-data-hook-when-cross-compile.patch
@@ -0,0 +1,54 @@
+From 28e4bc3216f8845cf278f0fbc6b2c30eebcc35aa Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petter=20Mab=C3=A4cker?= 
+Date: Sun, 7 Jun 2015 17:17:01 +0200
+Subject: [PATCH] handle install-data-hook when cross compile
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Avoid doing 'install-data-hook' when cross compiling since it isn't
+suitable to update rc.d or run the service when cross
+compiling.
+
+Upstream-Status: Pending
+
+Signed-off-by: Petter Mabäcker 
+---
+ Makefile.am  | 4 +++-
+ configure.ac | 1 +
+ 2 files changed, 4 insertions(+), 1 deletion(-)
+
+diff --git a/Makefile.am b/Makefile.am
+index 6693d46..935288f 100644
+--- a/Makefile.am
 b/Makefile.am
+@@ -13,6 +13,7 @@ else
+ init_ddir = $(sysconfdir)/init.d
+ init_d_SCRIPTS = pi-blaster.boot.sh
+ 
++if !CROSS_COMPILING
+ install-data-hook:
+   update-rc.d pi-blaster.boot.sh defaults
+   $(init_ddir)/pi-blaster.boot.sh start
+@@ -20,4 +21,5 @@ install-data-hook:
+ uninstall-hook:
+   update-rc.d pi-blaster.boot.sh remove
+   killall pi-blaster
+-endif
++endif # !CROSS_COMPILING
++endif # !HAVE_SYSTEMD
+diff --git a/configure.ac b/configure.ac
+index 5d0c1fa..aaf4465 100644
+--- a/configure.ac
 b/configure.ac
+@@ -23,6 +23,7 @@ if test "x$with_systemdsystemunitdir" != xno; then
+  AC_SUBST([systemdsystemunitdir], [$with_systemdsystemunitdir])
+ fi
+ AM_CONDITIONAL(HAVE_SYSTEMD, [test -n "$with_systemdsystemunitdir" -a 
"x$with_systemdsystemunitdir" != xno ])
++AM_CONDITIONAL(CROSS_COMPILING, [test x"$cross_compiling" = x"yes" ])
+ 
+ # Checks for programs.
+ AC_PROG_CC
+-- 
+1.9.1
+
diff --git a/recipes-devtools/pi-blaster/files/enable-autotools-support.patch 
b/recipes-devtools/pi-blaster/files/enable-autotools-support.patch
deleted file mode 100644
index f0d4958..000
--- a/recipes-devtools/pi-blaster/files/enable-autotools-support.patch
+++ /dev/null
@@ -1,77 +0,0 @@
-Add autotools configuration files to simplify cross-compilation
-
-Upstream-Status: Submitted [https://github.com/sarfata/pi-blaster/pull/25]
-
-Signed-off-by: Alex Lennon 
-
-diff -Nur git.org/Makefile git.new/Makefile
 git.org/Makefile   2014-06-11 15:42:26.490930706 +0100
-+++ git.new/Makefile   1970-01-01 01:00:00.0 +0100
-@@ -1,23 +0,0 @@
--.PHONY: all
--all:  pi-blaster
--
--REVISION=$(shell egrep -q '000f$$' /proc/cpuinfo && echo 2 || echo 1)
--
--pi-blaster:   pi-blaster.c
--  gcc -Wall -g -O2 -o $@ $< -DREVISION=$(REVISION)
--
--clean:
--  rm -f pi-blaster
--
--install: pi-blaster
--  cp -f pi-blaster.boot.sh /etc/init.d/pi-blaster
--  chmod +x /etc/init.d/pi-blaster
--  cp -f pi-blaster /usr/sbin/pi-blaster
--  update-rc.d pi-blaster defaults
--  /etc/init.d/pi-blaster start
--  
--uninstall:
--  -/etc/init.d/pi-blaster stop
--  rm /usr/sbin/pi-blaster
--  rm /etc/init.d/pi-blaster
--  update-rc.d pi-blaster remove
-diff -Nur git.org/Makefile.am git.new/Makefile.am
 git.org/Makefile.am1970-01-01 01:00:00.0 +0100
-+++ git.new/Makefile.am2014-06-11 15:40:16.562930372 +0100
-@@ -0,0 +1,9 @@
-+AUTOMAKE_OPTIONS = foreign
-+
-+CFLAGS = -Wall -pedantic
-+
-+sbin_PROGRAMS = pi-blaster
-+pi_blaster_SOURCES = pi-blaster.c
-+
-+init_ddir = $(sysconfdir)/init.d
-+init_d_SCRIPTS = pi-blaster.boot.sh
-diff -Nur git.org/autogen.sh git.new/autogen.sh
 git.org/autogen.sh 1970-01-01 01:00:00.0 +0100
-+++ git.new/autogen.sh 2014-06-11 15:35:57.798929684 +0100
-@@ -0,0 +1,9 @@
-+#!/bin/sh
-+
-+echo "Generating configure files... may take a while."
-+
-+autoreconf --install --force && \
-+  echo "Preparing was successful if there was no error messages above." && \
-+  echo "Now type:" && \
-+  echo "  ./configure && make&qu

[yocto] [meta-raspberrypi][PATCH 1/6] bcm: Bump SRCREV

[Petter Mabäcker]

Update to latest version of firmware.git

[Support #60]

Signed-off-by: Petter Mabäcker 
---
 recipes-bsp/common/firmware.inc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-bsp/common/firmware.inc b/recipes-bsp/common/firmware.inc
index ad3176a..a5a5412 100644
--- a/recipes-bsp/common/firmware.inc
+++ b/recipes-bsp/common/firmware.inc
@@ -1,5 +1,5 @@
-RPIFW_SRCREV ?= "e42a747e8d5c4a2fb3e837d0924c7cc3936a"
-RPIFW_DATE ?= "20150206"
+RPIFW_SRCREV ?= "89881b5488a5a60088677333dcbd97e1836c0e7e"
+RPIFW_DATE ?= "20150630"
 RPIFW_SRC_URI ?= 
"git://github.com/raspberrypi/firmware.git;protocol=git;branch=master"
 RPIFW_S ?= "${WORKDIR}/git"
 
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] firmware.inc: Fetch a zip instead of cloning a git repo

[Petter Mabäcker]

On 06/26/2015 04:16 PM, Jon Szymaniak wrote:
On Fri, Jun 26, 2015 at 4:31 AM, Burton, Ross > wrote:



On 26 June 2015 at 05:16, Jon Szymaniak mailto:jon.szyman...@gmail.com>> wrote:

GitHub provides this ability to download repository contents at
a specified changeset as a zip file. This is generally *much*
quicker
than fetching the entire git repository.


Github also can and will regenerate these tarballs whenever it
feels like it, so you'll need to periodically update the
checksums.  Obviously as existing developers will tend to have the
tarballs cached locally, it can be a while before this failure is
reported back.

A better solution might be to add support for "depth" to the git
fetcher, so you can grab just the commit you are interested in
instead of the entire repository.

Ross


Hi Ross,

Excellent point about the regeneration potentially yielding different 
checksums.  I suppose they could change the compression level they use 
at any moment in time... I'll look into adding that depth support to 
the fetcher, as that doesn't look too hard at all.


I'm open to other suggestions as well, as this was just a first stab 
at it. I've been seeing that cloning this git repo containing binary 
firmware blobs takes an absurd amount of time, if it even finishes at 
all successfully.


Cheers,
Jon




Hi Jon,

Any news about this? I have also used a very similar changeset like you 
suggests (use .zip from github) ontop of meta-raspberrypi when building, 
to get rid of the annoying problem that it takes a very long time or 
even worse that you get a timeout.


My suggestion is to go for the .zip changeset at least until --depth=1 
is supported in the git fetcher.


@Andrei any comments from your side regarding this discussion?

BR,
Petter


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] firmware.inc: fetch from SVN instead of Git

[Petter Mabäcker]

On 07/04/2015 07:29 AM, Nikolay Dimitrov wrote:

Hi Jonathan,

On 07/04/2015 06:48 AM, Jonathan Liu wrote:

Reduces the download time significantly.

Signed-off-by: Jonathan Liu 
---
  recipes-bsp/common/firmware.inc | 6 +++---
  1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/recipes-bsp/common/firmware.inc 
b/recipes-bsp/common/firmware.inc

index ad3176a..100df3a 100644
--- a/recipes-bsp/common/firmware.inc
+++ b/recipes-bsp/common/firmware.inc
@@ -1,7 +1,7 @@
-RPIFW_SRCREV ?= "e42a747e8d5c4a2fb3e837d0924c7cc3936a"
+RPIFW_SRCREV ?= "461"
  RPIFW_DATE ?= "20150206"
-RPIFW_SRC_URI ?= 
"git://github.com/raspberrypi/firmware.git;protocol=git;branch=master"

-RPIFW_S ?= "${WORKDIR}/git"
+RPIFW_SRC_URI ?= 
"svn://github.com/raspberrypi/firmware;protocol=https;module=trunk"

+RPIFW_S ?= "${WORKDIR}/trunk"

  SRC_URI = "${RPIFW_SRC_URI}"
  SRCREV = "${RPIFW_SRCREV}"



Just tested the download times for this repo:

git (deep clone): 24m
svn: 3m8s
git (shallow clone): 40s

Isn't it possible to use "--depth 1" for git clone? I would rather
prefer seeing this instead of just giving up and going back to svn...

Regards,
Nikolay
Jonathan, I understand your problem, I have pointed out 
"https://github.com/raspberrypi/firmware/archive/${RPIFW_SRCREV}.zip"; 
ontop of HEAD when building in order to get rid of this problem. But I 
agree with Nikolay that going back to svn feels like a step in the wrong 
direction and instead we should push for a changle like the one 
discussed in the thread: '[yocto] [meta-raspberrypi][PATCH] 
firmware.inc: Fetch a zip instead of cloning a git repo'


or by using "--depth=1" (which isn't supported in the bitbake git 
fetcher for the moment..).


I will try to push for that one of the solutions (--depth=1 or .zip) is 
merged soon so we once for all can get rid of this annoying problem.


BR,
Petter

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto