nyuuzyou/wikis huggingface dataset:
Fosdem 2011

Category:Conferences
= OpenEmbedded booth =
== Manning ==
You are going to FOSDEM 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 (Saturday)
* Ulf Samuelsson (Saturday and Sunday occasionally)
* Philip Balister (As needed)
* Florian Boor (Saturday)
== Devices ==
Add your name and what devices you'll bring for the stand.
Ulf Samuelsson - AT91SAM9M10EKES booting Openembedded/Android from SD-Card
 (No flash on board enabled)
Robert Schuster - Pandaboard - Hopefully booting Angstrom with some desktop and Java foo. Try to get hold of a small TFT display
== Flyers and posters ==
You can bring and/or print OpenEmbedded flyers and posters? Add your name and what you'll bring.
 * Florian: Poster from last year, flyers
== Power extensions, adapters and other stand material ==
Bringing devices is cool but we need a way to bring power to them too. Additionally people might need power sockets for different systems than the european one. List your name
and what stuff you can bring.
* Robert Schuster:
**3-socket power extension (EU)
**tape
= General attendance =
Attending FOSDEM 2011? Add your name to this page so that other developers can look out for you!
* Esben Haabendal
* Frans Meulenbroeks (eFfeM) (sunday only)
* Philip Balister (Crofton)
* Robert Schuster (rschus/thebohemian)
* Ulf Samuelsson
* Graeme Gregory (XorA)
* Florian Boor (florian)
* Denis Carikli (GNUtoo)
== Hotels ==
Although FOSDEM itself takes place at the ULB campus, most folks prefer to stay nearer the city centre.
The Astrid has traditionally been the default choice for OE developers, though there are many other hotels in the area. If you are staying in a hotel other than the Astrid, feel free to add it to this section for the benefit of others.
Scandic Grand Place.
 Rue d'Arenberg 18
 Close to beer event (300 m) and Central Station.
 Tram to Fosdem around the corner.
Git

= OpenEmbedded Git repository =
The Git repository is now the official source repository. Monotone is no longer used.
See GitPhraseBook for instructions on how to use the OE git repo.
* Web interfaces: http://cgit.openembedded.org/
* Git repository: git://git.openembedded.org/openembedded
= Other Repositories of Interest =
* http://git.openmoko.org/
* http://git.yoctoproject.org/
See GitPhraseBook for ideas on how to use additional remote repositories.
= Other topics =
* MultipleRepositoryMethods
= Why Git =
Why did we switch from monotone to git:
* better support for branching and merging (this is where git shines)
* much faster
* much larger user base -- many people doing OE work are already using git for kernel work 
Mail list discussions on the topic:
* http://thread.gmane.org/gmane.comp.handhelds.openembedded/8657/focus=9085
* http://thread.gmane.org/gmane.comp.handhelds.openembedded/17795/focus=17844
* http://thread.gmane.org/gmane.comp.handhelds.openembedded/18091/focus=18097
* http://thread.gmane.org/gmane.comp.handhelds.openembedded/17868/focus=17892
* http://thread.gmane.org/gmane.comp.handhelds.openembedded/18959/focus=18983
Category:Dev
Category:User
GitServerSetup

= Git Service Overview =
Our git services are hosted on git.openembedded.org. There is a user called git and the repositories are located within /home/git/repositories. There is one repository for managing gitosis itself and currently one called openembedded.git with our metadata. git, webgit and gitosis are installed as debian packages, /etc/gitweb.con is pointing to /home/git/repositories. git-daemon is running as a serv the service configuration can be found in /var/services/git-daemon/run and it points to /home/git/repositories as configuration as well.
= Service Infrastructure =
== gitosis ==
Installed with debian. Clone :gitosis-admin if you are part of the admin team
== gitweb ==
/etc/gitweb.conf, it will list repositories from /home/git/repositories that have the gitweb flag in the object dir. This is the case for openembedded.git
== git-daemon ==
It is running as runsv service. This means there is a /var/run/service/git-daemon/ directory and inside the run file is the command of git-daemon. As basepath it is pointing to /home/git/repositores. Everything with a special flag inside the repository will be exported via git-daemon. This is the case for the openembedded.git repository
= Managing and Troubleshooting =
== Adding new keys ==
You will need admin rights. Then you can git-clone git@git.openembedded.org:gitosis-admin. You can add a key to keydir. Use name.pub for the key, then you can add name to the gitosis.conf. Commit your change and then git-push and the guy is able to push afterwards.
== How the commit mails and ciabot work ==
In the openembedded.git repository there is the activated "update" hook. At the end of this script git-notify in /home/git is called. git-notify was copied from the wine project at a certain date, see the top of the file.
== Troubleshooting ==
Add loglevel = DEBUG below [gitosis] (2nd line). Then you get more output when login fails or no permissions are given.
Category:Dev
Gitlab

== OpenEmbedded Gitlab project ==
Based on discussions from ELCE 2019 in Lyon, we are starting to experiment with a Gitlab group for OpenEmbedded: https://gitlab.com/openembedded.
The main idea is to try to offer an OpenEmbedded branded / managed project for users to host their layers or any other relevant OpenEmbedded git projects.
== Admins and permissions ==
=== Top level permission ===
The owners for the Gitlab group are:
* Members of the OpenEmbedded board
* Paul Barker and Nicolas Dechesne who have volunteered to start this project
* Additional admins can be added at the discretion of the OpenEmbedded board.
== Mirrors == 
OpenEmbedded main repositories are mirrored on the OpenEmbedded Gitlab group. Note that they are read-only mirrors from https://git.openembedded.org/, and there is no change to the OpenEmbedded patch review process.
=== User project ===
When a user's request to create and maintain a new layer on the OpenEmbedded Gitlab instance is approved, he will get Maintainer role on that project. As such that user will now be responsible for the administration of the newly created project. 
== How to make requests ==
All requests for new project and/or permissions must be done using Gitlab issues on the admin project at: https://gitlab.com/openembedded/admin/issues. Community projects will be created under the Community subgroup, see https://gitlab.com/openembedded/community.
Happy Hours

The OpenEmbedded Board would like to invite you to a monthly virtual happy hour.
We welcome everyone to come and show off their projects and give us all a chance to say hello. Very informal! Everyone welcome!
* Now regularly scheduled at alternating times for Europe and Oceania, see Calendar 
* At https://zoom.us/j/99151508871 (Meeting ID: 991 5150 8871). Sponsored by Automotive Grade Linux
* https://lists.openembedded.org/g/openembedded-core/message/137354
Hash Equivalence Server

=Running a Local Hash Equivalence Server for debugging=
If you are having trouble with the automatically started hash equivalence server and need to run it manually for debugging, use the following steps:
# Start a new bitbake shell. This should drop you in your build directory
# Start the server by running bitbake-hashserv -b unix://./hashserv.sock -l DEBUG -d cache/hashserv.db. Note if you change PERSISTENT_DIR or CACHE variable in local.conf, your database file may live in a different location and you'll need to modify the above command to point your database file.
# Modify local.conf and add the line: BB_HASHSERVE = "unix://${TOPDIR}/hashserv.sock"
# Run your build as normal in a different bitbake shell. You should see useful logging information in the hashserver output
Holding a Workshop

== Workshops we have already run ==
* https://pretalx.com/oe-workshop-2020/
* https://pretalx.com/openembedded-workshop-2023/
* https://pretalx.com/oe-ws-2024/
* https://pretalx.com/openembedded-workshop-2025/
== Setting up the Call for Participation ==
We use Pretalx for managing the CFP and scheduling process. As of October 2023, they offer up to a 25% discount for community organizations who are not trying to make a large profit. Setup the workshop in pretalx, then email sales and ask for the discount information.
Once you have the discount code, the billing page should show a sticker saying 25% discount. Click place binding order and you come to an invoice you can download. EMail the PDF to the SPI treasurer for payment.
For FOSDEM, some people will be submitting to FOSDEM for the larger audience, but once the FOSDEM schedule is published, people with talks that are good for the workshop and not accepted at FOSDEM might want to give it during the workshop. We have had people do talks at both and make changes for the workshop to make it more developer centric. Don't discourage people submitting to both.
== Setting up the ticket shop ==
We use Pretix for tickets.
== Finding workshop space ==
Spaces used:
 * Agora used in 2023. We had about 40 people and that was the upper limit for the space. Getting in and out of the building needed a key card, which was a bit of a headache. The location was great, once we found the door, since it is very close to a tram line coming from the center of Brussels. We also plan to use it in 2024, since we know the space and it basically works for us.
For FOSDEM we have used Silversquare to find space.
== Setting up the ticket shop ==
We have a ticket shop with Pretix.
Create a new event and you will have the option to clone an existing shop. This copies most of the information you need and then you need to edit carefully to fix dates and links. Verify the pricing and ticket types. We typically have an early bird price, a regular price and supporter ticket that has the option for the purchaser to set their own price.
Before letting the shop go live, submit a ticket to the SPI treasurer to make sure the paypal linkage is still good. The ticket sales flow directly to avoid routing money through personal accounts. Send an email to treasurer at rt.spi-inc.org so the request can be tracked. You will to make sure the person checking the linkage has an account in our pretix. As of Nov 2024 this is true.
Pretix bills SPI directly for ticket fees. You receive a statement from them that should be sent to the SPI treasurer for their records.
== Other details ==
 * Promote via social media
 * Remind people via email
 * Monitor proposals
 * Review proposals
 * Create schedule
 * Monitor ticket sales
 * Send invoices to sponsors
== Post Workshop Tasks ==
 * Submit invoice for space to SPI
 * Submit catering invoice to SPI
 * Send a survey to attendees
How to help out

OE is great and I want to contribute something back. How?
That of course depends on your skills. But you don't need to be an Überhacker to be welcome in the OE community. This is an absolutely non-complete list of things you might want to consider:
* Tell others about your positive experience with OE
* Donate some money (tax-deductible!) to the e.V.
* Send patches to improve any aspect of the code
* Try to verify, refute or fix bugs (OE-Core bugs are tracked in the Yocto Project Bugzilla)
* Help out with the Documentation
* Help us push patches upstream or participate in our bug days
* Add another entry to this list of how to help, yes, that would help us, too ;-)
Category:FAQ
Category:User
IMote2

Original design by Intel Research and now available from Crossbow (www.xbow.com)
Pre openembedded based images (and oe ones when complete) available from imote2-linux.sourceforge.net.
Kernel git repositories at git.kernel.org
Maintained in kernel and OE by Jonathan Cameron
This one is a small pxa271 board targeting wireless sensor apps (hence no real local
interface)
* 32MB RAM
* 32MB Flash
* CC2420 802.15.4 radio (currently not supported in mainline kernel but very very dodgy drivers are in older versions on imote2-linux.sourceforge.net) Will be rewritten eventually to conform to new 802.15.4 framework in kernel.
=== Daughter boards ===
====IMB400 Basic Sensor Board====
* Accelerometer (ST LIS30L02dq)
* Light sensor (TSL2561)
* ADC (MAX1363)
* Temp sensor (TI TMP175)
* Humididy sensor (SHT15)
====Multimedia board==== 
* Camera ov7670
* Audio (broken in kernel as of 2.6.32-rc6 works in 2.6.31)
* PIR sensor (not supported but trivial to add)
====UCAM wifi board====
* 802.11b/g via Marvell sd8686
* ADC (MAX1239)
 
Category:machine
IRC

= Channels =
Server: irc.libera.chat
* #oe - for discussions relating to the building and testing of Open Embedded and for debugging of the building of distributions with OE. If you need help with a distribution based on OE or a GUI environment shipped with OE, then PLEASE go to one or more of the following channels instead
* #yocto - for discussions relating to the Yocto Project.
To reduce spam, the irc channels require you to have an account on irc.libera.chat, so anon access via Kiwi irc webclient needs some
setup.
Register your nickname on irc.libera.chat following this instructions
= Bots =
There is also infobot, which gathers various information from the channels. Poke around.
= Channel-Logs =
Conversation in those channels can be reviewed at:
* https://www.yoctoproject.org/irc/oe/
* https://libera.irclog.whitequark.org/yocto/
= IRC Clients =
* Mac OS X: http://homepage.mac.com/philrobin/conversation/ | http://colloquy.info/ | http://www.pidgin.im/
* GNU/Linux, *BSD: http://www.irssi.org/ | https://hexchat.github.io/ | http://www.pidgin.im/
* Windows XP: http://www.xchat.org/ |http://www.pidgin.im/
* Windows Vista/7: http://www.pidgin.im/
* Opie: Opie-Irc 
* Firefox: Chatzilla (very easy to install and use)
* https://kiwiirc.com/nextclient/
Category:Community
I want an image with package XYZ installed

Q: How do I add package XYZ to an image I compile?
A:
* http://pokylinux.org/doc/poky-handbook.html#usingpoky-extend-customimage (Poky Handbook)
* http://bec-systems.com/site/177/the-correct-way-to-add-packages-to-an-openembedded-image (The correct way to add packages to an OpenEmbedded Image)
=== In brief ===
* check (OE_DIR)/recepies/image directory for the image recepies
* edit/create your new image recepie 
For exampe create 'minimal-image-wiki.bb' receipie with the content:
 require minimal-image.bb
 IMAGE_INSTALL += "nano mtd-utils"
 
 export IMAGE_BASENAME = "minimalist-wiki"
This image will consist of all program from 'minimal-image' plus 'nano' and 'mtd-utils'.
To build: 
bitbake minimal-image-wiki
Category:FAQ
Infrastructure

= Notes on the OE project infrastructure =
= Servers =
* melo (VM at OSUOSL, donated by nslu2-linux project)
** admins: Mickey, Zecke, RP, cbrake, Rolf, khem, rwhitby, nas-admin.org staff,OSUOSL staff
** backups: daily by cbrake using rsnapshot (3 rotating daily snapshots).
*** /etc, /home/git, and /README
*** Tinderbox mysql databases are dumped and backed up
** 1.5GB RAM, 50GB of disk space, 2CPU
** MySQL databases are stored on a separate high availability DB server
* garnet (VM at OSUOSL)
** 1GB RAM, 100GB of disk space, 2CPU
** admins: Mickey, Zecke, cbrake, ka6sox, khem, nas-admin.org staff,OSUOSL staff
= Services =
* melo
** This wiki site
** Git
*** GitServerSetup
** OE Documentation
*** Automatic Documentation Update -- OE Documentation source is currently stored in the main OE dev repository. A process is maintained by cbrake that automatically updates the documentation daily, and uploads to the OE web site.
** Test builds (mysql)
** IRC ciabot
** commit bot
** Source Mirror
** Bugzilla (mysql)
** Patch Queue
* linuxtogo
** Mailing lists
* emerald
* Angstrom Autobuilder
* garnet
** build server
= Other topics =
* backups
* Web Site Infrastructure Discussion
* DNS Configuration
= The OE infrastructure is donated and maintained by =
* Mickey (amethyst server)
* Harald Welte (hosting)
* Linuxtogo.org (maillists)
* nslu2-linux.org (Melo server)
* nas-admin.org (emerald server)
* nas-admin.org (garnet server)
* BEC Systems (donated CPU for Melo server)
* OSUOSL (co-locates the Melo server and associated infrastructure)
* nas-admin.org (Group that maintains and admins the infrastructure used by the Melo and Garnet servers)
* EUKREA Electromatique (donated 3 HD for OSUOSL infrastructure)
Please considering donating to support this project.
Category:Dev
Insights Into Practical Advice In pregnancy

Newly women that are pregnant have to use care of themselves. She has to adhere to precautions that are prescribed by doctors. At home, they should take rest properly there are separate precautions in each and every trimester in the pregnancy period. It is one from the most pleasurable and interesting duration of women’s life when she feels a soul inside her and would like to be considered a good mother.There is a 1 away from each 89 births chance for miracle of life pregnancy video of Pregnancy Method Twins. Your chances are thin under ordinary circumstances. On the off chance that you simply or your accomplice have a place which has a family with good child, your probabilities of having child are expanded. Ethnicity and age likewise influence your shots of experiencing child as officially specified previously. African American ladies tend to be susceptible to consider with child while Caucasian and Asian ladies possess a much lower possibility. child are also more basic in established ladies and in females who are tall and overweight. To guarantee Pregnancy Miracle Method Twins, you may take richness meds or experience some strategy yet regularly imagined twins aren't anything with a lesser extent a wonder.To find good reasons to stop is simple: the initial three months there is morning sickness and exhaustion. The next three is the pregnancy miracle book a hoax months they are starting to show, and the last three months are extremely uncomfortable which simply walking the short distance to the bathroom is sufficient, let alone walking on the treadmill for 10 mins. Women who tend to be more than thirty five years and also have abandoned having a baby must also never give up hope. It is a misconceived notion that elderly women cannot get pregnant. You can surely give birth to some healthy baby if you desire to have one. It is quite disheartening when your attempts to get pregnant fail whenever. Check out for holistic books that will make suggestions regarding how to conceive and provides birth to your healthy baby. You may also desire to investigate internet on suggestions to become pregnant and in addition reviews of ladies who have had a fantastic experience along with the ways and means they adopt for conceiving.There is no doubt any time the right time comes, it's impossible to prevent you from conceiving a child. But from your side too, you should incorporate certain pregnancy miracle book changes. Keep a a record of your ovulation cycle along with the most fertile time period of your cycle. Having regular intercourse during such fertile periods will heighten the probability of pregnancy.
Jobs

Post links to OpenEmbedded related jobs. Please include the date you post the job so people can easily see what is current. Delete the job when you fill it, or it is no longer available. We'll remove postings older than three months. If you want to extend a notice, update the date. Insert newer jobs at the top of the list and keep things in date order, with newest at the top.
== June 2015 ==
== May 2015 ==
 * Yocto Developer (BMW Group)
== April 2015 ==
 * Software Engineer, Intuitive Surgical
Category:Admin
Kernel Building

== Default Build ==
For a default build, just run:
 bitbake virtual/kernel
After done, you can collect the built image from under the deploy folder, for example: build/tmp/deploy/glibc/images/vmware/bzImage-vmware.bin.
== Kernel image type ==
What kind of kernel image to build is controlled by the variable KERNEL_IMAGETYPE, which is normally defined in the machine config file. For example, build image for u-boot
 KERNEL_IMAGETYPE = "uImage"
== Select kernel version ==
FIXME.
== Default configuration ==
The default .config file used is normally placed somewhere under recipes/linux named defconfig.
You may want to search for it, say for vmware:
 find recipes/linux -name "vmware*"
 
And you find it in: 
 recipes/linux/linux/vmware/defconfig
 
== Apply custom patches ==
FIXME
== Customize configuration ==
If you need to customize the kernel configuration, you may run the menuconfig task by:
 bitbake -c menuconfig virtual/kernel
Note: by default these command requires you to run in X Windows. If you want to work in text terminal only, here's a how to.
== Compile ==
After that, you can compile the kernel by:
 bitbake -f -c compile virtual/kernel
== Fine control ==
If you need more control over the configuration and compile process, add this somewhere into your local.conf:
 INHERIT += "devshell"
and then you can go to the shell by:
 bitbake -c devshell virtual/kernel
The build environment will be well setup for you; you can run regular make commands like make bzImage ...etc
Please note, that the INHERIT step depends on the distribution you're using, some of the distributions already include the INHERIT in their configuration, so it might work already. You can check that easily using listtask task.
== Preserving the custom configuration ==
Changes are lost if you remove the tmpdir or do a "bitbake -c clean virtual/kernel", so you
may consider replacing the defconfig with it.
Category:User
Category:FAQ
LayerIndex/Checker

This is a little project to increase the quality of the LayerIndex entries.
We do not have a name yet, so we just call it 'Checker' for now.
It uses existing tools and the guidelines documented e.g. in the BSP guides and in the existing tests/tooling.
Currently it does 3 things:
a) grep LAYERSERIES_COMPAT <layer>/conf/layer.conf
a1) grep for 'dunfell' (or gatesgart)
b) grep LAYERDEPENDS <layer>/conf/layer.conf
[ run bitbake-layer layerindex-fetch $layer ]
c) run layer check script: yocto-check-layer (from OE-core repo)
An example run is available on this page for 'dunfell' LayerIndex/Checker/dunfell
Code is at: https://github.com/dl9pf/layerindexchecker 
Next steps:
* need help with:
** Update layerindex to add field noting the layer passed the 'checker' (or however we will name it)
** Expose api call to upload this for branch/layer/package combination
** option: add field showing if the checker did run/run last
** option: add field noting the error if it did not pass
* will do myself
** update script to work against api
** enhance script to pick machines for BSP layers
----
https://www.openembedded.org/wiki/LayerIndex/Checker
LayerIndex/Checker/Usual Issues

Usual issues that lead to yocto-check-layer failing:
a) The layer does change recipes just by being present
* this means that usually a .bbappend has a change which is not conditional or in other ways inactive until enabled by the user
** Patterns that can be used for this are:
*** _append_someoverride - to activate the layer, an override needs to be added
**** e.g. FILESEXTRAPATHS_prepend_rpi , SRC_URI_append_rpi , RDEPENDS_${PN}_append_rpi with the override _rpi being defined for the various pi boards
*** FOO_ENABLE = "1" and ${@bb.utils.contains('FOO_ENABLE', '1', 'case_yes', 'case_no', d)}
**** e.g. require ${@bb.utils.contains('FOO_ENABLE', '1', 'foo_bar.inc', , d)}
b) append files to layers that are not a hard requirement
* use the dynamic-layers approach - see: 
** https://github.com/agherzan/meta-raspberrypi/tree/master/dynamic-layers
** https://github.com/agherzan/meta-raspberrypi/blob/master/conf/layer.conf
c) The layer is missing either LAYERSERIES_COMPAT or LAYERDEPENDS
d) The layer has been restructured, the folders registered with the layerindex are no longer there - resubmit and note what entry should be replaced !