Re: [yocto] How to customize a file coming from another recipe?

Hi, On 11/09/13 20:24, Brad Litterell wrote: > This installs a default configuration file for the service which I now > want to customize. What is the recommended way to overwrite or > customize files in another package? > > Is the best course to create a recipe bbappend for the > lighttpd_1.4.3

Re: [yocto] Sending mail from embedded device

On 06/08/13 18:27, Gary Thomas wrote: > On 2013-08-06 10:01, Mark Hatle wrote: >> On 8/6/13 10:00 AM, Jack Mitchell wrote: >>> On 06/08/13 15:50, Mark Hatle wrote: On 8/6/13 9:41 AM, Jack Mitchell wrote: > On 06/08/13 15:31, Gary Thomas wrote: >> My embedded device needs to send out em

Re: [yocto] Network booting

On 02/08/13 08:35, Chris Tapp wrote: >> Depends on the bios, if your machine's bios supports PXE, then you >> do not need ipxe, just a tftp server set up on the LAN that serves >> PXELinux. > > My case is a bit more complicated as I also can't have non-secure > (t)ftp! Are you saying that PXE can

Re: [yocto] Network booting

On 01/08/13 19:53, Chris Tapp wrote: > I think it is ;-) I think I'll still need to use ipxe as I need to be > able to boot without DHCP support as well. Depends on the bios, if your machine's bios supports PXE, then you do not need ipxe, just a tftp server set up on the LAN that serves PXELinux.

Re: [yocto] Network booting

Hi Chris, On 01/08/13 09:08, Tomas Frydrych wrote: > On 31/07/13 21:30, Chris Tapp wrote: > It's relatively easy to add support for tftp to the yocto live image > scripts; this allows you to either boot from the network, or install > from the network. I have have some raw patch

Re: [yocto] Network booting

On 31/07/13 21:30, Chris Tapp wrote: > Is there an easy way to have a system boot and load the rootfs from a > network server? > > I'm using an x86 system and can have the kernel and an initrd on it. > I would use bootp, but a lot of end users either don't have this or > will not allow it to be us

Re: [yocto] Changing syslinux configuration

On 06/07/13 02:23, Paul D. DeRocco wrote: > Does anyone know what recipe actually sets LABELS? The relevant image classes do. Tomas -- http://sleepfive.com ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] Userland and vc-graphics

On 06/07/13 12:22, Paul Barker wrote: > So if there recipes are fulfilling the exact same purpose, I think we > should strip out vc-graphics completely and always build from source. > I've never seen a use case for the pre-compiled vc-graphics recipes > within OpenEmbedded/Yocto. > > Does anyone e

Re: [yocto] run commands after installation

On 26/06/13 15:32, Katu Txakur wrote: > I want to create a user after adding the snmp recipe. The command to do > that is: > > net-snmp-config --create-snmpv3-user -a "my_password" myuser > > What's the best way to do it? I have tried from do_install_append and > also from ROOTFS_POSTPROCESS_COMM

Re: [yocto] -rt and COMPATIBLE_MACHINES

Hi Paul, On 20/06/13 20:40, Paul D. DeRocco wrote: > My question is this: why was I able to build core-image base without > complaint in the first place? The kernel recipes it has available > (linux-yocto_*) also set COMPATIBLE_MACHINE to a list of qemu machines. It probably built the linux-dummy

Re: [yocto] Error including meta-oracle-java in custom image

Hi, On 04/06/13 08:41, Marcelo Valle wrote: > 1. > Fetcher failure for URL: > 'http://download.oracle.com/otn-pub/java/jdk/7u2-b13/jre-7u2-linux-x64.tar.gz'. > Checksum mismatch! > > ... > > To fix it i've update oracle-jse-jre-x86-64_1.7.0.bb > with these

Re: [yocto] Commercial usage of Yocto

Hi, On 04/06/13 05:35, Kumita Bruce wrote: > I have one question, can Yocto be used for commercial purpose? If the > answer is yes, what should I do before using it for commercial purpose? Yocto is used in scores of a great variety of commercial products out there, which is facilitated by the br

Re: [yocto] [meta-raspberrypi] Thoughts on Raspberry Pi firmware

On 14/05/13 13:09, Paul Barker wrote: > Secondly, is there any use case for building vc-graphics or > vc-graphics-hardfp to provide virtual/egl and virtual/libgles2 > (which rely on binary files from the raspberry pi firmware repo) > instead of compiling from source using the userland package? It

Re: [yocto] recipe gsl-1.15

On 09/05/13 16:48, Edward Vidal wrote: > "file://NEWS;beginline=362;endline=363;md5=325d4344063147ef38e3ac2cbf1cc157" You should be hashing the actual license file, not the NEWS file. Also, the above is only hashing one line of the file, while your md5 sum is for the whole file. Tomas __

Re: [yocto] Trouble patching a package

On 22/04/13 13:56, Saridakis, Dean (US SSA) wrote: >>> Seems like this ought to be pretty easy based on the docs - Not sure >>> what I've got wrong. I've added an append to my layer w/ >>> >>> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" >>> >>> SRC_URI += "0001-yada-yada.patch" >>> >>> # Comment

Re: [yocto] any point in a single machine recipe using a machine-specific file?

On 19/04/13 15:34, Robert P. J. Day wrote: > On Fri, 19 Apr 2013, Tomas Frydrych wrote: > >> On 19/04/13 15:15, Robert P. J. Day wrote: >>> i'd wonder, if you're building for a different machine, why are >>> you including the meta-rpi layer? >>

Re: [yocto] any point in a single machine recipe using a machine-specific file?

On 19/04/13 15:15, Robert P. J. Day wrote: > i'd wonder, if you're building for a different machine, why are > you including the meta-rpi layer? Because at a distro-level you often want to target different architectures. > best answer i'd be able to give is that it's not essential but it > won't

Re: [yocto] any point in a single machine recipe using a machine-specific file?

On 19/04/13 15:02, Burton, Ross wrote: > On 19 April 2013 14:49, Robert P. J. Day wrote: >> but in the case of the rpi, is there any value in putting the files >> under a machine-named subdirectory? of course it won't hurt, but is >> there any point to it? > > You could argue the clarity that i

[yocto] GObject Introspection support for Yocto: meta-gir

Support for GObject Introspection is one of the gaping omissions in current Yocto / OE coverage, and here at sleep(5) we thought it was time someone took the bull by the horns and did something about it ... so without further ado: https://github.com/Guacamayo/meta-gir The repo contains a lengt

Re: [yocto] No keyboard in X

On 21/03/13 20:11, Chris Tapp wrote: > I've got a system (Danny, meta-intel-cedartrail) with a custom > /etc/mini_x/session file which is used to run an application at > startup. > > This all works to the extent that the application starts and runs, > but the keyboard doesn't work - 'Esc' should c

Re: [yocto] Creating tailored image without standard rootfs files

On 21/03/13 15:09, Peter Bergin wrote: > for my Yocto build I want to create two separate images as output > because in my system I have two separate partitions. One partition > containing the root file system and one partition containing > configuration and application data. What I want is to crea

Re: [yocto] [meta-raspberrypi][PATCH 0/2] Binary graphics library fixes

On 08/02/13 13:03, Andrei Gherzan wrote: > > > > On Fri, Feb 8, 2013 at 12:17 PM, Tomas Frydrych > mailto:tf+lists.yo...@r-finger.com>> wrote: > > Hi Andrei, > > On 07/02/13 14:26, Andrei Gherzan wrote: > > We are moving to userland repo. So

Re: [yocto] pulseaudio madness

On 06/02/13 22:43, Gary Thomas wrote: >>> You might want to have a look at Guacamayo's use of PA, that uses it >>> and will automatically switch output when new speakers are plugged in >>> too.https://github.com/Guacamayo >> >> Thanks, that helped. I've built Guacamayo for my RaspberryPi and >

Re: [yocto] [meta-raspberrypi][PATCH 0/2] Binary graphics library fixes

Hi Andrei, On 07/02/13 14:26, Andrei Gherzan wrote: > We are moving to userland repo. So we will build our libraries I tried to use the userland repo about a week ago and had to revert back to using the binary firmware; the userland tree seem to miss some bcm headers, so it was impossible to buil

Re: [yocto] Running Sato/X11 as non-root

On 06/02/13 14:40, Gary Thomas wrote: > In my attempt to get pulseaudio running, I need to bring up > my X11 session with a user that is not root. The default > (core-image-sato) always starts X11 as root. This yields > these errors when starting (with pulseaudio installed): > W: [pulseaudio] m

Re: [yocto] pulseaudio madness

On 06/02/13 13:50, Gary Thomas wrote: > On 2013-02-05 06:52, Burton, Ross wrote: >> Hi Gary, >> >> On 5 February 2013 12:44, Gary Thomas wrote: >>> I have a multi-media application/system (built with Poky/Yocto of >>> course) >>> that is currently using ALSA for the sound. This works great but no

Re: [yocto] Matchbox keyboard

On 05/02/13 19:19, Gary Thomas wrote: > On 2013-02-05 12:00, Tomas Frydrych wrote: >> On 05/02/13 18:47, Gary Thomas wrote: >>> Sorry if this isn't the best place to ask... >>> >>> I have a GUI application running on Poky/Yocto with Sato using >>>

Re: [yocto] Matchbox keyboard

On 05/02/13 18:47, Gary Thomas wrote: > Sorry if this isn't the best place to ask... > > I have a GUI application running on Poky/Yocto with Sato using > only a touch screen. My application window takes up the whole > display which is *very* small (320x240). If I try and accept > text input, I c

Re: [yocto] [meta-raspberrypi][PATCH 2/2] Add RPROVIDES for OpenGL libraries

On 30/01/13 21:51, Philipp Wagner wrote: > https://github.com/djwillis/meta-raspberrypi/issues/55 > > PROVIDES = "virtual/libgl virtual/libgles2 virtual/egl" > +RPROVIDES = "virtual/libgl virtual/libgles2 virtual/egl" As I noted in the above issue, this really is wrong; there is *no* libgl provid

Re: [yocto] I think my kernel image just went back in time...

On 09/12/12 23:17, Chris Tapp wrote: > In tmp/deploy/images: > > 1) bzImage had a timestamp of 2012-12-09 21:49 and the file ended > -20121209214459.bin > > 2) Cleaned the image and the task it contained (to pick up some > changes on rebuild) and deleted the image files (.hddimg, etc.) in > tmp/d

Re: [yocto] Set hostname on image?

On 21/12/12 15:04, Jonas Jonsson L wrote: > The installed (/etc/hostname) file is created & installed in the > base-files recipe, but I don't understand how to set/use the > hostname-variable in that recipe so that it becomes what I want it to be > (unless I start editing that recipe ). > > I

Re: [yocto] Use of BBPATH in a layer.conf file.

On 02/12/12 22:51, Scott Garman wrote: > Robert Day has brought up an inconsistency in the way we append to > BBPATH within a couple of our layer.conf files. > > In meta-hob, meta-yocto-bsp, and meta-intel, we do: > > BBPATH := "${BBPATH}:${LAYERDIR}" > > but in meta-yocto, we do: > > BBPATH :=

Re: [yocto] Problem compiling diffutils on poky-tiny in danny

Hi Tim, On 14/11/12 01:11, Tim Bird wrote: > ./wctype.h:448:1: error: static declaration of 'iswalnum' follows non-static > declaration > ./wctype.h:460:1: error: static declaration of 'iswalpha' follows non-static > declaration > ... > Has anyone seen this type of error before, or can provide s

Re: [yocto] [PATCH resend][opkg-utils] opkg.py/opkg-build: fix creation of tar archives

On 24/10/12 12:14, Richard Purdie wrote: > On Wed, 2012-10-24 at 12:53 +0200, Steffen Sledz wrote: >> Since openSUSE 12.2 the installed tar uses posix instead of gnu encoding >> by default. This format is not fully supported by opkg and results in >> ipk packages not installable at the target. >> >

Re: [yocto] AUTOREV problems

Hi, On 22/10/12 12:56, Seth Bollinger wrote: > 1. What is the expected operation of bitbake builds for recipes using > autorev? It should just work (and FWIW, it's working here). > 2. How can I get my autorev recipes to rebuild when their repositories > change? > 3. If this is working for eve

Re: [yocto] why was meta-dlna submodule history stripped out?

On 20/10/12 13:16, Paul Eggleton wrote: > On Friday 19 October 2012 11:01:09 Saul Wold wrote: > Long term however I'd rather see the additional unique recipes in meta- > guacamayo itself go into more official OE community layers. Ah, so there is an official community and an unoffical one, this com

Re: [yocto] why was meta-dlna submodule history stripped out?

Hi Saul On 19/10/12 19:01, Saul Wold wrote: > My apologies, I updated the MAINTAINER and README files. Thanks. >> (I am delighted Intel is finding Guacamayo useful, but the obliteration >> of the history makes it look as if the credit for this official Yocto >> layer goes to Intel; I am sure tha

[yocto] why was meta-dlna submodule history stripped out?

Looking over meta-dlna in Yocto git I see it's little more than a fork of meta-guacamayo from guacamayo-project.org -- could someone please explain to me why the git history was stripped out from this 'combo' layer? (I am delighted Intel is finding Guacamayo useful, but the obliteration of the hi

[yocto] why was meta-dlna submodule history stripped out?

Looking over meta-dlna in Yocto git I see it's little more than a fork of meta-guacamayo from guacamayo-project.org -- could someone please explain to me why the git history was stripped out from this 'combo' layer? (I am delighted Intel is finding Guacamayo useful, but the obliteration of the hi

Re: [yocto] how to use SECTION in .bb file

On 12/10/12 08:41, Liu wrote: > Dear all, I want to add some packages to poky,then I faced a question > : In a recipe there is "SECTION" variable,it is explaned where > package should be put .But I do not understand what it really > means. It's for packages managers to allow them to group common p

Re: [yocto] Making recipes depend on specific layers

Hi, On 05/10/12 14:58, Philip Balister wrote: > I run into problems (typically with BSP layers) where I want the layer > to build only against oe-core, but I also would like to have recipes > that depend on other layers. Typically, a "complex" image that uses > packages built from other layers. N

Re: [yocto] The BitBake equivalent of "Hello, World!"

>> Tasks must be Python functions. >> >> > No, they can be shell functions too. Probably worth adding that if you are doing an _append() on a task function, you have to match the original function type. E.g., if you want to append a shell snippet to a python task function, you need to do

Re: [yocto] How do you release distros produced with Yocto? How should I?

Hi, On 02/10/12 19:45, Jerrod Peach wrote: > I don't think that's actually what we want. The architecture of each > machine will be the same. That is, one ASIC will generally be on all the > printers in a family of products. I think I actually have one machine + > multiple distros. Or, should

Re: [yocto] How do you release distros produced with Yocto? How should I?

Hi, On 02/10/12 17:43, Jerrod Peach wrote: > I'm also starting to think there might be a better way to handle this with > Yocto's concept of distros (perhaps have a distro for printer X, and a > different one for printer Y, each pointing at versions of code that are > good for the respective print

Re: [yocto] opengl / libgl / libgles

On 06/09/12 11:00, Andrei Gherzan wrote: > Hello, > > In DISTRO_FEATURES we have opengl. That is pretty vague and generally we > don't want to have mesa on machines where there is no libgl but only gles + > egl. For example if we want to compile something that adds a DEPENDS based > on DISTRO_FEAT

Re: [yocto] yocto beagleboard.conf -- should it not go away?

On 05/09/12 22:46, Richard Purdie wrote: > On Tue, 2012-09-04 at 09:58 +0100, Tomas Frydrych wrote: >> Hi Bruce, >> >> On 03/09/12 22:08, Bruce Ashfield wrote: >>> That being said, taking a step back, what are you trying to get out of >>> meta-yocto in t

Re: [yocto] raspberrypi image questions

On 05/09/12 22:56, Jack Mitchell wrote: > On 05/09/2012 22:46, Paul Eggleton wrote: >> On Wednesday 05 September 2012 12:16:44 Gary Thomas wrote: >>> I just built Yocto/Poky for the raspberrypi, following the >>> recent thread on this list. I noticed that the resulting SD >>> image is ~4GB, but mo

Re: [yocto] core-image-minimal linux kernel version

On 05/09/12 20:03, James Macon wrote: > I found it but this is only partially the answer. I found > PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto" in qemu.inc but there > is no recipe for linux-yocto. There are recipes for linux-yocto_3.* , > linux-yocto-tiny, and linux-yocto-rt_3*. > > So

Re: [yocto] core-image-minimal linux kernel version

Hi, On 05/09/12 18:35, James Macon wrote: > I successfully built core-image-minimal. I now what to understand how the > build determine what linux kernel it will be using because the next step I > will want to do is add my own recipe that references my own kernel. I > have not been able to fi

Re: [yocto] yocto beagleboard.conf -- should it not go away?

On 05/09/12 15:45, William Mills wrote: >> Its accepted that most layers will append to BBPATH. I do think its >> acceptable for a distro policy layer to prepend though and this is why >> meta-yocto does this. I don't remember the exact reason right now but >> the principle stands. > > So how shou

Re: [yocto] yocto beagleboard.conf -- should it not go away?

On 05/09/12 10:15, Paul Eggleton wrote: > On Wednesday 05 September 2012 09:49:11 Tomas Frydrych wrote: > It has been considered witin OE to be best practice to append to BBPATH and > not prepend, the thinking being that then the search path matches the order > of > the l

Re: [yocto] yocto beagleboard.conf -- should it not go away?

On 04/09/12 21:25, William Mills wrote: > I suspect the current issue is just growing pains for a case that has > not been tested. The simplest fix would be for meta-ti to preppend itself to the path the same way meta-yocto does, i.e., in the layer.conf BBPATH := "${LAYERDIR}:${BBPATH}" In fa

Re: [yocto] yocto beagleboard.conf -- should it not go away?

Hi Bruce, On 03/09/12 22:08, Bruce Ashfield wrote: > That being said, taking a step back, what are you trying to get out of > meta-yocto in this scenario ? a) I am targeting multiple chips, including TI Omap and Intel Atom. meta-yocto is a prerequisite for the various machines in meta-intel, so

Re: [yocto] Building a Custom Raspberry Pi Image using OpenEmbedded and Yocto

Hi Jack, On 03/09/12 18:52, Jack Mitchell wrote: > As some of you know I run a small Raspberry Pi community site[1] and I > would like to write a follow up to an earlier blog post about preparing > yourself for programming on the Raspberry Pi with the Yocto Project. I don't know if of any use to

Re: [yocto] yocto beagleboard.conf -- should it not go away?

Hi, On 03/09/12 21:15, Bruce Ashfield wrote: > On Mon, Sep 3, 2012 at 4:06 PM, Tomas Frydrych > So we fix the configuration of the layers .. I expect this is not actually that trivial. I think the only way to do this is properly is for the layer priorities to be respected by all files

[yocto] yocto beagleboard.conf -- should it not go away?

Hi, I am wondering why yocto includes a beagleboard.conf when it is unable to support much of the board's features, and there is a dedicated layer for TI stuff that defines the beagleboard machine properly. I actually have a fairly practical gripe here: it is currently not possible to include bo

Re: [yocto] netbase_4.47.bbappend

Hi, On 03/09/12 19:03, Raul Rosetto Munoz wrote: > in my netbase_4.47.bbappend file i have this: > > FILESEXTRAPATHS_prepend := "${THISDIR}/netbase-4.47" I think you are missing a trailing ':' here, so your path is getting merged together with whatever is already there (probably the path added b

Re: [yocto] meta-raspberry pi libav bbappend

On 31/08/12 10:10, Jack Mitchell wrote: > Thanks for the suggestion but unfortunately no dice. It was working > about a week ago with this BBMASK...The only big change I can see is > that omxplayer now depends in libav, but I have tried just masking the > whole recipes-multimedia path with the same

Re: [yocto] meta-raspberry pi libav bbappend

On 31/08/12 09:44, Jack Mitchell wrote: > My BBMASK is: > >BBMASK = > > "meta-raspberrypi/recipes-multimedia/libav|meta-raspberrypi/recipes-core/systemd" I think it matches against full paths, so try: ".*/meta-raspberrypi/recipes-multimedia/libav|.*/meta-raspberrypi/recipes-core/systemd"

Re: [yocto] WARNING: QA Issue: udev: /lib/libgudev-1.0.so.0.0.1, installed in the base_prefix, requires a shared library under exec_prefix (/usr)

On 25/08/12 16:29, Andrei Gherzan wrote: > The obvious fix would be to move libgudev in /usr but before > doing this we need to be sure that nobody needs this in the early stages of > booting. That does not really matter; as things are if something is trying to use libgudev before /usr is mounted,

Re: [yocto] dev manual section on "customizing images" needs serious adjustment

On 24/08/12 16:45, Robert P. J. Day wrote: > On Fri, 24 Aug 2012, Scott Garman wrote: > >> On 08/23/2012 01:13 AM, Tomas Frydrych wrote: >>> Hi, >>> >>> On 22/08/12 21:37, Robert P. J. Day wrote: >>>> One way to get additional software into an

Re: [yocto] dev manual section on "customizing images" needs serious adjustment

Hi, On 22/08/12 21:37, Robert P. J. Day wrote: > One way to get additional software into an image is to create a > custom image. The manual should make it clear that this is *the* canonical way to add software to your images. Modifications to local.conf are temporary tweaks for testing/debugging

Re: [yocto] what's the preferred way of creating images for a classic beagle rev C4?

Hi, On 08/07/12 19:21, Robert P. J. Day wrote: > is it adequate to use the canonical beagleboard support in yocto, or > should i take advantage of the developments in the meta-ti layer? > this is for a training course so i don't need production-level > reliability so much as i want access to as

Re: [yocto] the current yocto FAQ is pretty much valueless

Hi Koen, On 27/06/12 22:58, Koen Kooi wrote: > I have no problem with poky-the-distro, I have a problem with > poky-the-buildsystem. I warned mallum about this confusion years ago, > but you know how stubborn he can be :) The Yocto naming confusion is entirely of Yocto making, nothing at all to d

Re: [yocto] the current yocto FAQ is pretty much valueless

Hi Koen, On 27/06/12 15:59, Koen Kooi wrote: > Yocto is NOT a distro. Is that so? :-), meta-yocto distro.conf: DISTRO = "poky" DISTRO_NAME = "Yocto (Built by Poky 7.0)" DISTRO_VERSION = "1.2" I am well aware that textual meaning is pretty much constructed by the reader, and that authorial inte

Re: [yocto] LAMP layer

On 27/06/12 16:22, Jack Mitchell wrote: > Lighttpd (already in core) > nginx > Hiawatha (my personal favourite - I have a recipe I already use in > conjunction with PHP) I'd add Cherokee to the list; there is a recipe in meta-oe. Tomas ___ yocto mailing

Re: [yocto] the current yocto FAQ is pretty much valueless

Hi, On 26/06/12 18:59, Brian Duffy wrote: > No, an FAQ should not get you the expertise to create a commercial grade > product. Reading the documentation should though. You don't want users to > have to study source code. If you were paying for the tools, then that would be a reasonable expectati

Re: [yocto] the current yocto FAQ is pretty much valueless

Hi Tim, On 26/06/12 19:52, Tim Bird wrote: > On 06/26/2012 10:18 AM, Tomas Frydrych wrote: > For example, after reading various FAQs > I still have no idea what kind of thing "Poky" is. I know > that bitbake is a build tool. I know that OE is a package > meta-informatio

Re: [yocto] the current yocto FAQ is pretty much valueless

On 26/06/12 17:53, Robert P. J. Day wrote: > and if you want major industry players to take yocto seriously, the > last thing you want to do is answer their heartfelt pleas for > assistance with, "i'm sorry, that's technically not a yocto question, > you should try another mailing list." That's

Re: [yocto] the current yocto FAQ is pretty much valueless

On 26/06/12 17:06, Paul Eggleton wrote: > On Tuesday 26 June 2012 08:46:45 Darren Hart wrote: >> On 06/26/2012 03:09 AM, Paul Eggleton wrote: >>> I suggested to Scott R previously that it might be worth having a project >>> FAQ (i.e., what is this project about, what is it intended to be used for >

Re: [yocto] the current yocto FAQ is pretty much valueless

On 26/06/12 10:09, Robert P. J. Day wrote: > A bad Frequently Asked Questions (FAQ) sheet is one that is composed > not of the questions people actually ask, but of the questions the > FAQ's author wishes people would ask. Perhaps you've seen the type > before: Nice quote, but unfortunately based

Re: [yocto] is it "IMAGE_INSTALL +=" or "IMAGE_INSTALL_append ="?

Hi, On 19/06/12 19:47, Chris Tapp wrote: > Is there a section that explains the order in which all these things > happen? i.e. items in local.conf happen before/after... IIRC, the evaluation orders is: 1. variables on the command line (e.g., 'MACHINE=beagleboard bitbake myimage') are evaluated f

Re: [yocto] developing with devshell and effect of the bitbake.conf file

Hi Scott, On 19/06/12 19:13, Rifenbark, Scott M wrote: > Hi, I want to throw this out for discussion. I recently was looking > at a section in the YP Reference manual > (http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#platdev-appdev-devshell) > where it talks about d

Re: [yocto] how do I prevent a specific package from being built/installed (e.g., bash)?

Hi, On 16/06/12 17:24, Anders Roxell wrote: > See subject. > Is there some config-file for package-masks (like portage's > /etc/portage/package.mask)? Packages are getting installed because something depends on them, so if you want an image that has different contents than one of the default imag

Re: [yocto] Help needed understanding do_rootfs error

Hi Chris, On 15/06/12 21:09, Chris Tapp wrote: > On 15 Jun 2012, at 07:01, Tomas Frydrych wrote: >> Incidentally, the GLES libs are not currently packaged by >> meta-raspberrypi, I submitted a pull request for this yesterday. > > Thanks, that will be nice. I want to l

Re: [yocto] RFC: poky-tiny: init procedure

Hi Darren, On 16/06/12 00:15, Darren Hart wrote: > I dont think > Tim's comment was wrong there. Of course "big system" is subjective, to > me that's anything over 4 MB of storage and 8MB of RAM, for Tim, that's > 1 MB of RAM. Indeed, I was thinking of something like the OpenRisc board (http://op

Re: [yocto] RFC: poky-tiny: init procedure

On 15/06/12 20:49, Tim Bird wrote: > On 06/14/2012 11:31 PM, Tomas Frydrych wrote: > IMHO, the whole notion of starting with a big system and > subtracting what you don't want in order to create a minimal > system is the wrong approach. At no point in this discussion was

Re: [yocto] RFC: poky-tiny: init procedure

Hi Darren, On 14/06/12 22:09, Darren Hart wrote: > This solution improves the kick-the-tires > experience with poky-tiny, without pulling in all of init, I think you really should quantify what 'all of init' means, without this you are addressing a problem that is merely perceived. Just a quick

Re: [yocto] Help needed understanding do_rootfs error

Hi, On 14/06/12 22:42, Chris Tapp wrote: > On 14 Jun 2012, at 21:44, Chris Tapp wrote: > >> The log for do_rootfs is showing: < snip > error: Failed >> dependencies: libGL.so.1 is needed by libglut3-7.11-r13.2.armv6 >> libGL.so.1 is needed by column-wallboard-1.0-r1.armv6 libGL.so.1 is >> needed

Re: [yocto] RFC: poky-tiny: init procedure

Hi Darren, On 14/06/12 01:33, Darren Hart wrote: > o Do not include the standard Busybox init ... > o Do not provide inittab functionality I am not entirely clear what you are hoping to gain by creating a home grown init solution? A system that runs nothing but a shell is really not useful for a

Re: [yocto] Not booting on BeagleBoard xM 0x2

On 13/06/12 03:34, Bruce Ashfield wrote: > On Tue, Jun 12, 2012 at 7:38 PM, Ryan Julian wrote: >> Hi Bruce, >> >> The build I'm using already includes Denys' patch. >> >> I was referring to Tomas' original problem, in which the MMC card >> successfully initialized, but the kernel still panics whil

Re: [yocto] RaspberryPi Kernel - sometimes it works, sometimes it doesn't

On 11/06/12 17:29, Paul Eggleton wrote: > On Monday 11 June 2012 06:53:32 Khem Raj wrote: >> On 6/11/2012 12:29 AM, Tomas Frydrych wrote: >>> I find that -c clean does not work very well, afterward the package >>> gets recompiled but instead of the actual package pac

Re: [yocto] RaspberryPi Kernel - sometimes it works, sometimes it doesn't

Hi, On 10/06/12 12:30, Chris Tapp wrote: > I've been building the 3.1.9 Raspberry Pi kernel under Denzil using > the meta layer at https://github.com/djwillis/meta-raspberrypi. This > uses a kernel recipe based on the git repository at > https://github.com/raspberrypi/linux/commits/rpi-patches. >

Re: [yocto] Hob implementation: vanilla or branded?

Hi, On 31/05/12 17:55, Barros Pena, Belen wrote: > I would like to know what the Yocto Project community thinks about these 2 > approaches. Vanilla please, 'branded' applications are so 1990s. I think very few users care whether an application looks different on a different OS then their own, but

Re: [yocto] Per-machine DEPENDS

On 23/05/12 08:55, Chris Tapp wrote: > Do overrides work with any variable? The RPi layer is using BBMASK to > filter out some recipes when building against Yocto. This has to be > manually added to local.conf. It does not have to be local.conf; if you are adding meta-raspberrypi, you have to set

Re: [yocto] [poky] RaspberryPi Layer

So, I have run into three issues with the meta-raspberrypi layer when trying use it with Poky: * the libav bbappend; this can be BBMASKED on distro level, so that's not a significant problem, * rpi-zram-service: a simple but rather hackish fix is to provide rpi-zram-service-initd package that p

Re: [yocto] [poky] RaspberryPi Layer

Hi, On 21/05/12 09:47, Andrei Gherzan wrote: > There are issues that cannot be solved with just one layer. A distro is > a workaround but still. More about this, rpi layer will be included in > yocto project repos as Richard plans so it makes sense to have a yocto > specific layer. It could be a

Re: [yocto] [poky] RaspberryPi Layer

Hi, On 19/05/12 22:51, Andrei Gherzan wrote: > After an exchange of messages with Richard, Saul and John Willis (he > already started a layer for oe and did a good job in it) i want to > announce that i started start a fork from his layer and with Florin > Sarbu will prepare a layer for RaspberryP

Re: [yocto] Raspberry Pi [was Re: Kernel modules fail to compile for ARM]

Hi Bruce, On 15/05/12 19:07, Bruce Ashfield wrote: > On 12-05-15 01:36 PM, Tomas Frydrych wrote: >> Let me turn this question back at you then: is Yocto going to be doing >> thorough Q&A for all of these HW platforms? Decent Q&A is what really >> sets Yocto apart, an

Re: [yocto] Raspberry Pi [was Re: Kernel modules fail to compile for ARM]

Hi Bruce, On 15/05/12 16:44, Bruce Ashfield wrote: > On 12-05-15 05:15 AM, Tomas Frydrych wrote: >> On 14/05/12 19:52, Chris Tapp wrote: >>> I'm trying to put a BSP together for an ARM system (Raspberry Pi, >>> ARM1176JZF-S CPU). >> >> I got the feeling

[yocto] Raspberry Pi [was Re: Kernel modules fail to compile for ARM]

On 14/05/12 19:52, Chris Tapp wrote: > I'm trying to put a BSP together for an ARM system (Raspberry Pi, > ARM1176JZF-S CPU). I got the feeling that there might be multiple OE/RPI efforts going on at the same time unaware of each other, e.g., I noticed this meta-raspberrypi layer on github that

Re: [yocto] Build time data

On 12/04/12 01:30, Darren Hart wrote: > Next up is storage. Indeed. In my experience by far the biggest limiting factor in the builds is getting io bound. If you are not running a dedicated build machine, it is well worth using a dedicated disk for the poky tmp dir; assuming you have cpu time lef

Re: [yocto] [Yocto] How to remove a particular package or packages collection for an image

On 10/04/12 08:20, Jegan Chandru wrote: > I did dry-run on core-image-custom and I see mostly all packages from > yocto included in my image, the packages that I do not need. So, how can > I remove a particular package or a package collection, say graphics or > some X packages for my image. Is it

Re: [yocto] managing layer priorities

Hi Paul, On 09/04/12 15:09, Paul Eggleton wrote: > On Monday 09 April 2012 14:58:49 Tomas Frydrych wrote: > I realise what you're trying to do, but you should bear in mind when you do > this you are relying on unintentional behaviour that may change in future. I am no

Re: [yocto] managing layer priorities

On 09/04/12 14:04, Gary Thomas wrote: > On 2012-04-09 00:18, Tomas Frydrych wrote: >> On 08/04/12 23:28, Tomas Frydrych wrote: >>> Is there a way to change the priority that a layer assigns itself in its >>> layer.conf? E.g., I want to add meta-oe alongside of meta-yocto

Re: [yocto] managing layer priorities

On 08/04/12 23:28, Tomas Frydrych wrote: > Is there a way to change the priority that a layer assigns itself in its > layer.conf? E.g., I want to add meta-oe alongside of meta-yocto, but I > want it to have a lower priority than the latter. Currently meta-yocto > gives itself "

[yocto] managing layer priorities

Hi, Is there a way to change the priority that a layer assigns itself in its layer.conf? E.g., I want to add meta-oe alongside of meta-yocto, but I want it to have a lower priority than the latter. Currently meta-yocto gives itself "5" and meta-oe "6", I'd like to change this without having to mod

Re: [yocto] using and auditing kernel config fragments

On 06/04/12 14:40, Autif Khan wrote: > I forgot to mention - Under Networking Support -> Wireless, you need > to enable cfg80211 AND msc80211 (Generic IEEE 802.11 Netowrking Stack) > > Then the Ralink driver support shows up under Wireless LAN Thanks, that's the bit I was missing. :) Tomas _

[yocto] using and auditing kernel config fragments

Hi, I am trying to add a kernel config fragment to the yocto 2.6.37 kernel for BeagleBoard, because I need a driver for a rt2800usb dongle. For some reason which I cannot work out, the rt2800usb options are removed (rather then disabled) from the yocto kernel config, i.e., if I run 'bitbake -c me

Re: [yocto] Not booting on BeagleBoard xM 0x2

On 04/04/12 15:10, Gary Thomas wrote: > On 2012-04-04 06:50, Bruce Ashfield wrote: >> On 12-04-04 08:04 AM, Andrea Galbusera wrote: >>> Hi Tomas, >>> >>> On Wed, Apr 4, 2012 at 12:14 PM, Tomas Frydrych >>> wrote: >>>> Hi, >>>&

  1   2   >