Re: [yocto] Enable a recipe/package only when other dependent recipe/package is part of image.

[Amarnath Valluri]

On Friday 22 April 2016 02:09 PM, Valluri, Amarnath wrote:


Hello,

I have my own layer, that provides configuration packages for core 
Linux components, for example ‘connman-conf’ for ‘connman’ package.


I would like to provide a pakcagegroup-config, that should 
automatically select the configuration packages that are part of image 
configuration. Say if ‘connman’ is part of image then it should add 
‘connman-conf’ to its RDEPENDS_${PN}.


For this I try to use ‘oe.packagedata.pkgmap’, to check if the core 
component exists as below:




def check_if_enabled(comp, trueval, d):

   import oe.packagedata

   pkgmap = oe.packagedata.pkgmap(d)

   if pkgmap is not None and pkgmap.get(comp) is not None:

  return trueval

   return “”

RDEPENDS_${PN} = “ \

${@check_if_enabled(“connman”, “connman-conf”, d)} \

“

---

This works as expected when the packagedata is available, i.e., image 
is build at least once first, then my layer is added to BBLAYERS and 
then rebuild the image.


But this fails when there is no packagedata cache available.

Can someone help me to resolve this properly.

Thanks,

Amarnath



-
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki 
Business Identity Code: 0357606 - 4 
Domiciled in Helsinki 


This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH] rpi-base.inc: Include pi3-miniuart-bt-overlay.dtb

[Andrei Gherzan]

This is used to switch BT from ttyUSB0 to ttyS0 (miniUART).

Signed-off-by: Andrei Gherzan 
---
 conf/machine/include/rpi-base.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index f64bc9d..56ca83e 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -36,6 +36,7 @@ KERNEL_DEVICETREE ?= " \
 overlays/rpi-ft5406-overlay.dtb \
 overlays/w1-gpio-overlay.dtb \
 overlays/w1-gpio-pullup-overlay.dtb \
+overlays/pi3-miniuart-bt-overlay.dtb \
 "
 KERNEL_IMAGETYPE ?= "Image"
 
-- 
2.8.0

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

Re: [yocto] [meta-raspberrypi][PATCH 1/5] linux-raspberrypi: Bump to v4.4.7

[Andrei Gherzan]

On Fri, Apr 22, 2016 at 04:46:11PM +0200, Andrei Gherzan wrote:
> Signed-off-by: Andrei Gherzan 
> ---
>  recipes-kernel/linux/linux-raspberrypi_4.4.bb | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb 
> b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> index 8e4530f..9cb8aae 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> @@ -1,8 +1,8 @@
>  FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
>
> -LINUX_VERSION ?= "4.4.6"
> +LINUX_VERSION ?= "4.4.7"
>
> -SRCREV = "2faaa2ccef9e4c595bd26f14285c225ceea6097e"
> +SRCREV = "3de232825c9ba5989522b8691eb6ac5df6619458"
>  SRC_URI = 
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y \
> file://0001-dts-add-overlay-for-pitft22.patch \
>  "
> --
> 2.8.0
>

Merged this series to master.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Andrei Gherzan]

Hi Trevor,

On Wed, Apr 13, 2016 at 06:04:28PM -0400, Trevor Woerner wrote:
> On Wed 2016-03-30 @ 04:35:47 PM, Petter Mabäcker wrote:
> > rpi-ft5406 is an enabler for Official Raspberry Pi 7 inch
> > touchscreen support.
>
> I have an official raspberry pi 7" touchscreen and it's not obvious to me how
> I would go about enabling it in my config. If I had one of the others I would
> simply add:
>
>   MACHINE_FEATURES += "pitft pitft22"
>
> or
>
>   MACHINE_FEATURES += "pitft pitft28r"
>
> to my conf/local.conf, but what do I do for the official touchscreen?
>
> Also, by trial and error I've discovered that my touchscreen comes up as
> /dev/fb0 and not /dev/fb1. But the xorg config for touchscreen support assumes
> /dev/fb1. Am I doing something wrong in my build or can anyone think of a
> reason why my screen would be /dev/fb0 instead of /dev/fb1?
>
> By the way
>
>   MACHINE_FEATURES += "pitft pitft22"
>
> seems to work for me if I use /dev/fb0, but I'm not sure if that's a fluke?
>

Sorry for not being able to follow this thread. Did you manage to make
it work?


Regards,
--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] userland: fix wayland PACKAGECONFIG

[Andrei Gherzan]

Hi Jonathan,

On Wed, Apr 13, 2016 at 06:09:55PM +1000, Jonathan Liu wrote:
> The wayland-native dependency was not added correctly.
>
> Signed-off-by: Jonathan Liu 
> ---
>  recipes-graphics/userland/userland_git.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-graphics/userland/userland_git.bb 
> b/recipes-graphics/userland/userland_git.bb
> index ef06b12..2fdfeed 100644
> --- a/recipes-graphics/userland/userland_git.bb
> +++ b/recipes-graphics/userland/userland_git.bb
> @@ -45,7 +45,7 @@ EXTRA_OECMAKE = "-DCMAKE_BUILD_TYPE=Release 
> -DCMAKE_EXE_LINKER_FLAGS='-Wl,--no-a
>
>  PACKAGECONFIG ?= "${@bb.utils.contains('DISTRO_FEATURES', 'wayland', 
> 'wayland', '', d)}"
>
> -PACKAGECONFIG[wayland] = "-DBUILD_WAYLAND=TRUE 
> -DWAYLAND_SCANNER_EXECUTABLE:FILEPATH=${STAGING_BINDIR_NATIVE}/wayland-scanner,wayland-native,wayland"
> +PACKAGECONFIG[wayland] = "-DBUILD_WAYLAND=TRUE 
> -DWAYLAND_SCANNER_EXECUTABLE:FILEPATH=${STAGING_BINDIR_NATIVE}/wayland-scanner,,wayland
>  wayland-native"
>
>  CFLAGS_append = " -fPIC"

Master has a similar commit merged. Thanks.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] Change serial console for Raspberry Pi 3

[Andrei Gherzan]

Hi Martin,

On Tue, Apr 05, 2016 at 09:08:54AM +0200, Martin Bergek wrote:
> With the Raspberry Pi 3 the serial ports ttyS0 and ttyAMA0 have been switched 
> around. This causes an issue with the serial console that has previously been 
> set to ttyAMA0, causing the boot process to halt. I have a 100% failure rate 
> when booting a Raspberry Pi 3 image built using the master branch of 
> meta-raspberrypi. After a lot of testing it appears that the system fails to 
> boot whenever the kernel command line specifies a console - regardless of 
> whether it is ttyAMA0 or ttyS0.
>
> This patch changes the serial console and kernel command line to use default 
> values, allowing the raspberrypi3 machine configuration to assign different 
> values and to remove the kernel console. Now I get the console output to the 
> screen but at least it boots. Not sure if this is an acceptable way of doing 
> it but it fixed my problem.
>
> This patch has been verified on both the 4.1 and 4.4 kernel. It has also been 
> tested with the raspberrypi2 machine configuration.
>
> Signed-off-by: Martin Bergek 
> ---
> conf/machine/include/rpi-base.inc  | 2 +-
> conf/machine/raspberrypi3.conf | 4 
> recipes-kernel/linux/linux-raspberrypi.inc | 2 +-
> 3 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/conf/machine/include/rpi-base.inc 
> b/conf/machine/include/rpi-base.inc
> index 792150e..5d6280b 100644
> --- a/conf/machine/include/rpi-base.inc
> +++ b/conf/machine/include/rpi-base.inc
> @@ -7,7 +7,7 @@ include conf/machine/include/soc-family.inc
>
> IMAGE_FSTYPES ?= "tar.bz2 ext3 rpi-sdimg"
>
> -SERIAL_CONSOLE = "115200 ttyAMA0"
> +SERIAL_CONSOLE ?= "115200 ttyAMA0"
>
> XSERVER = " \
> xserver-xorg \
> diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf
> index 1b73f2f..2c76dc2 100644
> --- a/conf/machine/raspberrypi3.conf
> +++ b/conf/machine/raspberrypi3.conf
> @@ -6,4 +6,8 @@ MACHINEOVERRIDES = "raspberrypi2:${MACHINE}"
>
> MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-brcm43430"
>
> +# Change serial console due to swapped ttyAMA0 and ttyS0 on the Raspberry Pi 
> 3
> +SERIAL_CONSOLE = "115200 ttyS0"
> +CMDLINE = "dwc_otg.lpm_enable=0 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait"
> +
> include conf/machine/raspberrypi2.conf
> diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
> b/recipes-kernel/linux/linux-raspberrypi.inc
> index 24e7fe2..a3fe61a 100644
> --- a/recipes-kernel/linux/linux-raspberrypi.inc
> +++ b/recipes-kernel/linux/linux-raspberrypi.inc
> @@ -20,7 +20,7 @@ KERNEL_DEFCONFIG_raspberrypi ?= "bcmrpi_defconfig"
> KERNEL_DEFCONFIG_raspberrypi2 ?= "bcm2709_defconfig"
>
> # CMDLINE for raspberrypi
> -CMDLINE = "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 root=/dev/mmcblk0p2 
> rootfstype=ext4 rootwait"
> +CMDLINE ?= "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 root=/dev/mmcblk0p2 
> rootfstype=ext4 rootwait"
>
> # Add the kernel debugger over console kernel command line option if enabled
> CMDLINE_append = ' ${@base_conditional("ENABLE_KGDB", "1", 
> "kgdboc=ttyAMA0,115200", "", d)}'

This issue was fixed in master using serial0 magic string and the new
firmware. This will unlock your serial console. Be aware that you will
need to use enable_uart to force core_freq.

Cheers!

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH] README: Switch from redmine to github issues

[Andrei Gherzan]

Signed-off-by: Andrei Gherzan 
---
 README | 15 ++-
 1 file changed, 6 insertions(+), 9 deletions(-)

diff --git a/README b/README
index 5a6a0d9..c39f9ed 100644
--- a/README
+++ b/README
@@ -332,18 +332,15 @@ When sending patches to mailing list, please use 
something like:
 
 git send-email --to yocto@yoctoproject.org 
 
-7.B. Redmine
-
-In order to manage and trace the meta-raspberrypi issues, we use redmine:
-http://redmine.gherzan.ro/projects/meta-raspberrypi
-
-Here we report, trace and develop bugs, features or support tickets for this
-yocto BSP later.
+7.B. Github issues
+==
+In order to manage and trace the meta-raspberrypi issues, we use github issues:
+https://github.com/agherzan/meta-raspberrypi/issues
 
-If you push patches which have a redmine issue associated, please provide the
+If you push patches which have a github issue associated, please provide the
 issue number in the commit log just before "Signed-off-by" line(s). Example 
line
 for a bug:
-[Bug #13]
+[Issue #13]
 
 
 8. Maintainers
-- 
2.8.0

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

Re: [yocto] [meta-raspberrypi][PATCH] u-boot-rpi2: use the upstreamed U-Boot

[Andrei Gherzan]

Hi Steve,

On Mon, Jan 25, 2016 at 04:32:27PM -0800, Steve Rae wrote:
>
>
> On 16-01-25 01:32 PM, Khem Raj wrote:
> > Hi Steve
> >
> > > On Jan 25, 2016, at 1:00 PM, Steve Rae  wrote:
> > >
> > > For Raspberry Pi 2, use the U-Boot from "den".
> >
> >
> > Can this be done by using/extending OE-Core recipe please ?
> >
> >
>
> I modelled it after the existing RPi recipe:
> diff recipes-bsp/u-boot/u-boot-rpi_git.bb
> recipes-bsp/u-boot/u-boot-rpi2_git.bb
> sorry -- I don't know enough about this to answer your question...
> Which recipe should I "extend"? Could you please provide more details?
> Thanks in advance, Steve

Khem Raj is proposing to use a uboot recipe from oe-core
https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-bsp/u-boot
and extend it with a bbappend to include rpi support. Is that possible?

P.S.: Sorry for this late reply. I'm trying to catch up with some old
threads.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] rpi-base.inc: Include pi3-miniuart-bt-overlay.dtb

[Andrei Gherzan]

On Mon, Apr 25, 2016 at 09:06:15AM +0200, Andrei Gherzan wrote:
> This is used to switch BT from ttyUSB0 to ttyS0 (miniUART).
>
> Signed-off-by: Andrei Gherzan 
> ---
>  conf/machine/include/rpi-base.inc | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/conf/machine/include/rpi-base.inc 
> b/conf/machine/include/rpi-base.inc
> index f64bc9d..56ca83e 100644
> --- a/conf/machine/include/rpi-base.inc
> +++ b/conf/machine/include/rpi-base.inc
> @@ -36,6 +36,7 @@ KERNEL_DEVICETREE ?= " \
>  overlays/rpi-ft5406-overlay.dtb \
>  overlays/w1-gpio-overlay.dtb \
>  overlays/w1-gpio-pullup-overlay.dtb \
> +overlays/pi3-miniuart-bt-overlay.dtb \
>  "
>  KERNEL_IMAGETYPE ?= "Image"
>
> --
> 2.8.0
>

Merged to master.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] README: Switch from redmine to github issues

[Andrei Gherzan]

On Mon, Apr 25, 2016 at 10:10:40AM +0200, Andrei Gherzan wrote:
> Signed-off-by: Andrei Gherzan 
> ---
>  README | 15 ++-
>  1 file changed, 6 insertions(+), 9 deletions(-)
>
> diff --git a/README b/README
> index 5a6a0d9..c39f9ed 100644
> --- a/README
> +++ b/README
> @@ -332,18 +332,15 @@ When sending patches to mailing list, please use 
> something like:
>
>  git send-email --to yocto@yoctoproject.org 
>
> -7.B. Redmine
> -
> -In order to manage and trace the meta-raspberrypi issues, we use redmine:
> -http://redmine.gherzan.ro/projects/meta-raspberrypi
> -
> -Here we report, trace and develop bugs, features or support tickets for this
> -yocto BSP later.
> +7.B. Github issues
> +==
> +In order to manage and trace the meta-raspberrypi issues, we use github 
> issues:
> +https://github.com/agherzan/meta-raspberrypi/issues
>
> -If you push patches which have a redmine issue associated, please provide the
> +If you push patches which have a github issue associated, please provide the
>  issue number in the commit log just before "Signed-off-by" line(s). Example 
> line
>  for a bug:
> -[Bug #13]
> +[Issue #13]
>
>
>  8. Maintainers
> --
> 2.8.0
>

Merged to master.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] Yocto Project Status WW17

[Burton, Ross]

On 25 April 2016 at 00:17, Trevor Woerner  wrote:

> > CROPS is docker magic to do builds on Windows/Mac.  Todor did a
> > presentation at ELC: http:
> > //
> events.linuxfoundation.org/sites/events/files/slides/Todor_Minchev_CROPS_ELC_2016.pdf
> > <
> http://events.linuxfoundation.org/sites/events/files/slides/Todor_Minchev_CROPS_ELC_2016.pdf
> >
>
> I was *very* excited to learn about CROPS at ELC, which is why I was
> wondering
> if it was available to experiment with somewhere?


The slides have links to the git repos and some instructions.  I'm sure
Todor would help if you have any specific questions.

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

Re: [yocto] Using Yocto with NXP QorIQ Processors

[Chris Trobridge]

Thanks Zhenhua,
That sounds more positive.
One think that has been pointed out to me is that there are community layers 
that are support outside of NXP that sit between Yocto and NXP 
(http://freescale.github.io/#) that track issues etc more actively.  These does 
not appear to involve the ppc processors so are the arm processors more 
actively supported? (I presume this just depends on the community support.)
We use the original pcc qoriq processors and so would be interested in ppc 
support but that's still more of a future project.  Relative support arm vs ppc 
would be a consideration but the meta-fsl-layer in yocto is reassuring (I 
didn't manage to find it before!).
Regards,Chris
From: zhenhua@nxp.com
To: christrobri...@hotmail.com
CC: yocto@yoctoproject.org
Subject: RE: [yocto] Using Yocto with NXP QorIQ Processors
Date: Tue, 19 Apr 2016 03:16:16 +









Hi Chris,

 
The QorIQ SDK uses recent Yocto version, e.g. the SDK 2.0  is based on Yocto 
2.0(Jethro).  When the SDK is formally released in Q2/2016, the SDK recipes will
 be upstreamed to master of community layers.
 
You can use either SDK ISOs available in NXP official website(www.nxp.com) or 
the BSP layers in Yocto website (http://git.yoctoproject.org/cgit.cgi/).


·
QorIQ ARM targets: meta-fsl-arm

·
QorIQ PPC targets: meta-fsl-ppc

 
 
Best Regards,
 
Zhenhua

 



From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Chris Trobridge

Sent: Monday, April 18, 2016 9:58 PM

To: yocto@yoctoproject.org

Subject: [yocto] Using Yocto with NXP QorIQ Processors


 

Has anyone attempted to use the Qoriq BSP layers with them main Yocto release 
rather than the NXP (ex Freescale) SDK they come bundled in?

 


I ask because the NXP SDK is somewhat behind the main Yocto release schedule.


 


It should be easier to port the BSP to the current Yocto but I have no idea 
what issues I am likely to hit.


 


I will try this at some point when I have enough free time but for planning 
purposes I would interested in how anyone else has got on attempting this.


 


Are Qoriq users restricted to the official SDK or would they get third-party 
support?


 


Regards,


Chris


 



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

Re: [yocto] [Yocto] Enable a recipe/package only when other dependent recipe/package is part of image.

[Burton, Ross]

On 25 April 2016 at 07:46, Amarnath Valluri 
wrote:

> I would like to provide a pakcagegroup-config, that should automatically
> select the configuration packages that are part of image configuration. Say
> if ‘connman’ is part of image then it should add ‘connman-conf’ to its
> RDEPENDS_${PN}.
>
>
You can't do that.

A packagegroup is just a recipe that generates packages with no contents,
just dependencies.  They are built once and don't know what image they're
being "built for", or what other packages are being built.  What would you
packagegroup do if it were built directly, not via dependencies from an
image?

The low-fi way to implement this would be for the layer that adds
connman-conf to also add a bbappend for connman to depend on connman-conf.

An alternative would be to have some naming pattern for conf packages
(-conf is reasonable) and invent a new image-feature called conf-packages
that uses a glob to find all complementary packages matching the *-conf
pattern.  This is how dev-pkgs, dbg-pkgs, doc-pkgs etc work.  I believe
this is just a matter of setting COMPLEMENTARY_GLOB[conf-pkgs] = '*-conf'
in your configuration.

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

Re: [yocto] [Yocto] Enable a recipe/package only when other dependent recipe/package is part of image.

[Amarnath Valluri]

Thanks Ross for your suggestions.

On Monday 25 April 2016 02:46 PM, Burton, Ross wrote:


On 25 April 2016 at 07:46, Amarnath Valluri 
mailto:amarnath.vall...@intel.com>> wrote:


I would like to provide a pakcagegroup-config, that should
automatically select the configuration packages that are part of
image configuration. Say if ‘connman’ is part of image then it
should add ‘connman-conf’ to its RDEPENDS_${PN}.


You can't do that.

A packagegroup is just a recipe that generates packages with no 
contents, just dependencies.  They are built once and don't know what 
image they're being "built for", or what other packages are being 
built.  What would you packagegroup do if it were built directly, not 
via dependencies from an image?

Yes, i agree.


The low-fi way to implement this would be for the layer that adds 
connman-conf to also add a bbappend for connman to depend on connman-conf.
I considered this initially, but the issue with .bbappend is it leads to 
rebuilding of core packages when this configuration layer add to 
bblayers, to (re)build image, which we would like to avoid.




An alternative would be to have some naming pattern for conf packages 
(-conf is reasonable) and invent a new image-feature called 
conf-packages that uses a glob to find all complementary packages 
matching the *-conf pattern.  This is how dev-pkgs, dbg-pkgs, doc-pkgs 
etc work. I believe this is just a matter of 
setting COMPLEMENTARY_GLOB[conf-pkgs] = '*-conf' in your configuration.

I will try this, thanks.

- Amarnath
-
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki 
Business Identity Code: 0357606 - 4 
Domiciled in Helsinki 


This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Strange dependency

[Gary Thomas]

I have a distribution which normally includes x11.  I just
ran a build with
  DISTRO_FEATURES_remove = "x11 wayland"

Why on earth did this require qemu-native to be rebuilt?
One would think that qemu-native would be independent of the
DISTRO_FEATURES??

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

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

[yocto] Error installing wpa-supplicant

[Gary Thomas]

I tried to add wpa-supplicant to my working/installed system
and got this error:

Removing any system startup links for dbus-1 ...
Running groupadd commands...
NOTE: dbus: Performing groupadd with [ -r netdev]
ERROR: dbus: groupadd command did not succeed.
To remove package debris, try `opkg remove dbus-1`.
To re-attempt the install, try `opkg install dbus-1`.
...
Collected errors:
 * pkg_run_script: package "dbus-1" preinst script returned status 1.
 * preinst_configure: Aborting installation of dbus-1.
 * opkg_install: Cannot install package wpa-supplicant.

When I tried to rerun it, I got this:

root@teton-p7618:~# opkg remove dbus-1
No packages removed.
root@teton-p7618:~# opkg install dbus-1
Installing dbus-1 (1.10.6-r0.3) on root.
 Removing any system startup links for dbus-1 ...
Running groupadd commands...
NOTE: dbus: Performing groupadd with [ -r netdev]
ERROR: dbus: groupadd command did not succeed.
To remove package debris, try `opkg remove dbus-1`.
To re-attempt the install, try `opkg install dbus-1`.
Collected errors:
 * pkg_get_installed_files: Failed to open ///var/lib/opkg/info/dbus-1.list: No 
such file or directory.
 * pkg_run_script: package "dbus-1" preinst script returned status 1.
 * preinst_configure: Aborting installation of dbus-1.
 * opkg_install: Cannot install package dbus-1.

What might be the issue here and how to I resolve it?

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

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

[yocto] Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream

[Jaggi, Manish]

In my bb file I added the below line,


SRCREV = "2134d97aa3a7ce38bb51f933f2e20cafde371085"
SRC_URI = "git://git.yoctoproject.org/linux-yocto-dev"

The revision id is of v4.4.3 tag.


Below errors are generated upon kernel fetching


ERROR: linux-4.4 do_fetch: Fetcher failure: Unable to find revision 
2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream
ERROR: linux-4.4 do_fetch: Function failed: Fetcher failure for URL: 
'git://git.yoctoproject.org/linux-yocto-dev'. Unable to fetch URL from any 
source.

It seems the revid / tag is not on any branch
git branch  --contains 2134d97aa3a7ce38bb51f933f2e20cafde371085
returns nothing.

How to fix this issue ?


Regards,
Manish Jaggi
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Enable a recipe/package only when other dependent recipe/package is part of image.

[Valluri, Amarnath]

Hello,

I have my own layer, that provides configuration packages for core Linux 
components, for example 'connman-conf' for 'connman' package.

I would like to provide a pakcagegroup-config, that should automatically select 
the configuration packages that are part of image configuration. Say if 
'connman' is part of image then it should add 'connman-conf' to its 
RDEPENDS_${PN}.

For this I try to use 'oe.packagedata.pkgmap', to check if the core component 
exists as below:

def check_if_enabled(comp, trueval, d):
   import oe.packagedata
   pkgmap = oe.packagedata.pkgmap(d)

   if pkgmap is not None and pkgmap.get(comp) is not None:
  return trueval

   return ""

RDEPENDS_${PN} = " \
   ${@check_if_enabled("connman", "connman-conf", d)} \
"
---

This works as expected when the packagedata is available, i.e., image is build 
at least once first, then my layer is added to BBLAYERS and then rebuild the 
image.
But this fails when there is no packagedata cache available.

Can someone help me to resolve this properly.

Thanks,
Amarnath
-
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki 
Business Identity Code: 0357606 - 4 
Domiciled in Helsinki 

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto ADT eclipse plugin and devtool

[Benjamin Gaignard]

Hello,

devtool usage is well documented in ADT manual:
http://www.yoctoproject.org/docs/latest/adt-manual/adt-manual.html#using-devtool-in-your-sdk-workflow
but not explicit mention of how use it within Eclipse.

Do you know if we can use devtool, for example to compile and load new
code, directly inside Eclipse ?

Regards,
Benjamin

-- 
Benjamin Gaignard

Graphic Working Group

Linaro.org │ Open source software for ARM SoCs

Follow Linaro: Facebook | Twitter | Blog
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Error installing wpa-supplicant

[Gary Thomas]

On 2016-04-25 15:21, Gary Thomas wrote:

I tried to add wpa-supplicant to my working/installed system
and got this error:

Removing any system startup links for dbus-1 ...
Running groupadd commands...
NOTE: dbus: Performing groupadd with [ -r netdev]
ERROR: dbus: groupadd command did not succeed.
To remove package debris, try `opkg remove dbus-1`.
To re-attempt the install, try `opkg install dbus-1`.
...
Collected errors:
  * pkg_run_script: package "dbus-1" preinst script returned status 1.
  * preinst_configure: Aborting installation of dbus-1.
  * opkg_install: Cannot install package wpa-supplicant.

When I tried to rerun it, I got this:

root@teton-p7618:~# opkg remove dbus-1
No packages removed.
root@teton-p7618:~# opkg install dbus-1
Installing dbus-1 (1.10.6-r0.3) on root.
  Removing any system startup links for dbus-1 ...
Running groupadd commands...
NOTE: dbus: Performing groupadd with [ -r netdev]
ERROR: dbus: groupadd command did not succeed.
To remove package debris, try `opkg remove dbus-1`.
To re-attempt the install, try `opkg install dbus-1`.
Collected errors:
  * pkg_get_installed_files: Failed to open ///var/lib/opkg/info/dbus-1.list: 
No such file or directory.
  * pkg_run_script: package "dbus-1" preinst script returned status 1.
  * preinst_configure: Aborting installation of dbus-1.
  * opkg_install: Cannot install package dbus-1.

What might be the issue here and how to I resolve it?



Interesting info from 'strace'

1147  execve("/usr/local/bin/ groupadd -r netdev", [" groupadd -r netdev"], [/* 12 vars */]) = -1 ENOENT (No such file 
or directory)
1147  execve("/usr/bin/ groupadd -r netdev", [" groupadd -r netdev"], [/* 12 vars */]) = -1 ENOENT (No such file or 
directory)

1147  execve("/bin/ groupadd -r netdev", [" groupadd -r netdev"], [/* 12 vars 
*/]) = -1 ENOENT (No such file or directory)
1147  execve("/usr/local/sbin/ groupadd -r netdev", [" groupadd -r netdev"], [/* 12 vars */]) = -1 ENOENT (No such file 
or directory)
1147  execve("/usr/sbin/ groupadd -r netdev", [" groupadd -r netdev"], [/* 12 vars */]) = -1 ENOENT (No such file or 
directory)

1147  execve("/sbin/ groupadd -r netdev", [" groupadd -r netdev"], [/* 12 vars 
*/]) = -1 ENOENT (No such file or directory)

seems to be a problem with finding the 'groupadd' command?

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

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

[yocto] Compiling tollchain at x64 to run at x86

[Daniel.]

Hi everybody

I need to install a toolchain compiled by Yocto but my machine (where the
toolchain will be compiled) is a x64, and the machine where the toolchain
will run is x86. How can I achieve this?

Best regards,
- dhs

-- 
*"Do or do not. There is no try"*
  *Yoda Master*
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream

[Burton, Ross]

On 25 April 2016 at 14:30, Jaggi, Manish 
wrote:

> It seems the revid / tag is not on any branch
> git branch  --contains 2134d97aa3a7ce38bb51f933f2e20cafde371085
> returns nothing.
>
> How to fix this issue ?
>

You probably want to use git branch -r --contains 213... as otherwise git
branch will only list local branches.  The web UI says that this commit
exists on master though...

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

Re: [yocto] [Fwd: gobject introspection release notes]

[Chris Trobridge]

Any ideas as to why "qemu-ppc64 crashes out immediately"?
I can confirm the build ends in a segfault when I tried building 
gobject-introspection for the t1042d4rdb-64b machine.  
I did get one qemu crash recorded by Fedora but the actual crash dumps 
(appended) are for a PowerPC.  That said, given the dump, either the processor 
got nowhere or they are likely corrupt.  The invalid access reported is roughly 
to the stack but with the upper 32-bits zeroed.
If I configure bitbake for a 32-bit build (t1042d4rdb) then the build fails 
with  "Unable to find CPU definition" (cpu e5500) so a 32-bit build is out of 
the question too.
The command line from the wrapper is:PSEUDO_UNLOAD=1 qemu-ppc -r 2.6.32  -cpu 
e5500 -L /home/chris/yocto/build/tmp/sysroots/t1042d4rdb -E 
LD_LIBRARY_PATH=$GIR_EXTRA_LIBS_PATH:.libs:/home/chris/yocto/build/tmp/sysroots/t1042d4rdb//usr/lib:/home/chris/yocto/build/tmp/sysroots/t1042d4rdb//lib
  "$@"
The cpu is supported by the fedora qemu-ppc64, but not qemu-ppc - ie it's a 
64-bit processor that's not supported in 32-bit mode.
This is not massively urgent for me but it may be important in the future and I 
am curious as to whether the problem is in the qemu emulation or in the 
emulated code.
Regards,Chris 

| Invalid data memory access: 0x007fe8f0| NIP 0040008046c8   LR 
 CTR  XER  CPU#0| MSR 
80006000 HID0   HF 6000 idx 0| TB 00025634 
110100571322161| GPR00  0040007fe970 004000848e00 
0040007fe970| GPR04    
| GPR08    
| GPR12    
| GPR16    
| GPR20    
| GPR24    
| GPR28    
| CR   [ -  -  -  -  -  -  -  -  ] RES 
| FPR00    
| FPR04    
| FPR08    
| FPR12    
| FPR16    
| FPR20    
| FPR24    
| FPR28    
| FPSCR | Invalid segfault errno (4200)| 
NIP 0040008046c8   LR  CTR  XER 
 CPU#0| MSR 80006000 HID0   HF 
6000 idx 0| TB 00025634 110100578368626| GPR00  
0040007fe970 004000848e00 0040007fe970| GPR04  
  | GPR08  
  | GPR12  
  | GPR16  
  | GPR20  
  | GPR24  
  | GPR28  
  | CR   [ -  -  -  -  
-  -  -  -  ] RES | FPR00  
  | FPR04  
  | FPR08  
  | FPR12  
  | FPR16  
  | FPR20  
  | FPR24  
  | FPR28  
  | FPSCR | 
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
  -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Compiling tollchain at x64 to run at x86

[Daniel.]

Hi everybody, download a ready to run script from
http://downloads.yoctoproject.org/releases/yocto/yocto-1.6/toolchain/i686/poky-eglibc-i686-core-image-sato-armv7a-vfp-neon-toolchain-1.6.sh
and worked fine!

Cheers,

2016-04-25 11:26 GMT-03:00 Daniel. :

> Hi everybody
>
> I need to install a toolchain compiled by Yocto but my machine (where the
> toolchain will be compiled) is a x64, and the machine where the toolchain
> will run is x86. How can I achieve this?
>
> Best regards,
> - dhs
>
> --
> *"Do or do not. There is no try"*
>   *Yoda Master*
>



-- 
*"Do or do not. There is no try"*
  *Yoda Master*
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream

[Jaggi, Manish]

From: Burton, Ross 
Sent: Monday, April 25, 2016 8:12 PM
To: Jaggi, Manish
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Fetcher failure: Unable to find revision 
2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream


On 25 April 2016 at 14:30, Jaggi, Manish 
mailto:manish.ja...@caviumnetworks.com>> wrote:
It seems the revid / tag is not on any branch
git branch  --contains 2134d97aa3a7ce38bb51f933f2e20cafde371085
returns nothing.

How to fix this issue ?

You probably want to use git branch -r --contains 213... as otherwise git 
branch will only list local branches.  The web UI says that this commit exists 
on master though...

[Manish] Same output with -r.
Can you please share the link of web ui. As per the error it is not on master 
branch.


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

[yocto] More up to date network boot (PXE?) reference

[Ronald Oakes]

My target will need to be loaded over the network - maintaining only a
ram file system.  So, I've been reading up on doing network booting
using PXE or gPXE.  However, the best reference (or the one I'm most
likely to trust) is coming from the Yocto Project Wiki.  Except it is
5.5 years out of date (September 2010).

So, can anyone recommend a more recent reference to consult in trying
to make sure I've got my build (etc.) set up correctly?

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

Re: [yocto] Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream

[Bruce Ashfield]

On 2016-04-25 12:10 PM, Jaggi, Manish wrote:



*From:* Burton, Ross 
*Sent:* Monday, April 25, 2016 8:12 PM
*To:* Jaggi, Manish
*Cc:* yocto@yoctoproject.org
*Subject:* Re: [yocto] Fetcher failure: Unable to find revision
2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from
upstream

On 25 April 2016 at 14:30, Jaggi, Manish
mailto:manish.ja...@caviumnetworks.com>> wrote:

It seems the revid / tag is not on any branch
git branch  --contains 2134d97aa3a7ce38bb51f933f2e20cafde371085
returns nothing.

How to fix this issue ?


You probably want to use git branch -r --contains 213... as otherwise
git branch will only list local branches.  The web UI says that this
commit exists on master though...

[Manish] Same output with -r.
Can you please share the link of web ui. As per the error it is not on
master branch.


linux-yoct-dev and linux-yocto-4.4 are different trees. linux-yocto-dev
tracks the latest mainline kernel, not -stable.

So if you are looking for 4.4.3 on linux-yocto-dev, you aren't going
to find it.

Bruce




Ross




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

[yocto] [meta-raspberrypi][PATCH] linux-raspberrypi_4.4.bb: Upgrade to 4.4.8

[Khem Raj]

Fixes for gcc6
Drop upstreamed patch

Signed-off-by: Khem Raj 
---
 .../0001-dts-add-overlay-for-pitft22.patch | 106 -
 recipes-kernel/linux/linux-raspberrypi_4.4.bb  |   6 +-
 2 files changed, 2 insertions(+), 110 deletions(-)
 delete mode 100644 
recipes-kernel/linux/linux-raspberrypi-4.4/0001-dts-add-overlay-for-pitft22.patch

diff --git 
a/recipes-kernel/linux/linux-raspberrypi-4.4/0001-dts-add-overlay-for-pitft22.patch
 
b/recipes-kernel/linux/linux-raspberrypi-4.4/0001-dts-add-overlay-for-pitft22.patch
deleted file mode 100644
index 7cb076f..000
--- 
a/recipes-kernel/linux/linux-raspberrypi-4.4/0001-dts-add-overlay-for-pitft22.patch
+++ /dev/null
@@ -1,106 +0,0 @@
-From a28bd410022b32a64e208f04b45add6326990332 Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Petter=20Mab=C3=A4cker?= 
-Date: Fri, 8 Jan 2016 09:02:44 +0100
-Subject: [PATCH] dts: add overlay for pitft22
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-Upstream-Status: Pending
-
-Add the pitft22 overlay from adafruit Adafruit-Pi-Kernel-o-Matic repo:
-https://github.com/adafruit/Adafruit-Pi-Kernel-o-Matic
-
-Signed-off-by: Petter Mabäcker 

- arch/arm/boot/dts/overlays/Makefile|  1 +
- arch/arm/boot/dts/overlays/pitft22-overlay.dts | 69 ++
- 2 files changed, 70 insertions(+)
- create mode 100755 arch/arm/boot/dts/overlays/pitft22-overlay.dts
-
-Index: kernel-source/arch/arm/boot/dts/overlays/pitft22-overlay.dts
-===
 /dev/null
-+++ kernel-source/arch/arm/boot/dts/overlays/pitft22-overlay.dts
-@@ -0,0 +1,69 @@
-+/*
-+ * Device Tree overlay for pitft by Adafruit
-+ *
-+ */
-+
-+/dts-v1/;
-+/plugin/;
-+
-+/ {
-+compatible = "brcm,bcm2835", "brcm,bcm2708", "brcm,bcm2709";
-+
-+fragment@0 {
-+target = <&spi0>;
-+__overlay__ {
-+status = "okay";
-+
-+spidev@0{
-+status = "disabled";
-+};
-+
-+spidev@1{
-+status = "disabled";
-+};
-+};
-+};
-+
-+fragment@1 {
-+target = <&gpio>;
-+__overlay__ {
-+pitft_pins: pitft_pins {
-+brcm,pins = <25>;
-+brcm,function = <1>; /* out */
-+brcm,pull = <0>; /* none */
-+};
-+};
-+};
-+
-+fragment@2 {
-+target = <&spi0>;
-+__overlay__ {
-+/* needed to avoid dtc warning */
-+#address-cells = <1>;
-+#size-cells = <0>;
-+
-+pitft: pitft@0{
-+compatible = "ilitek,ili9340";
-+reg = <0>;
-+pinctrl-names = "default";
-+pinctrl-0 = <&pitft_pins>;
-+
-+spi-max-frequency = <3200>;
-+rotate = <90>;
-+fps = <25>;
-+bgr;
-+buswidth = <8>;
-+dc-gpios = <&gpio 25 0>;
-+debug = <0>;
-+};
-+
-+};
-+};
-+
-+__overrides__ {
-+speed =   <&pitft>,"spi-max-frequency:0";
-+rotate =  <&pitft>,"rotate:0";
-+fps = <&pitft>,"fps:0";
-+debug =   <&pitft>,"debug:0";
-+};
-+};
-Index: kernel-source/arch/arm/boot/dts/overlays/Makefile
-===
 kernel-source.orig/arch/arm/boot/dts/overlays/Makefile
-+++ kernel-source/arch/arm/boot/dts/overlays/Makefile
-@@ -43,6 +43,7 @@ dtbo-$(RPI_DT_OVERLAYS) += pi3-disable-b
- dtbo-$(RPI_DT_OVERLAYS) += pi3-miniuart-bt.dtbo
- dtbo-$(RPI_DT_OVERLAYS) += piscreen.dtbo
- dtbo-$(RPI_DT_OVERLAYS) += piscreen2r.dtbo
-+dtbo-$(RPI_DT_OVERLAYS) += pitft22-overlay.dtbo
- dtbo-$(RPI_DT_OVERLAYS) += pitft28-capacitive.dtbo
- dtbo-$(RPI_DT_OVERLAYS) += pitft28-resistive.dtbo
- dtbo-$(RPI_DT_OVERLAYS) += pps-gpio.dtbo
diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb 
b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
index 9cb8aae..f6e1005 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
@@ -1,10 +1,8 @@
 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
 
-LINUX_VERSION ?= "4.4.7"
+LINUX_VERSION ?= "4.4.8"
 
-SRCREV = "3de232825c9ba5989522b8691eb6ac5df6619458"
+SRCREV = "fe7ad6aa5c6940817fe971d80a7b2a1d6052190a"
 SRC_URI = 
"git://github.c

Re: [yocto] Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream

[Jaggi, Manish]

From: Bruce Ashfield [bruce.ashfi...@windriver.com]
Sent: Monday, April 25, 2016 11:04 PM
To: Jaggi, Manish; Burton, Ross
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Fetcher failure: Unable to find revision 
2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream

On 2016-04-25 12:10 PM, Jaggi, Manish wrote:
>
> 
> *From:* Burton, Ross 
> *Sent:* Monday, April 25, 2016 8:12 PM
> *To:* Jaggi, Manish
> *Cc:* yocto@yoctoproject.org
> *Subject:* Re: [yocto] Fetcher failure: Unable to find revision
> 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from
> upstream
>
> On 25 April 2016 at 14:30, Jaggi, Manish
>  > wrote:
>
> It seems the revid / tag is not on any branch
> git branch  --contains 2134d97aa3a7ce38bb51f933f2e20cafde371085
> returns nothing.
>
> How to fix this issue ?
>
>
> You probably want to use git branch -r --contains 213... as otherwise
> git branch will only list local branches.  The web UI says that this
> commit exists on master though...
>
> [Manish] Same output with -r.
> Can you please share the link of web ui. As per the error it is not on
> master branch.

linux-yoct-dev and linux-yocto-4.4 are different trees. linux-yocto-dev
tracks the latest mainline kernel, not -stable.

So if you are looking for 4.4.3 on linux-yocto-dev, you aren't going
to find it.

[Manish] the 4.4.3 tag is also not on master branch of the 4.4 tree. 
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-4.4/tag/?h=standard/base&id=v4.4.3
The master is 4.4 

A clone and check from tag works manually, but when bitbake fetches it, it 
throws error as bitbake is not able to find the commit on master branch.
How to fix thisk

Bruce

>
>
> Ross
>
>

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

Re: [yocto] Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream

[Bruce Ashfield]

On 2016-04-25 9:05 PM, Jaggi, Manish wrote:



From: Bruce Ashfield [bruce.ashfi...@windriver.com]
Sent: Monday, April 25, 2016 11:04 PM
To: Jaggi, Manish; Burton, Ross
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Fetcher failure: Unable to find revision 
2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream

On 2016-04-25 12:10 PM, Jaggi, Manish wrote:



*From:* Burton, Ross 
*Sent:* Monday, April 25, 2016 8:12 PM
*To:* Jaggi, Manish
*Cc:* yocto@yoctoproject.org
*Subject:* Re: [yocto] Fetcher failure: Unable to find revision
2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from
upstream

On 25 April 2016 at 14:30, Jaggi, Manish
mailto:manish.ja...@caviumnetworks.com>> wrote:

 It seems the revid / tag is not on any branch
 git branch  --contains 2134d97aa3a7ce38bb51f933f2e20cafde371085
 returns nothing.

 How to fix this issue ?


You probably want to use git branch -r --contains 213... as otherwise
git branch will only list local branches.  The web UI says that this
commit exists on master though...

[Manish] Same output with -r.
Can you please share the link of web ui. As per the error it is not on
master branch.


linux-yoct-dev and linux-yocto-4.4 are different trees. linux-yocto-dev
tracks the latest mainline kernel, not -stable.

So if you are looking for 4.4.3 on linux-yocto-dev, you aren't going
to find it.

[Manish] the 4.4.3 tag is also not on master branch of the 4.4 tree.
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-4.4/tag/?h=standard/base&id=v4.4.3
The master is 4.4


It's on standard/base. master is left as the initial branch point of
the repository. When LTSI is available, I tend to update master, but
since 4.4 has no LTSI content, I leave master alone.

Also note: I'm currently not pushing and -stable updates to that tree,
since I'm temporarily frozen for the yocto 2.1 release.




A clone and check from tag works manually, but when bitbake fetches it, it 
throws error as bitbake is not able to find the commit on master branch.
How to fix thisk


don't use master, use standard/base as the branch.

Bruce



Bruce




Ross






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

[yocto] Kernel Build error

[Harinath maddelal]

Hi All,


When i'm trying to build my kernel using yocto, im getting following error

|   CHK include/generated/compile.h
|   AS  arch/mips/kernel/r4k_fpu.o
| 
/home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:
 Assembler messages:
| 
/home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:89:
 Error: opcode not supported on this processor: mips3 (mips3) `sdc1 
$f0,272+0($4)'
| 
/home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:90:
 Error: opcode not supported on this processor: mips3 (mips3) `sdc1 
$f2,272+16($4)'
| 
/home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:91:
 Error: opcode not supported on this processor: mips3 (mips3) `sdc1 
$f4,272+32($4)'
| 
/home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:92:
 Error: opcode not supported on this processor: mips3 (mips3) `sdc1 
$f6,272+48($4)'
| 
/home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:93:
 Error: opcode not supported on this processor: mips3 (mips3) `sdc1 
$f8,272+64($4)'
| 
/home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:94:
 Error: opcode not supported on this processor: mips3 (mips3) `sdc1 
$f10,272+80($4)'
| 
/home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:95:
 Error: opcode not supported on this processor: mips3 (mips3) `sdc1 
$f12,272+96($4)'
| 
/home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:96:
 Error: opcode not supported on this processor: mips3 (mips3) `sdc1 
$f14,272+112($4)'
| 
/home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:97:
 Error: opcode not supported on this processor: mips3 (mips3) `sdc1 
$f16,272+128($4)'
| 
/home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:98:
 Error: opcode not supported on this processor: mips3 (mips3) `sdc1 
$f18,272+144($4)'
| 
/home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:99:
 Error: opcode not supported on this processor: mips3 (mips3) `sdc1 
$f20,272+160($4)'
| 
/home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:100:
 Error: opcode not supported on this processor: mips3 (mips3) `sdc1 
$f22,272+176($4)'



Can you please tell me what could be the issue? We have used mips32r2 in our 
machine file but if the error log is observed where it says "Error: opcode not 
supported on this processor: mips3 (mips3) `sdc1 $f6,272+48($4)".


Can you please help me resolve this issue. Thanks in Advance


Thanks and Regards,
Harinath

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

Re: [yocto] Kernel Build error

[Khem Raj]

which version of kernel are you compiling and what version of gcc is in
play ?

On Mon, Apr 25, 2016 at 11:31 PM Harinath maddelal <
harinath.madd...@inedasystems.com> wrote:

> Hi All,
>
>
> When i'm trying to build my kernel using yocto, im getting following error
>
> |   CHK include/generated/compile.h
> |   AS  arch/mips/kernel/r4k_fpu.o
> |
> /home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:
> Assembler messages:
> |
> /home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:89:
> Error: opcode not supported on this processor: mips3 (mips3) `sdc1
> $f0,272+0($4)'
> |
> /home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:90:
> Error: opcode not supported on this processor: mips3 (mips3) `sdc1
> $f2,272+16($4)'
> |
> /home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:91:
> Error: opcode not supported on this processor: mips3 (mips3) `sdc1
> $f4,272+32($4)'
> |
> /home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:92:
> Error: opcode not supported on this processor: mips3 (mips3) `sdc1
> $f6,272+48($4)'
> |
> /home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:93:
> Error: opcode not supported on this processor: mips3 (mips3) `sdc1
> $f8,272+64($4)'
> |
> /home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:94:
> Error: opcode not supported on this processor: mips3 (mips3) `sdc1
> $f10,272+80($4)'
> |
> /home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:95:
> Error: opcode not supported on this processor: mips3 (mips3) `sdc1
> $f12,272+96($4)'
> |
> /home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:96:
> Error: opcode not supported on this processor: mips3 (mips3) `sdc1
> $f14,272+112($4)'
> |
> /home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:97:
> Error: opcode not supported on this processor: mips3 (mips3) `sdc1
> $f16,272+128($4)'
> |
> /home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:98:
> Error: opcode not supported on this processor: mips3 (mips3) `sdc1
> $f18,272+144($4)'
> |
> /home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:99:
> Error: opcode not supported on this processor: mips3 (mips3) `sdc1
> $f20,272+160($4)'
> |
> /home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/kernel/r4k_fpu.S:100:
> Error: opcode not supported on this processor: mips3 (mips3) `sdc1
> $f22,272+176($4)'
>
>
> Can you please tell me what could be the issue? We have used mips32r2 in
> our machine file but if the error log is observed where it says "Error:
> opcode not supported on this processor: mips3 (mips3) `sdc1 $f6,272+48($4)".
>
>
> Can you please help me resolve this issue. Thanks in Advance
>
>
> Thanks and Regards,
> Harinath
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto