date:20160513

[yocto] help

2016-05-13 Thread Chandrakanth Sherkhane (IC Nexus)

Dear Yocto mailing list,

 

We are IC Nexus Co. Ltd. in Taipei City - Taiwan, a developer and
manufacturer of ARM-based Embedded Single Board Computers and Smart LCD
Display products (on Android / Linux / Yocto Project). We are currently
selling our products with Yocto O.S. to our worldwide customers.

 

Could anyone help to provide more details for,

1. Yocto Virtual Keyboard in French language - is it available now?

2. If not available, when will it be available?

3. Is the Yocto Virtual Keyboard available in any other languages?

 

We will appreciate your quick reply - Thank you very much!

 

Kind Regards,

Chandrakanth Sherkhane

IC Nexus Co. Ltd.

Tel: +886-2-2789-1200 ext. 114

Email: c...@icnexus.com.tw

Web: http://www.icnexus.com.tw

 

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

Re: [yocto] help

2016-05-13 Thread Chris Z.



On Fri, May 13, 2016 at 9:25 AM, Chandrakanth Sherkhane (IC Nexus) <
c...@icnexus.com.tw> wrote:

> Dear Yocto mailing list,
>
>
>
> We are IC Nexus Co. Ltd. in Taipei City – Taiwan, a developer and
> manufacturer of ARM-based Embedded Single Board Computers and Smart LCD
> Display products (on Android / Linux / Yocto Project). We are currently
> selling our products with Yocto O.S. to our worldwide customers.
>
>
>
> Could anyone help to provide more details for,
>
> 1. Yocto Virtual Keyboard in French language - is it available now?
>
> 2. If not available, when will it be available?
>
> 3. Is the Yocto Virtual Keyboard available in any other languages?
>
>
>
> We will appreciate your quick reply - Thank you very much!
>
>
>
> Kind Regards,
>
> Chandrakanth Sherkhane
>
> IC Nexus Co. Ltd.
>
> Tel: +886-2-2789-1200 ext. 114
>
> Email: c...@icnexus.com.tw
>
> Web: http://www.icnexus.com.tw
>
>
>
> --
> ___
> 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] Antwort: Re: How to build a simple kernel modul

2016-05-13 Thread Esponde, Joel

Hi,

I guess you forgot to add your module to the image recipe:

IMAGE_INSTALL_append = " ledmodule"

If you are working on your module code, you may prefer to copy your module with
ssh to the target system and load it dynamically with commands like this:
$ scp
$BUILDDIR/tmp/work/-poky-linux-gnueabi/ledmodule/0.1-r0/ledmodule.ko
:/lib/modules//kernel/drivers/
$ ssh /sbin/depmod -a
$ ssh /sbin/modprobe ledmodule

Hope this helps !

Joël Esponde
Honeywell | Sensing and Productivity Solutions

De : s.jar...@esa-grimma.de [mailto:s.jar...@esa-grimma.de]
Envoyé : jeudi 12 mai 2016 14:43
À : Esponde, Joel
Objet : Antwort: Re: [yocto] How to build a simple kernel modul

Hej Joel,

Thanks for the template. But could it be that the recipe creates an empty or
non working package?

I call my modul "ledmodul". The compilation works fine. The object and ko files
are created. Under the kernel the ledmodule/0.1-r0 dir is created. The
"deploy-rpms" dir contains 4 rpm packages. The "kernel-module-ledmodule-..."
contains the ko file. I think this is fine.

I don't know how to include this modul. I found that the "local.conf" has to be
extended by:

KERNEL_MODULE_AUTOLOAD += "ledmodule"

By doing it nothings happens. My driver is not loaded. Seems my new modul is
not installed into the system. Maybe you can tell me how to include a driver
right into the system?

Regards from Germany!

Stefan Jaritz

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.

Von:"Esponde, Joel"
mailto:joel.espo...@honeywell.com>>
An:"pet...@technux.se"
mailto:pet...@technux.se>>,
"yocto@yoctoproject.org"
mailto:yocto@yoctoproject.org>>
Datum:10.05.2016 12:30
Betreff:Re: [yocto] How to build a simple kernel modul
Gesendet von:
yocto-boun...@yoctoproject.org

Hi,

And here is a hello world module example:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-skeleton/recipes-kernel/hello-mod

Joël Esponde
Honeywell | Sensing and Productivity Solutions

De : yocto-boun...@yoctoproject.org
[mailto:yocto-boun...@yoctoproject.org] De la part de Petter Mabäcker
Envoyé : mardi 10 mai 2016 06:51
À : yocto@yoctoproject.org
Objet : Re: [yocto] How to build a simple kernel modul

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 \
file://Makefile \
"
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

Re: [yocto] how to install a kernel module

2016-05-13 Thread Esponde, Joel

Hi,

FYI, image recipes are in recipes-core/images folders.
So if you created your own image recipe, my previous mail should answer your
need.

Otherwise, I don't know if you could just add this line to your local.conf
file...

IMAGE_INSTALL_append = " ledmodule"

The best way to know that your IMAGE_INSTALL variable is correctly set is to
call this bitbake command:

$ bitbake -e

Bitbake will output all the build environment variables and functions related
to your image recipe.
So you will be able to check with this command that IMAGE_INSTALL has
effectively your module name added to the list.

bitbake -e is a very important command when working with Yocto.

Regards,

Joël Esponde
Honeywell | Sensing and Productivity Solutions

De : yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] De
la part de s.jar...@esa-grimma.de
Envoyé : jeudi 12 mai 2016 16:32
À : yocto@yoctoproject.org
Objet : [yocto] how to install a kernel module

Hej

I created a recipe for a own modul. It's similar to the example given at:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-skeleton/recipes-kernel/hello-mod

I checked the bitbake process. A "kernel-module-" package is
created and filled with the ko-file.

Actually I am failing to bring the module into my image and run it. Are there a
special command for the "local.conf" or so?

How and where to include the module?

Regards!

Stefan Jaritz

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

Re: [yocto] help

2016-05-13 Thread Burton, Ross

On 13 May 2016 at 08:25, Chandrakanth Sherkhane (IC Nexus) <
c...@icnexus.com.tw> wrote:

> Could anyone help to provide more details for,
>
> 1. Yocto Virtual Keyboard in French language - is it available now?
>
> 2. If not available, when will it be available?
>
> 3. Is the Yocto Virtual Keyboard available in any other languages?
>

There's no such thing as the Yocto Virtual Keyboard.  I presume you mean
matchbox-keyboard.  Looking at the sources:

$ ls layouts/*xml
layouts/keyboard-dvorak.xmllayouts/keyboard-fi.xml
 layouts/keyboard-ru.xml  layouts/keyboard.xml
layouts/keyboard-extended.xml  layouts/keyboard-numpad.xml
 layouts/keyboard-us.xml

There's no French layout, but these should provide plenty of examples as to
how to build it yourself.  If you implement the layout, please consider
sending the patch so everyone else can use it.

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

Re: [yocto] help

2016-05-13 Thread Herman van Hazendonk

Alternatively when you are using meta-qt5 layer, you could use something 
like Maliit input framework (which is used by various distributions 
(Jolla/Sailfish/Ubuntu/LuneOS) as well).


https://github.com/meta-qt5/meta-qt5/tree/master/recipes-qt/maliit

Herrie

On 2016-05-13 11:26, Burton, Ross wrote:

On 13 May 2016 at 08:25, Chandrakanth Sherkhane (IC Nexus)
 wrote:


Could anyone help to provide more details for,

1. Yocto Virtual Keyboard in French language - is it available now?

2. If not available, when will it be available?

3. Is the Yocto Virtual Keyboard available in any other languages?


There's no such thing as the Yocto Virtual Keyboard.  I presume you
mean matchbox-keyboard.  Looking at the sources:

$ ls layouts/*xml
layouts/keyboard-dvorak.xmllayouts/keyboard-fi.xml
layouts/keyboard-ru.xml  layouts/keyboard.xml
layouts/keyboard-extended.xml  layouts/keyboard-numpad.xml
layouts/keyboard-us.xml

There's no French layout, but these should provide plenty of examples
as to how to build it yourself.  If you implement the layout, please
consider sending the patch so everyone else can use it.

Ross


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

[yocto] Antwort: RE: how to install a kernel module

2016-05-13 Thread S . Jaritz

Thanks for taking the time to help me

I tried your approach but it does not worked.

I tell what I figured out so far:

I.) checking the target system
1.) When flashing the images into my device and boot the system, the 
driver is not loaded.
2.) lsmod shows that there is no driver loaded
3.) modprobe tells me that there is no 'lib/modules' dir

II.) checking yocto
1.) Bitbake creates a package for my machine ("sama5d3xek") -> there are 
several packages; all are empty except the one with the "kernel-module-" 
prefix
2.) checking the "deploy/images" dir -> the module is not listed at the 
"*.manifest" file
3.) checking the "modules-*.tgz" file -> modules are in(like the ext4.ko) 
but not the ledmodule.ko

As far as I understand yocto and the meta-atmel layer there are "two" 
images build. One is the kernel and it goes under the "work/sama5d3xek..." 
dir. The other one is the rootfs and it goes under the "work/cortexahf..." 
dir. By using the module class for my ledmodule recipe yocto is generating 
it in the kernel dir.
I think I need to tell yocto in some way that it should include the module 
in the kernel(where the bb is placed) or at the rootfs (where the recipe 
is missing).
For me it seems that I have to rewrite my recipe. I delete the module 
class reference and adjust the install path to /lib/modules.
But it looks for me more as an workaround, because adding a own 
driver/module seems a common task which should be supported my yocto. I 
like to know the common way how to do it.

When checking the kernel package for the module the path for it is 
"/lib/modules/4.1.0_linux4sam.../extra/ledmodule.ko". The dir 
"/lib/modules/4.1.0_linux4sam.../" not exits at my target.

Regards!

Stefan Jaritz



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.



Von:"Esponde, Joel" 
An: "s.jar...@esa-grimma.de" , 
"yocto@yoctoproject.org" 
Datum:  13.05.2016 11:15
Betreff:RE: [yocto] how to install a kernel module



Hi,
 
FYI, image recipes are in recipes-core/images folders.
So if you created your own image recipe, my previous mail should answer 
your need.
 
Otherwise, I don’t know if you could just add this line to your local.conf 
file…
 
IMAGE_INSTALL_append = " ledmodule"
 
The best way to know that your IMAGE_INSTALL variable is correctly set is 
to call this bitbake command:
 
$ bitbake  -e
 
Bitbake will output all the build environment variables and functions 
related to your image recipe.
So you will be able to check with this command that IMAGE_INSTALL has 
effectively your module name added to the list.
 
bitbake -e is a very important command when working with Yocto.
 
Regards,
 
Joël Esponde
Honeywell | Sensing and Productivity Solutions
 
De : yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org
] De la part de s.jar...@esa-grimma.de
Envoyé : jeudi 12 mai 2016 16:32
À : yocto@yoctoproject.org
Objet : [yocto] how to install a kernel module
 
Hej 

I created a recipe for a own modul. It's similar to the example given at: 

http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-skeleton/recipes-kernel/hello-mod
 


I checked the bitbake process. A "kernel-module-" package is 
created and filled with the ko-file. 

Actually I am failing to bring the module into my image and run it. Are 
there a special command for the "local.conf" or so? 

How and where to include the module? 

Regards!

Stefan Jaritz


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, i

[yocto] Solved - Antwort: RE: how to install a kernel module

2016-05-13 Thread S . Jaritz

I solved that problem

Using 

IMAGE_INSTALL += "ledmodule"

instead of

IMAGE_INSTALL_append = " ledmodule"

caused that the module was installed.

I found the hint in

https://communities.intel.com/thread/56810?start=0&tstart=0

Thanks for the help. Maybe a tip in the recipe template "hello_mod" could 
help other people trying to build theire own modules.

Stefan Jaritz


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.



Von:Stefan Jaritz/User/ESA-Grimma/DE
An: "Esponde, Joel" , Christian Ege 

Kopie:  "yocto@yoctoproject.org" 
Datum:  13.05.2016 11:53
Betreff:Antwort: RE: [yocto] how to install a kernel module


Thanks for taking the time to help me

I tried your approach but it does not worked.

I tell what I figured out so far:

I.) checking the target system
1.) When flashing the images into my device and boot the system, the 
driver is not loaded.
2.) lsmod shows that there is no driver loaded
3.) modprobe tells me that there is no 'lib/modules' dir

II.) checking yocto
1.) Bitbake creates a package for my machine ("sama5d3xek") -> there are 
several packages; all are empty except the one with the "kernel-module-" 
prefix
2.) checking the "deploy/images" dir -> the module is not listed at the 
"*.manifest" file
3.) checking the "modules-*.tgz" file -> modules are in(like the ext4.ko) 
but not the ledmodule.ko

As far as I understand yocto and the meta-atmel layer there are "two" 
images build. One is the kernel and it goes under the "work/sama5d3xek..." 
dir. The other one is the rootfs and it goes under the "work/cortexahf..." 
dir. By using the module class for my ledmodule recipe yocto is generating 
it in the kernel dir.
I think I need to tell yocto in some way that it should include the module 
in the kernel(where the bb is placed) or at the rootfs (where the recipe 
is missing).
For me it seems that I have to rewrite my recipe. I delete the module 
class reference and adjust the install path to /lib/modules.
But it looks for me more as an workaround, because adding a own 
driver/module seems a common task which should be supported my yocto. I 
like to know the common way how to do it.

When checking the kernel package for the module the path for it is 
"/lib/modules/4.1.0_linux4sam.../extra/ledmodule.ko". The dir 
"/lib/modules/4.1.0_linux4sam.../" not exits at my target.

Regards!

Stefan Jaritz



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.




Von:"Esponde, Joel" 
An: "s.jar...@esa-grimma.de" , 
"yocto@yoctoproject.org" 
Datum:  13.05.2016 11:15
Betreff:RE: [yocto] how to install a kernel module



Hi,
 
FYI, image recipes are in recipes-core/images folders.
So if you created your own image recipe, my previous mail should answer 
your need.
 
Otherwise, I don’t know if you could just add this line to your local.conf 
file…
 
IMAGE_INSTALL_append = " ledmodule"
 
The best way to know that your IMAGE_INSTALL variable is correctly set is 
to call this bitbake c

Re: [yocto] Solved - Antwort: RE: how to install a kernel module

2016-05-13 Thread Esponde, Joel

Great news !

BTW, I am surprised about this result… IMAGE_INSTALL_append works for me…
And the link you provided tells that _append method is preferred to +=…

Joël Esponde
Honeywell | Sensing and Productivity Solutions

De : s.jar...@esa-grimma.de [mailto:s.jar...@esa-grimma.de]
Envoyé : vendredi 13 mai 2016 13:18
À : Esponde, Joel; k423...@gmail.com; yocto@yoctoproject.org
Objet : Solved - Antwort: RE: [yocto] how to install a kernel module

I solved that problem

Using

IMAGE_INSTALL += "ledmodule"

instead of

IMAGE_INSTALL_append = " ledmodule"

caused that the module was installed.

I found the hint in

https://communities.intel.com/thread/56810?start=0&tstart=0

Thanks for the help. Maybe a tip in the recipe template "hello_mod" could help 
other people trying to build theire own modules.

Stefan Jaritz


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.



Von:Stefan Jaritz/User/ESA-Grimma/DE
An:"Esponde, Joel" 
mailto:joel.espo...@honeywell.com>>, Christian Ege 
mailto:k423...@gmail.com>>
Kopie:"yocto@yoctoproject.org" 
mailto:yocto@yoctoproject.org>>
Datum:13.05.2016 11:53
Betreff:Antwort: RE: [yocto] how to install a kernel module



Thanks for taking the time to help me

I tried your approach but it does not worked.

I tell what I figured out so far:

I.) checking the target system
1.) When flashing the images into my device and boot the system, the driver is 
not loaded.
2.) lsmod shows that there is no driver loaded
3.) modprobe tells me that there is no 'lib/modules' dir

II.) checking yocto
1.) Bitbake creates a package for my machine ("sama5d3xek") -> there are 
several packages; all are empty except the one with the "kernel-module-" prefix
2.) checking the "deploy/images" dir -> the module is not listed at the 
"*.manifest" file
3.) checking the "modules-*.tgz" file -> modules are in(like the ext4.ko) but 
not the ledmodule.ko

As far as I understand yocto and the meta-atmel layer there are "two" images 
build. One is the kernel and it goes under the "work/sama5d3xek..." dir. The 
other one is the rootfs and it goes under the "work/cortexahf..." dir. By using 
the module class for my ledmodule recipe yocto is generating it in the kernel 
dir.
I think I need to tell yocto in some way that it should include the module in 
the kernel(where the bb is placed) or at the rootfs (where the recipe is 
missing).
For me it seems that I have to rewrite my recipe. I delete the module class 
reference and adjust the install path to /lib/modules.
But it looks for me more as an workaround, because adding a own driver/module 
seems a common task which should be supported my yocto. I like to know the 
common way how to do it.

When checking the kernel package for the module the path for it is 
"/lib/modules/4.1.0_linux4sam.../extra/ledmodule.ko". The dir 
"/lib/modules/4.1.0_linux4sam.../" not exits at my target.

Regards!

Stefan Jaritz



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

[yocto] autotools error when building libdbus-c++; autoreconf "possibly undefined macro: AC_DEFINE"

2016-05-13 Thread S . Jaritz

Hej

I try to build the libdbus-c++ libary. The build process is based on 
autotools. When compiling it  do_configure throws an error. The macro 
"AC_DEFINE" is not found. Any idea how to make autoreconf run?

Below I listed to recipe and after the Error plot

# libdbus-c++_0.9.bb ###
SUMMARY = "libdbus-c++"
SECTION = "ccc"
LICENSE = "GPLv2+"
LIC_FILES_CHKSUM = "file://COPYING;md5=fbc093901857fcd118f065f900982c24"

inherit autotools

SRC_URI[md5sum] = "e752116f523fa88ef041e63d3dee4de2"
SRC_URI[sha256sum] = 
"bc11ac297b3cb010be904c72789695543ee3fdf3d75cdc8225fd371385af4e61"
SRC_URI = "
https://sourceforge.net/projects/dbus-cplusplus/files/dbus-c++/0.9.0/libdbus-c++-0.9.0.tar.gz
"

S = "${WORKDIR}/libdbus-c++-0.9.0"

BBCLASSEXTEND += "native"


# Error ###
| autoreconf: Entering directory `.'
| autoreconf: configure.ac: not using Gettext
| autoreconf: running: aclocal 
--system-acdir=/home/user/myTC/poky/build/tmp/work/cortexa5hf-vfp-poky-linux-gnueabi/libdbus-c++/0.9-r0/build/aclocal-copy/
 
-I 
/home/user/myTC/poky/build/tmp/work/cortexa5hf-vfp-poky-linux-gnueabi/libdbus-c++/0.9-r0/libdbus-c++-0.9.0/m4/
 
-I 
/home/user/myTC/poky/build/tmp/work/cortexa5hf-vfp-poky-linux-gnueabi/libdbus-c++/0.9-r0/libdbus-c++-0.9.0/m4/
 
--force -I m4
| autoreconf: configure.ac: tracing
| autoreconf: running: libtoolize --copy --force
| libtoolize: putting auxiliary files in '.'.
| libtoolize: copying file './ltmain.sh'
| libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
| libtoolize: copying file 'm4/libtool.m4'
| libtoolize: copying file 'm4/ltoptions.m4'
| libtoolize: copying file 'm4/ltsugar.m4'
| libtoolize: copying file 'm4/ltversion.m4'
| libtoolize: copying file 'm4/lt~obsolete.m4'
| autoreconf: running: 
/home/user/myTC/poky/build/tmp/sysroots/x86_64-linux/usr/bin/autoconf 
--include=/home/user/myTC/poky/build/tmp/work/cortexa5hf-vfp-poky-linux-gnueabi/libdbus-c++/0.9-r0/libdbus-c++-0.9.0/m4/
 
--force
| configure.ac:54: error: possibly undefined macro: AC_DEFINE
|   If this token and others are legitimate, please use 
m4_pattern_allow.
|   See the Autoconf documentation.
| autoreconf: 
/home/user/myTC/poky/build/tmp/sysroots/x86_64-linux/usr/bin/autoconf 
failed with exit status: 1


Mit freundlichen Grüßen

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.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] autotools error when building libdbus-c++; autoreconf "possibly undefined macro: AC_DEFINE"

2016-05-13 Thread Burton, Ross

On 13 May 2016 at 15:21,  wrote:

> I try to build the libdbus-c++ libary. The build process is based on
> autotools. When compiling it  do_configure throws an error. The macro
> "AC_DEFINE" is not found. Any idea how to make autoreconf run?
>

Try also inheriting pkgconfig.  I've noticed that if the pkgconfig macros
are not present then autoreconf fails in *very* strange ways.

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

[yocto] Yocto Project Status WW20

2016-05-13 Thread Jolley, Stephen K

Current Dev Position: YP 2.2 M1
Next Deadline: YP 2.2 cut off: June 13, 2016

SWAT team rotation: Juro -> Anibal
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Key Status/Updates:

  *   The bitbake python3 branch is nearing readiness, the OE-Core branch is 
not quite at the same level of cleanliness but has the functionality and just 
needs cleanup. Known issues remaining are toaster and various tools in 
scripts/, help in testing would be most welcome as we have found several distro 
specific issues so far.
  *   With python3, basic image execution is known to work, as is testimage 
(qemu runtime testing) and basic oe-selftests.
  *   We have various significant changes from Khem such as gcc 6, glibc 
upgrade and so on. A portion of these have merged into master, the rest should 
enter -next for testing over the weekend.
  *   We now have automated BuildLog generation in the wiki to help our build 
triage (SWAT) process which starts the process improvements planned in 2.2 
(thanks Joshua!)
  *   There was a nice cleanup to staging.bbclass from Peter (thanks!)
  *   There is a good discussion happening on the architecture list about 
trying to come up with a standardized way of defining builds and possibly 
handling layer checkout. Please join the discussion if interested.
  *   WDD continues to rise :(
  *   YP 1.8.2 is now in QA
  *   meta-intel 5.0 should finish QA today

Key YP 2.2 Dates:

  *   YP 2.2 M1 cut off would be: 6/13/16
  *   YP 2.2 M1 release would be: 6/24/16
  *   YP 2.2 M2 cut off would be: 7/18/16
  *   YP 2.2 M2 release would be: 7/29/16
  *   YP 2.2 M3 cut off would be: 8/29/16
  *   YP 2.2 M3 release would be: 9/9/16
  *   YP 2.2 M4 cut off would be: 10/3/16
  *   YP 2.2 M4 release would be: 10/28/16

Tracking Metrics:
WDD 2618 (last week 2532)
(https://wiki.yoctoproject.org/charts/combo.html)

Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.2_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.2_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.2_Features

[If anyone has suggestions for other information you'd like to see on this 
weekly status update, let us know!]

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone:(503) 712-0534
*Cell:   (208) 244-4460
* Email:stephen.k.jol...@intel.com

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

[yocto] errors.yoctoproject

2016-05-13 Thread akuster808

Do I need an account enabled to submit to errors.yoctoproject?

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

[yocto] [meta-raspberrypi][PATCH 2/2] firmware: Update to "20160512" snapshot

2016-05-13 Thread Khem Raj

Signed-off-by: Khem Raj 
---
 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 8f095b9..bf11e4c 100644
--- a/recipes-bsp/common/firmware.inc
+++ b/recipes-bsp/common/firmware.inc
@@ -1,5 +1,5 @@
-RPIFW_SRCREV ?= "c5e131971c323f5658c7c5d4b1dd105d37903a99"
-RPIFW_DATE ?= "20160421"
+RPIFW_SRCREV ?= "3816e1ce1e6ebc6d2bf0596dbd52849e16aa7e94"
+RPIFW_DATE ?= "20160512"
 RPIFW_SRC_URI ?= 
"git://github.com/raspberrypi/firmware.git;protocol=git;branch=master"
 RPIFW_S ?= "${WORKDIR}/git"
 
-- 
2.8.2

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

[yocto] [meta-raspberrypi][PATCH 1/2] userland: Update to tip of tree

2016-05-13 Thread Khem Raj

Drop the patch which is upstreamed slightly differently
use VMCS_INSTALL_PREFIX to /usr via EXTRA_OECMAKE

Signed-off-by: Khem Raj 
---
 .../0001-set-VMCS_INSTALL_PREFIX-to-usr.patch  | 28 --
 recipes-graphics/userland/userland_git.bb  |  6 ++---
 2 files changed, 3 insertions(+), 31 deletions(-)
 delete mode 100644 
recipes-graphics/userland/userland/0001-set-VMCS_INSTALL_PREFIX-to-usr.patch

diff --git 
a/recipes-graphics/userland/userland/0001-set-VMCS_INSTALL_PREFIX-to-usr.patch 
b/recipes-graphics/userland/userland/0001-set-VMCS_INSTALL_PREFIX-to-usr.patch
deleted file mode 100644
index 5165288..000
--- 
a/recipes-graphics/userland/userland/0001-set-VMCS_INSTALL_PREFIX-to-usr.patch
+++ /dev/null
@@ -1,28 +0,0 @@
-From b653ef9e770bd9e4976c058405b94b75873d2508 Mon Sep 17 00:00:00 2001
-From: Khem Raj 
-Date: Sun, 9 Aug 2015 23:58:17 -0700
-Subject: [PATCH 01/13] set VMCS_INSTALL_PREFIX to /usr
-
-in OE we dont use /opt/vc but standard prefix
-
-Signed-off-by: Khem Raj 

- makefiles/cmake/vmcs.cmake | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/makefiles/cmake/vmcs.cmake b/makefiles/cmake/vmcs.cmake
-index 0f8641b..e9d576d 100644
 a/makefiles/cmake/vmcs.cmake
-+++ b/makefiles/cmake/vmcs.cmake
-@@ -10,7 +10,7 @@ INCLUDE(CPack)
- if (ANDROID)
-   SET(VMCS_INSTALL_PREFIX "/vendor/brcm/islands" CACHE PATH "Prefix prepended 
to install directories" FORCE)
- else()
--  SET(VMCS_INSTALL_PREFIX "/opt/vc" CACHE PATH "Prefix prepended to install 
directories" FORCE)
-+  SET(VMCS_INSTALL_PREFIX "/usr" CACHE PATH "Prefix prepended to install 
directories" FORCE)
- endif()
- 
- SET(CMAKE_INSTALL_PREFIX "${VMCS_INSTALL_PREFIX}" CACHE INTERNAL "Prefix
--- 
-2.7.4
-
diff --git a/recipes-graphics/userland/userland_git.bb 
b/recipes-graphics/userland/userland_git.bb
index 0e7057e..7acd8b8 100644
--- a/recipes-graphics/userland/userland_git.bb
+++ b/recipes-graphics/userland/userland_git.bb
@@ -16,11 +16,10 @@ COMPATIBLE_MACHINE = "raspberrypi"
 
 SRCBRANCH = "master"
 SRCFORK = "raspberrypi"
-SRCREV = "703a2c4b35e23ee44ad84db6b9c3f89c0a627143"
+SRCREV = "17c28b9d1d234893b73adeb95efc4959b617fc85"
 
 SRC_URI = "\
 git://github.com/${SRCFORK}/userland.git;protocol=git;branch=${SRCBRANCH} \
-file://0001-set-VMCS_INSTALL_PREFIX-to-usr.patch \
 file://0002-cmake-generate-and-install-pkgconfig-files.patch \
 file://0003-Allow-applications-to-set-next-resource-handle.patch \
 file://0004-wayland-Add-support-for-the-Wayland-winsys.patch \
@@ -41,7 +40,8 @@ S = "${WORKDIR}/git"
 inherit cmake pkgconfig
 
 EXTRA_OECMAKE = "-DCMAKE_BUILD_TYPE=Release 
-DCMAKE_EXE_LINKER_FLAGS='-Wl,--no-as-needed' \
-"
+ -DVMCS_INSTALL_PREFIX=${exec_prefix} \
+"
 
 PACKAGECONFIG ?= "${@bb.utils.contains('DISTRO_FEATURES', 'wayland', 
'wayland', '', d)}"
 
-- 
2.8.2

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

Re: [yocto] errors.yoctoproject

2016-05-13 Thread Khem Raj

don’t think so

just do

echo `git config --get user.name` > ${HOME}/.oe-send-error
echo `git config --get user.email` >> ${HOME}/.oe-send-error

and it should be able to send

> On May 13, 2016, at 8:34 AM, akuster808  wrote:
> 
> Do I need an account enabled to submit to errors.yoctoproject?
> 
> - armin
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 0/1] Support for .dtbo files for dtb overlays, required by firmware after 2016/04/12

2016-05-13 Thread Herve Jourdain

The firmware after 2016/04/12 () seems to have altered the behavior of device 
tree loading on RaspberryPi: for overlays, it loads only .dtbo files, not .dtb 
anymore.
Also, it does not check for -overlay extension, so the name of the overlay that 
is placed in the "overlays" directory must be .dtbo, instead of 
-overlay.dtb.

This patch tries to address this issue for 4.4 and 4.1 kernels.
It must be used in conjunction with another patch to 
meta/recipes-kernel/linux-dtb.inc, which will allow the processing of .dtbo 
files, instead of only .dtb.

.dtb are still used, but only for the "real" device trees (not the overlays).

This is in line with the behavior of kernels 4.4.6+

Herve Jourdain (1):
  Support for .dtbo files for dtb overlays, required by firmware after
2016/04/12

 classes/linux-raspberrypi-base.bbclass |  4 +--
 classes/sdcard_image-rpi.bbclass   |  6 ++--
 conf/machine/include/rpi-base.inc  | 30 +--
 .../0002-fix-dtbo-rules.patch  | 35 ++
 .../0001-fix-dtbo-rules.patch  | 13 
 recipes-kernel/linux/linux-raspberrypi_4.1.bb  |  1 +
 recipes-kernel/linux/linux-raspberrypi_4.4.bb  |  1 +
 7 files changed, 70 insertions(+), 20 deletions(-)
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi-4.1/0002-fix-dtbo-rules.patch
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch

-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH 1/1] Support for .dtbo files for dtb overlays, required by firmware after 2016/04/12

2016-05-13 Thread Herve Jourdain

Signed-off-by: Herve Jourdain 
---
 classes/linux-raspberrypi-base.bbclass |  4 +--
 classes/sdcard_image-rpi.bbclass   |  6 ++--
 conf/machine/include/rpi-base.inc  | 30 +--
 .../0002-fix-dtbo-rules.patch  | 35 ++
 .../0001-fix-dtbo-rules.patch  | 13 
 recipes-kernel/linux/linux-raspberrypi_4.1.bb  |  1 +
 recipes-kernel/linux/linux-raspberrypi_4.4.bb  |  1 +
 7 files changed, 70 insertions(+), 20 deletions(-)
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi-4.1/0002-fix-dtbo-rules.patch
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch

diff --git a/classes/linux-raspberrypi-base.bbclass 
b/classes/linux-raspberrypi-base.bbclass
index 40beef1..f2f0a5a 100644
--- a/classes/linux-raspberrypi-base.bbclass
+++ b/classes/linux-raspberrypi-base.bbclass
@@ -32,8 +32,8 @@ def get_dts(d, ver):
 def split_overlays(d, out):
 dts = get_dts(d, None)
 if out:
-overlays = oe.utils.str_filter_out('\S+\-overlay\.dtb$', dts, d)
+overlays = oe.utils.str_filter_out('\S+\.dtbo$', dts, d)
 else:
-overlays = oe.utils.str_filter('\S+\-overlay\.dtb$', dts, d)
+overlays = oe.utils.str_filter('\S+\.dtbo$', dts, d)
 
 return overlays
diff --git a/classes/sdcard_image-rpi.bbclass b/classes/sdcard_image-rpi.bbclass
index 4dfd7a3..e510ce0 100644
--- a/classes/sdcard_image-rpi.bbclass
+++ b/classes/sdcard_image-rpi.bbclass
@@ -110,7 +110,7 @@ IMAGE_CMD_rpi-sdimg () {
;;
*)
if test -n "${DTS}"; then
-   # Device Tree Overlays are assumed to be suffixed by 
'-overlay.dtb' string and will be put in a dedicated folder
+   # Device Tree Overlays are assumed to be suffixed by 
'.dtbo' string and will be put in a dedicated folder
DT_OVERLAYS="${@split_overlays(d, 0)}"
DT_ROOT="${@split_overlays(d, 1)}"
 
@@ -124,9 +124,9 @@ IMAGE_CMD_rpi-sdimg () {
# Copy device tree overlays to dedicated folder
mmd -i ${WORKDIR}/boot.img overlays
for DTB in ${DT_OVERLAYS}; do
-   DTB_BASE_NAME=`basename ${DTB} .dtb`
+   DTB_BASE_NAME=`basename ${DTB} ".dtbo"`
 
-   mcopy -i ${WORKDIR}/boot.img -s 
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${DTB_BASE_NAME}.dtb 
::overlays/${DTB_BASE_NAME}.dtb
+   mcopy -i ${WORKDIR}/boot.img -s 
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${DTB_BASE_NAME}.dtbo 
::overlays/${DTB_BASE_NAME}.dtbo
done
fi
mcopy -i ${WORKDIR}/boot.img -s 
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}${KERNEL_INITRAMFS}-${MACHINE}.bin 
::${SDIMG_KERNELIMAGE}
diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index 56ca83e..47eb23b 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -22,21 +22,21 @@ KERNEL_DEVICETREE ?= " \
 bcm2709-rpi-2-b.dtb \
 bcm2710-rpi-3-b.dtb \
 \
-overlays/hifiberry-amp-overlay.dtb \
-overlays/hifiberry-dac-overlay.dtb \
-overlays/hifiberry-dacplus-overlay.dtb \
-overlays/hifiberry-digi-overlay.dtb \
-overlays/i2c-rtc-overlay.dtb \
-overlays/iqaudio-dac-overlay.dtb \
-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/rpi-ft5406-overlay.dtb \
-overlays/w1-gpio-overlay.dtb \
-overlays/w1-gpio-pullup-overlay.dtb \
-overlays/pi3-miniuart-bt-overlay.dtb \
+overlays/hifiberry-amp.dtbo \
+overlays/hifiberry-dac.dtbo \
+overlays/hifiberry-dacplus.dtbo \
+overlays/hifiberry-digi.dtbo \
+overlays/i2c-rtc.dtbo \
+overlays/iqaudio-dac.dtbo \
+overlays/iqaudio-dacplus.dtbo \
+overlays/lirc-rpi.dtbo \
+overlays/pitft22.dtbo \
+overlays/pitft28-resistive.dtbo \
+overlays/pps-gpio.dtbo \
+overlays/rpi-ft5406.dtbo \
+overlays/w1-gpio.dtbo \
+overlays/w1-gpio-pullup.dtbo \
+overlays/pi3-miniuart-bt.dtbo \
 "
 KERNEL_IMAGETYPE ?= "Image"
 
diff --git 
a/recipes-kernel/linux/linux-raspberrypi-4.1/0002-fix-dtbo-rules.patch 
b/recipes-kernel/linux/linux-raspberrypi-4.1/0002-fix-dtbo-rules.patch
new file mode 100644
index 000..25564c2
--- /dev/null
+++ b/recipes-kernel/linux/linux-raspberrypi-4.1/0002-fix-dtbo-rules.patch
@@ -0,0 +1,35 @@
+diff --git a/arch/arm/Makefile b/arch/arm/Makefile
+index afd559d..06819fd 100644
+--- a/arch/arm/Makefile
 b/arch/arm/Makefile
+@@ -322,6 +322,8 @@ $(INSTALL_TARGETS):
+ 
+ %.dtb: | scripts
+   $(Q)$(MAKE) $(build)=$(boot)/dts MACHINE=$(MACHINE) $(boot)/dts/$@
++%.dtbo: | scripts

[yocto] [PATCH 1/1] Support for .dtbo files for dtb overlays

2016-05-13 Thread Herve Jourdain

Signed-off-by: Herve Jourdain 
---
 meta/recipes-kernel/linux/linux-dtb.inc | 66 +
 1 file changed, 35 insertions(+), 31 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-dtb.inc 
b/meta/recipes-kernel/linux/linux-dtb.inc
index 651a19e..44782d8 100644
--- a/meta/recipes-kernel/linux/linux-dtb.inc
+++ b/meta/recipes-kernel/linux/linux-dtb.inc
@@ -31,44 +31,48 @@ do_compile_append() {
 }
 
 do_install_append() {
-   for DTB in ${KERNEL_DEVICETREE}; do
-   DTB=`normalize_dtb "${DTB}"`
-   DTB_BASE_NAME=`basename ${DTB} .dtb`
-   DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed 
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
-   DTB_PATH=`get_real_dtb_path_in_kernel "${DTB}"`
-   install -m 0644 ${DTB_PATH} 
${D}/${KERNEL_IMAGEDEST}/devicetree-${DTB_SYMLINK_NAME}.dtb
-   done
+for DTB in ${KERNEL_DEVICETREE}; do
+DTB=`normalize_dtb "${DTB}"`
+DTB_EXT=${DTB##*.}
+DTB_BASE_NAME=`basename ${DTB} ".${DTB_EXT}"`
+DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed 
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
+DTB_PATH=`get_real_dtb_path_in_kernel "${DTB}"`
+install -m 0644 ${DTB_PATH} 
${D}/${KERNEL_IMAGEDEST}/devicetree-${DTB_SYMLINK_NAME}.${DTB_EXT}
+done
 }
 
 do_deploy_append() {
-   for DTB in ${KERNEL_DEVICETREE}; do
-   DTB=`normalize_dtb "${DTB}"`
-   DTB_BASE_NAME=`basename ${DTB} .dtb`
-   DTB_NAME=`echo ${KERNEL_IMAGE_BASE_NAME} | sed 
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
-   DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed 
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
-   DTB_PATH=`get_real_dtb_path_in_kernel "${DTB}"`
-   install -d ${DEPLOYDIR}
-   install -m 0644 ${DTB_PATH} ${DEPLOYDIR}/${DTB_NAME}.dtb
-   ln -sf ${DTB_NAME}.dtb ${DEPLOYDIR}/${DTB_SYMLINK_NAME}.dtb
-   done
+for DTB in ${KERNEL_DEVICETREE}; do
+DTB=`normalize_dtb "${DTB}"`
+DTB_EXT=${DTB##*.}
+DTB_BASE_NAME=`basename ${DTB} ".${DTB_EXT}"`
+DTB_NAME=`echo ${KERNEL_IMAGE_BASE_NAME} | sed 
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
+DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed 
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
+DTB_PATH=`get_real_dtb_path_in_kernel "${DTB}"`
+install -d ${DEPLOYDIR}
+install -m 0644 ${DTB_PATH} ${DEPLOYDIR}/${DTB_NAME}.${DTB_EXT}
+ln -sf ${DTB_NAME}.${DTB_EXT} 
${DEPLOYDIR}/${DTB_SYMLINK_NAME}.${DTB_EXT}
+done
 }
 
 pkg_postinst_kernel-devicetree () {
-   cd /${KERNEL_IMAGEDEST}
-   for DTB in ${KERNEL_DEVICETREE}
-   do
-   DTB_BASE_NAME=`basename ${DTB} | awk -F "." '{print $1}'`
-   DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed 
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
-   update-alternatives --install 
/${KERNEL_IMAGEDEST}/${DTB_BASE_NAME}.dtb ${DTB_BASE_NAME}.dtb 
/boot/devicetree-${DTB_SYMLINK_NAME}.dtb ${KERNEL_PRIORITY} || true
-   done
+cd /${KERNEL_IMAGEDEST}
+for DTB in ${KERNEL_DEVICETREE}
+do
+DTB_EXT=${DTB##*.}
+DTB_BASE_NAME=`basename ${DTB} | awk -F "." '{print $1}'`
+DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed 
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
+update-alternatives --install 
/${KERNEL_IMAGEDEST}/${DTB_BASE_NAME}.${DTB_EXT} ${DTB_BASE_NAME}.${DTB_EXT} 
/boot/devicetree-${DTB_SYMLINK_NAME}.${DTB_EXT} ${KERNEL_PRIORITY} || true
+done
 }
 
 pkg_postrm_kernel-devicetree () {
-   cd /${KERNEL_IMAGEDEST}
-   for DTB in ${KERNEL_DEVICETREE}
-   do
-   DTB_BASE_NAME=`basename ${DTB} | awk -F "." '{print $1}'`
-   DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed 
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
-   update-alternatives --remove ${DTB_BASE_NAME}.dtb 
/boot/devicetree-${DTB_SYMLINK_NAME}.dtb ${KERNEL_PRIORITY} || true
-   done
+cd /${KERNEL_IMAGEDEST}
+for DTB in ${KERNEL_DEVICETREE}
+do
+DTB_EXT=${DTB##*.}
+DTB_BASE_NAME=`basename ${DTB} | awk -F "." '{print $1}'`
+DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed 
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
+update-alternatives --remove ${DTB_BASE_NAME}.${DTB_EXT} 
/boot/devicetree-${DTB_SYMLINK_NAME}.${DTB_EXT} ${KERNEL_PRIORITY} || true
+done
 }
-- 
2.7.4

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

[yocto] [PATCH 0/1] Support for .dtbo files for dtb overlays

2016-05-13 Thread Herve Jourdain

Recent kernels tend to use .dtbo files for device tree overlays, instead of 
.dtb before.
.dtb are still used, but only for the "real" device trees (not the overlays).

On some platforms (meta-raspberrypi for instance), recent firmware only loads 
.dtbo files for overlays.

This patch tries to address this issue, while not breaking support for .dtb 
overlays.
It allows the installation/deployment of both .dtb and .dtbo files, for device 
trees and overlays.

This is in line with the behavior of kernels 4.4.6+

Herve Jourdain (1):
  Support for .dtbo files for dtb overlays

 meta/recipes-kernel/linux/linux-dtb.inc | 66 +
 1 file changed, 35 insertions(+), 31 deletions(-)

-- 
2.7.4

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

[yocto] help

Re: [yocto] help

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

Re: [yocto] how to install a kernel module

Re: [yocto] help

Re: [yocto] help

[yocto] Antwort: RE: how to install a kernel module

[yocto] Solved - Antwort: RE: how to install a kernel module

Re: [yocto] Solved - Antwort: RE: how to install a kernel module

[yocto] autotools error when building libdbus-c++; autoreconf "possibly undefined macro: AC_DEFINE"

Re: [yocto] autotools error when building libdbus-c++; autoreconf "possibly undefined macro: AC_DEFINE"

[yocto] Yocto Project Status WW20

[yocto] errors.yoctoproject

[yocto] [meta-raspberrypi][PATCH 2/2] firmware: Update to "20160512" snapshot

[yocto] [meta-raspberrypi][PATCH 1/2] userland: Update to tip of tree

Re: [yocto] errors.yoctoproject

[yocto] [meta-raspberrypi][PATCH 0/1] Support for .dtbo files for dtb overlays, required by firmware after 2016/04/12

[yocto] [meta-raspberrypi][PATCH 1/1] Support for .dtbo files for dtb overlays, required by firmware after 2016/04/12

[yocto] [PATCH 1/1] Support for .dtbo files for dtb overlays

[yocto] [PATCH 0/1] Support for .dtbo files for dtb overlays

20 matches

Site Navigation

Mail list logo

Footer information