Hello Yocto Fans,
I am looking for a Yocto / Linux developer (m/w) for a Project in Germany.
I am interested in permanent employees or contractors who know Yocto well.
Concerning contractors part time support would also be an option as well as
remote possibility after a view weeks.
> From: Khem Raj [mailto:raj.k...@gmail.com]
>
> I agree on busybox differences but sometimes its not about
> the utilities they are needed for some sundry work.
> What would be interesting to know is how much size increase
> is caused by replacing all busybox functionality
> with other utiliti
> On Sep 15, 2015, at 7:47 AM, Trevor Woerner wrote:
>
> On 09/15/15 04:26, Paul D. DeRocco wrote:
>> My embedded system has enough room in it for full-featured command line
>> tools, instead of the wretched busybox. Does the Yocto meta-data include a
>> layer that provides such tools? Or does O
I've been redoing an old Danny project with Fido, running on an Atom mobo.
I created a fresh BSP with yocto-bsp, using a RT kernel, and haven't begun
to fiddle with the kernel configuration yet. It gets part way through the
boot process and hangs at "Switching to clocksource tsc". I've googled
this
> From: Bob Cochran
>
> Do you know offhand how much bigger the rootfs would be if you build
> core-image-base without busybox and instead use the real applications?
>
> Also, how many more packages have to be built / managed?
I just added packagegroup-core-full-cmdline to my image, and it incr
> From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
>
> core-image-full-cmdline (and the packagegroup it uses,
> packagegroup-core-full-
> cmdline) should give you the former, and the full tools will
> in almost all
> cases take precedence simply by being installed by virtue of
> the
-e
A release candidate build for yocto-1.8 is now available at:
http://autobuilder.yoctoproject.org/pub/releases/yocto-1.8_M1+snapshot
Please begin QA on this build as soon as possible.
Build hash information:
meta-intel : cea00968b858b60222d68103491f076067d73876
meta-fsl-arm : 24396b28f0
On 09/15/2015 02:22 PM, Trevor Woerner wrote:
On 09/15/15 13:01, Bob Cochran wrote:
On 09/15/2015 12:38 PM, Romain Perier wrote:
Hi all,
I disagree,
Unfortunately some embedded devices in the industry are not like most
of the tablets and smartphones in the market (no quad or octo cores
with fe
On 09/15/15 13:01, Bob Cochran wrote:
> On 09/15/2015 12:38 PM, Romain Perier wrote:
>> Hi all,
>>
>> I disagree,
>> Unfortunately some embedded devices in the industry are not like most
>> of the tablets and smartphones in the market (no quad or octo cores
>> with few GB of ram... and few GB of fl
On 09/15/2015 12:38 PM, Romain Perier wrote:
Hi all,
I disagree,
Unfortunately some embedded devices in the industry are not like most
of the tablets and smartphones in the market (no quad or octo cores
with few GB of ram... and few GB of flash...) ;) .For example,
these days, at work, we're
Hi,
I had a similar problem with you, but was able to fix it by replacing in
some global makefile:
CXX=${CROSS_COMPILE}g++
CC=${CROSS_COMPILE}gcc
LINKER=${CROSS_COMPILE}gcc
LOADER=${CROSS_COMPILE}ldd
with:
#CXX=${CROSS_COMPILE}g++
#CC=${CROSS_COMPILE}gcc
#LINKER=${CROSS_COMPILE}gcc
LINKER=$(CC)
Hi all,
I disagree,
Unfortunately some embedded devices in the industry are not like most
of the tablets and smartphones in the market (no quad or octo cores
with few GB of ram... and few GB of flash...) ;) .For example,
these days, at work, we're designing a board with the SoC zynq-7000
and a
On 09/15/15 12:03, Andy Pont wrote:
> Mark wrote...
>
>>> Bit of a newbie question (probably) but what is the easiest way to dump
>>> sysvinit and use Busybox init in a core-image-minimal image?
>> It has been a while since I've done this. But unless things have changed
>> dramatically. You will
Mark wrote...
> > Bit of a newbie question (probably) but what is the easiest way to dump
> > sysvinit and use Busybox init in a core-image-minimal image?
>
> It has been a while since I've done this. But unless things have changed
> dramatically. You will need to define your own custom image.
Hello,
I am attempting to create an image for a fitlet-x computer (AMD A4
Micro-6400T SoC). I followed the instructions for creating a minimal image
and then used Hob to customize the minimal image as follows:
machine: genericx86-64
image recipe: core-image-minimal-dev
recipe edits: added xserver
On 09/15/2015 10:53 AM, Trevor Woerner wrote:
> On 09/15/15 10:47, Trevor Woerner wrote:
>> The only place busybox (and
>> toybox) are needed today are in the MMU-less-type systems, such as
>> Cortex-Ms etc.
>
> Actually, the presence or lack of MMU is irrelevant, I meant to single
> out those sy
On 09/15/15 10:47, Trevor Woerner wrote:
> The only place busybox (and
> toybox) are needed today are in the MMU-less-type systems, such as
> Cortex-Ms etc.
Actually, the presence or lack of MMU is irrelevant, I meant to single
out those systems with limited on-SoC flash.
--
_
On 09/15/15 04:26, Paul D. DeRocco wrote:
> My embedded system has enough room in it for full-featured command line
> tools, instead of the wretched busybox. Does the Yocto meta-data include a
> layer that provides such tools? Or does OE? And how would I disable
> busybox in order to use the better
Hi Richard,
On 15/09/15 10:45, Richard Purdie wrote:
> On Tue, 2015-09-15 at 10:20 +0100, Chris Simmonds wrote:
>>
>> Also, I am not convinced this is a step in the right direction. I expect
>> to be able to compile a simple program using:
>>
>> $ gcc hello.c -o hello
>>
>> But with this new cross
On 9/15/15 6:16 AM, Andy Pont wrote:
> Hello,
>
> Bit of a newbie question (probably) but what is the easiest way to dump
> sysvinit and use Busybox init in a core-image-minimal image?
It has been a while since I've done this. But unless things have changed
dramatically. You will need to define
Hello,
Bit of a newbie question (probably) but what is the easiest way to dump
sysvinit and use Busybox init in a core-image-minimal image?
Thanks,
Andy.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On 15 September 2015 at 09:45, Paul Eggleton
wrote:
> core-image-full-cmdline (and the packagegroup it uses,
> packagegroup-core-full-
> cmdline) should give you the former, and the full tools will in almost all
> cases take precedence simply by being installed by virtue of the
> alternatives
> s
On Tue, 2015-09-15 at 10:20 +0100, Chris Simmonds wrote:
> On 15/09/15 09:58, Paul Eggleton wrote:
> > Hi Chris,
> >
> > On Tuesday 15 September 2015 09:48:34 Chris Simmonds wrote:
> >> I am using Yocto fido (1.8) to generate an SDK for a BeaglBone. I
> >> generate the it using the command:
> >>
>
On 15/09/15 09:58, Paul Eggleton wrote:
> Hi Chris,
>
> On Tuesday 15 September 2015 09:48:34 Chris Simmonds wrote:
>> I am using Yocto fido (1.8) to generate an SDK for a BeaglBone. I
>> generate the it using the command:
>>
>> $ bitbake core-image-minimal -c populate_sdk
>>
>> Having installed t
Hi Chris,
On Tuesday 15 September 2015 09:48:34 Chris Simmonds wrote:
> I am using Yocto fido (1.8) to generate an SDK for a BeaglBone. I
> generate the it using the command:
>
> $ bitbake core-image-minimal -c populate_sdk
>
> Having installed the resulting SDK and sourced
> /opt/poky/1.8/envir
Hi,
I am using Yocto fido (1.8) to generate an SDK for a BeaglBone. I
generate the it using the command:
$ bitbake core-image-minimal -c populate_sdk
Having installed the resulting SDK and sourced
/opt/poky/1.8/environment-setup-cortexa8hf-vfp-neon-poky-linux-gnueabi
I find that the sysroot is
Hi , all
The version of YP which I using is 1.6.2. When building the openssl, it
appears the problem as following :
ERROR: Function failed: do_configure (log file is located at
/home/ectrs/poky/cortexta8_build/tmp/work/i686-linux/openssl-native/1.0.1j-r0/temp/log.do_configure.
Hi Paul,
On Tuesday 15 September 2015 01:26:20 Paul D. DeRocco wrote:
> My embedded system has enough room in it for full-featured command line
> tools, instead of the wretched busybox. Does the Yocto meta-data include a
> layer that provides such tools? Or does OE? And how would I disable
> busyb
My embedded system has enough room in it for full-featured command line
tools, instead of the wretched busybox. Does the Yocto meta-data include a
layer that provides such tools? Or does OE? And how would I disable
busybox in order to use the better tools?
--
Ciao, Paul D. DeRocco
29 matches
Mail list logo
