Re: [yocto] [meta-raspberrypi][PATCH v6 0/4] Support for .dtbo files for dtb overlays, required by kernels 4.4.6+
On Thu, Jul 28, 2016 at 06:41:25PM -0700, Khem Raj wrote: > > > On Jul 20, 2016, at 3:00 PM, Herve Jourdain wrote: > > > > v6: rebased > > > > v5: modifications after more review > > * Added an Upstream-Status to the kernel patch > > * Only one instance of KERNEL_DEVICETREE defined (with the new .dtbo syntax) > > * Modification of the KERNEL_DEVICETREE is done in > > linux-raspberry-base.bbclass, based on the kernel version > > > > v4: rebased > > For kernels 4.4.9+, the behavior for the device tree overlays loading has > > been modified on RaspberryPi. > > For overlays, it loads .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 addresses the issue for kernels 4.4+, while keeping the same > > behavior for older kernels. > > This patch must be used in conjunction with another patch to > > meta/recipes-kernel/linux-dtb.inc, which will allow the processing of .dtbo > > files for overlays, instead of only .dtb like before. > > > > .dtb are still in use, but only for the "real" device trees (not the > > overlays). > > I have staged this series in > > https://github.com/kraj/meta-raspberrypi kraj/master > > However, this all has to wait on two things. > > The OE-core patch > > https://patchwork.openembedded.org/patch/123747/ > What is happening with this patch? So I can't merge these as long as this one is not merged. > and we need to branch out for krogoth > > > > > Herve Jourdain (4): > > linux-raspberrypi_4.4.bb: support for .dtbo files for dtb overlays > > rpi-base.inc: support for .dtbo files for dtb overlays > > linux-raspberrypi-base.bbclass: support for .dtbo files for dtb > >overlays > > sdcard_image-rpi.bbclass: support for .dtbo files for dtb overlays > > > > classes/linux-raspberrypi-base.bbclass | 19 ++ > > classes/sdcard_image-rpi.bbclass | 15 +--- > > conf/machine/include/rpi-base.inc | 30 +++ > > .../0001-fix-dtbo-rules.patch | 44 > > ++ > > recipes-kernel/linux/linux-raspberrypi_4.4.bb | 1 + > > 5 files changed, 81 insertions(+), 28 deletions(-) > > 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 mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- Andrei Gherzan signature.asc Description: PGP signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH v4 00/12] Support for VC4 graphics driver
On Thu, Jul 21, 2016 at 08:32:05PM +0800, Herve Jourdain wrote:
> v4 series:
> a. rebased
> b. Upstream-Status added to the patch to the VC4 driver (needed only for
> kernel 4.4, accepted upstream in 4.7)
>
> v3 series:
> a. patch rebased
> b. new revision of kernel, to get a version of the VC4 graphics driver that
> handles render nodes
> c. patch to the VC4 driver to enable proper working of the render nodes (need
> to add authorization for IOCTLs)
>
> v2 series:
> a. Fix the 4.4.10 kernel revision
> b. Effectively add vc4-kms-v3d overlay to the list of overlays to build
> (forgotten previously)
> c. Make the parameter to the v4c-kms-v3d overlay configurable
> d. Add default values for the cma parameter to the v4c-kms-v3d overlay,
> depending on the board (and the memory it has)
>
> This patch series enables the support for the VC4 graphics driver from Eric
> Anholt.
> There was a previous patch series by Javier Martinez Canillas, but it
> required use of a different kernel.
> VC4 is now supported in the raspberrypi official kernel, at least for 4.4.9+.
> The support in 4.1 exists, but it is NOT STABLE, so it has been deemed
> unreasonable to support VC4 with 4.1 kernels.
>
> THEREFORE, VC4 graphics is supported ONLY for kernel versions 4.4.9 and later.
>
> This patch series proposes to support VC4 by only adding 'vc4graphics' to
> MACHINE_FEATURES, for raspberrypi. If this is set, it will trigger all the
> necessary configuration/changes to use the VC4 driver, including
> mesa/wayland/weston currently, and adding the overlay required.
> In order for this series to work, some previous patches are needed (support
> for .dtbo, and fix of the mesa packaging when there is no DRI driver).
> The memory reserved for the VC4 driver has default values depending on the
> version of the board used, but it can be configured by setting VC4_CMA_SIZE
> to a value supported by the overlay ('cma-256', 'cma-192', 'cma-128',
> 'cma-96', 'cma-64').
> 'cma-256' is the recommended value, but it might not be possible on boards
> with 512MB or DRAM, or less...
> 'cma-64' is known to not being able to support FHD/1080p.
>
> It was tested with wayland/weston, without the support for X11.
>
> This patch series depends on two other patch series previously posted, that
> enable the support for .dtbo overlay files.
>
> Herve Jourdain (12):
> rpi-default-providers.inc: change default providers to support
> vc4graphics
> rpi-base.inc: add vc4-kms-v3d to the overlays to support vc4graphics
> raspberrypi.conf: set the default value of VC4_CMA_SIZE to support
> vc4graphics
> raspberrypi0.conf: set the default value of VC4_CMA_SIZE to support
> vc4graphics
> raspberrypi2.conf: set the default value of VC4_CMA_SIZE to support
> vc4graphics
> raspberrypi3.conf: set the default value of VC4_CMA_SIZE to support
> vc4graphics
> rpi-config_git.bb: add v4c overlay to config.txt to support
> vc4graphics
> wayland/weston_%.bbappend: modify configuration options to support
> vc4graphics
> weston/weston_%.bbappend: modify configuration options to support
> vc4graphics
> mesa_%.bbappend: new file to add the correct configuration options to
> support vc4graphics
> linux-rpi.inc: add the configuration options required to support
> vc4graphics
> linux-raspberrypi-4.4: add patch to enable proper operation of
> renderD128 device
>
> conf/machine/include/rpi-base.inc | 1 +
> conf/machine/include/rpi-default-providers.inc | 8 +++---
> conf/machine/raspberrypi.conf | 2 ++
> conf/machine/raspberrypi0.conf | 2 ++
> conf/machine/raspberrypi2.conf | 2 ++
> conf/machine/raspberrypi3.conf | 2 ++
> recipes-bsp/bootfiles/rpi-config_git.bb| 10 +++-
> recipes-graphics/mesa/mesa_%.bbappend | 4 +++
> recipes-graphics/wayland/weston_%.bbappend | 6 ++---
> recipes-graphics/weston/weston_%.bbappend | 13 +-
> .../0002-vc4-ioctl-rendering-allow.patch | 29
> ++
> recipes-kernel/linux/linux-raspberrypi_4.4.bb | 1 +
> recipes-kernel/linux/linux-rpi.inc | 10
> 13 files changed, 75 insertions(+), 15 deletions(-)
> create mode 100644 recipes-graphics/mesa/mesa_%.bbappend
> create mode 100644
> recipes-kernel/linux/linux-raspberrypi-4.4/0002-vc4-ioctl-rendering-allow.patch
>
> --
> 2.7.4
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
I would have wanted to merge this but they depend on dtbo support which
doesn't have the required bits in oe.core. So I can't merge this until
that lands in oe-core.
Regards,
--
Andrei Gherzan
signature.asc
Description: PGP signature
--
___
yocto mailing list
yocto@yoctoproject.or
Re: [yocto] [meta-raspberrypi] linux-raspberrypi versions
On Fri, Jul 22, 2016 at 07:07:07AM -0700, Khem Raj wrote: > On Fri, Jul 22, 2016 at 12:03 AM, piotr.lewicki > wrote: > > Hi all, > > > > I also think that's a good idea. In my opinion we should at least make > > latest LTS (4.4) the default kernel and try to add latest mainline. > > > > Probably the "proper way" of dealing with the issue is using branches. This > > way (as it is in oe-core): jethro would have kernel 3.18 and 4.1, krogoth > > would have 4.4 and 4.1 and master would only have 4.4 and latest mainline. > > 4.1 is also LTS, So it should be kept along with 4.4 until next LTS I'm 100% on removing < 4 and keep 4.4 default along with LTS 4.1 and the current tip. > > > > > Don't you think that it would be a good idea to create some "quasi" krogoth > > branch out of what is on master and then cleaning the master (e.g. removing > > kernel 3.18 and 4.1) ? > > > > > > BR, > > > > Piotr > > > > > > > > On 21.07.2016 17:39, Herve Jourdain wrote: > >> > >> Hi Paul, > >> > >> I had the same line of thoughts... > >> I believe 3.18 should be dropped, maybe even 4.1, default to 4.4, and > >> maybe > >> add 4.7 to the mix, since 4.7 seems to be where the bulk of the work is > >> done > >> now. > >> > >> Herve > >> > >> -Original Message- > >> From: yocto-boun...@yoctoproject.org > >> [mailto:yocto-boun...@yoctoproject.org] > >> On Behalf Of Paul Barker > >> Sent: jeudi 21 juillet 2016 09:03 > >> To: yocto@yoctoproject.org > >> Subject: [yocto] [meta-raspberrypi] linux-raspberrypi versions > >> > >> Hi all, > >> > >> I'm planning to look at the linux-raspberypi recipes once I've had time to > >> send V2 of my u-boot patches. I'd like to know people's thoughts on the > >> available kernel versions in the meta-raspberrypi layer: > >> > >> Is anyone still using the linux-raspberrypi 3.18 recipe? The commit > >> referenced in SRCREV is from June 2015. I think it's probably time to > >> retire > >> this unless anyone has a reason to keep it around. > >> > >> Is there any reason to keep linux-raspberrypi 4.1 as the default recipe? > >> The > >> last commit to the 4.1 branch was in April and the default branch on the > >> linux-raspberrypi GitHub repository has been > >> 4.4 since then. I think we should change the default version to 4.4 unless > >> there's a good reason not to. > >> > >> If there's no objections I'll send a couple of patches to drop 3.18 and > >> change the default to 4.4. > >> > >> Thanks, > >> Paul Barker > >> -- > >> ___ > >> yocto mailing list > >> yocto@yoctoproject.org > >> https://lists.yoctoproject.org/listinfo/yocto > >> > > > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- Andrei Gherzan signature.asc Description: PGP signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH v6 0/4] Support for .dtbo files for dtb overlays, required by kernels 4.4.6+
On Jul 31, 2016 12:48 PM, "Andrei Gherzan" wrote: > > On Thu, Jul 28, 2016 at 06:41:25PM -0700, Khem Raj wrote: > > > > > On Jul 20, 2016, at 3:00 PM, Herve Jourdain wrote: > > > > > > v6: rebased > > > > > > v5: modifications after more review > > > * Added an Upstream-Status to the kernel patch > > > * Only one instance of KERNEL_DEVICETREE defined (with the new .dtbo syntax) > > > * Modification of the KERNEL_DEVICETREE is done in linux-raspberry-base.bbclass, based on the kernel version > > > > > > v4: rebased > > > For kernels 4.4.9+, the behavior for the device tree overlays loading has been modified on RaspberryPi. > > > For overlays, it loads .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 addresses the issue for kernels 4.4+, while keeping the same behavior for older kernels. > > > This patch must be used in conjunction with another patch to meta/recipes-kernel/linux-dtb.inc, which will allow the processing of .dtbo files for overlays, instead of only .dtb like before. > > > > > > .dtb are still in use, but only for the "real" device trees (not the overlays). > > > > I have staged this series in > > > > https://github.com/kraj/meta-raspberrypi kraj/master > > > > However, this all has to wait on two things. > > > > The OE-core patch > > > > https://patchwork.openembedded.org/patch/123747/ > > > > What is happening with this patch? So I can't merge these as long as > this one is not merged. Yes. I am working on upstreaming it. We have to wait until this goes in. I have staged all rpi patches in my tree. So obe place to look for all > > > and we need to branch out for krogoth > > > > > > > > Herve Jourdain (4): > > > linux-raspberrypi_4.4.bb: support for .dtbo files for dtb overlays > > > rpi-base.inc: support for .dtbo files for dtb overlays > > > linux-raspberrypi-base.bbclass: support for .dtbo files for dtb > > >overlays > > > sdcard_image-rpi.bbclass: support for .dtbo files for dtb overlays > > > > > > classes/linux-raspberrypi-base.bbclass | 19 ++ > > > classes/sdcard_image-rpi.bbclass | 15 +--- > > > conf/machine/include/rpi-base.inc | 30 +++ > > > .../0001-fix-dtbo-rules.patch | 44 ++ > > > recipes-kernel/linux/linux-raspberrypi_4.4.bb | 1 + > > > 5 files changed, 81 insertions(+), 28 deletions(-) > > > 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 mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > > -- > Andrei Gherzan -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi] linux-raspberrypi versions
On Jul 31, 2016 12:55 PM, "Andrei Gherzan" wrote: > > On Fri, Jul 22, 2016 at 07:07:07AM -0700, Khem Raj wrote: > > On Fri, Jul 22, 2016 at 12:03 AM, piotr.lewicki wrote: > > > Hi all, > > > > > > I also think that's a good idea. In my opinion we should at least make > > > latest LTS (4.4) the default kernel and try to add latest mainline. > > > > > > Probably the "proper way" of dealing with the issue is using branches. This > > > way (as it is in oe-core): jethro would have kernel 3.18 and 4.1, krogoth > > > would have 4.4 and 4.1 and master would only have 4.4 and latest mainline. > > > > 4.1 is also LTS, So it should be kept along with 4.4 until next LTS > > I'm 100% on removing < 4 and keep 4.4 default along with LTS 4.1 and the > current tip. > Good so we are on same page. I have staged patches for this too. > > > > > > > > Don't you think that it would be a good idea to create some "quasi" krogoth > > > branch out of what is on master and then cleaning the master (e.g. removing > > > kernel 3.18 and 4.1) ? > > > > > > > > > BR, > > > > > > Piotr > > > > > > > > > > > > On 21.07.2016 17:39, Herve Jourdain wrote: > > >> > > >> Hi Paul, > > >> > > >> I had the same line of thoughts... > > >> I believe 3.18 should be dropped, maybe even 4.1, default to 4.4, and > > >> maybe > > >> add 4.7 to the mix, since 4.7 seems to be where the bulk of the work is > > >> done > > >> now. > > >> > > >> Herve > > >> > > >> -Original Message- > > >> From: yocto-boun...@yoctoproject.org > > >> [mailto:yocto-boun...@yoctoproject.org] > > >> On Behalf Of Paul Barker > > >> Sent: jeudi 21 juillet 2016 09:03 > > >> To: yocto@yoctoproject.org > > >> Subject: [yocto] [meta-raspberrypi] linux-raspberrypi versions > > >> > > >> Hi all, > > >> > > >> I'm planning to look at the linux-raspberypi recipes once I've had time to > > >> send V2 of my u-boot patches. I'd like to know people's thoughts on the > > >> available kernel versions in the meta-raspberrypi layer: > > >> > > >> Is anyone still using the linux-raspberrypi 3.18 recipe? The commit > > >> referenced in SRCREV is from June 2015. I think it's probably time to > > >> retire > > >> this unless anyone has a reason to keep it around. > > >> > > >> Is there any reason to keep linux-raspberrypi 4.1 as the default recipe? > > >> The > > >> last commit to the 4.1 branch was in April and the default branch on the > > >> linux-raspberrypi GitHub repository has been > > >> 4.4 since then. I think we should change the default version to 4.4 unless > > >> there's a good reason not to. > > >> > > >> If there's no objections I'll send a couple of patches to drop 3.18 and > > >> change the default to 4.4. > > >> > > >> Thanks, > > >> Paul Barker > > >> -- > > >> ___ > > >> yocto mailing list > > >> yocto@yoctoproject.org > > >> https://lists.yoctoproject.org/listinfo/yocto > > >> > > > > > > -- > > > ___ > > > yocto mailing list > > > yocto@yoctoproject.org > > > https://lists.yoctoproject.org/listinfo/yocto > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > -- > Andrei Gherzan -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH v4 00/12] Support for VC4 graphics driver
On Jul 31, 2016 12:54 PM, "Andrei Gherzan" wrote:
>
> On Thu, Jul 21, 2016 at 08:32:05PM +0800, Herve Jourdain wrote:
> > v4 series:
> > a. rebased
> > b. Upstream-Status added to the patch to the VC4 driver (needed only
for kernel 4.4, accepted upstream in 4.7)
> >
> > v3 series:
> > a. patch rebased
> > b. new revision of kernel, to get a version of the VC4 graphics driver
that handles render nodes
> > c. patch to the VC4 driver to enable proper working of the render nodes
(need to add authorization for IOCTLs)
> >
> > v2 series:
> > a. Fix the 4.4.10 kernel revision
> > b. Effectively add vc4-kms-v3d overlay to the list of overlays to build
(forgotten previously)
> > c. Make the parameter to the v4c-kms-v3d overlay configurable
> > d. Add default values for the cma parameter to the v4c-kms-v3d overlay,
depending on the board (and the memory it has)
> >
> > This patch series enables the support for the VC4 graphics driver from
Eric Anholt.
> > There was a previous patch series by Javier Martinez Canillas, but it
required use of a different kernel.
> > VC4 is now supported in the raspberrypi official kernel, at least for
4.4.9+.
> > The support in 4.1 exists, but it is NOT STABLE, so it has been deemed
unreasonable to support VC4 with 4.1 kernels.
> >
> > THEREFORE, VC4 graphics is supported ONLY for kernel versions 4.4.9 and
later.
> >
> > This patch series proposes to support VC4 by only adding 'vc4graphics'
to MACHINE_FEATURES, for raspberrypi. If this is set, it will trigger all
the necessary configuration/changes to use the VC4 driver, including
mesa/wayland/weston currently, and adding the overlay required.
> > In order for this series to work, some previous patches are needed
(support for .dtbo, and fix of the mesa packaging when there is no DRI
driver).
> > The memory reserved for the VC4 driver has default values depending on
the version of the board used, but it can be configured by setting
VC4_CMA_SIZE to a value supported by the overlay ('cma-256', 'cma-192',
'cma-128', 'cma-96', 'cma-64').
> > 'cma-256' is the recommended value, but it might not be possible on
boards with 512MB or DRAM, or less...
> > 'cma-64' is known to not being able to support FHD/1080p.
> >
> > It was tested with wayland/weston, without the support for X11.
> >
> > This patch series depends on two other patch series previously posted,
that enable the support for .dtbo overlay files.
> >
> > Herve Jourdain (12):
> > rpi-default-providers.inc: change default providers to support
> > vc4graphics
> > rpi-base.inc: add vc4-kms-v3d to the overlays to support vc4graphics
> > raspberrypi.conf: set the default value of VC4_CMA_SIZE to support
> > vc4graphics
> > raspberrypi0.conf: set the default value of VC4_CMA_SIZE to support
> > vc4graphics
> > raspberrypi2.conf: set the default value of VC4_CMA_SIZE to support
> > vc4graphics
> > raspberrypi3.conf: set the default value of VC4_CMA_SIZE to support
> > vc4graphics
> > rpi-config_git.bb: add v4c overlay to config.txt to support
> > vc4graphics
> > wayland/weston_%.bbappend: modify configuration options to support
> > vc4graphics
> > weston/weston_%.bbappend: modify configuration options to support
> > vc4graphics
> > mesa_%.bbappend: new file to add the correct configuration options to
> > support vc4graphics
> > linux-rpi.inc: add the configuration options required to support
> > vc4graphics
> > linux-raspberrypi-4.4: add patch to enable proper operation of
> > renderD128 device
> >
> > conf/machine/include/rpi-base.inc | 1 +
> > conf/machine/include/rpi-default-providers.inc | 8 +++---
> > conf/machine/raspberrypi.conf | 2 ++
> > conf/machine/raspberrypi0.conf | 2 ++
> > conf/machine/raspberrypi2.conf | 2 ++
> > conf/machine/raspberrypi3.conf | 2 ++
> > recipes-bsp/bootfiles/rpi-config_git.bb| 10 +++-
> > recipes-graphics/mesa/mesa_%.bbappend | 4 +++
> > recipes-graphics/wayland/weston_%.bbappend | 6 ++---
> > recipes-graphics/weston/weston_%.bbappend | 13 +-
> > .../0002-vc4-ioctl-rendering-allow.patch | 29
++
> > recipes-kernel/linux/linux-raspberrypi_4.4.bb | 1 +
> > recipes-kernel/linux/linux-rpi.inc | 10
> > 13 files changed, 75 insertions(+), 15 deletions(-)
> > create mode 100644 recipes-graphics/mesa/mesa_%.bbappend
> > create mode 100644
recipes-kernel/linux/linux-raspberrypi-4.4/0002-vc4-ioctl-rendering-allow.patch
> >
> > --
> > 2.7.4
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
>
> I would have wanted to merge this but they depend on dtbo support which
> doesn't have the required bits in oe.core. So I can't merge this until
> that lands in oe-c
Re: [yocto] [meta][PATCH] python-3.4-manifest: Add some missing RDEPENDS
On Fri, Jul 29, 2016 at 04:20:37PM -0400, Kyle Russell wrote:
> Signed-off-by: Kyle Russell
manifest is generated, you need to update the script which generates
that (read file header).
> ---
> meta/recipes-devtools/python/python-3.4-manifest.inc | 10 +-
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/meta/recipes-devtools/python/python-3.4-manifest.inc
> b/meta/recipes-devtools/python/python-3.4-manifest.inc
> index 97070b6..f71 100644
> --- a/meta/recipes-devtools/python/python-3.4-manifest.inc
> +++ b/meta/recipes-devtools/python/python-3.4-manifest.inc
> @@ -42,7 +42,7 @@ RDEPENDS_${PN}-crypt="${PN}-core"
> FILES_${PN}-crypt="${libdir}/python3.4/hashlib.* ${libdir}/python3.4/md5.*
> ${libdir}/python3.4/sha.* ${libdir}/python3.4/lib-dynload/crypt.*.so
> ${libdir}/python3.4/lib-dynload/_hashlib.*.so
> ${libdir}/python3.4/lib-dynload/_sha256.*.so
> ${libdir}/python3.4/lib-dynload/_sha512.*.so "
>
> SUMMARY_${PN}-ctypes="Python C types support"
> -RDEPENDS_${PN}-ctypes="${PN}-core"
> +RDEPENDS_${PN}-ctypes="${PN}-core ${PN}-subprocess"
> FILES_${PN}-ctypes="${libdir}/python3.4/ctypes
> ${libdir}/python3.4/lib-dynload/_ctypes.*.so
> ${libdir}/python3.4/lib-dynload/_ctypes_test.*.so "
>
> SUMMARY_${PN}-curses="Python curses support"
> @@ -122,7 +122,7 @@ RDEPENDS_${PN}-json="${PN}-core ${PN}-math ${PN}-re"
> FILES_${PN}-json="${libdir}/python3.4/json
> ${libdir}/python3.4/lib-dynload/_json.*.so "
>
> SUMMARY_${PN}-lang="Python low-level language support"
> -RDEPENDS_${PN}-lang="${PN}-core"
> +RDEPENDS_${PN}-lang="${PN}-core ${PN}-importlib"
> FILES_${PN}-lang="${libdir}/python3.4/lib-dynload/_bisect.*.so
> ${libdir}/python3.4/lib-dynload/_collections.*.so
> ${libdir}/python3.4/lib-dynload/_heapq.*.so
> ${libdir}/python3.4/lib-dynload/_weakref.*.so
> ${libdir}/python3.4/lib-dynload/_functools.*.so
> ${libdir}/python3.4/lib-dynload/array.*.so
> ${libdir}/python3.4/lib-dynload/itertools.*.so
> ${libdir}/python3.4/lib-dynload/operator.*.so
> ${libdir}/python3.4/lib-dynload/parser.*.so ${libdir}/python3.4/atexit.*
> ${libdir}/python3.4/bisect.* ${libdir}/python3.4/code.*
> ${libdir}/python3.4/codeop.* ${libdir}/python3.4/collections.*
> ${libdir}/python3.4/_collections_abc.* ${libdir}/python3.4/dis.*
> ${libdir}/python3.4/functools.* ${libdir}/python3.4/heapq.*
> ${libdir}/python3.4/inspect.* ${libdir}/python3.4/keyword.*
> ${libdir}/python3.4/opcode.* ${libdir}/python3.4/symbol.*
> ${libdir}/python3.4/repr.* ${libdir}/python3.4/token.*
> ${libdir}/python3.4/tokenize.* ${libdir}/python3.4/traceback.*
> ${libdir}/python3.4/weakref.* "
>
> SUMMARY_${PN}-logging="Python logging support"
> @@ -134,7 +134,7 @@ RDEPENDS_${PN}-mailbox="${PN}-core ${PN}-mime"
> FILES_${PN}-mailbox="${libdir}/python3.4/mailbox.* "
>
> SUMMARY_${PN}-math="Python math support"
> -RDEPENDS_${PN}-math="${PN}-core"
> +RDEPENDS_${PN}-math="${PN}-core ${PN}-crypt"
> FILES_${PN}-math="${libdir}/python3.4/lib-dynload/cmath.*.so
> ${libdir}/python3.4/lib-dynload/math.*.so
> ${libdir}/python3.4/lib-dynload/_random.*.so ${libdir}/python3.4/random.*
> ${libdir}/python3.4/sets.* "
>
> SUMMARY_${PN}-mime="Python MIME handling APIs"
> @@ -198,7 +198,7 @@ RDEPENDS_${PN}-resource="${PN}-core"
> FILES_${PN}-resource="${libdir}/python3.4/lib-dynload/resource.*.so "
>
> SUMMARY_${PN}-shell="Python shell-like functionality"
> -RDEPENDS_${PN}-shell="${PN}-core ${PN}-re"
> +RDEPENDS_${PN}-shell="${PN}-core ${PN}-re ${PN}-compression"
> FILES_${PN}-shell="${libdir}/python3.4/cmd.* ${libdir}/python3.4/commands.*
> ${libdir}/python3.4/dircache.* ${libdir}/python3.4/fnmatch.*
> ${libdir}/python3.4/glob.* ${libdir}/python3.4/popen2.*
> ${libdir}/python3.4/shlex.* ${libdir}/python3.4/shutil.* "
>
> SUMMARY_${PN}-smtpd="Python Simple Mail Transport Daemon"
> @@ -218,7 +218,7 @@ RDEPENDS_${PN}-stringold="${PN}-core ${PN}-re"
> FILES_${PN}-stringold="${libdir}/python3.4/lib-dynload/strop.*.so
> ${libdir}/python3.4/string.* ${libdir}/python3.4/stringold.* "
>
> SUMMARY_${PN}-subprocess="Python subprocess support"
> -RDEPENDS_${PN}-subprocess="${PN}-core ${PN}-io ${PN}-re ${PN}-fcntl
> ${PN}-pickle"
> +RDEPENDS_${PN}-subprocess="${PN}-core ${PN}-io ${PN}-re ${PN}-fcntl
> ${PN}-pickle ${PN}-threading"
> FILES_${PN}-subprocess="${libdir}/python3.4/subprocess.* "
>
> SUMMARY_${PN}-syslog="Python syslog interface"
> --
> 1.9.1
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
signature.asc
Description: Digital signature
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Recipe reporting system] Upgradable recipe name list
This mail was sent out by Recipe reporting system. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade at this time, they can fill RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder until newer upstream version was detected. Example: RECIPE_NO_UPDATE_REASON = "Version 2.0 is unstable" You can check the detail information at: http://recipes.yoctoproject.org/ Package VersionUpstream version Maintainer NoUpgradeReason - --- -- perl 5.22.1 5.24.1Alejandro Hernandez texinfo 6.06.1 Alejandro Hernandez python-git2.0.5 2.0.7 Alejandro Hernandez python-numpy 1.11.0 1.11.1Alejandro Hernandez ruby 2.2.5 2.3.1 Alejandro Hernandez python3 3.5.1 3.5.2 Alejandro Hernandez python2.7.11 2.7.12Alejandro Hernandez python3-git 1.0.2 2.0.7 Alejandro Hernandez cronie1.5.0 1.5.1 Alejandro Hernandez python-pexpect4.1.0 4.2.0 Alejandro Hernandez swig 3.0.8 3.0.10Alejandro Hernandez python3-setuptools22.0.5 25.1.1Alejandro Hernandez python-native 2.7.11 2.7.12Alejandro Hernandez python-setuptools 22.0.5 25.1.1Alejandro Hernandez perl-native 5.22.1 5.24.1Alejandro Hernandez python3-native3.5.1 3.5.2 Alejandro Hernandez liberation-fonts 1.04 2.00.1Alexander Kanavin 2.x depends on fontforge pa... gnutls3.5.1 3.5.2 Alexander Kanavin libwebp 0.5.0 0.5.1 Alexander Kanavin cmake 3.5.2 3.6.1 Alexander Kanavin nss 3.24 3.25 Alexander Kanavin lighttpd 1.4.39 1.4.41Alexander Kanavin ffmpeg3.13.1.1 Alexander Kanavin libassuan 2.4.2 2.4.3 Alexander Kanavin btrfs-tools 4.6.1 4.7 Alexander Kanavin procps3.3.11 3.3.12Alexander Kanavin cmake-native 3.5.2 3.6.1 Alexander Kanavin libidn1.32 1.33 Alexander Kanavin mkelfimage4.0+gitX 4.4+gitAUTOINC+58... Alexander Kanavin mkelfimage has been removed... mpg1231.23.5 1.23.6Alexander Kanavin dpkg 1.18.7 1.18.10 Aníbal Limón pinentry 0.9.2 0.9.7 Armin Kuster guilt-native 0.35+gitX 0.36+gitAUTOINC+2... Bruce Ashfield linux-libc-headers4.44.7 Bruce Ashfield linux-yocto-rt4.4.14+gitX4.4.15+gitAUTOINC... Bruce Ashfield linux-yocto 4.4.14+gitX4.4.15+gitAUTOINC... Bruce Ashfield linux-yocto-tiny 4.4.14+gitX4.4.15+gitAUTOINC... Bruce Ashfield kmod-native 22+gitX23+gitAUTOINC+65a... Chen Qi curl 7.49.1 7.50.0Chen Qi systemd 230+gitX 231+gitAUTOINC+38... Chen Qi kmod 22+gitX23+gitAUTOINC+65a... Chen Qi u-boot-fw-utils v2016.03+gitX v2016.07+gitAUTOI... Denys Dmytriyenko u-boot-mkimagev2016.03+gitX v2016.07+gitAUTOI... Denys Dmytriyenko u-bootv2016.03+gitX v2016.07+gitAUTOI... Denys Dmytriyenko createrepo0.4.11 0.10.4Hongxu Jia Versions after 0.9.* use YU... ncurses 6.0+20160319 6.0+20160625 Hongxu Jia man-pages 4.06 4.07 Hongxu Jia libgcrypt 1.7.0 1.7.2 Hongxu Jia gnupg 2.1.12 2.1.14Hongxu Jia libinput 1.3.0 1.4.0 Jussi Kukkonen libdrm2.4.68 2.4.70Jussi Kukkonen dropbear 2016.732016.74 Jussi Kukkonen augeas1.4.0 1.5.0 Jussi Kukkonen libgpg-error 1.23 1.24 Jussi Kukkonen vte 0.44.1 0.44.2Jussi Kukkonen xserver-xorg 1.18.3 1.18.4Jussi Kukkonen wayl
Re: [yocto] Trouble with yocto sdk in collaboration with eclipse and cmake
I have manually added the flags from CC (-march=armv7-a -marm -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a8) to the OECMAKE_C_FLAGS and then it works. I try to find a way, where CMAKE works out of the Box with yocto-plugin. I think the plugin is the problem for this issue. -Ursprüngliche Nachricht- Von: Khem Raj [mailto:raj.k...@gmail.com] Gesendet: Freitag, 29. Juli 2016 20:46 An: Hartwig, Guido Cc: yocto@yoctoproject.org Betreff: Re: [yocto] Trouble with yocto sdk in collaboration with eclipse and cmake > On Jul 29, 2016, at 1:27 AM, Hartwig, Guido wrote: > > Hi, > I have some trouble with the yocto sdk in collaboration with eclipse and > yocto CMake project. I have install all necessary eclipse plugins and linked > my sdk with the yocto-plugin as described in the manual. When I try to build > the "Hello World" yocto cmake project it fails with following message: > > .. > CMake Error at > /usr/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61 (message): The C > compiler > "/opt/puck/1.0.0/sysroots/x86_64-pucksdk-linux/usr/bin/arm-kostal-linux-gnueabi/arm-kostal-linux-gnueabi-gcc" > is not able to compile a simple test program ... > > This error occurs because the compiler is called with the wrong flags. > The SDK environment-setup script export the following environment > variables export CC="arm-kostal-linux-gnueabi-gcc -march=armv7-a -marm > -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a8 --sysroot=$SDKTARGETSYSROOT" > export CFLAGS=" -O2 -pipe -g -feliminate-unused-debug-types > -fdebug-prefix-map=/home/hartwig02/Workspace/build-puck/build/tmp/work/x86_64-nativesdk-pucksdk-linux/meta-environment-scb/1.0-r8=/usr/src/debug/meta-environment-scb/1.0-r8 > > -fdebug-prefix-map=/home/hartwig02/Workspace/build-puck/build/tmp/sysroots/x86_64-linux= > > -fdebug-prefix-map=/home/hartwig02/Workspace/build-puck/build/tmp/sysroots/x86_64-nativesdk-pucksdk-linux= > " > > The eclipse environment (set by the yocto plugin) shows the following > environment: > CC = arm-kostal-linux-gnueabi-gcc -march=armv7-a -marm -mfpu=neon > -mfloat-abi=hard -mcpu=cortex-a8 > --sysroot=/opt/puck/1.0.0/sysroots/cortexa8hf-neon-kostal-linux-gnueab > i CFLAGS = > --sysroot=/opt/puck/1.0.0/sysroots/cortexa8hf-neon-kostal-linux-gnueab > i OECMAKE_C_COMPILER = arm-kostal-linux-gnueabi-gcc > OECMAKE_C_FLAGS = > --sysroot=/opt/puck/1.0.0/sysroots/cortexa8hf-neon-kostal-linux-gnueabi > > I assume that yocto cmake uses the OECMAKE* variables to build the program. > The error occurs because the following compiler options (Tunes) are missing > "-march=armv7-a -marm -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a8" > > Now my questions > 1.Is it right that the yocto plugin cuts off the tunes from the > OECMAKE_C_COMPILER? > 2.Is there a reason that this compiler options are not appended to the > CFLAGS? CFLAGS should be passed down to cmake build system. That seems to be the problem you are seeing. Have you tried to append CFLAGS to OECMAKE_C_FLAGS ? > > Thank you for your help > > > > Mit freundlichen Grüßen / Kind regards > > KOSTAL Industrie Elektrik GmbH > > Dipl.-Ing. > Guido Hartwig > IE1 Entwicklung Elektronik > R & D Electronics > > Lange Eck 11, 58099 Hagen > Deutschland / Germany > Telefon: +49 2331 8040 - 688 > Telefax: +49 2331 8040 - 4660 > E-Mail: g.hart...@kostal.com > > Internet: http://www.kostal.com/industrie > > > > KOSTAL Industrie Elektrik GmbH - Sitz Lüdenscheid, Registergericht > Iserlohn HRB 3924 - USt-Id-Nr./Vat No.: DE 813742170 > Postanschrift: An der Bellmerei 10, D-58513 Lüdenscheid * Telefon: +49 > 2351 16-0 * Telefax: +49 2351 16-2400 > Werksanschrift: Lange Eck 11, D-58099 Hagen * Tel. +49 2331 8040-601 * > Fax +49 2331 8040-602 > Geschäftsführung: Axel Zimmermann, Dipl.-Ing. Marwin Kinzl, Dipl.-Oec. > Andreas Kostal > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
