Re: [yocto] libgcrypt building fails for armv6 binaries.

2017-09-23 Thread Yusuke Mitsuki 
Hello Armin.

Thanks for your reply.
It was very helpful.

2017-09-23 14:21 GMT+09:00 akuster <akus...@mvista.com>:
>
>
> On 09/22/2017 09:15 PM, Yusuke Mitsuki wrote:
>> Hello yocto
>>
>> libgcrypt has problem that build for armv6.
>> bitbake said error messages at do_compile as follows:
>> ...(snip)...
>> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S: Assembler 
>> messages:
>> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165:
>> Error: selected processor does not support `rbit r8,lr' in ARM mode
>> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165:
>> Error: selected processor does not support `rbit r9,r9' in ARM mode
>> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165:
>> Error: selected processor does not support `rbit r10,r10' in ARM mode
>> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165:
>> Error: selected processor does not support `rbit r11,r11' in ARM mode
>> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165:
>> Error: selected processor does not support `rbit r8,lr' in ARM mode
>> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1166:
>> Error: selected processor does not support `rbit r8,lr' in ARM mode
>> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1166:
>> Error: selected processor does not support `rbit r9,r9' in ARM mode
>> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1166:
>> Error: selected processor does not support `rbit r10,r10' in ARM mode
>> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1166:
>> Error: selected processor does not support `rbit r11,r11' in ARM mode
>> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1166:
>> Error: selected processor does not support `rbit r8,lr' in ARM mode
>> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1167:
>> Error: selected processor does not support `rbit r8,lr' in ARM mode
>> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1167:
>> Error: selected processor does not support `rbit r9,r9' in ARM mode
>> ...(snip)...
>>
>> I googled about this problem then I found the clue at here.
>> https://mail-index.netbsd.org/pkgsrc-bugs/2017/08/01/msg062410.html
>>
>> I thought it fixed at libcrypt_1.8.1.
>>
>> I tried update to 1.8.1. It seems fine.
>> So I suggest the libgcrypt updating for 1.8.1.
> It may be too late to update  as we are in the stabilization phase of
> the next release.
>>
>> By the way, I created the patch for this problem.
> The is great and much appreciated.
>
>> But I am not sure, where to send to this patch?
> Yes it is a bit confusing and we should revisit the documentation.
>> I could not found the guidelines of contributing [meta].
>> I should send to OE-Core's ML? or  here directly?
>
> The oe-core ML is the appropriate place.
>
>
>>
>> And, Would you let me know what strings of options to git send-email I
>> should to set?
> if you want to us git send mail, I use the following.
>
> git send-email -1 -M --to  openembedded-c...@lists.openembedded.org
> --subject-prefix=PATCH
>
> regards,
> Armin
>
>> Thanks.
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] libgcrypt building fails for armv6 binaries.

2017-09-22 Thread Yusuke Mitsuki 
Hello yocto

libgcrypt has problem that build for armv6.
bitbake said error messages at do_compile as follows:
...(snip)...
| ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S: Assembler messages:
| ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165:
Error: selected processor does not support `rbit r8,lr' in ARM mode
| ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165:
Error: selected processor does not support `rbit r9,r9' in ARM mode
| ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165:
Error: selected processor does not support `rbit r10,r10' in ARM mode
| ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165:
Error: selected processor does not support `rbit r11,r11' in ARM mode
| ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165:
Error: selected processor does not support `rbit r8,lr' in ARM mode
| ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1166:
Error: selected processor does not support `rbit r8,lr' in ARM mode
| ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1166:
Error: selected processor does not support `rbit r9,r9' in ARM mode
| ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1166:
Error: selected processor does not support `rbit r10,r10' in ARM mode
| ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1166:
Error: selected processor does not support `rbit r11,r11' in ARM mode
| ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1166:
Error: selected processor does not support `rbit r8,lr' in ARM mode
| ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1167:
Error: selected processor does not support `rbit r8,lr' in ARM mode
| ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1167:
Error: selected processor does not support `rbit r9,r9' in ARM mode
...(snip)...

I googled about this problem then I found the clue at here.
https://mail-index.netbsd.org/pkgsrc-bugs/2017/08/01/msg062410.html

I thought it fixed at libcrypt_1.8.1.

I tried update to 1.8.1. It seems fine.
So I suggest the libgcrypt updating for 1.8.1.

By the way, I created the patch for this problem.
But I am not sure, where to send to this patch?
I could not found the guidelines of contributing [meta].
I should send to OE-Core's ML? or  here directly??

And, Would you let me know what strings of options to git send-email I
should to set?

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

Re: [yocto] DEBUG: automake-native: class native found in blacklist, disable icecc ?

2017-09-14 Thread Yusuke Mitsuki 
Hi Riko

It seems you use,
poky: pyro
meta-openembedded:master

I think that you should checkout meta-openembedded to pyro branch.

You can get by command like a follows,

$ cd meta-openembedded
$ git checkout -b pyro origin/pyro

Otherwise, checkout poky to master...

I hope your helps.

2017/08/03 0:05 "Riko Ho" :

> Still got the same error after installing it? Any other clues?
> On Aug 2, 2017 9:53 PM, "Khem Raj"  wrote:
>
>> On Tue, Aug 1, 2017 at 11:42 PM, Riko Ho  wrote:
>> > Could it be this one ?
>> >
>> > https://www.devmanuals.net/install/ubuntu/ubuntu-12-04-lts-
>> precise-pangolin/install-libthread-queue-perl.html
>> >
>>
>> yes
>>
>> > Thanks
>> >
>> >
>> > On 02/08/17 14:38, Khem Raj wrote:
>> >
>> > apply the solutions they may work for ubuntu
>> >
>> > On Tue, Aug 1, 2017 at 11:33 PM, Riko Ho 
>> wrote:
>> >
>> > Dear Yocto Team Member,
>> >
>> > I'm building with Ubuntu 16
>> >
>> >
>> > On 02/08/17 14:31, Khem Raj wrote:
>> >
>> > On Tue, Aug 1, 2017 at 11:18 PM, Riko Ho 
>> wrote:
>> >
>> > Dear Yocto Team Member,
>> >
>> > That's the branch :
>> >
>> > ==
>> >
>> > meta-poky
>> > meta-yocto-bsp= "pyro:e5aa1ac23669a45491de9ecffac491c01e70203f"
>> > openembedded-core = "master:2fd0757ae7fd63bc93a4ce8579c6ba0cdbb4c1cd"
>> > meta-openembedded
>> > meta-oe
>> > meta-xfce
>> > meta-gnome
>> > meta-python
>> > meta-multimedia
>> > meta-networking   = "master:b063789560bfb9c60a7a15277b5b3a9839b5ba74"
>> > meta-browser  =
>> > "firefox-52.1.2esr-2:c79cf6c7811afd2cd167e8967e3c29b1e797371e"
>> > meta-ti   = "master:872d418f6e503dea66e3533f43e7a17618183982"
>> >
>> > Initialising tasks: 100%
>> > |###
>> #|
>> > Time: 0:00:08
>> > NOTE: Executing SetScene Tasks
>> > NOTE: Executing RunQueue Tasks
>> > ERROR: automake-native-1.15-r0 do_compile: oe_runmake failed
>> > ERROR: automake-native-1.15-r0 do_compile: Function failed: do_compile
>> (log
>> > file is located at
>> > /home/bianchi77/poky/build/tmp/work/x86_64-linux/automake-
>> native/1.15-r0/temp/log.do_compile.9291)
>> > ERROR: Logfile of failure stored in:
>> > /home/bianchi77/poky/build/tmp/work/x86_64-linux/automake-
>> native/1.15-r0/temp/log.do_compile.9291
>> > Log data follows:
>> > | DEBUG: Executing shell function do_compile
>> > | NOTE: Using icecc
>> > | NOTE: make -j 10
>> > | ERROR: oe_runmake failed
>> > | : && /home/bianchi77/poky/build/tmp/hosttools/mkdir -p doc && {
>> > PATH='/home/bianchi77/poky/build/tmp/work/x86_64-linux/autom
>> ake-native/1.15-r0/build/t/wrap:'$PATH
>> > && export PATH; } && /usr/bin/env perl ../automake-1.15/doc/help2man
>> > --output=doc/automake-1.15.1 automake-1.15
>> > | help2man: can't get `--help' info from automake-1.15
>> >
>> > What OS do you run on build machine ?
>> > if its archlinux then apply this patch to automake
>> >
>> > https://gist.github.com/xywei/03b546054f0d2e2f76c5ac530c88268a
>> >
>> > otherwise if its centos7 then install
>> >
>> > yum install perl-Thread-Queue
>> >
>> >
>> >
>> > | Try `--no-discard-stderr' if option outputs to stderr
>> > | Makefile:3687: recipe for target 'doc/automake-1.15.1' failed
>> > | make: *** [doc/automake-1.15.1] Error 255
>> > | ERROR: Function failed: do_compile (log file is located at
>> > /home/bianchi77/poky/build/tmp/work/x86_64-linux/automake-
>> native/1.15-r0/temp/log.do_compile.9291)
>> > ERROR: Task
>> > (virtual:native:/home/bianchi77/poky/meta/recipes-devtools/
>> automake/automake_1.15.bb:do_compile)
>> > failed with exit code '1'
>> > NOTE: Tasks Summary: Attempted 845 tasks of which 844 didn't need to be
>> > rerun and 1 failed.
>> >
>> > Summary: 1 task failed:
>> >
>> > virtual:native:/home/bianchi77/poky/meta/recipes-devtools/
>> automake/automake_1.15.bb:do_compile
>> > Summary: There were 4 WARNING messages shown.
>> > Summary: There were 2 ERROR messages shown, returning a non-zero exit
>> code.
>> > bianchi77@bianchi77-HP-Pavilion-dv6-Notebook-PC:~/poky/build$
>> >
>> > How can I fix that automake error ?
>> >
>> > I tried to run bitbake core-image-minimal for it.
>> > Thanks,
>> >
>> > On 31/07/17 21:26, Burton, Ross wrote:
>> >
>> > Then the branch you checked out.  git branch will tell you.
>> >
>> > Ross
>> >
>> > On 31 July 2017 at 14:17, Riko Ho  wrote:
>> >
>> > Git clone ...
>> >
>> > On Jul 31, 2017 9:16 PM, "Burton, Ross"  wrote:
>> >
>> > How did you get poky?
>> >
>> > Ross
>> >
>> > On 31 July 2017 at 14:14, Riko Ho  wrote:
>> >
>> > How can I see my branch?
>> >
>> > On Jul 31, 2017 9:12 PM, "Burton, Ross"  wrote:
>> >
>> > On 31 July 2017 at 03:33, Riko Ho  wrote:
>> >
>> > Is my auto make disabled with icecc ?
>> >
>> > How to

Re: [yocto] how to execute bitbake menuconfig from ssh server

2017-09-13 Thread Yusuke Mitsuki 
Hello

You can use screen.
If your host is ubuntu,you can get via apt as follows.

sudo apt install screen.

If necessary , you can set auto or screen to OE_TERMINAL environment.

2017/09/13 16:09 "yahia farghaly" :

> Hi,
>
> I am working with yocto from a remote server using ssh. i want to execute 
> *bitbake
> -c menuconfig virtual/kernel*  . It fails to open since it tries to open
> another shell.
> how can i redirect output of menuconfig to my current ssh session ?
>
> --
> Yahia Farghaly
> Graduated from Faculty of Engineering - Electronics and Communications
> Department at Cairo University.
> Linkedin  - GitHub
> 
>
>
>
> ‌
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH v2 1/2] bluez5: add functions/variables to enabling bluetooth on another raspberrypi

2017-09-08 Thread Yusuke Mitsuki 
Hello Andrei and Paul

Thanks for your replies.
I will create PR in github.


2017-09-07 2:52 GMT+09:00 Andrei Gherzan <and...@gherzan.ro>:
> On Wed, Sep 6, 2017 at 10:18 AM, Paul Barker <pbar...@toganlabs.com> wrote:
>>
>> On Tue, Sep 5, 2017 at 11:34 PM, Yusuke Mitsuki
>> <mickey.happygolu...@gmail.com> wrote:
>> > functions/variables in this bbappend implemented for only raspberrypi3.
>> > But these must be able to used to enabling bluetooth on another
>> > raspberrypi that has bluetooth feature such as raspberrypi0-wifi.
>> >
>> > The simple solution is a duplicating these but it is not good ideas for
>> > maintainance.
>> >
>> > Add functions/variables follows to simplify to enabling bluetooth on
>> > another raspberrypi that has bluetooth.
>> > - BCM_BT_SOURCES
>> > - enable_bcm_bluetooth()
>> > - BCM_BT_FIRMWARE
>> > - BCM_BT_SERVICE
>> >
>> > Signed-off-by: Yusuke Mitsuki <mickey.happygolu...@gmail.com>
>> > ---
>> >  recipes-connectivity/bluez5/bluez5_%.bbappend | 18 ++
>> >  1 file changed, 14 insertions(+), 4 deletions(-)
>> >
>> > diff --git a/recipes-connectivity/bluez5/bluez5_%.bbappend
>> > b/recipes-connectivity/bluez5/bluez5_%.bbappend
>> > index 956d776..b2fbf22 100644
>> > --- a/recipes-connectivity/bluez5/bluez5_%.bbappend
>> > +++ b/recipes-connectivity/bluez5/bluez5_%.bbappend
>> > @@ -1,6 +1,6 @@
>> >  FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>> >
>> > -SRC_URI_append_raspberrypi3 = " \
>> > +BCM_BT_SOURCES =  " \
>> >  file://BCM43430A1.hcd \
>> >  file://0001-bcm43xx-Add-bcm43xx-3wire-variant.patch \
>> >
>> > file://0002-bcm43xx-The-UART-speed-must-be-reset-after-the-firmw.patch \
>> > @@ -9,7 +9,7 @@ SRC_URI_append_raspberrypi3 = " \
>> >  file://brcm43438.service \
>> >  "
>> >
>> > -do_install_append_raspberrypi3() {
>> > +enable_bcm_bluetooth() {
>> >  install -d ${D}/lib/firmware/brcm/
>> >  install -m 0644 ${WORKDIR}/BCM43430A1.hcd
>> > ${D}/lib/firmware/brcm/BCM43430A1.hcd
>> >
>> > @@ -19,8 +19,18 @@ do_install_append_raspberrypi3() {
>> >  fi
>> >  }
>> >
>> > -FILES_${PN}_append_raspberrypi3 = " \
>> > +BCM_BT_FIRMWARE =  " \
>> >  /lib/firmware/brcm/BCM43430A1.hcd \
>> >  "
>> >
>> > -SYSTEMD_SERVICE_${PN}_append_raspberrypi3 = " brcm43438.service"
>> > +BCM_BT_SERVICE =  " brcm43438.service"
>> > +
>> > +SRC_URI_append_raspberrypi3 = " ${BCM_BT_SOURCES}"
>> > +
>> > +do_install_append_raspberrypi3() {
>> > +enable_bcm_bluetooth
>> > +}
>> > +
>> > +FILES_${PN}_append_raspberrypi3 = " ${BCM_BT_FIRMWARE}"
>> > +
>> > +SYSTEMD_SERVICE_${PN}_append_raspberrypi3 = " ${BCM_BT_SERVICE}"
>> > --
>> > 2.7.4
>> >
>>
>> This and the follow up patch look excellent, should be easy to modify
>> in the future if we need to.
>>
>> We have switched to using github pull requests for meta-raspberrypi.
>> Could you open a pull request on
>> https://github.com/agherzan/meta-raspberrypi with these changes
>> please? Let me know if you have any issues doing that.
>
>
> +1 from my side.  Thanks for this change. We still try to keep patches
> rolling to the mailing list too but the main development now happens through
> PRs in github.
>
> --
> Andrei Gherzan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH v2 2/2] bluez5: enable bluetooth on raspberrypi0-wifi

2017-09-05 Thread Yusuke Mitsuki 
Add functions/variable to enabling bluetooth on raspberrypi0-wifi.

Signed-off-by: Yusuke Mitsuki <mickey.happygolu...@gmail.com>
---
 recipes-connectivity/bluez5/bluez5_%.bbappend | 12 
 1 file changed, 12 insertions(+)

diff --git a/recipes-connectivity/bluez5/bluez5_%.bbappend 
b/recipes-connectivity/bluez5/bluez5_%.bbappend
index b2fbf22..03efd5c 100644
--- a/recipes-connectivity/bluez5/bluez5_%.bbappend
+++ b/recipes-connectivity/bluez5/bluez5_%.bbappend
@@ -25,6 +25,7 @@ BCM_BT_FIRMWARE =  " \
 
 BCM_BT_SERVICE =  " brcm43438.service"
 
+# for raspberrypi3
 SRC_URI_append_raspberrypi3 = " ${BCM_BT_SOURCES}"
 
 do_install_append_raspberrypi3() {
@@ -34,3 +35,14 @@ do_install_append_raspberrypi3() {
 FILES_${PN}_append_raspberrypi3 = " ${BCM_BT_FIRMWARE}"
 
 SYSTEMD_SERVICE_${PN}_append_raspberrypi3 = " ${BCM_BT_SERVICE}"
+
+# for raspberrypi0-wifi
+SRC_URI_append_raspberrypi0-wifi = " ${BCM_BT_SOURCES}"
+
+do_install_append_raspberrypi0-wifi() {
+enable_bcm_bluetooth
+}
+
+FILES_${PN}_append_raspberrypi0-wifi = " ${BCM_BT_FIRMWARE}"
+
+SYSTEMD_SERVICE_${PN}_append_raspberrypi0-wifi = " ${BCM_BT_SERVICE}"
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v2 1/2] bluez5: add functions/variables to enabling bluetooth on another raspberrypi

2017-09-05 Thread Yusuke Mitsuki 
functions/variables in this bbappend implemented for only raspberrypi3.
But these must be able to used to enabling bluetooth on another raspberrypi 
that has bluetooth feature such as raspberrypi0-wifi.

The simple solution is a duplicating these but it is not good ideas for 
maintainance.

Add functions/variables follows to simplify to enabling bluetooth on another 
raspberrypi that has bluetooth.
- BCM_BT_SOURCES
- enable_bcm_bluetooth()
- BCM_BT_FIRMWARE
- BCM_BT_SERVICE

Signed-off-by: Yusuke Mitsuki <mickey.happygolu...@gmail.com>
---
 recipes-connectivity/bluez5/bluez5_%.bbappend | 18 ++
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/recipes-connectivity/bluez5/bluez5_%.bbappend 
b/recipes-connectivity/bluez5/bluez5_%.bbappend
index 956d776..b2fbf22 100644
--- a/recipes-connectivity/bluez5/bluez5_%.bbappend
+++ b/recipes-connectivity/bluez5/bluez5_%.bbappend
@@ -1,6 +1,6 @@
 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
 
-SRC_URI_append_raspberrypi3 = " \
+BCM_BT_SOURCES =  " \
 file://BCM43430A1.hcd \
 file://0001-bcm43xx-Add-bcm43xx-3wire-variant.patch \
 file://0002-bcm43xx-The-UART-speed-must-be-reset-after-the-firmw.patch \
@@ -9,7 +9,7 @@ SRC_URI_append_raspberrypi3 = " \
 file://brcm43438.service \
 "
 
-do_install_append_raspberrypi3() {
+enable_bcm_bluetooth() {
 install -d ${D}/lib/firmware/brcm/
 install -m 0644 ${WORKDIR}/BCM43430A1.hcd 
${D}/lib/firmware/brcm/BCM43430A1.hcd
 
@@ -19,8 +19,18 @@ do_install_append_raspberrypi3() {
 fi
 }
 
-FILES_${PN}_append_raspberrypi3 = " \
+BCM_BT_FIRMWARE =  " \
 /lib/firmware/brcm/BCM43430A1.hcd \
 "
 
-SYSTEMD_SERVICE_${PN}_append_raspberrypi3 = " brcm43438.service"
+BCM_BT_SERVICE =  " brcm43438.service"
+
+SRC_URI_append_raspberrypi3 = " ${BCM_BT_SOURCES}"
+
+do_install_append_raspberrypi3() {
+enable_bcm_bluetooth
+}
+
+FILES_${PN}_append_raspberrypi3 = " ${BCM_BT_FIRMWARE}"
+
+SYSTEMD_SERVICE_${PN}_append_raspberrypi3 = " ${BCM_BT_SERVICE}"
-- 
2.7.4

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

Re: [yocto] [meta-raspberrypi][PATCH] bluez5: add functions for raspberrypi0-wifi

2017-09-05 Thread Yusuke Mitsuki 
Sorry I am late.
I could not get time enough for this work.

I will send patches soon.

By the way, If the Michal's  work that Andrei pointed and my patches are
similar, please drop my patches.



2017-09-04 20:05 GMT+09:00 Andrei Gherzan <and...@gherzan.ro>:

>
>
> On Fri, Aug 25, 2017 at 9:17 PM, Yusuke Mitsuki <
> mickey.happygolu...@gmail.com> wrote:
>
>> okay. I will try.
>>
>> 2017-08-25 17:51 GMT+09:00 Paul Barker <pbar...@toganlabs.com>:
>>
>>> On Thu, Aug 24, 2017 at 1:05 PM, Yusuke Mitsuki
>>> <mickey.happygolu...@gmail.com> wrote:
>>> > hciattach on raspberrypi0-wifi failed because BCM43430A1.hcd is not
>>> found.
>>> >
>>> > Paches that in order to use bluetooth with BCM43430 are not enabled.
>>> > Functions are only enabled with raspberrypi3 in bluez5_%.bbappend like
>>> as follows:
>>> >
>>> > - SRC_URI_append_raspberrypi3
>>> > - do_install_append_raspberrypi3()
>>> > - FILES_${PN}_append_raspberrypi3
>>> > - SYSTEMD_SERVICE_${PN}_append_raspberrypi3
>>> >
>>> > These should be enabled with raspberrypi0-wifi too.
>>> >
>>> > Signed-off-by: Yusuke Mitsuki <mickey.happygolu...@gmail.com>
>>> > ---
>>> >  recipes-connectivity/bluez5/bluez5_%.bbappend | 25
>>> +
>>> >  1 file changed, 25 insertions(+)
>>> >
>>> > diff --git a/recipes-connectivity/bluez5/bluez5_%.bbappend
>>> b/recipes-connectivity/bluez5/bluez5_%.bbappend
>>> > index 956d776..075dc2b 100644
>>> > --- a/recipes-connectivity/bluez5/bluez5_%.bbappend
>>> > +++ b/recipes-connectivity/bluez5/bluez5_%.bbappend
>>> > @@ -24,3 +24,28 @@ FILES_${PN}_append_raspberrypi3 = " \
>>> >  "
>>> >
>>> >  SYSTEMD_SERVICE_${PN}_append_raspberrypi3 = " brcm43438.service"
>>> > +
>>> > +SRC_URI_append_raspberrypi0-wifi = " \
>>> > +file://BCM43430A1.hcd \
>>> > +file://0001-bcm43xx-Add-bcm43xx-3wire-variant.patch \
>>> > +
>>> > file://0002-bcm43xx-The-UART-speed-must-be-reset-after-the-firmw.patch
>>> \
>>> > +file://0003-Increase-firmware-load-timeout-to-30s.patch \
>>> > +file://0004-Move-the-43xx-firmware-into-lib-firmware.patch \
>>> > +file://brcm43438.service \
>>> > +"
>>> > +
>>> > +do_install_append_raspberrypi0-wifi() {
>>> > +install -d ${D}/lib/firmware/brcm/
>>> > +install -m 0644 ${WORKDIR}/BCM43430A1.hcd
>>> ${D}/lib/firmware/brcm/BCM43430A1.hcd
>>> > +
>>> > +if ${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'true',
>>> 'false', d)}; then
>>> > +install -d ${D}${systemd_unitdir}/system
>>> > +install -m 0644 ${WORKDIR}/brcm43438.service
>>> ${D}${systemd_unitdir}/system
>>> > +fi
>>> > +}
>>> > +
>>> > +FILES_${PN}_append_raspberrypi0-wifi = " \
>>> > +/lib/firmware/brcm/BCM43430A1.hcd \
>>> > +"
>>> > +
>>> > +SYSTEMD_SERVICE_${PN}_append_raspberrypi0-wifi = " brcm43438.service"
>>>
>>> I don't like the amount of duplication here. Could you define some
>>> common variables and use those in the appends? This will make it
>>> easier to change/upgrade in the future and avoid risk of the
>>> duplicates falling out of sync with each other.
>>>
>>> Eg.
>>>
>>> RPI_WIFI_SOURCES = ""
>>>
>>> SRC_URI_append_raspberrypi3 = "${RPI_WIFI_SOURCES}"
>>> SRC_URI_append_raspberrypi0-wifi = "${RPI_WIFI_SOURCES}"
>>>
>>>
> I know Michal worked on this not long ago. Michal, could you give us some
> hints here? Maybe backport the changes in resinOS?
>
>
> --
> Andrei Gherzan
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] bluez5: add functions for raspberrypi0-wifi

2017-08-25 Thread Yusuke Mitsuki 
okay. I will try.

2017-08-25 17:51 GMT+09:00 Paul Barker <pbar...@toganlabs.com>:

> On Thu, Aug 24, 2017 at 1:05 PM, Yusuke Mitsuki
> <mickey.happygolu...@gmail.com> wrote:
> > hciattach on raspberrypi0-wifi failed because BCM43430A1.hcd is not
> found.
> >
> > Paches that in order to use bluetooth with BCM43430 are not enabled.
> > Functions are only enabled with raspberrypi3 in bluez5_%.bbappend like
> as follows:
> >
> > - SRC_URI_append_raspberrypi3
> > - do_install_append_raspberrypi3()
> > - FILES_${PN}_append_raspberrypi3
> > - SYSTEMD_SERVICE_${PN}_append_raspberrypi3
> >
> > These should be enabled with raspberrypi0-wifi too.
> >
> > Signed-off-by: Yusuke Mitsuki <mickey.happygolu...@gmail.com>
> > ---
> >  recipes-connectivity/bluez5/bluez5_%.bbappend | 25
> +
> >  1 file changed, 25 insertions(+)
> >
> > diff --git a/recipes-connectivity/bluez5/bluez5_%.bbappend
> b/recipes-connectivity/bluez5/bluez5_%.bbappend
> > index 956d776..075dc2b 100644
> > --- a/recipes-connectivity/bluez5/bluez5_%.bbappend
> > +++ b/recipes-connectivity/bluez5/bluez5_%.bbappend
> > @@ -24,3 +24,28 @@ FILES_${PN}_append_raspberrypi3 = " \
> >  "
> >
> >  SYSTEMD_SERVICE_${PN}_append_raspberrypi3 = " brcm43438.service"
> > +
> > +SRC_URI_append_raspberrypi0-wifi = " \
> > +file://BCM43430A1.hcd \
> > +file://0001-bcm43xx-Add-bcm43xx-3wire-variant.patch \
> > +file://0002-bcm43xx-The-UART-speed-must-be-reset-after-the-firmw.patch
> \
> > +file://0003-Increase-firmware-load-timeout-to-30s.patch \
> > +file://0004-Move-the-43xx-firmware-into-lib-firmware.patch \
> > +file://brcm43438.service \
> > +"
> > +
> > +do_install_append_raspberrypi0-wifi() {
> > +install -d ${D}/lib/firmware/brcm/
> > +install -m 0644 ${WORKDIR}/BCM43430A1.hcd ${D}/lib/firmware/brcm/
> BCM43430A1.hcd
> > +
> > +if ${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'true',
> 'false', d)}; then
> > +install -d ${D}${systemd_unitdir}/system
> > +install -m 0644 ${WORKDIR}/brcm43438.service
> ${D}${systemd_unitdir}/system
> > +fi
> > +}
> > +
> > +FILES_${PN}_append_raspberrypi0-wifi = " \
> > +/lib/firmware/brcm/BCM43430A1.hcd \
> > +"
> > +
> > +SYSTEMD_SERVICE_${PN}_append_raspberrypi0-wifi = " brcm43438.service"
>
> I don't like the amount of duplication here. Could you define some
> common variables and use those in the appends? This will make it
> easier to change/upgrade in the future and avoid risk of the
> duplicates falling out of sync with each other.
>
> Eg.
>
> RPI_WIFI_SOURCES = ""
>
> SRC_URI_append_raspberrypi3 = "${RPI_WIFI_SOURCES}"
> SRC_URI_append_raspberrypi0-wifi = "${RPI_WIFI_SOURCES}"
>
> --
> Paul Barker
> Togán Labs Ltd
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH] bluez5: add functions for raspberrypi0-wifi

2017-08-24 Thread Yusuke Mitsuki 
hciattach on raspberrypi0-wifi failed because BCM43430A1.hcd is not found.

Paches that in order to use bluetooth with BCM43430 are not enabled.
Functions are only enabled with raspberrypi3 in bluez5_%.bbappend like as 
follows:

- SRC_URI_append_raspberrypi3
- do_install_append_raspberrypi3()
- FILES_${PN}_append_raspberrypi3
- SYSTEMD_SERVICE_${PN}_append_raspberrypi3

These should be enabled with raspberrypi0-wifi too.

Signed-off-by: Yusuke Mitsuki <mickey.happygolu...@gmail.com>
---
 recipes-connectivity/bluez5/bluez5_%.bbappend | 25 +
 1 file changed, 25 insertions(+)

diff --git a/recipes-connectivity/bluez5/bluez5_%.bbappend 
b/recipes-connectivity/bluez5/bluez5_%.bbappend
index 956d776..075dc2b 100644
--- a/recipes-connectivity/bluez5/bluez5_%.bbappend
+++ b/recipes-connectivity/bluez5/bluez5_%.bbappend
@@ -24,3 +24,28 @@ FILES_${PN}_append_raspberrypi3 = " \
 "
 
 SYSTEMD_SERVICE_${PN}_append_raspberrypi3 = " brcm43438.service"
+
+SRC_URI_append_raspberrypi0-wifi = " \
+file://BCM43430A1.hcd \
+file://0001-bcm43xx-Add-bcm43xx-3wire-variant.patch \
+file://0002-bcm43xx-The-UART-speed-must-be-reset-after-the-firmw.patch \
+file://0003-Increase-firmware-load-timeout-to-30s.patch \
+file://0004-Move-the-43xx-firmware-into-lib-firmware.patch \
+file://brcm43438.service \
+"
+
+do_install_append_raspberrypi0-wifi() {
+install -d ${D}/lib/firmware/brcm/
+install -m 0644 ${WORKDIR}/BCM43430A1.hcd 
${D}/lib/firmware/brcm/BCM43430A1.hcd
+
+if ${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'true', 'false', 
d)}; then
+install -d ${D}${systemd_unitdir}/system
+install -m 0644 ${WORKDIR}/brcm43438.service 
${D}${systemd_unitdir}/system
+fi
+}
+
+FILES_${PN}_append_raspberrypi0-wifi = " \
+/lib/firmware/brcm/BCM43430A1.hcd \
+"
+
+SYSTEMD_SERVICE_${PN}_append_raspberrypi0-wifi = " brcm43438.service"
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH] bluez5: add functions for raspberrypi0-wifi

2017-08-24 Thread Yusuke Mitsuki 
I could not use bluetooth with raspberrypi0-wifi.
hciattach on raspberrypi0-wifi failed because BCM43430A1.hcd is not found.

Functions in bluez5_%.bbappend should be enabled with raspberrypi0-wifi too.

I know that these changes are redundant.

If you have any ideas for better solution, let me know.


Yusuke Mitsuki (1):
  bluez5: add functions for raspberrypi0-wifi

 recipes-connectivity/bluez5/bluez5_%.bbappend | 25 +
 1 file changed, 25 insertions(+)

-- 
2.7.4

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

[yocto] [meta-raspberrypi][morty][PATCH 2/2] xserver-xorg: add xf86-input-libinput to XSERVER_RRECOMMENDS

2017-04-23 Thread Yusuke Mitsuki 
oe-core's commit is not merged in morty branch.

| xorg-xserver recommends xf86-input-libinput since oe-core's commit
|
|   | commit 2d005faff6341a81a2afae28860101ba9db51ae8
|   | Author: Jussi Kukkonen <jussi.kukko...@intel.com>
|   | Date:   Wed Oct 26 11:37:38 2016 +0300
|   |
|   |conf: Use xf86-input-libinput by default
|   | ...

This is workaround to fix the problem that mouse does not work in morty.

Signed-off-by: Yusuke Mitsuki <mickey.happygolu...@gmail.com>
---
 recipes-graphics/xorg-xserver/xserver-xorg_%.bbappend | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/recipes-graphics/xorg-xserver/xserver-xorg_%.bbappend 
b/recipes-graphics/xorg-xserver/xserver-xorg_%.bbappend
index a5a6af3..6fd17da 100644
--- a/recipes-graphics/xorg-xserver/xserver-xorg_%.bbappend
+++ b/recipes-graphics/xorg-xserver/xserver-xorg_%.bbappend
@@ -7,3 +7,5 @@ PACKAGECONFIG_rpi ?= " \
 ${@bb.utils.contains("DISTRO_FEATURES", "wayland", "xwayland", "", d)} \
 ${@bb.utils.contains("DISTRO_FEATURES", "systemd", "systemd", "", d)} \
 "
+
+XSERVER_RRECOMMENDS_append = " xf86-input-libinput"
-- 
2.7.4

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

[yocto] [meta-raspberrypi][morty][PATCH 1/2] xserver-xf86-config: remove evdev configuration

2017-04-23 Thread Yusuke Mitsuki 
From: Andreas Müller <schnitzelt...@googlemail.com>

xorg-xserver recommends xf86-input-libinput since oe-core's commit

| commit 2d005faff6341a81a2afae28860101ba9db51ae8
| Author: Jussi Kukkonen <jussi.kukko...@intel.com>
| Date:   Wed Oct 26 11:37:38 2016 +0300
|
|conf: Use xf86-input-libinput by default
| ...

As nice side effect warnings for missing evdev in Xorg.0.log are gone.

Signed-off-by: Andreas Müller <schnitzelt...@googlemail.com>
Signed-off-by: Yusuke Mitsuki <mickey.happygolu...@gmail.com>
---
 .../rpi/xorg.conf.d/10-evdev.conf  | 40 --
 .../xorg-xserver/xserver-xf86-config_0.1.bbappend  | 22 ++--
 2 files changed, 10 insertions(+), 52 deletions(-)
 delete mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/10-evdev.conf

diff --git 
a/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/10-evdev.conf
 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/10-evdev.conf
deleted file mode 100644
index cc83ab2..000
--- 
a/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/10-evdev.conf
+++ /dev/null
@@ -1,40 +0,0 @@
-#
-# Catch-all evdev loader for udev-based systems
-# We don't simply match on any device since that also adds accelerometers
-# and other devices that we don't really want to use. The list below
-# matches everything but joysticks.
-
-Section "InputClass"
-Identifier "evdev pointer catchall"
-MatchIsPointer "on"
-MatchDevicePath "/dev/input/event*"
-Driver "evdev"
-EndSection
-
-Section "InputClass"
-Identifier "evdev keyboard catchall"
-MatchIsKeyboard "on"
-MatchDevicePath "/dev/input/event*"
-Driver "evdev"
-EndSection
-
-Section "InputClass"
-Identifier "evdev touchpad catchall"
-MatchIsTouchpad "on"
-MatchDevicePath "/dev/input/event*"
-Driver "evdev"
-EndSection
-
-Section "InputClass"
-Identifier "evdev tablet catchall"
-MatchIsTablet "on"
-MatchDevicePath "/dev/input/event*"
-Driver "evdev"
-EndSection
-
-Section "InputClass"
-Identifier "evdev touchscreen catchall"
-MatchIsTouchscreen "on"
-MatchDevicePath "/dev/input/event*"
-Driver "evdev"
-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 062de2d..b361eef 100644
--- a/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
+++ b/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
@@ -1,19 +1,17 @@
 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
 
-SRC_URI_append_rpi = " file://xorg.conf.d/10-evdev.conf \
-   file://xorg.conf.d/98-pitft.conf \
-   file://xorg.conf.d/99-calibration.conf \
- "
+SRC_URI_append_rpi = " \
+file://xorg.conf.d/98-pitft.conf \
+file://xorg.conf.d/99-calibration.conf \
+"
 
 do_install_append_rpi () {
-   install -d ${D}/${sysconfdir}/X11/xorg.conf.d/
-   install -m 0644 ${WORKDIR}/xorg.conf.d/10-evdev.conf 
${D}/${sysconfdir}/X11/xorg.conf.d/
-
-   PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
-   if [ "${PITFT}" = "1" ]; then
-   install -m 0644 ${WORKDIR}/xorg.conf.d/98-pitft.conf 
${D}/${sysconfdir}/X11/xorg.conf.d/
-   install -m 0644 ${WORKDIR}/xorg.conf.d/99-calibration.conf 
${D}/${sysconfdir}/X11/xorg.conf.d/
-   fi
+PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
+if [ "${PITFT}" = "1" ]; then
+install -d ${D}/${sysconfdir}/X11/xorg.conf.d/
+install -m 0644 ${WORKDIR}/xorg.conf.d/98-pitft.conf 
${D}/${sysconfdir}/X11/xorg.conf.d/
+install -m 0644 ${WORKDIR}/xorg.conf.d/99-calibration.conf 
${D}/${sysconfdir}/X11/xorg.conf.d/
+fi
 }
 
 FILES_${PN}_rpi += "${sysconfdir}/X11/xorg.conf 
${sysconfdir}/X11/xorg.conf.d/*"
-- 
2.7.4

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

Re: [yocto] Raspberry Pi2 Fails to boot into LXDE.

2017-03-09 Thread Yusuke Mitsuki 
Hello Steve

Would you try to other HDMI display such as PC monitor.

I suspects two points as follows.

* You enabled KMS(such as vc4graphics in MACHINE_FEATURE)
* Your display has not EDID.

If your HDMI settings in config.txt such as follows. There is a high
possibility that your HDMI display does not have EDID.

```
hdmi_group=2
hdmi_mode=87
```

When your display has not EDID, KMS will fail in initalization.
In such case, you have to create EDID file manually.

I hope this helps.


2017/03/10 14:43 "Gary Thomas" :

> On 2017-03-10 01:55, Steve Plant wrote:
>
>> OK, I have spent the last day googling my heart out trying to find the
>> Xorg.log file without any luck.
>>
>>
>> The problem is that due to the rpi hanging on boot, the only way I can
>> access the SD card to look for the file is place
>> it in a USB SD card reader and use my VirtualBox based Debian to "ls"
>> directores etc.
>>
>> Having established that there is no file located at /var/log/Xorg.log
>> (there isn't a log directory) but there is a
>> symbolic link in the var directory - goes nowhere.
>>
>>
>> After goggling I discovered that the file could also be in the
>> ~/.local/share/xorg/Xorg.0.log, however if I try to look
>> there I get "permission denied" and cannot seem to get to the root
>> directory of the card and I can't find a way around
>> this as I'm trying to access this directory through the USB card reader.
>>
>>
>> Looked everywhere with no answers, Is there anyone who could help me
>> here??
>>
>
> /var/log is on a volatile file system (i.e. it does not live on the SD
> card)
>
> If you can get into your board via SSH, you can copy the file and send it
>
> 
>> 
>> *From:* Khem Raj 
>> *Sent:* Wednesday, 8 March 2017 5:17 p.m.
>> *To:* Steve Plant
>> *Cc:* yocto@yoctoproject.org
>> *Subject:* Re: [yocto] Raspberry Pi2 Fails to boot into LXDE.
>>
>> On 17-03-08 12:40:51, Steve Plant wrote:
>>
>>> Hi All,
>>>
>>>
>>> Very new to all this linux world, and especially Yocto.
>>>
>>>
>>> I'm working on a embedded project at the moment using a raspberry pi2
>>> board.
>>>
>>>
>>> I have used toaster with Morty 2.2 to compile an image
>>> using"rpi-basic-image", to this I have added the following bitbake
>>> variables:
>>>
>>> Bitbake variables
>>>
>>> DISTRO
>>> poky
>>> DL_DIR
>>> /home/steve/poky/downloads
>>> IMAGE_FSTYPES
>>> ext3 jffs2 tar.bz2 rpi-sdimg
>>> IMAGE_INSTALL_append
>>> packagegroup-core-x11-base packagegroup-lxde-base connman
>>> PACKAGE_CLASSES
>>> package_rpm
>>> SSTATE_DIR
>>> /home/steve/poky/sstate-cache
>>>
>>> DISABLE_OVERSCAN
>>> 1
>>> GPU_MEM_1024
>>> 512
>>>
>>> I have dd'ed the image to an SD card increased the sdb2 partition to the
>>> max size and powered up the rpi. Everything looks fine to start with, as it
>>> displays the four raspberrys in the top left, then the white "Yocto
>>> Project" splash screen complete with small blue dot to the side appears,
>>> the progress bar moves across to 100 percent, then the screen turns black
>>> with a white
>>>
>> cursor in the middle and it appears to freeze with only a very dim one
>> second flash of the "act" led.
>>
>>>
>>>
>>> I have then connected the 7" touchscreen and apart from the added
>>> multicolored square at the very beginning I get the exact same boot up
>>> problem, hangs on the black screen with white cursor (good to see its all
>>> resized correctly for the TfT through!!)
>>>
>>>
>>> Before adding the packagegroup-core-x11-base and packagegroup-lxde-base
>>> I successfully copied over and ran the rpi-basic-image with no problem,
>>> ending up with a usable console.
>>>
>>>
>>> Looking for any help here, I'm thinking I've missed adding a package, or
>>> some type of local.conf instruction. any suggestions would be
>>> appreciated.
>>>
>>
>> Can you send the content of /var/log/Xorg.log file ?
>>
>
>
> --
> 
> Gary Thomas |  Consulting for the
> MLB Associates  |Embedded world
> 
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto