nyuuzyou/wikis huggingface dataset:
Adding a new Machine

== Kernel configuration ==
# Find out which kernel version your custom kernel is (e.g. 2.6.27)
# Extract the diff: diff -Nurd linux-2.6.27/ linux-2.6.27-mymachine/ (this step is optional if you already have a diff) 
# Add DEFAULT_PREFERENCE_mymachine = "1" and SRC_URI_append_mymachine = "file://mymachine.diff" to linux_2.6.27.bb
# Put defconfig in recipes/linux/linux-2.6.27/mymachine/defconfig
If you really, really need to be special (which you really don't need, but companies seem to feel better when their name is plastered all over the place e.g. linux-mycompany_2.6.27.bb) you can create your own kernel recipe with the naming options you mentioned, then please use linux.inc to the basics working well. If even that is not special enough, then well, you are on your own.
By reusing a linux_2.6.xx recipe you can easily see what kind of patches other machines are applying and how issues with that kernel get solved.
== General steps and traps ==
Most of the time people that add new hardware to OE go through something like this (ARM example):
# Add mymachine.conf, linux-mymachine_2.6.xx.bb, openmymachine.conf distro
# Complain toolchain doesn't build, copy over versions from angstrom to get it fixed
# Complain their device doesn't boot, change defconfig to support EABI to get it fixed
# Complain NFS doesn't work, change defconfig to get that fixed
The toolchain problems wouldn't have been there if people had used an existing, working distro like angstrom, the kernel issues mentioned above are all handled automagically by linux.inc.
So people, please start by reusing existing things and creating your own stuff when need arises, not when NIH arises.
== Further comments and information ==
* Adding a new Machine, Chapter 5. Common Use-cases/tasks, OpenEmbedded User Manual
* where available, don't forget to provide an URL to the machine's homepage in the machine configs for those who want to know more about it.
Category:Dev
Category:Machine
Barcelona, 2012

==Location ==
Hotel Fira Palace · Barcelona, Spain
Nov 7, 2012 at 17:00.
== Agenda ==
* Financial report
* Board Elections, Dr. Michael Lauer, Florian Boor, and Philip Balister's terms are ending.
== Forms ==
* Proxy form 
== Attendence Record ==
(Proxies are in brackets)
* Philip Balister (Denys Dmytriyenko, Steve Sakoman)
* Stefan Schmidt (Michael Lauer, Simon Busch)
* Jan Lübbe 
* Marco Cavallini (Frans Meulenbrooks) 
* Mark Hatle 
* Marcin Juszkiewicz
* Richard Purdie (Dirk Hohndel)
* Saul Wold
* David Stewart
* Scott Garman
* Otavio Salvador 
* Andrei Gherzan
* Khen Raj
* Leon Woestenberg
* Paul Eggleton
* Andrea Adami
* Anders Darander 
* Esben Haabendal
* Koen Kooi (Tom Rini, Graeme Gregory)
* Sean Hudson (Jeff Osier-Mixon)
== Meeting notes ==
 Meeting opened 17:00
 Philip presented Finance Report
 Main expenses on event box
 Vote in Otavio Salvador and Andrei Gherzan as new members of the e.V, no objections
 TSC report:
 * Next election Jul 2013 for Richard
 * reported on TSC activity, generally happy with the way its working
 * noted that we need to publish minutes on time
 Election of board members. Candidates, Philip Balister, Leon Woestenberg, Sean Hudson, three people, three positions, voted in with no objections
 Reminder to membership that if changes to the voting procedure or statutes are wanted, someone needs to drive and present a coherent proposal
 Meeting closed 17:38
Category:General_Assemblies
BeagleBoard

== Kernel Support in OE ==
=== Linux ===
OpenEmbedded offers more than one kernel for the BeagleBoard. All come with several patches but the support of the BeagleBoard hardware is not perfect yet.
The table summarizes the current status of hardware support. Please note that this applies to the kernels we have in OE only.
Boot 	USB OTG 	USB host	DVI	Audio out	Audio in	S-Video out	MMC / SD	RS232	Flash	DSP	SGX
2.6.27-r11	host only	 	 	 	 	 	 	 	 	 	
2.6.28-r12	 	 	 	 	 	 	 	 	 	 	
Currently 2.6.27 is the default kernel in OE. If you want to build 2.6.28 you can set PREFERRED_VERSION_linux-omap = "2.6.28" in your local.conf. Then build the kernel bitbake virtual/kernel or a filesystem that should include the kernel modules.
Another way to build the desired kernel is to point OE to the kernel bb directly. 
Category: Machine
Become Sponsor

= Overview =
This page describes how an organization can help OpenEmbedded.
= Sponsorship =
The OpenEmbedded project encourages organizations that benefit and use OE to become a sponsor. There are three levels of sponsorship, Gold, Silver, and Bronze.
== Gold Sponsorship ==
 Annual Cost: EUR 25000
== Silver Sponsorship ==
 Annual Cost: EUR 5000
== Bronze Sponsorship ==
 Annual Cost: EUR 500
= Project Contribution =
OE is always interested in getting help to improve the project and software. Anyone that has identified problems is encouraged to pitch in and help out. Additionally, help with specifics such as technical writing, design, testing, and other specialized skills would be valued.
Category:Verein
Berlin, 2016

= e.V. General Assembly (GA) Meeting for 2016 =
NOTE: for the OpenEmbedded Developer's European Meeting (OEDEM) 2016, held the same day at the same location, see the page OEDEM 2016
==Location ==
Berlin, Germany
October 14, 2015 at 0900 - 1000
== Agenda: General Assembly ==
* Treasurer report
* Update on eV status
== Forms ==
* Proxy form 
== Attendance ==
* Andrei Gherzan (agherzan)
* Jeff Osier-Mixon (jefro)
* Marco Cavallini (mckoan)
* Anders Darander
* Andrea Galbusera (gizero)
* Richard Purdie (RP)
* Changhyeok Bae (chbae)
* Nicolas Dechesne (ndec)
* Peter Kjellerstedt (Saur)
* Denys Dmytriyenko (denix)
* Khem Raj (khem)
BitBake (dev)

developer homepage
* First , RTFM ;-) (doc directory in the bitbake source)
* Don't forget mailinglist :
** http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel
Source tree is in git at http://git.openembedded.org/bitbake/
= Tutorial =
This tutorial focus bitbake developement, not bbclass or openembedded developement that is documented elsewhere.
== "Helloworld" using bb library ==
=== Simplest ===
#!/usr/bin/env python
# ex:ts=4:sw=4:sts=4:et
# -*- tab-width: 4; c-basic-offset: 4; indent-tabs-mode: nil -*-
import bb
version = bb.__version__
bb.note("Hello from helloworld using lib bb v%s." % ( version ))
=== with data module ===
#!/usr/bin/env python
# ex:ts=4:sw=4:sts=4:et
# -*- tab-width: 4; c-basic-offset: 4; indent-tabs-mode: nil -*-
import os , bb
from bb import data
hello = ("Hello from helloworld using lib bb v%s." % ( bb.__version__ ))
d = data.init()
data.setVar('HELLO_MSG', hello, d)
mystring = data.getVar('HELLO_MSG', d, 1)
bb.note(mystring)
data module is well documented because it uses doctest.
Enjoy to play with the different methods. 
=== with persist_data module ===
Now you want persistant data to exchange data between threads/tasks.
This can be done using bb.persist_data module that uses sqlite via pyslite2.
#!/usr/bin/env python
# ex:ts=4:sw=4:sts=4:et
# -*- tab-width: 4; c-basic-offset: 4; indent-tabs-mode: nil -*-
import bb, os, sys
from bb import data, persist_data, fetch
__version__ = "0.0.1"
 
def main():
 """
 The main Method
 """
 
 # persist_data module need debug_level to be set
 bb.msg.set_debug_level(0) 
 
 # init a data with PERSISTENT_DIR to set where the data will be saved
 d = data.init()
 data.setVar('PERSISTENT_DIR', os.getcwd(), d)
 
 # create persist_data base in bb_persist_data.sqlite3
 pd = persist_data.PersistData(d)
 
 # create a sql table
 pd.addDomain("MYBASE")
 
 # add a data in this table
 pd.setValue( "MYBASE", "TOTO", "hello world!")
 
 # print it
 val = pd.getValue ( "MYBASE", "TOTO")
 print val
 
if __name__ == '__main__':
 main()
You can edit and watch your base using sqlitebrowser for example. Should be useful for debug and test purpose. You can look also at fetch module source that use bb.persist_data.
Category:Dev
BitBake (user)

= Introduction =
BitBake is, at its simplest, a tool for executing tasks and managing metadata. As such, its similarities to GNU make and other build tools are readily apparent. It was inspired by Portage, the package management system used by the Gentoo Linux distribution. 
BitBake is the basis of the OpenEmbedded project, which is being used to build and maintain a number of embedded Linux distributions.
= Links =
* Manual: http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html
* Git repository: https://git.openembedded.org/bitbake/
= Version information =
OE-Core needs a fairly up-to-date version of BitBake; at minimum the most recent stable version is recommended. A sanity check on the BitBake version is performed at startup; if it is too old you will need to update before continuing.
Category:User
Bitbake World Status

The setup and jenkins scripts used to generate these reports are described here:
http://www.openembedded.org/wiki/Bitbake_World_Status_Setup
==3.1 Bitbake_World_Status_Dunfell==
==3.0 Bitbake_World_Status_Zeus==
==2.7 Bitbake_World_Status_Warrior==
==2.6 Bitbake_World_Status_Thud==
==2.5 Bitbake_World_Status_Sumo==
==2.4 Bitbake_World_Status_Rocko==
==2.3 Bitbake_World_Status_Pyro==
==2.2 Bitbake_World_Status_Morty==
==2.1 Bitbake_World_Status_Krogoth==
==2.0 Bitbake_World_Status_Jethro==
==1.8 Bitbake_World_Status_Fido==
==1.7 Bitbake_World_Status_Dizzy==
==1.6 Bitbake_World_Status_Daisy==
Bitbake World Status Setup

This page is replacement for my regular "State of bitbake world" e-mails like this one:
http://lists.openembedded.org/pipermail/openembedded-devel/2013-October/092818.html
In my setup there are currently 26 layers included (you can see exact list at the top of bitbake.log)
Basically it uses default distro-less configuration from oe-core with few tweaks, all tweaks are included in each log directory e.g.:
http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.world.qemuarm.20170213_095743.log/world_fixes.inc
It's not using "master" branches, but "jansa/master" branches in
* http://git.openembedded.org/openembedded-core-contrib/
* http://git.openembedded.org/meta-openembedded-contrib/
* https://github.com/shr-distribution/meta-smartphone
etc. it's only because it's easier for me to push some changes I need to review to that branch (or my changes before I even send them to list for review) and let Jenkins to verify them in very big build.
It's running on Ubuntu 16.04 LTS with dash still as default shell.
The jenkins jobs are described here https://github.com/shr-project/jenkins-jobs
Usually I build for 4 MACHINE qemuarm, qemuarm64, qemux86, qemux86-64. Each MACHINE takes about 20-24hours so sometimes there is bigger delay.
test-dependencies.sh build for all included recipes takes 11DAYS for 1 machine - so I don't do it very often, but incremental builds (with only recipes which failed last time) are fine.
Bitbake cheat sheet

==Intention==
This page is intended to make the life of new developers easier. Feel free to add all your usual bitbake commands to this page
==Start a build==
To get a package build just type
 bitbake foo
where foo is the name of the package without any extension or version number.
==Clean up==
 bitbake -c clean foo
This command will clean up your tmp dir for the given package. It is very useful if you work on a new .bb recipe. Without it your changes to the recipe may not work.
==Working with tmp/work==
To recompile your source code if you change a line in it.
 bitbake -f -c compile foo
The command above recompiled the code for foo. To build the ipk
use the command below
 bitbake foo
==Check Recipe Version==
 bitbake -s | grep foo
==Check Bitbake Version==
 bitbake --version
==Run Bitbake A Little at a Time==
 bitbake -c listtasks foo
 # lists the tasks
 bitbake -c taskname foo
==Show build environment==
 bitbake -e foo
Category:Dev
Branching Policy

OE-Core has six month development and release cycles, roughly being April and October each year. As each release is made, the release is given a name and its expected that other layers/repositories that would with the release use the same branch name to denote compatibility.
With the use of the git source control system, users are free and actively encouraged to create clones of the repositories to develop and submit changes against and they are also welcome to share branches in the contrib repositories as appropriate.
For OE-Core, a maintainer is generally appointed for the release branch at release time and this is recommended for other layers too.
Category:Policy
Bug days

Bug days have not happened for a while however the concept remains valid and as a project, we do hope to hold them again.
The general intent of such days would be to have a block of time where developers get together online and work on addressing specific topics such as:
* reducing the number of open bugs in the bugzilla by fixing bugs and triaging stale bugs
* reviewing and handling unmerged patches
* working though the patches we have against software and submitting suitable code upstream (push patches upstream)
Category:Policy
Buglabs-BUG

= Status =
The BUG by default runs a customized version of Poky Linux. 
Development branch of OpenEmbedded provides basic support for device. It is possible to run BugLabs software by using "hrw/oe-stable-2009" branch available in BugLabs svn server.
= Official maintainer =
 Marcin Juszkiewicz
= Hardware =
* CPU: i.MX31
* RAM: 128MB
* Flash: 32MB (used only for bootloader)
* Storage: microSD card (2GB one provided with device)
* Screen: built-in monochrome status display + upto 2 QVGA screens
* Connectivity: 
** built-in WiFi (Marvell 8686 SDIO) in r1.3 version of device
** built-in Bluetooth in r1.3 version of device
** external module with Marvell 8686 SPI Wifi ++ BlueTooth
* USB host
** On-The-Go connector in device
** USB Host port in VonHippel module
* Expansion modules
** LCD screen with touchscreen (QVGA resolution)
** motion detector 
** GPS
** BugBee
** VonHippel (USB Host, GPIO, SPI, I2C, I2S, ADC, DAC, serial lines)
** Camera
** Audio
Category:machine
Build Management Tooling

Over the years, people have created a diverse eco-system around OpenEmbedded to manage the build process. This page exists to collect articles and tools to help people focus on existing tools instead of creating new ones.
==Articles==
* https://blog.3mdeb.com/2019/2019-02-07-kas/
==Tools==
* https://github.com/garmin/pyrex
* https://github.com/siemens/kas
CeBIT 2011

= OpenEmbedded booth =
== Visit us ==
Hall 2, Booth F44
== Manning ==
You are going to CeBIT 2011 and can spend some time at the OpenEmbedded stand to explain interested individuals the virtues of OpenEmbedded? Add your name and on which day you'll be available.
* Robert Schuster
* Mickey Lauer
* Henning Heinold (3.3-5.3, only parttime, mainly on the navit booth)
== Devices ==
== Flyers and posters ==
 * Robert Schuster: ~500 OpenEmbedded flyers (will be sent from Florian to tarent office in Bonn)
== Free Tickets ==
CeBIT organizers provided us with lots of free tickets for the event. If you want one leave your name and email here (don't forget to obfuscate the later a bit).
Checklist for the General Assembly

== Checklist to organize the General Assembly ==
=== Preparing the General Assembly ===
# Pick date at least ~7 weeks from now
# Pick a venue for the conference
# Take the last invitation and change the date, location and the year of the assembly
# Point people to the proxy form. (Source - File:Proxy instructions-oe.odt)
# Create a WIKI page for the Agenda (TODO: Come up with a namespace)
# Send the Invitation, Proxyform and Agenda to the members list
=== Holding the General Assembly ===
# Start with the "Welcome"
# Make sure there are no valid objections to hold the assembly
# Make sure someone writes the protocol. It needs to include at least the following items:
## Beginning and end of the GA
## Attending members and proxies
## Agenda
## Decisions made by voting w/ vote stats
=== Paper work ===
# Turn the minutes into a proper protocol (whole sentences prefered)
# Send the protocol to the member list
# Send the protocol to the german authorities. The address is:
## TODO: Address / Club number for Amtsgericht
Category:VereinCategory:General_Assemblies
Clarifying Effective Solutions For nutrition

✅ Seven Ways to Spot a Superficial Person in Your Relationship - FamilyNutrition is often a fascinating subject that keeps scientists busy night and day. There is really a lot of interest in how nutrition operates from the human body and doctors and scientists are becoming increasingly more interested in these facts. The following tips are some of the more interesting highlights which were documented.Learning about and understanding nutrition is crucial to get affordable health. Teaching children about nutrition when they're young will help the crooks gergedan action; yapaysigara.biz, to be maintain healthy habits into adulthood. This preschool theme will even cover other key components of good health, like sleep and employ. This is a week long lesson plan using a different lesson for every day. Eat a good amount of fresh produce daily. The daily allowance recommended by the USDA for vegetables and fruit is between 9 and 13 servings daily. Though this number might seem high, there are some easy techniques for getting them in. Have fresh-squeezed OJ at breakfast time, or make your own pasta sauce beyond real tomatoes as well as other vegetables. Allopathic medicines, tobacco, alcohol, etc. , carry reasonable quantity of toxins, that happen to be unknown to common man. In today's world, the vegetables and fruit, which are designed to nourish our body, are contaminated with pesticides, chemicals and hormones used by its cultivation and preservation. Refrigerated food gets toxic when repeatedly encountered with heat. Milk, meat and also other nutritious food fed to infants contain pathetic factors, which result in obesity. All these factors play a vital role at the begining of ageing, skin problems, respiratory problems and weakening of man. This makes the need of this therapy much more compulsory plus a way unavoidable, by which every one of the toxins might be expelled in a single day. While in the case of fruits, copper sulphate, carbides and also other hormones are being used to present those tempting colours and size. The sensitive plant (Mimosa pudica) goes under the name of the Humble plant, Shame plant, Shy plant, Sleeping grass, Prayer Plant, and Touch-me-not. Although native to Central and South America, this plant are available in most tropical climes, usually in disturbed land around construction sites, orchards and agricultural land. In some countries it really is classed as a possible invasive.
Code of Conduct

OpenEmbedded events are working conferences intended for professional networking and collaboration in the embedded Linux community. Attendees are expected to behave according to professional standards and in accordance with their employer’s policies on appropriate workplace behavior.
While at OpenEmbedded events or related social networking opportunities, attendees should not engage in discriminatory or offensive speech or actions regarding gender, sexuality, race, or religion. Speakers should be especially aware of these concerns.
OpenEmbedded does not condone any statements by speakers contrary to these standards. OpenEmbedded reserves the right to deny entrance and/or eject from an event (without refund) any individual found to be engaging in discriminatory or offensive speech or actions.
Please bring any concerns to the immediate attention of OpenEmbedded event staff, or contact a member of the OpenEmbedded Board.
Category:Community
CommercialSupport

Commercial Support
A list of companies and individuals offering commercial support for OpenEmbedded and related projects.
== B ==
* BEC Systems
== D ==
* Dr. Michael 'Mickey' Lauer, IT-Freelancer
== K ==
* kernel concepts (see also Linux embedded services, porting and support, Open Source projects and news and µCross a commercial distribution built with OE)
* KOAN Software Italy, offers consulting, support and training services for Linux and OpenEmbedded. OpenEmbedded member and Yocto project participant. Linux embedded support, Linux embedded and OE/Yocto training worldwide, Device drivers development)
== M ==
* Marcin Juszkiewicz
== O ==
* O.S. Systems
== S ==
* Sidebranch, The Netherlands, helps companies build industrial products using Linux and OpenEmbedded. Extensive hardware and device driver knowledge.
* SlimLogic Comprehensive OpenEmbedded support for mobile and embedded Linux based products. Kernel subsystem maintainers.
== T ==
* Timesys helps developers build, secure, and maintain products using Linux and OpenEmbedded. This includes Linux development support, vulnerability monitoring and remediation SCA tool , security feature implementation services, long-term software updates and maintenance, test automation and remote access infrastructure, and collaborative consulting on a broad range of security and development services for embedded devices.
Category:User
Common mistakes in a recipe

This page should list common (!) mistakes when defining a recipe. a link or one sentence explaining what the problem is are a bonus. But keep it short!
= (R)DEPENDS, etc. =
libiconv in (R)DEPENDS
: Use "virtual/libiconv" instead as glibc based systems already have libiconv functionality from glibc. Uclibc based systems will get it from "libiconv". By building libiconv in glibc build You risk a corrupted TMPDIR which will need to be restarted from scratch.
kernel modules in RDEPENDS
: Never use RDEPENDS to drag kernel modules into an image, use RRECOMMENDS instead. The reason is that some devices can have those modules built-in into kernel.
Category:Dev
Category:FAQ
Creating a new Layer

== Before creating a new layer ==
Check if someone has already created a layer containing the metadata you're looking for - the layer index is the place where layers are tracked.
== How to create a new layer ==
Creating a layer is simple:
# Create a new directory (traditionally meta-<something>)
# Create a conf/layer.conf. You can simply copy meta-oe's one and just change "openembedded-layer" to something appropriate for your layer; you may also want to set the priority as appropriate.
# Depending on the type of layer, add the content: 
#* If the layer is adding support for a machine, add the machine configuration in conf/machine/
#* If the layer is adding distro policy, add the distro configuration in conf/distro/
#* If the layer introduces new recipes, put the recipes you need in recipes-* subdirectories of the layer directory. If you are bringing recipes across from OE-Classic see Migrating metadata to OE-Core.
== Best practices ==
To aid maintainability, the following recommendations are made for creating new layers:
* Avoid "overlaying" entire recipes from other layers in your configuration (i.e. copying the entire recipe into your layer and modifying it). Use .bbappend files to override the parts of the recipe you need to modify.
* Avoid duplicating include files - use .bbappends for each recipe that uses the inc file, or if you're introducing a new recipe that requires it, use the full path to refer to the original (e.g. require recipes-core/somepackage/somefile.inc instead of require somefile.inc). If you're finding you have to overlay the inc file it may indicate a deficiency in the inc file in the layer it originally belongs to, which should be addressed instead. An example here would be the way Qt 4 database support plugins are configured - OE-core doesn't have MySQL or PostgreSQL, however meta-oe does, so distro layers can use .bbappends for qt4-x11-free and/or qt4-embedded to modify a variable QT_SQL_DRIVER_FLAGS to enable the appropriate plugins. This variable was added to qt4.inc in OE-core specifically to make it easier to enable support for database engines not available in OE-Core.