Re: [yocto] Error during webkit compilation for rasberry pi3

2016-12-21 Thread Mont3z Claros
Thanks, Khem. I'll try this.
I've just asked this because I've got a black screen on my monitor
when using VC4 driver and when I've check the UART console I see the
error:

vc4-drm soc:gpu: failed to bind 3f902000.hdmi (ops vc4_hdmi_ops): -517
vc4-drm soc:gpu: master bind failed: -517
vc4-drm soc:gpu: failed to bind 3f902000.hdmi (ops vc4_hdmi_ops): -517
vc4-drm soc:gpu: master bind failed: -517

So, I'll try building it without opencl.
Montez.



On Wed, Dec 21, 2016 at 9:19 AM, Khem Raj <raj.k...@gmail.com> wrote:
> Perhaps by adding -DENABLE_OPENCL=OFF to the EXTRA_OECONF
>
> On Wed, Dec 21, 2016 at 7:20 AM, Mont3z Claros <mont3z.cla...@gmail.com> 
> wrote:
>> Thanks all for the help. I was able to build webkit using:
>> MACHINE_FEATURES += "vc4graphics"
>>
>> I'm sorry for asking those basic questions but is there a way to build
>> webkit without opencl for the raspberry pi3?
>>
>> Thanks,
>> Montez
>>
>> On Sun, Dec 11, 2016 at 9:55 PM, Gary Thomas <g...@mlbassoc.com> wrote:
>>> On 2016-12-11 16:49, Mont3z Claros wrote:
>>>>
>>>> Hi Khem,
>>>>
>>>> this layer is:
>>>>
>>>> https://layers.openembedded.org/layerindex/branch/master/layer/meta-webkit/
>>>>
>>>> I've also tried to use the webkit recipe from poky but I've got the
>>>> same error. In this case I used a different configuration because poky
>>>> doesn't have webkitgtk-bin (mini browser). To test that I've tried to
>>>> build a modified version of meta-web-kiosk
>>>>  (https://github.com/mont3z/meta-web-kiosk). This is still a work in
>>>> progress but basically it replaces midori by epiphany.
>>>>
>>>> local.conf:
>>>> MACHINE = "raspberrypi3"
>>>> DISTRO_FEATURES_append = " x11 gles2"
>>>>
>>>> command:
>>>> bitbake core-image-web-kiosk
>>>>
>>>> bblayes.conf:
>>>> BBLAYERS ?= " \
>>>>   /home/mont3z/yocto/poky/meta \
>>>>   /home/mont3z/yocto/poky/meta-poky \
>>>>   /home/mont3z/yocto/poky/meta-yocto-bsp \
>>>>   /home/mont3z/yocto/meta-openembedded/meta-oe \
>>>>   /home/mont3z/yocto/meta-raspberrypi \
>>>>   /home/mont3z/yocto/meta-web-kiosk \
>>>> "
>>>>
>>>> I also found this discussion about rpi2. I'll try to run some of those
>>>> configurations:
>>>> https://github.com/Igalia/meta-webkit/issues/1
>>>
>>>
>>> I built webkit for rpi3 just fine (yesterday 2016-12-11) using just
>>>   poky: e38775a1d82e6dc60fc96cf243ecb94be964d9b2
>>>   meta-raspberrypi: 44d41bf3e94c4c8fe5ad5a3650572c8d17ef36c9
>>> these were the current master as of then.
>>>
>>> What version(s) are you trying to use?
>>>
>>>
>>>>
>>>> On Sat, Dec 10, 2016 at 1:02 PM, Khem Raj <raj.k...@gmail.com> wrote:
>>>>>
>>>>> On Sat, Dec 10, 2016 at 7:52 AM, Mont3z Claros <mont3z.cla...@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I don't know what I'm doing wrong but I'm getting an error during
>>>>>> compilation of webkit for raspberry pi3. Please see below the error
>>>>>> and my configurations,
>>>>>>
>>>>>> Thanks,
>>>>>> Mont3z
>>>>>>
>>>>>> local.conf:
>>>>>> MACHINE = "raspberrypi3"
>>>>>> DISTRO_FEATURES_append = " x11 gles2"
>>>>>> IMAGE_INSTALL_append = " webkitgtk-bin"
>>>>>>
>>>>>> Error:
>>>>>> | ERROR: oe_runmake failed
>>>>>> | In file included from
>>>>>>
>>>>>> /home/mont3z/yocto/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/webkitgtk/2.14.2-r0/webkitgtk-2.14.2/Source/WebCore/platform/graphics/cairo/GraphicsContext3DCairo.cpp:51:0:
>>>>>> |
>>>>>> /home/mont3z/yocto/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/webkitgtk/2.14.2-r0/webkitgtk-2.14.2/Source/WebCore/platform/graphics/opengl/Extensions3DOpenGLES.h:109:5:
>>>>>> error: 'PFNGLFRAMEBUFFERTEXTURE2DMULTISAMPLEIMGPROC' does not name a
>>>>>> type
>>>>>> |  PFNGLFRAMEBUFFERTEXTURE2DMULTISAMPLEIMGPROC
>>>>>> m_glFramebufferTexture2DMultisampleIMG;
>>>>>> |  ^~~
>>>>>>
>>>>>> command:
>>>>>> bitbake core-image-sato
>>>>>>
>>>>>> bblayes.conf:
>>>>>> BBLAYERS ?= " \
>>>>>>   /home/mont3z/yocto/poky/meta \
>>>>>>   /home/mont3z/yocto/poky/meta-poky \
>>>>>>   /home/mont3z/yocto/poky/meta-yocto-bsp \
>>>>>>   /home/mont3z/yocto/meta-openembedded/meta-oe \
>>>>>>   /home/mont3z/yocto/meta-webkit \
>>>>>
>>>>>
>>>>>
>>>>> what does this layer do ?
>>>>>
>>>>>>   /home/mont3z/yocto/meta-raspberrypi \
>>>>>>   "
>>>
>>>
>>>
>>> --
>>> 
>>> Gary Thomas |  Consulting for the
>>> MLB Associates  |Embedded world
>>> 
>>> --
>>> ___
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Error during webkit compilation for rasberry pi3

2016-12-21 Thread Mont3z Claros
Thanks all for the help. I was able to build webkit using:
MACHINE_FEATURES += "vc4graphics"

I'm sorry for asking those basic questions but is there a way to build
webkit without opencl for the raspberry pi3?

Thanks,
Montez

On Sun, Dec 11, 2016 at 9:55 PM, Gary Thomas <g...@mlbassoc.com> wrote:
> On 2016-12-11 16:49, Mont3z Claros wrote:
>>
>> Hi Khem,
>>
>> this layer is:
>>
>> https://layers.openembedded.org/layerindex/branch/master/layer/meta-webkit/
>>
>> I've also tried to use the webkit recipe from poky but I've got the
>> same error. In this case I used a different configuration because poky
>> doesn't have webkitgtk-bin (mini browser). To test that I've tried to
>> build a modified version of meta-web-kiosk
>>  (https://github.com/mont3z/meta-web-kiosk). This is still a work in
>> progress but basically it replaces midori by epiphany.
>>
>> local.conf:
>> MACHINE = "raspberrypi3"
>> DISTRO_FEATURES_append = " x11 gles2"
>>
>> command:
>> bitbake core-image-web-kiosk
>>
>> bblayes.conf:
>> BBLAYERS ?= " \
>>   /home/mont3z/yocto/poky/meta \
>>   /home/mont3z/yocto/poky/meta-poky \
>>   /home/mont3z/yocto/poky/meta-yocto-bsp \
>>   /home/mont3z/yocto/meta-openembedded/meta-oe \
>>   /home/mont3z/yocto/meta-raspberrypi \
>>   /home/mont3z/yocto/meta-web-kiosk \
>> "
>>
>> I also found this discussion about rpi2. I'll try to run some of those
>> configurations:
>> https://github.com/Igalia/meta-webkit/issues/1
>
>
> I built webkit for rpi3 just fine (yesterday 2016-12-11) using just
>   poky: e38775a1d82e6dc60fc96cf243ecb94be964d9b2
>   meta-raspberrypi: 44d41bf3e94c4c8fe5ad5a3650572c8d17ef36c9
> these were the current master as of then.
>
> What version(s) are you trying to use?
>
>
>>
>> On Sat, Dec 10, 2016 at 1:02 PM, Khem Raj <raj.k...@gmail.com> wrote:
>>>
>>> On Sat, Dec 10, 2016 at 7:52 AM, Mont3z Claros <mont3z.cla...@gmail.com>
>>> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> I don't know what I'm doing wrong but I'm getting an error during
>>>> compilation of webkit for raspberry pi3. Please see below the error
>>>> and my configurations,
>>>>
>>>> Thanks,
>>>> Mont3z
>>>>
>>>> local.conf:
>>>> MACHINE = "raspberrypi3"
>>>> DISTRO_FEATURES_append = " x11 gles2"
>>>> IMAGE_INSTALL_append = " webkitgtk-bin"
>>>>
>>>> Error:
>>>> | ERROR: oe_runmake failed
>>>> | In file included from
>>>>
>>>> /home/mont3z/yocto/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/webkitgtk/2.14.2-r0/webkitgtk-2.14.2/Source/WebCore/platform/graphics/cairo/GraphicsContext3DCairo.cpp:51:0:
>>>> |
>>>> /home/mont3z/yocto/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/webkitgtk/2.14.2-r0/webkitgtk-2.14.2/Source/WebCore/platform/graphics/opengl/Extensions3DOpenGLES.h:109:5:
>>>> error: 'PFNGLFRAMEBUFFERTEXTURE2DMULTISAMPLEIMGPROC' does not name a
>>>> type
>>>> |  PFNGLFRAMEBUFFERTEXTURE2DMULTISAMPLEIMGPROC
>>>> m_glFramebufferTexture2DMultisampleIMG;
>>>> |  ^~~
>>>>
>>>> command:
>>>> bitbake core-image-sato
>>>>
>>>> bblayes.conf:
>>>> BBLAYERS ?= " \
>>>>   /home/mont3z/yocto/poky/meta \
>>>>   /home/mont3z/yocto/poky/meta-poky \
>>>>   /home/mont3z/yocto/poky/meta-yocto-bsp \
>>>>   /home/mont3z/yocto/meta-openembedded/meta-oe \
>>>>   /home/mont3z/yocto/meta-webkit \
>>>
>>>
>>>
>>> what does this layer do ?
>>>
>>>>   /home/mont3z/yocto/meta-raspberrypi \
>>>>   "
>
>
>
> --
> 
> Gary Thomas |  Consulting for the
> MLB Associates  |Embedded world
> 
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Error during webkit compilation for rasberry pi3

2016-12-11 Thread Mont3z Claros
Hi Khem,

this layer is:
https://layers.openembedded.org/layerindex/branch/master/layer/meta-webkit/

I've also tried to use the webkit recipe from poky but I've got the
same error. In this case I used a different configuration because poky
doesn't have webkitgtk-bin (mini browser). To test that I've tried to
build a modified version of meta-web-kiosk
 (https://github.com/mont3z/meta-web-kiosk). This is still a work in
progress but basically it replaces midori by epiphany.

local.conf:
MACHINE = "raspberrypi3"
DISTRO_FEATURES_append = " x11 gles2"

command:
bitbake core-image-web-kiosk

bblayes.conf:
BBLAYERS ?= " \
  /home/mont3z/yocto/poky/meta \
  /home/mont3z/yocto/poky/meta-poky \
  /home/mont3z/yocto/poky/meta-yocto-bsp \
  /home/mont3z/yocto/meta-openembedded/meta-oe \
  /home/mont3z/yocto/meta-raspberrypi \
  /home/mont3z/yocto/meta-web-kiosk \
"

I also found this discussion about rpi2. I'll try to run some of those
configurations:
https://github.com/Igalia/meta-webkit/issues/1

On Sat, Dec 10, 2016 at 1:02 PM, Khem Raj <raj.k...@gmail.com> wrote:
> On Sat, Dec 10, 2016 at 7:52 AM, Mont3z Claros <mont3z.cla...@gmail.com> 
> wrote:
>> Hi all,
>>
>> I don't know what I'm doing wrong but I'm getting an error during
>> compilation of webkit for raspberry pi3. Please see below the error
>> and my configurations,
>>
>> Thanks,
>> Mont3z
>>
>> local.conf:
>> MACHINE = "raspberrypi3"
>> DISTRO_FEATURES_append = " x11 gles2"
>> IMAGE_INSTALL_append = " webkitgtk-bin"
>>
>> Error:
>> | ERROR: oe_runmake failed
>> | In file included from
>> /home/mont3z/yocto/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/webkitgtk/2.14.2-r0/webkitgtk-2.14.2/Source/WebCore/platform/graphics/cairo/GraphicsContext3DCairo.cpp:51:0:
>> | 
>> /home/mont3z/yocto/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/webkitgtk/2.14.2-r0/webkitgtk-2.14.2/Source/WebCore/platform/graphics/opengl/Extensions3DOpenGLES.h:109:5:
>> error: 'PFNGLFRAMEBUFFERTEXTURE2DMULTISAMPLEIMGPROC' does not name a
>> type
>> |  PFNGLFRAMEBUFFERTEXTURE2DMULTISAMPLEIMGPROC
>> m_glFramebufferTexture2DMultisampleIMG;
>> |  ^~~
>>
>> command:
>> bitbake core-image-sato
>>
>> bblayes.conf:
>> BBLAYERS ?= " \
>>   /home/mont3z/yocto/poky/meta \
>>   /home/mont3z/yocto/poky/meta-poky \
>>   /home/mont3z/yocto/poky/meta-yocto-bsp \
>>   /home/mont3z/yocto/meta-openembedded/meta-oe \
>>   /home/mont3z/yocto/meta-webkit \
>
>
> what does this layer do ?
>
>>   /home/mont3z/yocto/meta-raspberrypi \
>>   "
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Error during webkit compilation for rasberry pi3

2016-12-10 Thread Mont3z Claros
Hi all,

I don't know what I'm doing wrong but I'm getting an error during
compilation of webkit for raspberry pi3. Please see below the error
and my configurations,

Thanks,
Mont3z

local.conf:
MACHINE = "raspberrypi3"
DISTRO_FEATURES_append = " x11 gles2"
IMAGE_INSTALL_append = " webkitgtk-bin"

Error:
| ERROR: oe_runmake failed
| In file included from
/home/mont3z/yocto/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/webkitgtk/2.14.2-r0/webkitgtk-2.14.2/Source/WebCore/platform/graphics/cairo/GraphicsContext3DCairo.cpp:51:0:
| 
/home/mont3z/yocto/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/webkitgtk/2.14.2-r0/webkitgtk-2.14.2/Source/WebCore/platform/graphics/opengl/Extensions3DOpenGLES.h:109:5:
error: 'PFNGLFRAMEBUFFERTEXTURE2DMULTISAMPLEIMGPROC' does not name a
type
|  PFNGLFRAMEBUFFERTEXTURE2DMULTISAMPLEIMGPROC
m_glFramebufferTexture2DMultisampleIMG;
|  ^~~

command:
bitbake core-image-sato

bblayes.conf:
BBLAYERS ?= " \
  /home/mont3z/yocto/poky/meta \
  /home/mont3z/yocto/poky/meta-poky \
  /home/mont3z/yocto/poky/meta-yocto-bsp \
  /home/mont3z/yocto/meta-openembedded/meta-oe \
  /home/mont3z/yocto/meta-webkit \
  /home/mont3z/yocto/meta-raspberrypi \
  "
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Meta layer for pine64

2016-09-23 Thread Mont3z Claros
Hi all,

On Thu, Sep 22, 2016 at 12:55 PM, Mont3z Claros <mont3z.cla...@gmail.com> wrote:
> On Thu, Sep 22, 2016 at 10:21 AM, Khem Raj <raj.k...@gmail.com> wrote:
>> On Thu, Sep 22, 2016 at 8:29 AM, Tom Rini <tr...@konsulko.com> wrote:
>>> On Wed, Sep 21, 2016 at 11:39:48AM -0700, Khem Raj wrote:
>>>> On Fri, Sep 16, 2016 at 2:01 PM, Mont3z Claros <mont3z.cla...@gmail.com> 
>>>> wrote:
>>>> > Hi all,
>>>> >
>>>> > I just finished a first beta version of a meta layer for SBC pine64.
>>>> > You can find it in  https://github.com/mont3z/meta-pine64
>>>> >
>>>> > I'd appreciate if anyone has any comments on possible improvements. A
>>>> > major problem I had was the necessity of two toolchains: one for
>>>> > compiling u-boot (32 bits) and another for compiling all other
>>>> > components (64 bis). At the moment I have a very ugly hack to do it.
>>>> > The 32 bit toolchain is an external toolchain and I set PATH
>>>> > environmental variable in u-boot recipe.
>>>>
>>>> I think it would be desirable to have single toolchain, u-boot is a
>>>> stand alone app
>>>> in general, if your compiler can do multilib builds for 32bit then it
>>>> would be possible
>>>> to build it. May be you should work with the toolchain team for pine64 to 
>>>> see if
>>>> that can be done. It will simplify using this layer.
>>>
>>> Actually, pine64 has a 64bit U-Boot, I think maybe the layer just needs
>>> to be updated to use mainline (or v2016.09.01) U-Boot.
>>>
>>>> Other option I would suggest to build u-boot externally for your SoC, we do
>>>> not necessarily need a bootloader for building final images anyway.
>>>
>>> Well, you do if you want a bootable image to be made :)  iirc all of the
>>> models are SD card only, no eMMC so assuming firmware "elsewhere" is a
>>> bad idea.
>>
>> You can always write a recipe to package a prebuilt u-boot.
>>
>
> Hi all,
>
> unfortunately the pine64 mainlilne u-boot is not compatible with the
> kernel I'm compiling.
> To package a prebuilt u-boot could be one solution. At the moment I'm
> investigating the possibility
> of patching u-boot to compile it with multilib.
>

from my research unfortunately the Cortex A53 from pine64 boots in
32-bit mode with armv7-a instruction set.
This means I cannot use -mabi=ilp32 from aarch64 toolchain to compile it.

After some discussion I also found that if I try to use pine64
mainline u-boot than I would need add support to every
weird interface that AW came up with. Which is something I don't even
understand. :-)

So, I'm considering to leave as it is for now and I'll try to add
recipes for mainline u-boot and mainline kernel (which is still beta).

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


Re: [yocto] Meta layer for pine64

2016-09-22 Thread Mont3z Claros
On Thu, Sep 22, 2016 at 10:21 AM, Khem Raj <raj.k...@gmail.com> wrote:
> On Thu, Sep 22, 2016 at 8:29 AM, Tom Rini <tr...@konsulko.com> wrote:
>> On Wed, Sep 21, 2016 at 11:39:48AM -0700, Khem Raj wrote:
>>> On Fri, Sep 16, 2016 at 2:01 PM, Mont3z Claros <mont3z.cla...@gmail.com> 
>>> wrote:
>>> > Hi all,
>>> >
>>> > I just finished a first beta version of a meta layer for SBC pine64.
>>> > You can find it in  https://github.com/mont3z/meta-pine64
>>> >
>>> > I'd appreciate if anyone has any comments on possible improvements. A
>>> > major problem I had was the necessity of two toolchains: one for
>>> > compiling u-boot (32 bits) and another for compiling all other
>>> > components (64 bis). At the moment I have a very ugly hack to do it.
>>> > The 32 bit toolchain is an external toolchain and I set PATH
>>> > environmental variable in u-boot recipe.
>>>
>>> I think it would be desirable to have single toolchain, u-boot is a
>>> stand alone app
>>> in general, if your compiler can do multilib builds for 32bit then it
>>> would be possible
>>> to build it. May be you should work with the toolchain team for pine64 to 
>>> see if
>>> that can be done. It will simplify using this layer.
>>
>> Actually, pine64 has a 64bit U-Boot, I think maybe the layer just needs
>> to be updated to use mainline (or v2016.09.01) U-Boot.
>>
>>> Other option I would suggest to build u-boot externally for your SoC, we do
>>> not necessarily need a bootloader for building final images anyway.
>>
>> Well, you do if you want a bootable image to be made :)  iirc all of the
>> models are SD card only, no eMMC so assuming firmware "elsewhere" is a
>> bad idea.
>
> You can always write a recipe to package a prebuilt u-boot.
>

Hi all,

unfortunately the pine64 mainlilne u-boot is not compatible with the
kernel I'm compiling.
To package a prebuilt u-boot could be one solution. At the moment I'm
investigating the possibility
of patching u-boot to compile it with multilib.

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


[yocto] Meta layer for pine64

2016-09-16 Thread Mont3z Claros
Hi all,

I just finished a first beta version of a meta layer for SBC pine64.
You can find it in  https://github.com/mont3z/meta-pine64

I'd appreciate if anyone has any comments on possible improvements. A
major problem I had was the necessity of two toolchains: one for
compiling u-boot (32 bits) and another for compiling all other
components (64 bis). At the moment I have a very ugly hack to do it.
The 32 bit toolchain is an external toolchain and I set PATH
environmental variable in u-boot recipe.

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


[yocto] Kernel too old with core-image-minimal for Pine64

2016-08-21 Thread Mont3z Claros
Dear all,

I'm working on a bsp layer for SBC Pine64 and my image is successfully
generated but I'm getting "FATAL: kernel too old" when booting the
rootfs init.

My kernel is version 3.10 and I used Linaro 5.3 to compile all
components of the image. I've tried adding: OLDEST_KERNEL = "3.10" and
I also try using Linaro 4.9 but I still get the same error. Please,
see below a snip of the error:

[   13.068932] EXT4-fs (mmcblk0p2): couldn't mount as ext3 due to
feature incompatibilities
[   13.086717] EXT4-fs (mmcblk0p2): couldn't mount as ext2 due to
feature incompatibilities
[   13.112988] EXT4-fs (mmcblk0p2): mounted filesystem with ordered
data mode. Opts: (null)
[   13.127040] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[   13.143393] devtmpfs: mounted
[   13.151972] Freeing unused kernel memory: 520K (ffc0009e4000 -
ffc000a66000)
FATAL: kernel too old
[   13.198566] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x7f00
[   13.198566]
[   13.218884] CPU: 2 PID: 1 Comm: init Not tainted 3.10.102-pine64 #1
[   13.230876] Call trace:

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


[yocto] Image partition with boot0 blob

2016-07-22 Thread Mont3z Claros
Hello all,

I'm trying to create an image with the following partition:

boot0_position=8  # KiB
uboot_position=19096  # KiB

boot0 is a blob and it loads u_boot. Please can some one help me on
this matter?

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


[yocto] Development of stage recipe

2016-07-15 Thread Mont3z Claros
Hi All,

I'm making a recipe to generate a component called ARM Trusted Firmware.
This component is not to be deployed and it'll be used by u-boot recipe to
generate a u-boot image.

I was thinking on using STAGING_LOADER_DIR but it seems that  this is
deprecated. I would like to ask what is the advised directory for such
binary file which is an intermediate product?

I also would like to confirm that I should use:

FILES_${PN} = ""
ALLOW_EMPTY_${PN} = "1"

to avoid this package from being deployed.

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