[yocto] Compiling meta-browser ==>chromium ? cleaning ?

[Riko Ho]

Hello Everyone,

I tried to compile chromium but never succeeded, took me already 12 
hours and stopped on 99%,

I used bitbake for doing it,

Is chromium not compatible with arm CPU ? it was working with X86_64 
before.

And how can I clean after building it ? It took about 70Gb of my drive

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

Re: [yocto] [meta-rockchip][PATCH 2/2] u-boot: Backport upstream fix for gmac_rockchip

[Trevor Woerner]

Hi Romain,

I assume this patch is meant to fix an ethernet issue in u-boot? How does
someone test that ethernet is working from u-boot?

Here is my firefly booting with these patches:


U-Boot SPL 2017.05 (Jun 17 2017 - 17:12:20)
Returning to boot ROM...

U-Boot 2017.05 (Jun 17 2017 - 17:12:20 -0400)

Model: Firefly-RK3288
DRAM:  1.7 GiB
MMC:   dwmmc@ff0c: 1, dwmmc@ff0f: 0
*** Warning - bad CRC, using default environment

In:serial
Out:   serial
Err:   serial
Net:   
Warning: ethernet@ff29 (eth0) using random MAC address - 
5a:40:1a:28:0e:43
eth0: ethernet@ff29
Hit any key to stop autoboot:  0 

Here is me configuring the networking stuff in u-boot:

=> setenv ipaddr 192.168.142.20
=> setenv netmask 255.255.255.0
=> setenv serverip 192.168.142.1

Then I try pinging my server:

=> ping 192.168.142.1
ethernet@ff29 Waiting for PHY auto negotiation to complete... done
Speed: 100, full duplex
Using ethernet@ff29 device

The next thing I know my firefly is rebooting:

data abort
pc : [<6ada703a>]  lr : [<6ada7dbb>]
reloc pc : [<0003303a>]lr : [<00033dbb>]
sp : 68d67e48  ip :  fp : 0002
r10: 68d77e60  r9 : 68d71ee8 r8 : 
r7 : 0001  r6 :  r5 : 002a  r4 : 6adfd04e
r3 : 1445  r2 : 148ea8c0 r1 : 018ea8c0  r0 : 6adfd04e
Flags: nzcv  IRQs off  FIQs off  Mode SVC_32
Resetting CPU ...


U-Boot SPL 2017.05 (Jun 17 2017 - 17:12:20)
Returning to boot ROM...
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] sdcard_image-rpi.bbclass: deploy vfat partition

[Khem Raj]

On Sat, Jun 17, 2017 at 8:20 AM, Tom Rini  wrote:
> On Fri, Jun 16, 2017 at 06:05:07PM -0700, Khem Raj wrote:
>> On Fri, Jun 16, 2017 at 12:12 PM, Matthew McClintock
>>  wrote:
>> > This is useful to update the bootloader/vfat partition from u-boot when
>> > you don't want to update everything:
>> >
>> > U-Boot> tftpboot 0x100 tmp/0VXje
>> > Waiting for Ethernet connection... done.
>> > Using sms0 device
>> > TFTP from server 192.168.0.1; our IP address is 192.168.0.26
>> > Filename 'image.vfat'.
>> > Load address: 0x100
>> > Loading: ##  40 MiB
>> >  2.1 MiB/s
>> > done
>> > Bytes transferred = 41943040 (280 hex)
>> > U-Boot> mmc part
>> >
>> > Partition Map for MMC device 0  --   Partition Type: DOS
>> >
>> > PartStart SectorNum Sectors UUIDType
>> >   1 819281920   a63a4fbc-01 0c Boot
>> >   2 90112   163840  a63a4fbc-02 83
>> > U-Boot> mmc erase 0x2000 0x14000
>> >
>> > MMC erase: dev # 0, block # 8192, count 81920 ... 81920 blocks erased:
>> > OK
>> > U-Boot> mmc write 0x100 0x2000 0x14000
>> >
>> > MMC write: dev # 0, block # 8192, count 81920 ... 81920 blocks written:
>> > OK
>> > U-Boot>
>> >
>> > Signed-off-by: Matthew McClintock 
>> > ---
>> >  classes/sdcard_image-rpi.bbclass | 8 
>> >  1 file changed, 8 insertions(+)
>> >
>> > diff --git a/classes/sdcard_image-rpi.bbclass 
>> > b/classes/sdcard_image-rpi.bbclass
>> > index af3e807..27a0dfc 100644
>> > --- a/classes/sdcard_image-rpi.bbclass
>> > +++ b/classes/sdcard_image-rpi.bbclass
>> > @@ -72,6 +72,10 @@ SDIMG = "${IMGDEPLOYDIR}/${IMAGE_NAME}.rootfs.rpi-sdimg"
>> >  # Additional files and/or directories to be copied into the vfat 
>> > partition from the IMAGE_ROOTFS.
>> >  FATPAYLOAD ?= ""
>> >
>> > +# SD card vfat partition image name
>> > +SDIMG_VFAT = "${IMGDEPLOYDIR}/${IMAGE_NAME}.vfat"
>> > +SDIMG_LINK_VFAT = "${IMGDEPLOYDIR}/${IMAGE_LINK_NAME}.vfat"
>> > +
>> >  IMAGE_CMD_rpi-sdimg () {
>> >
>> > # Align partitions
>> > @@ -145,6 +149,10 @@ IMAGE_CMD_rpi-sdimg () {
>> > echo "${IMAGE_NAME}" > ${WORKDIR}/image-version-info
>> > mcopy -i ${WORKDIR}/boot.img -v ${WORKDIR}/image-version-info ::
>> >
>> > +# Deploy vfat partition
>> > +cp ${WORKDIR}/boot.img ${SDIMG_VFAT}
>> > +ln -sf ${SDIMG_VFAT} ${SDIMG_LINK_VFAT}
>> > +
>>
>> it is of use if I am not using u-boot ? is there any penalty ?
>
> The stock firmware also uses a vfat partition, so this could just as
> easily hold those contents.

yes it does, can it do the same operations like u-boot ?

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

Re: [yocto] [meta-raspberrypi][PATCH] sdcard_image-rpi.bbclass: deploy vfat partition

[Tom Rini]

On Fri, Jun 16, 2017 at 06:05:07PM -0700, Khem Raj wrote:
> On Fri, Jun 16, 2017 at 12:12 PM, Matthew McClintock
>  wrote:
> > This is useful to update the bootloader/vfat partition from u-boot when
> > you don't want to update everything:
> >
> > U-Boot> tftpboot 0x100 tmp/0VXje
> > Waiting for Ethernet connection... done.
> > Using sms0 device
> > TFTP from server 192.168.0.1; our IP address is 192.168.0.26
> > Filename 'image.vfat'.
> > Load address: 0x100
> > Loading: ##  40 MiB
> >  2.1 MiB/s
> > done
> > Bytes transferred = 41943040 (280 hex)
> > U-Boot> mmc part
> >
> > Partition Map for MMC device 0  --   Partition Type: DOS
> >
> > PartStart SectorNum Sectors UUIDType
> >   1 819281920   a63a4fbc-01 0c Boot
> >   2 90112   163840  a63a4fbc-02 83
> > U-Boot> mmc erase 0x2000 0x14000
> >
> > MMC erase: dev # 0, block # 8192, count 81920 ... 81920 blocks erased:
> > OK
> > U-Boot> mmc write 0x100 0x2000 0x14000
> >
> > MMC write: dev # 0, block # 8192, count 81920 ... 81920 blocks written:
> > OK
> > U-Boot>
> >
> > Signed-off-by: Matthew McClintock 
> > ---
> >  classes/sdcard_image-rpi.bbclass | 8 
> >  1 file changed, 8 insertions(+)
> >
> > diff --git a/classes/sdcard_image-rpi.bbclass 
> > b/classes/sdcard_image-rpi.bbclass
> > index af3e807..27a0dfc 100644
> > --- a/classes/sdcard_image-rpi.bbclass
> > +++ b/classes/sdcard_image-rpi.bbclass
> > @@ -72,6 +72,10 @@ SDIMG = "${IMGDEPLOYDIR}/${IMAGE_NAME}.rootfs.rpi-sdimg"
> >  # Additional files and/or directories to be copied into the vfat partition 
> > from the IMAGE_ROOTFS.
> >  FATPAYLOAD ?= ""
> >
> > +# SD card vfat partition image name
> > +SDIMG_VFAT = "${IMGDEPLOYDIR}/${IMAGE_NAME}.vfat"
> > +SDIMG_LINK_VFAT = "${IMGDEPLOYDIR}/${IMAGE_LINK_NAME}.vfat"
> > +
> >  IMAGE_CMD_rpi-sdimg () {
> >
> > # Align partitions
> > @@ -145,6 +149,10 @@ IMAGE_CMD_rpi-sdimg () {
> > echo "${IMAGE_NAME}" > ${WORKDIR}/image-version-info
> > mcopy -i ${WORKDIR}/boot.img -v ${WORKDIR}/image-version-info ::
> >
> > +# Deploy vfat partition
> > +cp ${WORKDIR}/boot.img ${SDIMG_VFAT}
> > +ln -sf ${SDIMG_VFAT} ${SDIMG_LINK_VFAT}
> > +
> 
> it is of use if I am not using u-boot ? is there any penalty ?

The stock firmware also uses a vfat partition, so this could just as
easily hold those contents.

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

Re: [yocto] Qt5 will not build on Yocto edison image

[Ferry Toth]

I'm interrested in this too.

Edison has no display. So I think the question is what DISTRO_FEATURES to 
set.

As it is now, the following error occurs:
EGL disabled.
| Warning: Disabling Accessibility. This version of Qt is unsupported.
| No QPA platform plugin enabled!
|  If you really want to build without a QPA platform plugin you must pass
|  -no-qpa-platform-guard to configure. Doing this will
|  produce a Qt that can not run GUI applications.
|  The dependencies needed for xcb to build are listed in
|  src/plugins/platforms/xcb/README

However I don't think the layer has any PACKAGECONFIG that sets -no-qpa-
platform-guard.

So, what DISTRO_FEATURES need to be set to get a non-GUI Qt that runs on 
a headless server?

Op Thu, 15 Jun 2017 22:58:32 -0700, schreef Khem Raj:

> On 6/15/17 6:30 AM, Franck Furic wrote:
>> Hi,
>> 
>> 
>>  
>> I have bought an Intel Edison board and I would like build my image
>> including Qt Framework (meta-qt5).
>> 
>> 
>>  
>> In the past, (2 years ago) I have success to compile C++ program using
>> Qt by build my image with meta-qt5 I think it was 1.6.x version of
>> yocto project.
>> 
>> 
>>  
>> Now, it’s impossible for me to build an image including qt on yocto. I
>> have tried many thinks in different ways but nothing at the end.
>> 
>> 
>>  
>> Some people help me to do this here
>> https://communities.intel.com/thread/115234.
>> 
>> 
>>  
>> I have tried on dizzy branch and morty branch but i have always errors.
>> 
>> 
>>  
>> Someone can help me tell me the correct procedure to build an image
>> containing meta-qt5 on any version of yocto.
>> 
>> 
>>  
>> I need to develop some code with Qt Framework.
> 
> you can add the needed bits to image yourself. Like
> 
> IMAGE_INSTALL_append = "\
> qtbase \ qtbase-tools \ qtbase-fonts \ qtbase-plugins \ qtwebkit \
> qtwayland \ qtwayland-plugins \ cinematicexperience \
> "
> 
> in local.conf
> 
> 
> 
> 
>> 
>>  
>> 
>>  
>> Description : FranckFuric
>> 
>> 
>>  
>> Description : Facebook 
>> Description : youtube-logo   
>>  Site web :
>> www.madelin-sa.com   |  E-boutique :
>> www.storemadelin-sa.com 
>> 
>> 
__
>> 
>> Ce message contient des informations confidentielles ou appartenant à
>> la société MADELIN SA et est établi à l'attention  exclusive de ses
>> destinataires.
>> 
>> Toute divulgation, utilisation, diffusion ou reproduction (totale ou
>> partielle) de ce message, ou des informations qu'il contient, doit être
>> préalablement autorisée.
>> 
>> Si vous n'êtes pas destinataire de ce message, merci de le détruire
>> immédiatement et d'avertir l'expéditeur de l'erreur de distribution et
>> de la destruction du message
>> 
>> 
>>  
>> 
>>


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