Re: [yocto] I hate busybox!

> 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

Re: [yocto] I hate busybox!

> 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

[yocto] Hanging during kernel boot

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

Re: [yocto] I hate busybox!

> 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 >

Re: [yocto] I hate busybox!

> 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

Re: [yocto] I hate busybox!

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

Re: [yocto] I hate busybox!

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

Re: [yocto] gcc reports sysroot is /not/exist!

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

[yocto] Legacy library find.pl will be removed from the Perl core distribution in the next major release

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

[yocto] gcc reports sysroot is /not/exist!

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

Re: [yocto] gcc reports sysroot is /not/exist!

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 >

[linux-yocto] FW: [PATCH] Bluetooth: Delay check for conn->smp in smp_conn_security()

Hi all, I am sorry to send a few copies of this patch there. According to the original author request, the patch need to keep the original author info. Therefore, I modified the related comments, so that match the author request. Best Regards Zheng Wu >-Original Message- >From:

[yocto] I hate busybox!

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

Re: [yocto] gcc reports sysroot is /not/exist!

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

Re: [yocto] gcc reports sysroot is /not/exist!

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: > >>

Re: [yocto] I hate busybox!

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 >

[linux-yocto] [PATCH] Bluetooth: Delay check for conn->smp in smp_conn_security()

From: Johan Hedberg There are several actions that smp_conn_security() might make that do not require a valid SMP context (conn->smp pointer). One of these actions is to encrypt the link with an existing LTK. If the SMP context wasn't initialized properly we should still

Re: [yocto] I hate busybox!

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

Re: [yocto] Dumping sysvinit

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.

Re: [yocto] Dumping sysvinit

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

Re: [yocto] I hate busybox!

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

[yocto] Trouble installing from usb

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

Re: [yocto] I hate busybox!

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

[yocto] Release Candidate Build for yocto-1.8 now available.

-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 :

Re: [yocto] I hate busybox!

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

[yocto] Dumping sysvinit

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

Re: [yocto] Dumping sysvinit

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

Re: [yocto] gcc reports sysroot is /not/exist!

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

Re: [yocto] I hate busybox!

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

Re: [yocto] I hate busybox!

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. --