[yocto] yocto-1.5.3.rc1 now available

[Flanagan, Elizabeth]

The first release candidate for 1.5.3 is now available at:

http://autobuilder.yoctoproject.org/pub/releases/yocto-1.5.3.rc1

bitbake 3bb3f1823bdd46ab34577d43f1e39046a32bca77
eclipse-poky-juno 79cd3c6ff119526f3f85567253450d2e857afed0
eclipse-poky-kepler e2cc15b1549d197ab15073f52274401d0fd86686
meta-fsl-arm 5fdb620c09df11e70434092f675c891e0ba84108
meta-fsl-ppc 40465bac88ca28b554cff35346341d19552548bf
meta-intel 7203d4de60f69190b5eae308ed2d09edbc63ea1f
meta-minnow 9aa60d0eaf03fe30670acf581eaf7e57c76b5f99
meta-qt3 4772424ab69908d4e3b9d6d4717ca889468e6acd
oecore 026d26e3b6c2f608cc03aa00fe1fb1ace9e070d8
poky dc743744d8e3a9caef577aeab6b7f51bc08ded17


-- 
Elizabeth Flanagan
Yocto Project
Build and Release
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] IMAGE_INSTALL

[Rudolf Streif]

Hi Barath,

That alone won't work. You can either quick and dirty add

IMAGE_INSTALL_append = " coreutils"

to your conf/local.conf file or you write your recipe but it will need to
include another image recipe:

>
> DESCRIPTION = "A test image for Gumstix boards."
> LICENSE = "CLOSED"
>
>  require recipes-core/images/core-image-base.bb


> IMAGE_INSTALL += " \
>   coreutils \
> "
>
>
then you can build your image with bitbake -k myimage given that you named
you recipe above myimage.bb

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

Re: [yocto] IMAGE_INSTALL

[Bharath Chandra]

Hi Rudolf,

I need to include only coreutils package in my image. I have written a
recipe file as follows
My recipe file is as follows:

DESCRIPTION = "A test image for Gumstix boards."
LICENSE = "CLOSED"

IMAGE_INSTALL += " \
  coreutils \
"

Thanks,
Bharath.




On Tue, Jul 8, 2014 at 5:42 PM, Rudolf Streif 
wrote:

> Hi Bharath,
>
> IMAGE_INSTALL += " \
>
>> coreutils \
>> "
>>
>
> You may want to post your entire recipe.
>
>
>> in my image file. But, I do not see any coreutils package in tmp folder.
>> Let me know if my understanding is wrong.
>>
>>
> It should be in tmp/work/i586-poky-linux/coreutils/ if you are building
> for x86.
>
> Did you check your image too?
>
>
> Best regards,
> Rudi
>



-- 
Thanks & Regards,
Bharath Chandra Elluru.
Contact Number:785-979-4875.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] core-image-weston: do_rootfs failure installing libcogl

[Rudolf Streif]

> Can you file a bug?
>


Thanks, Ross. Done. 6514
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] IMAGE_INSTALL

[Rudolf Streif]

Hi Bharath,

IMAGE_INSTALL += " \

> coreutils \
> "
>

You may want to post your entire recipe.


> in my image file. But, I do not see any coreutils package in tmp folder.
> Let me know if my understanding is wrong.
>
>
It should be in tmp/work/i586-poky-linux/coreutils/ if you are building for
x86.

Did you check your image too?


Best regards,
Rudi
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] MIPI for Intel E3800 Bay Trail

[Rudolf Streif]

Søren,

Thank you for your response. Yes, Bay Trail is essentially supported
however I do not know if there are any MIPI drivers available for that
platform.

MIPI stands for the Mobile Industry Processor Interface. The standard is
created by the MIPI Alliance (http://www.mipi.org). Intel Bay Trail E3800
chips support it and so do Freescale i.MX6. The standard defines multiple
interfaces. In this case it's mostly about the camera interface.

Thanks,
Rudi


On Tue, Jul 8, 2014 at 2:56 PM, Søren Holm  wrote:

>
> I don't know what MIPI is but the Baytrail platform is supported from
> v3.13 as
> far as I remember.
>
> Tirsdag den 8. juli 2014 12:14:10 skrev Rudolf Streif:
> > This question is lesser a matter of YP but probably of upstream support.
> > Nevertheless, the YP kernel experts would certainly know. Which, if any,
> of
> > the YP kernels provide MIPI drivers for the Intel E3800?
> >
> > Thanks,
> > Rudi
>
> --
> Søren Holm
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] IMAGE_INSTALL

[Bharath Chandra]

Hi All,

I want to include coreutils package in my image. I have included
IMAGE_INSTALL += " \
coreutils \
"
in my image file. But, I do not see any coreutils package in tmp folder.
Let me know if my understanding is wrong.

Thanks & Regards,
Bharath Chandra Elluru.
Contact Number:785-979-4875.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] MIPI for Intel E3800 Bay Trail

[Søren Holm]

I don't know what MIPI is but the Baytrail platform is supported from v3.13 as 
far as I remember.

Tirsdag den 8. juli 2014 12:14:10 skrev Rudolf Streif:
> This question is lesser a matter of YP but probably of upstream support.
> Nevertheless, the YP kernel experts would certainly know. Which, if any, of
> the YP kernels provide MIPI drivers for the Intel E3800?
> 
> Thanks,
> Rudi

-- 
Søren Holm
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Minimalist Initrd

[Burton, Ross]

On 6 July 2014 04:57, Jeremy Moles  wrote:
> I've encountered a scenario wherein I have only (and this constraint can't
> be worked around) 13MB of space into which I can place a JFFS2 image which
> can be used to continue the system startup (which is initially started by an
> older version of uboot).
>
> I'm having trouble finding a clean solution within the Yocto/OE world for
> this issue. Thus far, I've been using an old, generic, super-tiny ARM-based
> initrd I made years ago which just does a few (proprietary) things in the
> linux and then fires off /sbin/init in the "real" filesystem.
>
> What I need now, however, is a recipe (or perhaps hints on where to start
> when rolling my own recipe) for generating little more than an image (JFFS2
> or cpio.gz) with busybox in it. I can handle the rest view function
> overrides, I just need the base startup.

This sounds exactly like what core-image-minimal-initramfs is for.  If
it's not what you want, it certainly demonstrates how to trim an image
down in size.

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

Re: [yocto] core-image-weston: do_rootfs failure installing libcogl

[Burton, Ross]

On 8 July 2014 18:28, Rudolf Streif  wrote:
> I am attempting to build core-image-weston with Poky from Master. It fails
> creating the rootfs when smart tries to install libcogl (details at the
> end):
>
> error: libcogl20-1.18.0-r0@i586 conflicts with
> libcogl-path20-1.18.0-r0@i586

That's interesting, I just built core-image-weston from master and it
worked fine.  Then again looking at the packages generated and their
contents, something very strange is happening :/

Can you file a bug?

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

[yocto] MIPI for Intel E3800 Bay Trail

[Rudolf Streif]

This question is lesser a matter of YP but probably of upstream support.
Nevertheless, the YP kernel experts would certainly know. Which, if any, of
the YP kernels provide MIPI drivers for the Intel E3800?

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

[yocto] core-image-weston: do_rootfs failure installing libcogl

[Rudolf Streif]

I am attempting to build core-image-weston with Poky from Master. It fails
creating the rootfs when smart tries to install libcogl (details at the
end):

error: libcogl20-1.18.0-r0@i586 conflicts with
libcogl-path20-1.18.0-r0@i586

I have searched for this issue in Bugzilla and across the web. No luck. Is
that something anyone here knows about?

Thanks,
Rudi







Build Configuration:
BB_VERSION= "1.23.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Fedora-18"
TARGET_SYS= "i586-poky-linux"
MACHINE   = "qemux86"
DISTRO    = "poky"
DISTRO_VERSION= "1.6+snapshot-20140708"
TUNE_FEATURES = "m32 i586"
TARGET_FPU= ""
meta
meta-yocto
meta-yocto-bsp= "master:a5531a2b8983318b99c119a87b78a92cf84160b8"

NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Unable to install packages. Command
'/run/media/rudi/SanDisk-256G/develop/yocto/yocto-git/x86/tmp/sysroots/x86_64-linux/usr/bin/smart
--data-dir=/run/media/rudi/SanDisk-256G/develop/yocto/yocto-git/x86/tmp/work/qemux86-poky-linux/core-image-weston/1.0-r0/rootfs/var/lib/smart
install -y packagegroup-core-ssh-dropbear@all psplash@i586
libclutter-1.0-examples@i586 packagegroup-base-extended@qemux86 smartpm@i586
packagegroup-core-tools-debug@qemux86 packagegroup-core-eclipse-debug@all
weston@i586 weston-init@all gtk+3-demo@i586 weston-examples@i586
packagegroup-core-sdk@all packagegroup-core-standalone-sdk-target@all
rpm@i586 packagegroup-core-boot@qemux86 locale-base-en-us@i586
locale-base-en-gb@i586' returned 1:
Loading cache...
Updating cache...   
[100%]

Computing transaction...error: Can't install libcogl-path20-1.18.0-r0@i586:
unable to install provider for libcogl20 >= 1.18.0:
error: libcogl20-1.18.0-r0@i586 conflicts with
libcogl-path20-1.18.0-r0@i586


ERROR: Function failed: do_rootfs
E
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, July 8, 2014 8:00 AM US Pacific Time

[Jolley, Stephen K]

Attendees: Stephen, Michael, Bruce, Tom, David, Saul, Jefro, Nitin, Belen, 
Richard, Mathew, Alex G., Doug, Alex D.,



* Opens collection - 5 min (Stephen)

* Yocto 1.7 status - 5 min (Stephen/team)

https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.7_Status

https://wiki.yoctoproject.org/wiki/Yocto_1.7_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_1.7_Features

We had a number of bugs in YP 1.7 M1 rc1 and so to give us time to fix them we 
did a 1.5.3 build holding off YP 1.7 M1 rc2.  It failed in AB.  So Monday we 
did a build on YP 1.7 M1 rc2 with fixes and it should be out of QA later this 
week.  We will do a build shortly again on YP 1.5.3 with fixes to allow it to 
run in AB successfully.  We should QA YP 1.5.3 next week.



* SWAT team rotation: Richard -> Ross

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team



* Opens - 10 min

Stephen for Denys - It was suggested that we move the bi-weekly schedule to 
starting next week.  This will allow Denys to attend more often.



* Team Sharing - 10 min

Michael - We has some data loss last week and believe all data has been 
restored, but if anyone has issues with the data that was restored, please work 
with Michael.

Richard - We have made some changes to the shared libraries and we have added 
some package dependency checking.


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

[linux-yocto] [PATCH 01/17] net: lsi_acp_net: Added new string to DT match

[Charlie Paul]

From: Anders Berg 

Add a the vendor prefixed compatible string to the match table.

Signed-off-by: Anders Berg 
---
 drivers/net/ethernet/lsi/lsi_acp_net.c |3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/net/ethernet/lsi/lsi_acp_net.c 
b/drivers/net/ethernet/lsi/lsi_acp_net.c
index 5589619..de1e895 100644
--- a/drivers/net/ethernet/lsi/lsi_acp_net.c
+++ b/drivers/net/ethernet/lsi/lsi_acp_net.c
@@ -2078,7 +2078,8 @@ static int __devexit appnic_drv_remove(struct 
platform_device *pdev)
 }
 
 static const struct of_device_id appnic_dt_ids[] = {
-   { .compatible = "acp-femac", }
+   { .compatible = "lsi,acp-femac" },
+   { .compatible = "acp-femac" }
 };
 MODULE_DEVICE_TABLE(of, appnic_dt_ids);
 
-- 
1.7.9.5

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

[linux-yocto] [PATCH 04/17] i2c: axxia: Minor cleanup (cosmetic)

[Charlie Paul]

From: Anders Berg 

Remove unused definitions and remove redundant variable.

Signed-off-by: Anders Berg 
---
 drivers/i2c/busses/i2c-axxia.c |   27 +++
 1 file changed, 11 insertions(+), 16 deletions(-)

diff --git a/drivers/i2c/busses/i2c-axxia.c b/drivers/i2c/busses/i2c-axxia.c
index db1a2d3..7355975 100644
--- a/drivers/i2c/busses/i2c-axxia.c
+++ b/drivers/i2c/busses/i2c-axxia.c
@@ -49,8 +49,6 @@ struct i2c_regs {
__le32 mst_tx_xfer;
__le32 mst_addr_1;
__le32 mst_addr_2;
-#define CHIP_READ(_chip)  (((_chip) << 1) | 1)
-#define CHIP_WRITE(_chip) (((_chip) << 1) | 0)
__le32 mst_data;
__le32 mst_tx_fifo;
__le32 mst_rx_fifo;
@@ -115,9 +113,7 @@ struct axxia_i2c_dev {
struct i2c_adapter adapter;
/* clock reference for i2c input clock */
struct clk *i2c_clk;
-   /* ioremapped registers cookie */
-   void __iomem *base;
-   /* pointer to register struct */
+   /* pointer to registers */
struct i2c_regs __iomem *regs;
/* irq number */
int irq;
@@ -365,7 +361,7 @@ axxia_i2c_isr(int irq, void *_dev)
/* Transfer error? */
idev->msg_err = status & MST_STATUS_ERR;
i2c_int_disable(idev, ~0);
-   dev_err(idev->dev, "error %s, rx=%u/%u tx=%u/%u\n",
+   dev_dbg(idev->dev, "error %s, rx=%u/%u tx=%u/%u\n",
status_str(status),
readl(&idev->regs->mst_rx_bytes_xfrd),
readl(&idev->regs->mst_rx_xfer),
@@ -439,13 +435,13 @@ axxia_i2c_xfer_msg(struct axxia_i2c_dev *idev, struct 
i2c_msg *msg)
i2c_int_enable(idev, int_mask);
 
ret = wait_for_completion_timeout(&idev->msg_complete,
-   I2C_XFER_TIMEOUT);
+ I2C_XFER_TIMEOUT);
 
i2c_int_disable(idev, int_mask);
 
WARN_ON(readl(&idev->regs->mst_command) & 0x8);
 
-   if (WARN_ON(ret == 0)) {
+   if (ret == 0) {
dev_warn(idev->dev, "xfer timeout (%#x)\n", msg->addr);
axxia_i2c_init(idev);
return -ETIMEDOUT;
@@ -471,7 +467,7 @@ axxia_i2c_stop(struct axxia_i2c_dev *idev)
writel(0xb, &idev->regs->mst_command);
i2c_int_enable(idev, int_mask);
ret = wait_for_completion_timeout(&idev->msg_complete,
-   I2C_STOP_TIMEOUT);
+ I2C_STOP_TIMEOUT);
i2c_int_disable(idev, int_mask);
if (ret == 0)
return -ETIMEDOUT;
@@ -500,11 +496,11 @@ axxia_i2c_xfer(struct i2c_adapter *adap, struct i2c_msg 
msgs[], int num)
 static u32
 axxia_i2c_func(struct i2c_adapter *adap)
 {
-   return I2C_FUNC_I2C |
-   I2C_FUNC_10BIT_ADDR |
-   I2C_FUNC_SMBUS_EMUL |
-   I2C_FUNC_SMBUS_BLOCK_DATA;
-
+   u32 caps = (I2C_FUNC_I2C |
+   I2C_FUNC_10BIT_ADDR |
+   I2C_FUNC_SMBUS_EMUL |
+   I2C_FUNC_SMBUS_BLOCK_DATA);
+   return caps;
 }
 
 static const struct i2c_algorithm axxia_i2c_algo = {
@@ -554,7 +550,6 @@ axxia_i2c_probe(struct platform_device *pdev)
goto err_cleanup;
}
 
-   idev->base = base;
idev->regs = (struct __iomem i2c_regs*)base;
idev->i2c_clk  = i2c_clk;
idev->dev  = &pdev->dev;
@@ -627,7 +622,7 @@ axxia_i2c_remove(struct platform_device *pdev)
i2c_del_adapter(&idev->adapter);
free_irq(idev->irq, idev);
clk_put(idev->i2c_clk);
-   iounmap(idev->base);
+   iounmap(idev->regs);
kfree(idev);
return 0;
 }
-- 
1.7.9.5

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

Re: [yocto] Aarch64 support

[Maxin B. John]

Hi Atul,

On Tue, Jul 08, 2014 at 07:43:03PM +0530, atulkumar singh wrote:
> Hi Fathi and Maxin,
> 
> Thanks as you are helping me in sorting out my issue for Aarch64 support in
> meta-toolchain while building bitbake for yocto.
> And "not working" means if we go into the machine/layer/recipes link and under
> the meta-aarch64 layer the git repository link which is mention is not 
> working.
> Please let me know with your valuable suggestion.

The "meta-aarch64" is present in "meta-linaro" repository. 
Clone meta-linaro :

# git clone git://git.linaro.org/openembedded/meta-linaro.git
# cd meta-linaro/meta-aarch64
 
> Thanks and regards,
> Atul
> 
> On 8 Jul 2014 18:14, "Fathi Boudra"  wrote:
> 
> On 8 July 2014 13:27, atulkumar singh  wrote:

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

Re: [yocto] Aarch64 support

[atulkumar singh]

Hi Fathi and Maxin,

Thanks as you are helping me in sorting out my issue for Aarch64 support in
meta-toolchain while building bitbake for yocto.
And "not working" means if we go into the machine/layer/recipes link and
under the meta-aarch64 layer the git repository link which is mention is
not working.
Please let me know with your valuable suggestion.

Thanks and regards,
Atul
On 8 Jul 2014 18:14, "Fathi Boudra"  wrote:

> On 8 July 2014 13:27, atulkumar singh  wrote:
> > Hi Maxin,
> >
> > Thanks for your suggestion for the same.
> > But that git repository for meta-aarch64 is not working.
>
> What do you mean by "not working". We produce daily builds and they're
> tested.
>
> > Thanks and regards
> > Atul
> >
> > On 8 Jul 2014 01:25, "Maxin B. John"  wrote:
> >>
> >> Hi Atul,
> >>
> >> On Tue, Jul 08, 2014 at 12:41:22AM +0530, atulkumar singh wrote:
> >> > Hi All,
> >> >
> >> > Is there support for Aarch64(64 bit ARMv8) available right now?
> >> Yes. Aarch64 support is available in meta-linaro/meta-aarch64
> >> URL: http://git.linaro.org/?p=openembedded/meta-linaro.git
> >>
> >> > If so then what i need to mention as a MACHINE in local.conf.
> >> You can choose between:
> >> 1. genericarmv8b - generic armv8 big endian machine
> >> 2. genericarmv8 - generic armv8 machine
> >>
> >> > Please let me know with your valuable suggestion if any.
> >> Please use http://layers.openembedded.org/
> >> to search Machine/Layers/Recipes supported by OpenEmbedded.
> >>
> >> > Thanks and regards,
> >> > Atul
> >>
> >> Best Regards,
> >> Maxin
> >>
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
>
>
> Cheers,
> --
> Fathi Boudra
> Linaro.org | Open source software for ARM SoCs
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Agenda: Yocto Project Technical Team Meeting - Tuesday, July 8, 2014 8:00 AM US Pacific Time

[Jolley, Stephen K]

Agenda:



* Opens collection - 5 min (Stephen)

* Yocto 1.7 status - 5 min (Stephen/team)

https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.7_Status

https://wiki.yoctoproject.org/wiki/Yocto_1.7_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_1.7_Features

* SWAT team rotation: Ross -> Cristian

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

* Opens - 10 min

* Team Sharing - 10 min





We encourage people attending the meeting to logon the Yocto Project IRC 
chancel during the meeting (optional):



Yocto IRC: http://webchat.freenode.net/?channels=#yocto

IRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html



Conference Details:

Company:   WIND RIVER SYS

Ready-Access Number: 8007302996/9139049836

Access Code: 2705751


For International numbers see: 
https://www.yoctoproject.org/tools-resources/community/weekly-technical-call


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

Re: [yocto] Aarch64 support

[Fathi Boudra]

On 8 July 2014 13:27, atulkumar singh  wrote:
> Hi Maxin,
>
> Thanks for your suggestion for the same.
> But that git repository for meta-aarch64 is not working.

What do you mean by "not working". We produce daily builds and they're tested.

> Thanks and regards
> Atul
>
> On 8 Jul 2014 01:25, "Maxin B. John"  wrote:
>>
>> Hi Atul,
>>
>> On Tue, Jul 08, 2014 at 12:41:22AM +0530, atulkumar singh wrote:
>> > Hi All,
>> >
>> > Is there support for Aarch64(64 bit ARMv8) available right now?
>> Yes. Aarch64 support is available in meta-linaro/meta-aarch64
>> URL: http://git.linaro.org/?p=openembedded/meta-linaro.git
>>
>> > If so then what i need to mention as a MACHINE in local.conf.
>> You can choose between:
>> 1. genericarmv8b - generic armv8 big endian machine
>> 2. genericarmv8 - generic armv8 machine
>>
>> > Please let me know with your valuable suggestion if any.
>> Please use http://layers.openembedded.org/
>> to search Machine/Layers/Recipes supported by OpenEmbedded.
>>
>> > Thanks and regards,
>> > Atul
>>
>> Best Regards,
>> Maxin
>>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>


Cheers,
-- 
Fathi Boudra
Linaro.org | Open source software for ARM SoCs
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] some wiki pages on building your very first poky/yocto project

[Robert P. J. Day]

  not sure if others will find this useful but i'm teaching an
oe/poky/yocto course in a couple weeks, and i decided to slap together
some publicly-readable wiki pages that i plan on sending ahead of time
to upcoming students to walk them through setting up their development
host, and downloading, and finally building their very first project,
the purpose being so that when i show up that first morning, everyone
has a build host ready to go and we don't have to waste any time
downloading packages and layers and so on.

  everything falls off of this new top-level wiki page of mine:

http://www.crashcourse.ca/wiki/index.php/Poky

and the plan is for impending students to read and work through the
sections:

* Setting up your build host
* Doing your first build

  there's lots more coming, but those first two sections should act as
pre-class preparation. i'm still adding stuff to them, but if anyone
has any thoughts on what else to put there, feel free. it's all very
ad hoc, but i really want to avoid wasted time the first morning of
the course screwing around with build hosts.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

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

Re: [yocto] Aarch64 support

[Maxin B. John]

Hi Atul,

On Tue, Jul 08, 2014 at 03:57:44PM +0530, atulkumar singh wrote:
> Hi Maxin,
> 
> Thanks for your suggestion for the same.
> But that git repository for meta-aarch64 is not working.

"It works for me" ..

# git clone git://git.linaro.org/openembedded/meta-linaro.git

> Thanks and regards
> Atul

Best Regards,
Maxin
 
> On 8 Jul 2014 01:25, "Maxin B. John"  wrote:
> 
> Hi Atul,
> 
> On Tue, Jul 08, 2014 at 12:41:22AM +0530, atulkumar singh wrote:
> > Hi All,
> >
> > Is there support for Aarch64(64 bit ARMv8) available right now?
> Yes. Aarch64 support is available in meta-linaro/meta-aarch64
> URL: http://git.linaro.org/?p=openembedded/meta-linaro.git
> 
> > If so then what i need to mention as a MACHINE in local.conf.
> You can choose between:
> 1. genericarmv8b - generic armv8 big endian machine
> 2. genericarmv8 - generic armv8 machine
> 
> > Please let me know with your valuable suggestion if any.
> Please use http://layers.openembedded.org/
> to search Machine/Layers/Recipes supported by OpenEmbedded.
> 
> > Thanks and regards,
> > Atul
> 
> Best Regards,
> Maxin
> 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Aarch64 support

[atulkumar singh]

Hi Maxin,

Thanks for your suggestion for the same.
But that git repository for meta-aarch64 is not working.

Thanks and regards
Atul
On 8 Jul 2014 01:25, "Maxin B. John"  wrote:

> Hi Atul,
>
> On Tue, Jul 08, 2014 at 12:41:22AM +0530, atulkumar singh wrote:
> > Hi All,
> >
> > Is there support for Aarch64(64 bit ARMv8) available right now?
> Yes. Aarch64 support is available in meta-linaro/meta-aarch64
> URL: http://git.linaro.org/?p=openembedded/meta-linaro.git
>
> > If so then what i need to mention as a MACHINE in local.conf.
> You can choose between:
> 1. genericarmv8b - generic armv8 big endian machine
> 2. genericarmv8 - generic armv8 machine
>
> > Please let me know with your valuable suggestion if any.
> Please use http://layers.openembedded.org/
> to search Machine/Layers/Recipes supported by OpenEmbedded.
>
> > Thanks and regards,
> > Atul
>
> Best Regards,
> Maxin
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] GDB related issue on host machine

[Vinay Kumar. G]

Hi,

I am new to this forum. I am facing some difficulties in debugging a.out
on host os(without target connection). Using "powerpc-poky-linux-gdb a.out".

Once entered to gdb did below steps
set sysroot /home/../ppc/sysroots/ppc7400-poky-linux
file a.out
b main
continue  > shows message The program is not being run.

If I execute "run" gives "The program is not being run."

Any help is appreciated. :)
Thanks.
This message contains information that may be privileged or confidential and is 
the property of the KPIT Technologies Ltd. It is intended only for the person 
to whom it is addressed. If you are not the intended recipient, you are not 
authorized to read, print, retain copy, disseminate, distribute, or use this 
message or any part thereof. If you receive this message in error, please 
notify the sender immediately and delete all copies of this message. KPIT 
Technologies Ltd. does not accept any liability for virus infected mails.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QEMU in SDK

[Chong Lu]

I mean you can use adt-installer to make your sdk environment. (3.1.1. 
Using the ADT Installer)
After you run adt-installer script, you can get kernel and rootfs in 
download_image directory.


Best Regards
Chong


On 07/08/2014 05:39 PM, Joseph Andrew de la Peña wrote:

Good day Chong,

Actually, I have used ADT (Section 3.4 Optionally Building a Toolchain 
Installer). I used the method -c populate_sdk and it generated a 
toolchain script from my existing build workdir's core-image-XXX. I 
ran the toolchain and it generated a sysroots dir to /path/to/sysroots 
(SDK_PATH).


Here's the directory structure:
+ SDK_PATH
--- + environment-setup-XXX
--- + site-config-XXX
--- + sysroots (dir)
-- + XXX-poky-linux (dir)
-- + XXX-pokysdk-linux (dir)
--- + version-XXX

The poky-linux dir does not contain a build dir and nowhere are the 
images (kernel and ext3) to be found. Thus, the main problem is how 
can I ran qemu with my SDK setup. This would lead to my sub question: 
since QEMU needs the kernel and ext3 files, how can I automatically 
copy these images from my existing build workdir to the newly created 
SDK dir.


Thanks,
Joseph





On Tue, Jul 8, 2014 at 3:26 PM, Chong Lu > wrote:


Hi Joseph,

Maybe you can use adt-installer.


http://www.yoctoproject.org/docs/latest/adt-manual/adt-manual.html#using-the-adt-installer

Best Regards
Chong

On 07/08/2014 02:15 PM, Joseph Andrew de la Peña wrote:

Good day ALL,

I was wondering if it's possible to automatically add QEMU
dependencies (kernel and ext3 files) into the script generated by
do_populate_sdk? Then after running the generated SDK script, the
images will reside in /path/to/sysroots/xxx-poky-xxx/tmp/images?
Then just add an environment variable to the environment script
to locate the images path. Is this possible?

The intention is to run QEMU in a host machine with extracted
SDK. Any suggestions on other better ways to run QEMU in another
machine w/ SDK would be great.

Thanks,
Joseph







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

Re: [yocto] QEMU in SDK

[Joseph Andrew de la Peña]

Good day Chong,

Actually, I have used ADT (Section 3.4 Optionally Building a Toolchain
Installer). I used the method -c populate_sdk and it generated a toolchain
script from my existing build workdir's core-image-XXX. I ran the toolchain
and it generated a sysroots dir to /path/to/sysroots (SDK_PATH).

Here's the directory structure:
+ SDK_PATH
--- + environment-setup-XXX
--- + site-config-XXX
--- + sysroots (dir)
-- + XXX-poky-linux (dir)
-- + XXX-pokysdk-linux (dir)
--- + version-XXX

The poky-linux dir does not contain a build dir and nowhere are the images
(kernel and ext3) to be found. Thus, the main problem is how can I ran qemu
with my SDK setup. This would lead to my sub question: since QEMU needs the
kernel and ext3 files, how can I automatically copy these images from my
existing build workdir to the newly created SDK dir.

Thanks,
Joseph





On Tue, Jul 8, 2014 at 3:26 PM, Chong Lu  wrote:

>  Hi Joseph,
>
> Maybe you can use adt-installer.
>
>
> http://www.yoctoproject.org/docs/latest/adt-manual/adt-manual.html#using-the-adt-installer
>
> Best Regards
> Chong
>
> On 07/08/2014 02:15 PM, Joseph Andrew de la Peña wrote:
>
> Good day ALL,
>
>  I was wondering if it's possible to automatically add QEMU dependencies
> (kernel and ext3 files) into the script generated by do_populate_sdk? Then
> after running the generated SDK script, the images will reside in
> /path/to/sysroots/xxx-poky-xxx/tmp/images? Then just add an environment
> variable to the environment script to locate the images path. Is this
> possible?
>
>  The intention is to run QEMU in a host machine with extracted SDK. Any
> suggestions on other better ways to run QEMU in another machine w/ SDK
> would be great.
>
>  Thanks,
> Joseph
>
>
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] kernel source code

[Robert Yang]

On 07/08/2014 02:04 PM, jags gediya wrote:

I have run below command

bitbake -c fetchall core-image-minimal

It has created downloads directory and packages source codes are
there inside, but i am not able to find the kernel and u-boot source code.


By default, the kernel-source code is:

/downloads/git2/git.yoctoproject.org.linux-yocto-3.14.git

And the u-boot is:
/downloads/git2/git.denx.de.u-boot.git

You can check the SRC_URI in the recipe to figure out the source type, they will
be in DL_DIR if tarball, and DL_DIR/git2 if git, the similar to svn (DL_DIR/svn)
and others.

Usually, the "bitbake -e  >recipe.py" then look at recipe.py helps.

// Robert



I have build core-image-minimal without internet connectivity, and kernel and
u-boot have also built properly. I am not getting from where it is taking
the source code for kernel and u-boot.

I am building yocto sdk for imx6l evolution kit and i have checked out
daisy branch.

Please suggest where can be the source code for kernel and u-boot
before build but after running fetchall command.


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

Re: [yocto] QEMU in SDK

[Chong Lu]

Hi Joseph,

Maybe you can use adt-installer.

http://www.yoctoproject.org/docs/latest/adt-manual/adt-manual.html#using-the-adt-installer

Best Regards
Chong

On 07/08/2014 02:15 PM, Joseph Andrew de la Peña wrote:

Good day ALL,

I was wondering if it's possible to automatically add QEMU 
dependencies (kernel and ext3 files) into the script generated by 
do_populate_sdk? Then after running the generated SDK script, the 
images will reside in /path/to/sysroots/xxx-poky-xxx/tmp/images? Then 
just add an environment variable to the environment script to locate 
the images path. Is this possible?


The intention is to run QEMU in a host machine with extracted SDK. Any 
suggestions on other better ways to run QEMU in another machine w/ SDK 
would be great.


Thanks,
Joseph




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