https://wiki.yoctoproject.org/wiki/api.php?action=feedcontributions&user=MichaelHalstead&feedformat=atomYocto Project - User contributions [en]2024-03-29T15:06:29ZUser contributionsMediaWiki 1.39.5https://wiki.yoctoproject.org/wiki/index.php?title=File:Screenshot_from_2024-03-11_12-54-38.png&diff=86266File:Screenshot from 2024-03-11 12-54-38.png2024-03-11T19:55:27Z<p>MichaelHalstead: cgit screenshot to post to https://bugzilla.yoctoproject.org/show_bug.cgi?id=15441</p>
<hr />
<div>== Summary ==<br />
cgit screenshot to post to https://bugzilla.yoctoproject.org/show_bug.cgi?id=15441</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User_talk:Pacopedraza&diff=86254User talk:Pacopedraza2024-03-01T17:30:43Z<p>MichaelHalstead: Welcome!</p>
<hr />
<div>'''Welcome to ''Yocto Project''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br />
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 17:30, 1 March 2024 (UTC)</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User:Pacopedraza&diff=86253User:Pacopedraza2024-03-01T17:30:43Z<p>MichaelHalstead: Creating user page for new user.</p>
<hr />
<div>SW Engineer with a rich decade with software developent experience, mostly focused in Quality Assurance and Automation. Working in different projects for Mobile Platforms, Embedded Linux (yocto), consumer electronics suchs as Drones, Scooters, and nowadays in Electrical Vehicles.</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User_talk:Onkelpit&diff=86252User talk:Onkelpit2024-03-01T17:30:23Z<p>MichaelHalstead: Welcome!</p>
<hr />
<div>'''Welcome to ''Yocto Project''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br />
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 17:30, 1 March 2024 (UTC)</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User:Onkelpit&diff=86251User:Onkelpit2024-03-01T17:30:23Z<p>MichaelHalstead: Creating user page for new user.</p>
<hr />
<div>Computer Scientist<br />
Embedded since 2017<br />
Yocto since 2019<br />
Cutting Videos for the YP and OE for YouTube</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User_talk:Bkdaugherty&diff=86183User talk:Bkdaugherty2024-02-02T21:00:57Z<p>MichaelHalstead: Welcome!</p>
<hr />
<div>'''Welcome to ''Yocto Project''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br />
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 21:00, 2 February 2024 (UTC)</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User:Bkdaugherty&diff=86182User:Bkdaugherty2024-02-02T21:00:57Z<p>MichaelHalstead: Creating user page for new user.</p>
<hr />
<div>Hey! I work at Span on an embedded Linux project using Yocto.</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User_talk:Simonew&diff=86136User talk:Simonew2023-12-19T19:11:21Z<p>MichaelHalstead: Welcome!</p>
<hr />
<div>'''Welcome to ''Yocto Project''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br />
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 19:11, 19 December 2023 (UTC)</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User:Simonew&diff=86135User:Simonew2023-12-19T19:11:21Z<p>MichaelHalstead: Creating user page for new user.</p>
<hr />
<div>I just started out to get involved upstream and want to use the opportunity when I find stuff missing/outdated here to add it directly.</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=Contribute_to_Toaster&diff=86096Contribute to Toaster2023-11-30T21:53:33Z<p>MichaelHalstead: Updating dead link</p>
<hr />
<div>[[Category:Toaster]]<br />
This page summarises the Toaster development process. We hope this will help you start contributing to the project. We were previously using a process that involved the toaster-next branch on poky-contrib. This workflow was especially useful in an environment where Toaster was undergoing a lot of change and needed the ability to layer patch sets upon each other before they had been taken up by bitbake. Since that is not currently the case, toaster-next just adds complication; so it has been removed from this workflow. See [[Contribute to Toaster (toaster-next version)]] for the old toaster-next based workflow.<br />
<br />
== What can I do? ==<br />
<br />
The [https://bugzilla.yoctoproject.org/buglist.cgi?product=Toaster Yocto Project Bugzilla instance] lists all the things that need to be done:<br />
<br />
* If the issue says <strong>GUI design available</strong> in the Whiteboard field, there is a design specification document attached to the issue that you should follow. Send questions / comments about it to the [https://lists.yoctoproject.org/listinfo/toaster Toaster mailing list]<br />
* If the issue says <strong>GUI design pending</strong> in the Whiteboard field, there is some design work still to be done. Feel free to take the issue and send an email to the [https://lists.yoctoproject.org/listinfo/toaster Toaster mailing list] to find out why the design work is not done yet<br />
<br />
== Set up the local repository ==<br />
<br />
For development of Toaster we recommend setting up a local install of Toaster. Installation instructions are available in the main [https://docs.yoctoproject.org/dunfell/toaster-manual/toaster-manual-setup-and-use.html#starting-toaster-for-local-development Toaster documentation]<br />
<br />
== Submitting patches ==<br />
<br />
Publishing your patches to Toaster is a two step process.<br />
# Sending patches to the [https://lists.yoctoproject.org/listinfo/toaster/| Toaster mailing list] for review<br />
# Submitting the patches that you reviewed to the upstream repository<br />
<br />
By submitting your patches first to the Toaster mailing list, you can be sure the patches are reviewed by the people in the community who are familiar with the Toaster source code, and who have experience developing web applications.<br />
<br />
That also means that, by the time the patches are submitted to the upstream mailing lists, they are in pretty good shape. That helps the project maintainers, and hopefully also helps you.<br />
<br />
Toaster code lives in Bitbake repository at [http://git.openembedded.org/bitbake/|http://git.openembedded.org/bitbake/].<br />
All contributions must be upstreamed to the Bitbake repository in order to make it to the "master" branch of the poky/ repository.<br />
<br />
=== Workflow ===<br />
To contribute to toaster you will also need authorization to write to the upstream yocto project repository. Contact a member of the toaster team for details.<br />
<br />
1) Download master branch of the yocto project<br />
<code> git clone git://git.yoctoproject.org/poky && cd poky </code><br />
<br />
2) Add poky-contrib to the local repository you set up above<br />
<code> git remote add poky-contrib ssh://git@push.yoctoproject.org/poky-contrib </code><br />
<br />
3) Fetch the poky-contrib branches<br />
<code> git fetch --all </code><br />
<br />
4) Start your feature branch off of master, name style of branch is convention, but suggested. <br />
<code> git checkout -b username/toaster/FeatureOrBug origin/master </code><br />
<br />
5) Do Work <br />
<br />
6) Test the changes. Run the Django unit tests. People put effort into these so we should make sure we use them. This assumes you have phantomjs installed. This can usually be done from the distribution <code> apt-get install phantomjs</code>, for example. If you want to test against Chrome or Firefox, see the README in bitbake/lib/toaster/tests/browser. <br />
<code> pip3 install selenium </code><br />
<code>TOASTER_TESTS_BROWSER=phantomjs bitbake/lib/toaster/manage.py test orm toastergui tests.browser </code><br />
<br><br />
Note: If you would like to run the tests in a container so they are repeatable and do not continually break due to host upgrades see [[Running Toaster Tests with Containers]]<br />
<br />
7) Rebase on master. It has probably changed while you were working (unless you are really really fast!)<br />
<code> git rebase origin/master </code><br />
<br />
8) Push your feature branch to poky-contrib<br />
<code> git push -u poky-contrib username/toaster/FeatureOrBug:username/toaster/FeatureOrBug</code><br />
<br />
9) Send to the toaster-mailing list using one of the methods outlined below.<br />
<br />
10) NOTE: when the patch has been accepted upstream, you can clean up your poy-contrib branch with:<br />
<br />
<code> git push -u poky-contrib :username/toaster/FeatureOrBug </code><br />
<br />
=== Sending patches to Toaster Project ===<br />
<br />
<strong>NOTE:</strong> The format of the commit message should be like this<br />
<br />
<pre><br />
toaster: <module> <short one line summary><br />
<br />
long(er) description<br />
<br />
[YOCTO #0000]<br />
<br />
Signed-off-by: First Last <name@domain.com><br />
</pre><br />
<br />
Where YOCTO #0000 is the related bug number if there is one. Signed off by with your git commit -s credentials.<br />
<br />
We accept patches on the [https://www.yoctoproject.org/tools-resources/community/mailing-lists toaster mailing list] ( toaster@yoctoproject.org ) by "git send-email".<br />
<br />
e.g.<br />
<code><br />
$ git send-email HEAD^ <br />
</code><br />
<br />
Alternatively, you can use the utilities in the script directory to prepare your patch<br />
<br />
1) Use the create-pull-request script (from poky) to create a pull request while on your feature branch<br />
<code>./scripts/create-pull-request -s "toaster: Fixes and clean ups" -u poky-contrib -r origin/master</code><br />
<br />
2) Review their content, especially the summary mail:<br />
<code>edit ./pull-<pid>/0000-cover-letter.patch</code><br />
<br />
3)When you are satisfied, you can send them with:<br />
<code>./scripts/send-pull-request -a -p ./pull-<pid></code> -t toaster@yoctoproject.org<br />
<br />
A comprehensive document about commit messages is available on the [http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines openembedded wiki]<br />
<br />
More help learning git is available on [https://try.github.io github] and [http://git-scm.com/documentation/ the official documentation]<br />
<br />
=== Sending branches to Toaster Project ===<br />
<br />
If you wish to submit whole branches please use the poky-contrib repository see [[Poky Contributions#Poky_Contrib_Branch]] for setup guide.<br />
<br />
Once you have pushed a branch please then send an email to the [https://www.yoctoproject.org/tools-resources/community/mailing-lists toaster mailing list] with the subject in the following format:<br />
<br />
<code><br />
[review-request] my_branch_name<br />
</code><br />
<br />
In the body of the email it's useful to describe your branch's functionality, which commits and a link to the git web.<br />
<br />
If you need any assistance please post on the mailing list.<br />
<br />
=== Submitting patch sets for integration into Bitbake ===<br />
<br />
Toaster patches are normally submitted upstream to the BitBake repository by the reviewer (not the author). This tells the upstream maintainers that the patches have been reviewed by the people who are familiar with the Toaster source code, and makes their busy lives a bit easier.<br />
<br />
Since development happens on the poky-contrib repository, but the patches need to be merged to the Bitbake repository, the following process should be executed.<br />
<br />
1) Bring master up to date<br />
<code> git fetch origin master</code><br />
<code> git checkout master </code><br />
<code> git pull [master] </code><br />
<br />
2) Checkout the target branch you wish to upstream<br />
<br />
(a) If you are working with a single branch do this:<br />
<br />
<code>git checkout username/toaster/FeatureOrBug</code><br />
<br />
(b) If you are including several branches into this one submission, gather the commit IDs for each branch and do this:<br />
<br />
<code>git cherry-pick commit-id-a </code><br />
<code>git cherry-pick commit-id-b </code><br />
<code>... </code><br />
<br />
3) Create a new branch for submission <br />
<code> git checkout -b yourname/submit/username/toaster/FeatureOrBug </code><br />
This will look something like<br />
<code> git checkout -b bavery/submit/bob/toaster/FixBug1234 </code><br />
where bavery is signing off on and upstreaming bob's fix to the Yocto Bugzilla bug 1234.<br />
<BR><br />
----<br />
---- <br />
* Alternatively, you can use the patchworks web site:<br />
2) Create a new branch for submission <br />
<code> git checkout -b yourname/submit/username/toaster/FeatureOrBug </code><br />
This will look something like<br />
<code> git checkout -b bavery/submit/bob/toaster/FixBug1234 </code><br />
where bavery is signing off on and upstreaming bob's fix to the Yocto Bugzilla bug 1234.<br />
3) Download and apply the mbox patch from the website: https://patchwork.openembedded.org/project/toaster/patches/<br />
<br />
<code> git am -s the-downloaded-patch.mbox </code><br />
----<br />
----<br />
<br><br />
4) Make sure the branch is rebased on current master. <br />
<code>git rebase origin/master</code><br />
<br />
5) Test the changes. Run the Django unit tests. People put effort into these so we should make sure we use them. his assumes you have phantomjs installed. This can usually be done from the distribution <code> apt-get install phantomjs</code>, for example. If you want to test against Chrome or Firefox, see the README in bitbake/lib/toaster/tests/browser.<br />
<code> pip3 install selenium </code><br />
<code>TOASTER_TESTS_BROWSER=phantomjs bitbake/lib/toaster/manage.py test orm toastergui tests.browser </code><br />
<br />
6) Add signed off by to the commit messages (Note: If you applied the mbox patch with <code> git am -s foo.mbox</code> You do not need to sign off again.)<br />
<code>git filter-branch -f --msg-filter 'cat && echo "Signed-off-by: $(git config --get user.name) <$(git config --get user.email)>"' master..HEAD</code><br />
<br />
7) Push the modified commit messages and rebased version to poky-contrib<br />
<code>git push -u poky-contrib yourname/submit/username/toaster/FeatureOrBug </code><br />
<br />
8) Use the create-pull-request script (from poky) to create a pull request for the appropriate tree/mailing list<br />
<br />
(a) For the 'bitbake' tree (e.g. bitbake/.../toasterui.py, bitbake/.../toastergui/*):<br />
<br />
<code>./scripts/create-pull-request -d bitbake -s "toaster: Fixes and clean ups" -u poky-contrib -r origin/master</code><br />
<br />
(b) for the 'meta' tree (e.g. meta/classes/toaster.class):<br />
<br />
<code>./scripts/create-pull-request -d meta -s "toaster: Fixes and clean ups" -u poky-contrib -r origin/master</code><br />
<br><br />
<strong>Note: If the patch creates any NEW files, the integration scripts that pull it into bitbake will fail. So, if new files are created as part of this patch set, you need to explicitly point that out in the body of the email for the patch set or do it as a PR rather than as a patch set.<br />
</strong><br />
<br />
9) Review their content, especially the summary mail:<br />
<code>edit ./pull-<pid>/0000-cover-letter.patch</code><br />
<br />
10) When you are satisfied, you can send them with:<br />
--- for the 'bitbake' tree:<br />
<code>./scripts/send-pull-request -a -p ./pull-<pid></code> -t bitbake-devel@lists.openembedded.org<br />
--- for the 'meta' tree:<br />
<code>./scripts/send-pull-request -a -p ./pull-<pid></code> -t openembedded-core@lists.openembedded.org<br />
<br />
==== Submitting patches for prior releases ====<br />
<br />
The procedure is the same, but using the prior release as the base branch instead of the "master" branch in bitbake.<br />
<br />
Also, make sure that you add the name of the prior release for which the patchset is intended in the prefix of the patchset, as parameter to the "create-pull-request" command, e.g. '''-p 1.26''' for the 1.26 branch.<br />
<br />
==== Gotchas ====<br />
===== Too Big =====<br />
Sometimes the mailer will refuse to send patches, especially on binary or long-line files. The proper way to go around that is to reply to the patchset you've submitted to the mailing list, asking for a git pull directly from the poky-contrib branch.<br />
===== One Patch of a Long Patch Set Needs Resubmission =====<br />
Suppose you upstream a 10 commit patch set to the bitbake-devel list and someone finds an issue with patch #3. Regenerating the whole series is silly so how do you address this? First, follow the bitbake submission steps until you end up on the yourname/submit/the/target/branch branch. Then you can (note <strong>the reset --hard will wipe any local changes in your working dir so commit or stash first</strong>):<br><br />
<code><br />
git checkout -b yourname/submit/the/target/branch-newHEAD<br />
git reset --hard <commit of resubmission issue> <br />
git commit --amend --signoff <br />
git send-email --in-reply-to="longNumber.git.me@mycomp.com" --subject-prefix="bitbake-devel] [PATCHVX 03/10" --to=bitbake-devel@lists.openembedded.org --no-chain-reply-to --suppress-cc=all -M -1 --relative=bitbake<br />
</code><br><br />
The longNumber.git.me@mycomp.com comes from the email message id for the particular patch #3 so that the email threading works. In gmail, you can click on the dropdown button on the right side of the screen and choose "Show Original". This will have a field in the header like Message-Id: <4551b56f132497c055f39567946a5d3be347d770.1468363530.git.myemailusername@mycompany.com> The entire string except the '<>' are used. for example:<br><br />
<code><br />
--in-reply-to="4551b56f132497c055f39567946a5d3be347d770.1468363530.git.myemailusername@mycompany.com"<br />
</code><br><br />
<br />
The first issue you are likely to face is that the git filter-branch command in the standard instructions may sign off on too many commits. If you know you just want to sign off on the last 7 commits on the yourname/submit/the/target/branch you can:<br />
<code><br />
git filter-branch -f --msg-filter 'cat && echo "Signed-off-by: $(git config --get user.name) <$(git config --get user.email)>"' HEAD~7..HEAD<br />
</code><br />
<br />
=== Submitting patches for documentation ===<br />
<br />
Documentation patches should be sent to [https://lists.yoctoproject.org/listinfo/yocto Yocto mailing list] with [yocto-docs] in the subject, CC Scott Rifenbark (and make sure you send it to his gmail, not his defunct Intel address). For his email address, look at [http://lists.openembedded.org/pipermail/bitbake-devel/2015-October/006632.html this post].<br />
<br />
== Code syle guide ==<br />
<br />
=== Templates ===<br />
<br />
Django has a template language which allows us to render pages based on the data (context). We use the template language to setup the initial state of the page and to create re-usable components that can be included in other pages.<br />
<br />
The recommend template code style is as follows<br />
<br />
'''Yes please:'''<br />
<br />
<pre><br />
{{var}}<br />
<br />
<div><br />
{# Maintaining indentation #}<br />
{% if %}<br />
<p>this</p><br />
{% else %}<br />
<p>that</p><br />
{% endif %}<br />
</div><br />
<br />
{% comment %}<br />
This is a longer comment that describes all the things<br />
that are below in quite a bit of detail because they're<br />
a little more difficult to understand.<br />
{% endcomment %}<br />
<br />
{% for layer in layers_list %}<br />
{{layer}}<br />
{% endfor %}<br />
<br />
</pre><br />
<br />
'''No thank you:'''<br />
<pre><br />
{{var}}<br />
<div><br />
{# Maintaining indentation #}<br />
{%if%}<p>this</p>{%else%}<p>that</p>{%endif%}<br />
</div><br />
<br />
<br />
{#This is a longer comment that describes all the things that are below in quite a bit of detail because they're a little more difficult to understand. #}<br />
{%for o in layers_list%}{{o}}{%endfor%}<br />
</pre><br />
<br />
Note:<br />
* Maintain indentation as you would with other languages<br />
* White space after '%'<br />
* Comment blocks for longer comments<br />
<br />
<br />
=== Javascript ===<br />
<br />
'''Yes please:'''<br />
<pre><br />
<br />
"use strict";<br />
<br />
/* These hold some numbers */<br />
var oneVar = 1;<br />
var twoVar = 2;<br />
<br />
var cheesesTypes = {<br />
cheddar : 1,<br />
stilton : 2,<br />
emmental : 3, <br />
};<br />
<br />
function doThingsHere(){<br />
return 1;<br />
}<br />
<br />
/* If one equals two do some other things and make sure that<br />
* if the the click handler is setup correctly.<br />
*/<br />
if (one === two) {<br />
var cheese = "cheddar";<br />
oneVar = doThingsHere();<br />
<br />
$(this).click(function (event){<br />
alert("Hello");<br />
});<br />
}<br />
<br />
$("#little-mouse").focusout(function(){<br />
alert("bye")<br />
});<br />
<br />
if (oneVar)<br />
noThingHere();<br />
else<br />
doThingHere();<br />
</pre><br />
<br />
'''No thank you:'''<br />
<pre><br />
// These hold some numbers<br />
oneVar = 1<br />
twoVar = 2<br />
<br />
var cheesesTypes = { cheddar : 1, stilton : 2, emmental : 3, }<br />
<br />
function doThingsHere ()<br />
{<br />
return 1;<br />
}<br />
<br />
//If one equals two do some other things and make sure that if the the click handler is setup correctly.<br />
if( one === two ) {<br />
var cheese = "cheddar";<br />
oneVar = doThingsHere();<br />
<br />
$(this).click(function(event){ alert("Hello"); });<br />
}<br />
<br />
document.getElementById("little-mouse").addEventListener("focusout", function(){<br />
alert("bye")<br />
});<br />
<br />
if (oneVar)<br />
{<br />
noThingHere();<br />
} else { doThingHere(); }<br />
</pre><br />
<br />
Note:<br />
* Variables should be marked with "var" <br />
* Semicolons should be used<br />
* Keep as close to 80 cols as possible<br />
* Use 2 space per indentation<br />
* Open curly braces after parenthesis for functions and close on a new line<br />
* Use camelCase for function names and variable names <br />
<br />
<br />
Make use of running your Javascript through jshint we have a .jshint configuration file in that js directory (toastergui/static/js)<br />
<br />
e.g. install jshint and add to your current PATH, then run:<br />
<code><br />
$ npm install jshint; export PATH=$PATH:$PWD/node_modules/.bin/<br />
$ jshint ./toastergui/static/js/base.js<br />
</code><br />
<br />
=== HTML ===<br />
<br />
'''Yes please:'''<br />
<pre><br />
<div id="something-area"><br />
<p class="important">This is some text</p><br />
</div><br />
<br />
<div><br />
<p id="important-text>This is some text</p><br />
</div><br />
<br />
<br />
</pre><br />
<br />
'''No thank you:'''<br />
<pre><br />
<div id="somethingarea"><br />
<p class="Important">This is some text</p></div><br />
<div id="somethingarea"><br />
<p id="ImportantText">This is<br />
some text<br />
</p><br />
<br />
</div><br />
</pre><br />
<br />
Note:<br />
* 2 space indentation<br />
* Lower case, ids hyphenated when multiple words<br />
* No duplicate ids <br />
<br />
* Run your HTML through a [http://validator.w3.org/#validate_by_input HTML validator] available for [http://validator.w3.org/source/ local install]. The w3c validator it's self doesn't currently validate html5, it uses as a back end [https://validator.github.io/validator/ Nu Html Checker] which can be installed as a standalone service, full instructions in the readme.<br />
<br />
Quick install instructions:<br />
<pre><br />
$ mkdir html5-validator && cd html5-validator<br />
$ export JAVA_HOME=/usr/lib/jvm/java-6-openjdk<br />
$ git clone https://github.com/validator/validator.git<br />
$ python build/build.py all<br />
$ python build/build.py all<br />
</pre><br />
<br />
HTML can be indented quickly using tidy, for example:<br />
<pre><br />
tidy -xml --indent auto --indent-spaces 2 --quiet yes -w -1 --show-body-only yes ./index.html <br />
</pre><br />
<br />
=== Python ===<br />
<br />
Lenient [https://www.python.org/dev/peps/pep-0008 pep8]<br />
Ignoring most of the whitespace around character issues (E124,E203,E201,E265,E303,E302,E231) see toaster/.pep8 and [http://pep8.readthedocs.org/en/latest/intro.html#error-codes error code list]<br />
<br />
Fix all issues identified by running code through pep8. We have a fairly lenient config file (toaster/.pep8).<br />
<br />
e.g.<br />
<code><br />
$ pep8 ./toastergui/urls.py<br />
</code><br />
<br />
Run code through pylint and fix identified issues - Some can be reasonably ignored such as doc strings for every function or star-args. No pylintrc config provided here as most issues identified are highly contextual and should be ignored on a case by case basis.<br />
<br />
<code><br />
$ pylint --load-plugins pylint_django toastergui/tests.py<br />
</code><br />
<br />
== Working with design ==<br />
<br />
Yes, the Yocto Project is one of those lucky projects with designers around to help in UI matters. We have a document explaining how to work with the design contributors: [[File:Working_with_design.pdf]]<br />
<br />
== Debugging Toaster ==<br />
<br />
Toaster can be quite complex given that it includes a wide range of technologies and languages from bitbake, events, python, Django, Sqlite, Javescript, CCS, HTML, and more. Here are hints and tips for debugging all of these aspects of Toaster.<br />
<br />
=== General debugging tips ===<br />
<br />
* The logger is your best friend<br />
* When possible, build from command line in the Toaster environment to see log messages and errors directly<br />
* Use "quilt-native" as your quick sanity build target<br />
* For python code you can use pudb (https://wiki.yoctoproject.org/wiki/TipsAndTricks/DebuggingBitbakeInPudb)<br />
* For bbclass code (toaster.bbclass) find or set up a python section to use pudb (see above link)<br />
* Brute force find is your friend for mysterious error messages and tracking all places a variable is used<br />
** find bitbake/lib/toaster -exec grep -l "SEARCH_TEXT" {} \; 2> /dev/null<br />
* Look in https://wiki.yoctoproject.org/wiki/TipsAndTricks<br />
<br />
=== How to debug a ... ===<br />
<br />
* A stalled build:<br />
** Cancel the build and look at one of the below logs to find the exception. The error message should give a clue on the user resolution or indicate a bug to file<br />
** Failures in git and shell calls are (as of YP-2.4 Rocko) captured as visible build errors in the GUI<br />
* Python file of a build management script (localhostbecontroller.py,...):<br />
** Use log statements, and watch "build/toaster_runbuilds.log" (where you started Toaster)<br />
* Python file of a build runtime scripts:<br />
** Use log statements, and watch "build-toaster-x/toaster_ui.log"<br />
* Python file of a Toaster management script (projects, tables):<br />
** Use log statements, and watch "build/toaster_web.log" (where you started Toaster)<br />
* Template file<br />
** Usually the error will appear in the browser via Django, with a trace<br />
** Add random display text to insure the page your editing is the one that shows<br />
** Display internal values via page template to see what gets passed<br />
** Add internal values into the context and add to the page template<br />
** Use the Firefox/Chrome developer "inspector" to examine the DOM<br />
* Javascript file<br />
** Use the Firefox/Chrome developer "inspector" to do inline debugging<br />
** Watch the Firefox/Chrome developer "console" for error messages<br />
* The Toaster Database<br />
** Use an application like "sqlitebrowser" to examine the tables and records<br />
** Use a Python script to find and dump desired database records (see http://events.linuxfoundation.org/sites/events/files/slides/BitbakeAnalytics_ELC_Portland.pdf)<br />
<br />
=== Specific error scenarios ... ===<br />
<br />
* The build progress gets stuck at "Loading..."<br />
** You have a syntax error, either in 'localhostbecontroller.py', the helper classes in 'models.py', or in the related javascript. Look at the tail of "toaster_runbuilds.log" file for pythons errors, and in your browser's "Console" for javascript errors.<br />
* The message "Sorry, An error has occurred loading this page"<br />
** The included javascript has a syntax error. The HTML page being rendered has local JS code at the top that caches these errors and displays the observed message (in order to be less ugly to the customer). That code also tries to add the error message to the browser console but that does not always work, and you are left with no clue<br />
** You can start bisecting the recent edits you made to the respective JS files to locate the problem change<br />
** You can also add a breakpoint in the mentioned catch code to see if you can see the error directly<br />
<br />
=== How to update from a fix in a ... ===<br />
<br />
* Template file: save your text edit and refresh page<br />
* Javascript file: save your text edit and refresh page (or leave page and come back)<br />
* Builder scripts: save your text edit and restart Toaster ("localhostbecontroller.py", "buildinfohelper.py", "toasterui.py", "bbcontroller.py",...)<br />
* Views and URLs: save your text edit and refresh page<br />
* Model class members: save your text edit and restart Toaster. You may also need a migration file.<br />
* Model method: save your text edit and refresh page, else restart Toaster<br />
* Fixture file (settings.xml, poky.xml, custom.xml): delete Toaster database and restart fresh<br />
<br />
=== Where to debug ... ===<br />
<br />
* Toaster start and stop, database init<br />
** bin/toaster<br />
* Project Defaults (Default machine, distro, layers, ...)<br />
** bldcontrol/management/commands/checksettings.py<br />
** orm/fixtures/*.xml<br />
* Layer Index content (Available machines, distros, layers, ...)<br />
** orm/management/commands/lsupdates.py<br />
* Build cloning<br />
** bldcontrol/localhostbecontroller.py<br />
* Build start<br />
** bldcontrol/localhostbecontroller.py<br />
* URL mappings<br />
** toastergui/urls.py<br />
* Views<br />
** toastergui/views.py<br />
** toastergui/templates/*<br />
* Toaster Tables (Layers, Distros, Machines, ...)<br />
** toastergui/tables.py<br />
** toastergui/static/js/libtoaster.js<br />
* Events<br />
** meta/classes/toaster.bbclass -> <br />
** lib/bb/ui/toasterui.py -> <br />
** lib/bb/ui/buildinfohelper.py -> <br />
** orm/models.py et. al.</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=Toaster&diff=86095Toaster2023-11-30T21:51:25Z<p>MichaelHalstead: Updated dead link to old Yocto Project 1.0 docs</p>
<hr />
<div>[[Category:Toaster]]<br />
[[Toaster]] is a web-based interface to OpenEmbedded and BitBake.<br />
[[File:Screenshot toaster.png|thumb|Screenshot of Toaster 2.1]]<br />
General discussion about '''Toaster''' happens on a dedicated mailing list: [https://lists.yoctoproject.org/listinfo/toaster https://lists.yoctoproject.org/listinfo/toaster]<br />
<br />
=== Using Toaster ===<br />
<br />
Toaster can run in various modes and setups.<br />
<br />
* '''Local mode''' - in this mode Toaster is setup for use as a local development tool. It can be used to configure builds or just as a receiver for builds done on the command line with bitbake. You can launch it like this:<br />
<br />
$ source oe-init-build-env<br />
$ source toaster start<br />
<br />
You then navigate to the link in your browser (e.g. http://localhost:8000) and configure a project. Or start building in the normal way with bitbake via the command line. Toaster will automatically pick up the builds and you will be able to see them on the build dashboard in your browser.<br />
<br />
* '''Production mode''' - All the same functionality as the local mode but with the web server setup as a shared service for multiple developers to use, this sets up Toaster as a wsgi application and [[Setting up a production instance of Toaster|requires additional configuration]].<br />
<br />
=== Toaster How-to's ===<br />
<br />
Specific pages with Toaster how-tos are available below.<br />
<br />
* [[Contribute to Toaster]]<br />
* [[Testing Toaster]]<br />
* [[Setting up a local instance of Toaster]]<br />
* [[Setting up a production instance of Toaster]] - documentation for Interactive mode<br />
* [https://docs.yoctoproject.org/dunfell/toaster-manual/toaster-manual-setup-and-use.html#using-the-toaster-web-interface How to use the Toaster web interface]<br />
* [[How to delete information from the Toaster database]]<br />
* [[How to support permission management in Build Mode for Toaster]]<br />
* [[ToasterTable]]: Toaster's internal API for adding sortable, filterable, paged tables<br />
<br />
=== About Toaster ===<br />
[[File:Screenshot toaster analyis.png|thumb|Analysis of builds using Toaster]]<br />
<br />
* [[File:Working_with_design.pdf]]<br />
* [https://bugzilla.yoctoproject.org/buglist.cgi?list_id=213820&columnlist=status_whiteboard%2Cassigned_to%2Ctarget_milestone%2Cbug_status%2Cshort_desc%2Cbug_severity%2Cpriority&classification=Build%20System%20%26%20Metadata&query_based_on=Toaster-Opens&query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=IN%20PROGRESS%20DESIGN&bug_status=IN%20PROGRESS%20DESIGN%20COMPLETE&bug_status=IN%20PROGRESS%20IMPLEMENTATION&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&component=toaster&product=Toaster&known_name=Toaster-Opens Bug list]<br />
* [[Toaster architecture design]]<br />
* [[Toaster and bitbake communications]]<br />
* [[Toaster database]]<br />
* [[Toaster testing plan]]<br />
<br />
=== In progress documentation ===<br />
<br />
We are currently preparing the documentation for the Toaster build functionality. The content here is just a brain dump of what we need to cover (in no particular order). Feel free to add and create content as you see fit:<br />
<br />
*[[Using virtualenv]]<br />
*[[Setting up a production instance of Toaster]]<br />
*[[manage.py commands]] - this should include an explanation of lsupdates<br />
*[[Start Toaster in managed mode]]</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User_talk:Yocto_noob&diff=85979User talk:Yocto noob2023-10-12T17:42:46Z<p>MichaelHalstead: Welcome!</p>
<hr />
<div>'''Welcome to ''Yocto Project''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br />
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 17:42, 12 October 2023 (UTC)</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User:Yocto_noob&diff=85978User:Yocto noob2023-10-12T17:42:46Z<p>MichaelHalstead: Creating user page for new user.</p>
<hr />
<div>starting with yocto project, gathering as much as I can.</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User_talk:Mcheiswa&diff=85973User talk:Mcheiswa2023-10-11T16:15:47Z<p>MichaelHalstead: Welcome!</p>
<hr />
<div>'''Welcome to ''Yocto Project''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br />
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 16:15, 11 October 2023 (UTC)</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User:Mcheiswa&diff=85972User:Mcheiswa2023-10-11T16:15:47Z<p>MichaelHalstead: Creating user page for new user.</p>
<hr />
<div>Aspiring graduate engineer hoping to learn more about yocto project and contribute to the project</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User_talk:Quaresma.jose&diff=85971User talk:Quaresma.jose2023-10-11T16:15:07Z<p>MichaelHalstead: Welcome!</p>
<hr />
<div>'''Welcome to ''Yocto Project''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br />
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 16:15, 11 October 2023 (UTC)</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User:Quaresma.jose&diff=85970User:Quaresma.jose2023-10-11T16:15:07Z<p>MichaelHalstead: Creating user page for new user.</p>
<hr />
<div>OpenEmbedded user who loves keep it simple</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&diff=85948Security private reporting2023-09-29T20:43:42Z<p>MichaelHalstead: Add a second keyserver link</p>
<hr />
<div>= (WIP) Security team and private reporting =<br />
<br />
== How to Report a Vulnerability? ==<br />
<br />
Please send a message to security [at] yoctoproject [dot] org, including as many details as possible: the layer or software module affected, the recipe and its version, and an example code, if available.<br />
<br />
''' Branches maintained with security fixes'''<br />
----------------------------------------------<br />
See [https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance Stable branches maintenance]for detailed info regarding the policies and maintenance of Stable branch.<br />
<br />
Versions in grey are no longer actively maintained with security patches, but well-tested patches may still be accepted for them.<br />
<br />
== How to Contact the Yocto Project regarding Security ==<br />
<br />
We have set up two security-related mailing lists:<br />
<br />
* '''Public List'''<br />
: yocto [dash] security [at] yoctoproject[dot] org<br />
: This is a public mailing list for anyone to subscribe to. This list is an open list to discuss public security issues/patches and security-related initiatives. For more information, including subscription information, please see the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list info page].<br />
<br />
* '''Private List'''<br />
: security [at] yoctoproject [dot] org<br />
: This is a private mailing list for reporting non-published potential vulnerabilities. The list is monitored by the Yocto Project Security team.<br />
<br />
<br />
'''What you should do if you find a security vulnerability'''<br />
---------------------------------------------<br />
If you find a security flaw; a crash, an information leakage, or anything that can have a security impact if exploited in any Open Source packages used by the Yocto Project, please report this to the Yocto Project Security Team. If you prefer to contact the upstream project directly, please send a copy to the security team at Yocto as well.<br />
If you believe this is highly sensitive information, please report the vulnerability in a secure way, i.e. encrypt the email and send it to the private list. This ensures that the exploit is not leaked and exploited before a response/fix has been generated.<br />
<br />
<br />
'''What Yocto Security Team does when it receives a security vulnerability'''<br />
---------------------------------------------<br />
The YP Security Team team performs a quick analysis and reports the flaw to the upstream project. Normally the upstream project analyzes the problem. If they deem it a real security problem in their software, they develop and release a fix following their own security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.<br />
<br />
The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are normally non-public.<br />
<br />
When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.<br />
<br />
<br />
<br />
'''If an upstream project does not respond quickly'''<br />
---------------------------------------------<br />
If an upstream project does not fix the problem in a reasonable time, the Yocto's Security Team will contact other interested parties (usually other distributions) in the community and together try to solve the vulnerability as quickly as possible. <br />
<br />
The Yocto Project Security team adheres to the 90 days disclosure policy by default. An increase of the embargo time is possible when necessary.<br />
<br />
== Security Team Appointment ==<br />
<br />
The Yocto Project Security Team consists of at least three members. When new members are needed, the YP TSC asks for nominations by public channels, including also the limit date. Self-nominations are possible. When the limit time is reached, the YP TSC posts the list of candidates for the comments of project participants and developers. Comments may be sent publicly or privately to the YP and OE TSCs. The candidates are approved by both YP TSC and OE TSC and the final list of the team members is announced publicly.<br />
<br />
YP Security Team members may resign at any time.<br />
<br />
== Current Security Team Members ==<br />
<br />
<br />
Current Yocto Project Security Team members are: <br />
: : - '''mhalstead [at] linuxfoundation [dot] org''' <br />
<br />
<br />
: For secure communications, please send your messages encrypted to both using the following GPG keys. <br />
: Remember message headers are not encrypted so do not include sensitive information in the subject line.<br />
<br />
: Download public keys: [https://pgp.mit.edu/pks/lookup?op=vindex&search=0x3373170601861969 Michael Halstead] or [https://keyserver.ubuntu.com/pks/lookup?op=get&search=0xd1f2407285e571ed12a407a73373170601861969 Michael Halstead]</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User_talk:MadDave&diff=85922User talk:MadDave2023-09-12T18:18:28Z<p>MichaelHalstead: Welcome!</p>
<hr />
<div>'''Welcome to ''Yocto Project''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br />
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 18:18, 12 September 2023 (UTC)</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User:MadDave&diff=85921User:MadDave2023-09-12T18:18:28Z<p>MichaelHalstead: Creating user page for new user.</p>
<hr />
<div>Developing software since 1980, hardly a novice, trying to get Yocto to build from a base port supplied to me, it doesnt, it produces the most odd errors, the error on the screen, the comments in the log dont match, I want to put some debug in to find out whats going on, the instructions in https://docs.yoctoproject.org/dev/dev-manual/debugging.html dont output anything to log or screen, the comments that I dont want to see anything on the console are frankly wrong - I WANT to see what is happening so I can workout what ISNT working. Credit me with a little brain power. <br />
<br />
I am an old grey beard, frustrated as hell with the tools that get more and more complex and less and less able to do the job, I want a hammer to bash in a nail, not something that requires a doctorate and 200 years of rocket science study that might, if the wind is in the right direction, the planets aligned correctly, the dog behaving itself and my blood pressure below that of an imminent heart failure might produce a plasticine mallet that wont darned work anyway.</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=Main_Page&diff=85904Main Page2023-09-01T21:50:44Z<p>MichaelHalstead: Make the triage bugs easier to find</p>
<hr />
<div>== Welcome to the Yocto Project Wiki! ==<br />
The [http://yoctoproject.org Yocto Project] is an open-source project that delivers a set of tools that create operating system images for embedded Linux systems. The Yocto Project tools are based on the [http://www.openembedded.org/wiki/Main_Page OpenEmbedded] (OE) project, which uses the BitBake build tool, to construct complete Linux images. BitBake and OE are combined to form a reference build host known as Poky which includes the following [[Core Components|core components]]. This [https://www.youtube.com/watch?v=utZpKM7i5Z4 video] will help explain what it's all about.<br />
<br />
===Where to Start?===<br />
If you're new to Yocto take a look at the '''[[Glossary]]''' so you're familiar with the terms used in this wiki and the project documentation. Then take a look at the [https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html '''Quick Start Guide''']. You can follow the steps in this document to clone the poky repository, quickly configure your build environment, and then try a build. Corporate firewalls can be problematic so network proxy configurations are detailed on the '''[[Working Behind a Network Proxy]]''' page. We advise you go straight for the [[Working_Behind_a_Network_Proxy#Option_2:_Chameleonsocks| Chameleonsocks option]].<br />
<br />
===Where to Next?===<br />
Thanks to the quick start guide, it's pretty easy to get your first Linux image and and running. Here are some places to look for help when improving your Yocto skills.<br />
* The [https://linuxfoundation.org Linux Foundation] have some great [https://docs.google.com/presentation/d/1LmI3mHoD_Dzl8wplIYcUBrFF8BzDb_EadTvfbnpSK7Q/edit training slides]. There is also an [https://docs.google.com/presentation/d/1HoDtyN5SzlmuTN47ab4Y7w_i6c_VEW6EBUD944ntf38/edit#slide advanced slide deck] for more more experienced users. <br />
* The first tool you'll need to get familiar with is '''bitbake''', so reading through the [https://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html user manual] is recommended. You don't need to understand it all right now, but bookmark this page for reference. Implementation of bitake is covered in the [[Bitbake Internals Primer]] <br />
* Once you start adding packages and configuring your image to create your own distribution, things can go wrong and it can hard to track down the root cause. There is no shortage of Yocto documentation resource, but if you're not exactly sure what you're looking for this '''[[Documentation Decoder]]''' will help you out. Also take a look at the [https://wiki.yoctoproject.org/wiki/Cookbook '''Cookbook'''] and [https://wiki.yoctoproject.org/wiki/Technical_FAQ troubleshooting guide]. Also [https://www.yoctoproject.org/blogs/jefro/2016/yocto-project-books these books] are helpful. <br />
* Some new tools such as [http://www.yoctoproject.org/docs/current/toaster-manual/toaster-manual.html Toaster], [[Extensible SDK]] and [https://github.com/crops CROPS] are making it easier to get the best out of Yocto on Windows and Mac OS X. Take a look at the new workflow in [[Developer Workflow Improvements]].<br />
* There is also a [https://wiki.yoctoproject.org/wiki/TipsAndTricks '''Tips and Tricks'''] section where more experienced developers contribute to articles that will help those new to Yocto Project.<br />
* You can also read and participate on the [https://lists.yoctoproject.org mailing lists] - start with the [https://lists.yoctoproject.org/g/yocto main list] first - and the IRC channel. More information about the Yocto Project mailing lists, IRC and Matrix channels can be found [https://www.yoctoproject.org/community/mailing-lists/ here].<br />
<br />
== Project planning ==<br />
<br />
=== Features === <br />
* [[Yocto Feature Summary]] (Current and Next)<br />
<br />
=== Project Planning for current release ===<br />
<br />
* [[Planning]]<br />
<br />
=== Project Status and Schedule ===<br />
* [[Weekly_Status]]<br />
* Testresults - https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/log/?h=intel-yocto-testresults<br />
<br />
=== Future Directions ===<br />
* [[Future_Directions]]<br />
<br />
== Documentation ==<br />
<br />
* [[Documentation Decoder]]<br />
<br />
=== Improvement ideas ===<br />
<br />
* [[Documentation Production Workflow]]<br />
<br />
== Release Engineering ==<br />
<br />
* [[Yocto Release Engineering | Yocto Project Release Engineering]]<br />
* [[Yocto Release Engineering | Release Activity (with status, version info, QA links, etc)]]<br />
<br />
== QA & Automation ==<br />
<br />
* [[The_Yocto_Autobuilder| The Yocto Project Autobuilder]]<br />
* [[QA| Yocto Project QA Main Page]]<br />
* [[QA/Archive| Yocto Project QA Test Report Archive ]]<br />
<br />
== Quick guide for newcomers ==<br />
<br />
If you are new to the project and are willing to contribute, please refer to our [[Newcomers|guide for newcomers]].<br />
<br />
== TSC ==<br />
* Yocto Project Technical Steering Committee [[TSC]] <br />
<br />
== Wiki reference sitemap ==<br />
* [[Glossary]]<br />
* [[Working Behind a Network Proxy]]<br />
* [[FAQ]] and [[Technical FAQ]]. These need to be unified.<br />
* [[Cookbook]] and [[TipsAndTricks | Tips and Tricks]]. Need clear messaging on how these should be differentiated.<br />
* [[Developer Workflow Improvements]], including [[Nodejs Workflow Improvements]]<br />
* [[Bug_Triage | Bug Triage Reference ]]<br />
* [[Planning and Governance]]<br />
* [[Community Guidelines]]<br />
* [[Yocto Release Engineering | Yocto Project Release Engineering]]<br />
* [[License Infrastructure Interest Group | License Infrastructure]]<br />
* [[Processes and Activities]]<br />
* [[Member Technical Contacts]]<br />
* [[Projects]]<br />
* [[Security]] - find out what we do about CVEs and security<br />
* [[Yocto Interest Groups]]<br />
* [[Toaster]] - the web interface <br />
* [[YoctoProjectEvents]] - links to YoctoProject/OpenEmbedded related conferences and events<br />
* [[Archive]] - Graveyard for out of date articles.<br />
<br />
== Other resources ==<br />
* [http://yoctoproject.org Yocto Project Front Page]<br />
* [http://git.yoctoproject.org/ Yocto Project Git Source Repos]<br />
* [https://docs.yoctoproject.org/ Yocto Project Documentation]<br />
* [https://bugzilla.yoctoproject.org/ Yocto Project Bugzilla]<br />
* [https://www.yoctoproject.org/tools-resources/community/mailing-lists Yocto Project Mailing Lists]<br />
* [http://recipes.yoctoproject.org/rrs Yocto Project Recipe Reporting System]<br />
* [https://autobuilder.yoctoproject.org/typhoon Yocto Project Autobuilder]<br />
* [http://downloads.yoctoproject.org/releases/yocto/ Yocto Project Releases Downloads]<br />
* [http://autobuilder.yoctoproject.org/pub/nightly/ Yocto Project Nightly Build Images]<br />
* [http://downloads.yoctoproject.org/mirror/sources/ Upstream Sources Mirror]<br />
* [http://www.openembedded.org/wiki/Main_Page OpenEmbedded Wiki]<br />
* [http://cgit.openembedded.org/ OpenEmbedded Git Repos]<br />
* [http://layers.openembedded.org/ OpenEmbedded Community Layers] <br />
* [http://patchwork.openembedded.org/ OpenEmbedded Patch Tracking System]<br />
* '''IRC''': [https://libera.chat/ irc.libera.chat]<br />
:* #yocto - Public discussions on the Yocto Project.<br />
:* #oe - Public discussions on OpenEmbedded Core.</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=Main_Page&diff=85903Main Page2023-09-01T21:40:16Z<p>MichaelHalstead: Removing Testopia reference</p>
<hr />
<div>== Welcome to the Yocto Project Wiki! ==<br />
The [http://yoctoproject.org Yocto Project] is an open-source project that delivers a set of tools that create operating system images for embedded Linux systems. The Yocto Project tools are based on the [http://www.openembedded.org/wiki/Main_Page OpenEmbedded] (OE) project, which uses the BitBake build tool, to construct complete Linux images. BitBake and OE are combined to form a reference build host known as Poky which includes the following [[Core Components|core components]]. This [https://www.youtube.com/watch?v=utZpKM7i5Z4 video] will help explain what it's all about.<br />
<br />
===Where to Start?===<br />
If you're new to Yocto take a look at the '''[[Glossary]]''' so you're familiar with the terms used in this wiki and the project documentation. Then take a look at the [https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html '''Quick Start Guide''']. You can follow the steps in this document to clone the poky repository, quickly configure your build environment, and then try a build. Corporate firewalls can be problematic so network proxy configurations are detailed on the '''[[Working Behind a Network Proxy]]''' page. We advise you go straight for the [[Working_Behind_a_Network_Proxy#Option_2:_Chameleonsocks| Chameleonsocks option]].<br />
<br />
===Where to Next?===<br />
Thanks to the quick start guide, it's pretty easy to get your first Linux image and and running. Here are some places to look for help when improving your Yocto skills.<br />
* The [https://linuxfoundation.org Linux Foundation] have some great [https://docs.google.com/presentation/d/1LmI3mHoD_Dzl8wplIYcUBrFF8BzDb_EadTvfbnpSK7Q/edit training slides]. There is also an [https://docs.google.com/presentation/d/1HoDtyN5SzlmuTN47ab4Y7w_i6c_VEW6EBUD944ntf38/edit#slide advanced slide deck] for more more experienced users. <br />
* The first tool you'll need to get familiar with is '''bitbake''', so reading through the [https://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html user manual] is recommended. You don't need to understand it all right now, but bookmark this page for reference. Implementation of bitake is covered in the [[Bitbake Internals Primer]] <br />
* Once you start adding packages and configuring your image to create your own distribution, things can go wrong and it can hard to track down the root cause. There is no shortage of Yocto documentation resource, but if you're not exactly sure what you're looking for this '''[[Documentation Decoder]]''' will help you out. Also take a look at the [https://wiki.yoctoproject.org/wiki/Cookbook '''Cookbook'''] and [https://wiki.yoctoproject.org/wiki/Technical_FAQ troubleshooting guide]. Also [https://www.yoctoproject.org/blogs/jefro/2016/yocto-project-books these books] are helpful. <br />
* Some new tools such as [http://www.yoctoproject.org/docs/current/toaster-manual/toaster-manual.html Toaster], [[Extensible SDK]] and [https://github.com/crops CROPS] are making it easier to get the best out of Yocto on Windows and Mac OS X. Take a look at the new workflow in [[Developer Workflow Improvements]].<br />
* There is also a [https://wiki.yoctoproject.org/wiki/TipsAndTricks '''Tips and Tricks'''] section where more experienced developers contribute to articles that will help those new to Yocto Project.<br />
* You can also read and participate on the [https://lists.yoctoproject.org mailing lists] - start with the [https://lists.yoctoproject.org/g/yocto main list] first - and the IRC channel. More information about the Yocto Project mailing lists, IRC and Matrix channels can be found [https://www.yoctoproject.org/community/mailing-lists/ here].<br />
<br />
== Project planning ==<br />
<br />
=== Features === <br />
* [[Yocto Feature Summary]] (Current and Next)<br />
<br />
=== Project Planning for current release ===<br />
<br />
* [[Planning]]<br />
<br />
=== Project Status and Schedule ===<br />
* [[Weekly_Status]]<br />
* Testresults - https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/log/?h=intel-yocto-testresults<br />
<br />
=== Future Directions ===<br />
* [[Future_Directions]]<br />
<br />
== Documentation ==<br />
<br />
* [[Documentation Decoder]]<br />
<br />
=== Improvement ideas ===<br />
<br />
* [[Documentation Production Workflow]]<br />
<br />
== Release Engineering ==<br />
<br />
* [[Yocto Release Engineering | Yocto Project Release Engineering]]<br />
* [[Yocto Release Engineering | Release Activity (with status, version info, QA links, etc)]]<br />
<br />
== QA & Automation ==<br />
<br />
* [[The_Yocto_Autobuilder| The Yocto Project Autobuilder]]<br />
* [[QA| Yocto Project QA Main Page]]<br />
* [[QA/Archive| Yocto Project QA Test Report Archive ]]<br />
<br />
== Quick guide for newcomers ==<br />
<br />
If you are new to the project and are willing to contribute, please refer to our [[Newcomers|guide for newcomers]].<br />
<br />
== TSC ==<br />
* Yocto Project Technical Steering Committee [[TSC]] <br />
<br />
== Wiki reference sitemap ==<br />
* [[Glossary]]<br />
* [[Working Behind a Network Proxy]]<br />
* [[FAQ]] and [[Technical FAQ]]. These need to be unified.<br />
* [[Cookbook]] and [[TipsAndTricks | Tips and Tricks]]. Need clear messaging on how these should be differentiated.<br />
* [[Developer Workflow Improvements]], including [[Nodejs Workflow Improvements]]<br />
* [[Planning and Governance]]<br />
* [[Community Guidelines]]<br />
* [[Yocto Release Engineering | Yocto Project Release Engineering]]<br />
* [[License Infrastructure Interest Group | License Infrastructure]]<br />
* [[Processes and Activities]]<br />
* [[Member Technical Contacts]]<br />
* [[Projects]]<br />
* [[Security]] - find out what we do about CVEs and security<br />
* [[Yocto Interest Groups]]<br />
* [[Toaster]] - the web interface <br />
* [[YoctoProjectEvents]] - links to YoctoProject/OpenEmbedded related conferences and events<br />
* [[Archive]] - Graveyard for out of date articles.<br />
<br />
== Other resources ==<br />
* [http://yoctoproject.org Yocto Project Front Page]<br />
* [http://git.yoctoproject.org/ Yocto Project Git Source Repos]<br />
* [https://docs.yoctoproject.org/ Yocto Project Documentation]<br />
* [https://bugzilla.yoctoproject.org/ Yocto Project Bugzilla]<br />
* [https://www.yoctoproject.org/tools-resources/community/mailing-lists Yocto Project Mailing Lists]<br />
* [http://recipes.yoctoproject.org/rrs Yocto Project Recipe Reporting System]<br />
* [https://autobuilder.yoctoproject.org/typhoon Yocto Project Autobuilder]<br />
* [http://downloads.yoctoproject.org/releases/yocto/ Yocto Project Releases Downloads]<br />
* [http://autobuilder.yoctoproject.org/pub/nightly/ Yocto Project Nightly Build Images]<br />
* [http://downloads.yoctoproject.org/mirror/sources/ Upstream Sources Mirror]<br />
* [http://www.openembedded.org/wiki/Main_Page OpenEmbedded Wiki]<br />
* [http://cgit.openembedded.org/ OpenEmbedded Git Repos]<br />
* [http://layers.openembedded.org/ OpenEmbedded Community Layers] <br />
* [http://patchwork.openembedded.org/ OpenEmbedded Patch Tracking System]<br />
* '''IRC''': [https://libera.chat/ irc.libera.chat]<br />
:* #yocto - Public discussions on the Yocto Project.<br />
:* #oe - Public discussions on OpenEmbedded Core.</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User_talk:Haward01&diff=85863User talk:Haward012023-07-23T21:04:23Z<p>MichaelHalstead: Welcome!</p>
<hr />
<div>'''Welcome to ''Yocto Project''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br />
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 21:04, 23 July 2023 (UTC)</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User:Haward01&diff=85862User:Haward012023-07-23T21:04:22Z<p>MichaelHalstead: Creating user page for new user.</p>
<hr />
<div>I learned C, C++, Bash, Linux device drivers, python in sequence, after diving in linux device drivers I assumed yocto meet linux device drivers requirements.</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User_talk:Takayasu_Ito&diff=85800User talk:Takayasu Ito2023-05-24T16:42:14Z<p>MichaelHalstead: Welcome!</p>
<hr />
<div>'''Welcome to ''Yocto Project''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br />
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 16:42, 24 May 2023 (UTC)</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User:Takayasu_Ito&diff=85799User:Takayasu Ito2023-05-24T16:42:14Z<p>MichaelHalstead: Creating user page for new user.</p>
<hr />
<div>Started embedded Linux development in 2003, since 2006 he has been an employee of Lineo Solutions Inc. mainly working on GUI/NetWork related development on the userland side.<br />
Since 2015, he has been involved in YoctoProject related support work, and since 2016, he has been a technical speaker and hands-on seminar instructor. He also participates as a primary respondent on YoctoBBQ, a QA site provided in Japanese.<br />
With these achievements, he was appointed as YoctoProject Ambassador in October 2020.<br />
Recently, he has been contributing to the documentation published by YoctoProject.</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=Hash_Equivalence_Server&diff=85794Hash Equivalence Server2023-05-18T17:40:50Z<p>MichaelHalstead: Document the public YP AB hashserv setup</p>
<hr />
<div>There are two hashserv instances running on on the Yocto Project autobuilder. The private read-write at '''hashserv.yocto.io:8686''' and the read-only public copy at '''hashserv.yocto.io:8687'''.<br />
<br />
On a VM with 7.5GB of memory and 2 vcpus we created a 150GB fast volume and mounted it at /home/hashserv. Our hashserv.db hovers at about 35GB and has gone as high as 90GB. We setup up automated snapshots for backup.<br />
<br />
Run some commands to set up a user and grab the code:<br />
adduser --system hashserv<br />
su - hashserv<br />
git clone https://git.openembedded.org/bitbake<br />
exit<br />
<br />
Copy the following to /etc/systemd/system/hashserv.service<br />
<br />
<nowiki># /etc/systemd/system/hashserv.service<br />
[Unit]<br />
Description=Bitbake Hash Server<br />
After=network.target<br />
<br />
[Service]<br />
User=hashserv<br />
WorkingDirectory=/home/hashserv<br />
Type=simple<br />
ExecStart=/usr/bin/python3 /home/hashserv/bitbake/bin/bitbake-hashserv --bind :8686<br />
<br />
[Install]<br />
WantedBy=multi-user.target</nowiki><br />
<br />
<br />
Copy the following to /etc/systemd/system/hashserv-readonly.service<br />
<nowiki># /etc/systemd/system/hashserv-readonly.service<br />
[Unit]<br />
Description=Bitbake Read-Only Hash Server<br />
After=network.target<br />
<br />
[Service]<br />
User=hashserv<br />
WorkingDirectory=/home/hashserv<br />
Type=simple<br />
ExecStart=/usr/bin/python3 /home/hashserv/bitbake/bin/bitbake-hashserv --bind :8687 --read-only<br />
<br />
[Install]<br />
WantedBy=multi-user.target</nowiki><br />
<br />
Some commands to enable and start the services:<br />
systemctl daemon-reload<br />
systemctl enable hashserv.service hashserv-readonly.service<br />
systemctl start hashserv.service hashserv-readonly.service <br />
<br />
Then we opened up the firewall for 8686/tcp to our autobuilder private network and opened 8687/tcp to the world. There is no authentication so it's important to use the correct firewall settings.</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=Releases&diff=85773Releases2023-05-03T22:24:44Z<p>MichaelHalstead: Add missing bitbake branch names</p>
<hr />
<div><!-- keywords: release names codenames versions version names numbers branches branchx --><br />
<br />
== Release Activity==<br />
<br />
Releases can be downloaded at https://www.yoctoproject.org/software-overview/downloads/<br />
<br />
{| class="wikitable" border="2"<br />
!Codename<br />
!Yocto Project Version<br />
!Release Date<br />
!Current Version<br />
!Support Level<br />
!Poky Version<br />
!BitBake branch<br />
! Maintainer<br />
|-<br />
|Nanbield <br/>(like 'man field')<br />
|4.3<br />
| October 2023<br />
|<br />
|Future - Support for 7 months (until April 2024)<br />
|N/A<br />
|2.6<br />
|Richard Purdie <richard.purdie@linuxfoundation.org><br />
|-<br />
|Mickledore<br />
|4.2<br />
| April 2023<br />
|<br />
|Future - Support for 7 months (until October 2023)<br />
|N/A<br />
|2.4<br />
|Richard Purdie <richard.purdie@linuxfoundation.org><br />
|-<br />
|Langdale<br />
|4.1<br />
| October 2022<br />
| 4.1.3 (March 2023)<br />
| Support until May 2023<br />
|N/A<br />
|2.2<br />
|Steve Sakoman <steve@sakoman.com><br />
|-<br />
|Kirkstone <br/>(like 'kirk stun')<br />
|4.0<br />
|May 2022<br />
|4.0.9 (April 2023)<br />
|Long Term Support (minimum Apr. 2024¹)<br />
|N/A<br />
|2.0<br />
|Steve Sakoman <steve@sakoman.com><br />
|-<br />
|-style="color: slategray;"<br />
|Honister<br />
|3.4<br />
|October 2021<br />
|3.4.4 (May 2022)<br />
|EOL<br />
|N/A<br />
|1.52<br />
|Anuj Mittal <anuj.mittal@intel.com><br />
|-<br />
|-style="color: slategray;"<br />
|Hardknott<br />
|3.3<br />
|April 2021<br />
|3.3.6 (April 2022)<br />
|EOL<br />
|N/A<br />
|1.50<br />
|Anuj Mittal <anuj.mittal@intel.com><br />
|-<br />
|-style="color: slategray;"<br />
|Gatesgarth<br />
|3.2<br />
|Oct 2020<br />
|3.2.4 (May 2021)<br />
|EOL<br />
|N/A<br />
|1.48<br />
|Anuj Mittal <anuj.mittal@intel.com><br />
|-<br />
|Dunfell<br />
|3.1<br />
|April 2020<br />
|3.1.24 (March 2023)<br />
|Long Term Support (until Apr. 2024¹)<br />
|23.0<br />
|1.46<br />
|Steve Sakoman <steve@sakoman.com><br />
|-style="color: slategray;"<br />
|Zeus<br />
|3.0<br />
|October 2019<br />
|3.0.4 (August 2020)<br />
|EOL<br />
|22.0.3<br />
|1.44<br />
| Anuj/Armin<br />
|-style="color: slategray;"<br />
|Warrior<br />
|2.7<br />
|April 2019<br />
|2.7.4 (June 2020)<br />
|EOL<br />
|21.0<br />
|1.42<br />
|Armin Kuster <akuster808@gmail.com><br />
|-style="color: slategray;"<br />
|Thud<br />
|2.6<br />
|Nov 2018<br />
|2.6.4 (October 2019)<br />
|EOL<br />
|20.0<br />
|1.40<br />
| Armin Kuster <akuster808@gmail.com><br />
|-style="color: slategray;"<br />
|Sumo<br />
|2.5<br />
|April 2018<br />
|2.5.3 (April 2019)<br />
|EOL<br />
|19.0<br />
|1.38<br />
| Armin Kuster <akuster808@gmail.com><br />
|-style="color: slategray;"<br />
|Rocko<br />
|2.4<br />
|Oct 2017<br />
|2.4.4 (November 2018)<br />
|EOL<br />
|18.0<br />
|1.36<br />
| Armin Kuster <akuster808@gmail.com><br />
|-style="color: slategray;"<br />
|Pyro<br />
|2.3<br />
|May 2017<br />
|2.3.4 (July 2018)<br />
|EOL<br />
|17.0<br />
|1.34<br />
| Armin Kuster <akuster808@gmail.com><br />
|-style="color: slategray;"<br />
|Morty<br />
|2.2<br />
|Nov 2016<br />
|2.2.4 (July 2018)<br />
|EOL<br />
|16.0<br />
|1.32<br />
| Armin Kuster <akuster808@gmail.com><br />
|-style="color: slategray;"<br />
|Krogoth<br />
|2.1<br />
|Apr 2016<br />
|2.1.3 (July 2017)<br />
|EOL<br />
|15.0<br />
|1.30<br />
| Armin Kuster <akuster808@gmail.com><br />
|-style="color: slategray;"<br />
|Jethro<br />
|2.0<br />
|Nov 2015<br />
|2.0.3 (January 2016)<br />
|EOL<br />
|14.0<br />
|1.28<br />
|Robert Yang <liezhi.yang@windriver.com><br />
|-style="color: slategray;"<br />
|Fido<br />
|1.8<br />
|Apr 2015<br />
|1.8.2<br />
|EOL<br />
|13.0<br />
|1.26<br />
|Joshua Lock <joshua.g.lock@intel.com><br />
|-style="color: slategray;"<br />
|Dizzy<br />
|1.7<br />
|Oct 2014<br />
|1.7.3<br />
|EOL<br />
|12.0<br />
|1.24<br />
| Armin Kuster <akuster808@gmail.com><br />
|-style="color: slategray;"<br />
|Daisy<br />
|1.6<br />
|Apr 2014<br />
|1.6.3<br />
|EOL<br />
|11.0<br />
|1.22<br />
| Saul Wold <sgw@linux.intel.com><br />
|-style="color: slategray;"<br />
|Dora<br />
|1.5<br />
|Oct 2013<br />
|1.5.4<br />
|EOL<br />
|10.0<br />
|1.20<br />
| Robert Yang <liezhi.yang@windriver.com> <br />
|-style="color: slategray;"<br />
|Dylan<br />
|1.4<br />
|Apr 2013<br />
|1.4.3<br />
|EOL<br />
|9.0<br />
|1.18<br />
| Paul Eggleton <paul.eggleton@linux.intel.com> <br />
|-style="color: slategray;"<br />
|Danny<br />
|1.3<br />
|Oct 2012<br />
|1.3.2<br />
|EOL<br />
|8.0<br />
|1.16<br />
|Ross Burton <ross.burton@intel.com> <br />
|-style="color: slategray;"<br />
|Denzil<br />
|1.2<br />
|Apr 2012<br />
|1.2.2<br />
|EOL<br />
|7.0<br />
|1.15<br />
|-style="color: slategray;"<br />
|Edison<br />
|1.1<br />
|Oct 2011<br />
|1.1.2<br />
|EOL<br />
|6.0<br />
|1.13<br />
|-style="color: slategray;"<br />
|Bernard<br />
|1.0<br />
|Apr 2011<br />
|1.0.2<br />
|EOL<br />
|5.0<br />
|1.11<br />
|-style="color: slategray;"<br />
|Laverne<br />
|0.9<br />
|Oct 2010<br />
|<br />
|<br />
|4.0<br />
|1.11<br />
|-style="color: slategray;"<br />
|Green<br />
|N/A<br />
|11 June 2010<br />
|<br />
|<br />
|3.3<br />
|<br />
|-style="color: slategray;"<br />
|Purple<br />
|N/A<br />
|15 Dec 2009<br />
|<br />
|<br />
|3.2<br />
|<br />
|-style="color: slategray;"<br />
|Pinky<br />
|N/A<br />
|12 Nov 2009<br />
|<br />
|<br />
|3.1<br />
|<br />
|-style="color: slategray;"<br />
|Blinky<br />
|N/A<br />
|1 Aug 2007<br />
|<br />
|<br />
|3.0<br />
|<br />
|-style="color: slategray;"<br />
|Clyde<br />
|N/A<br />
|19 Jan 2007<br />
|<br />
|<br />
|2.0<br />
|<br />
|-style="color: slategray;"<br />
|Inky<br />
|N/A<br />
|10 Feb 2006<br />
|<br />
|<br />
|1.0<br />
|<br />
|}<br />
<br />
'''Note:''' see also [[Stable Release and LTS]], [[Linux Yocto]], [[Planning]] and [[Release Feature Table]] pages. EOL means some community support on email lists but no commit updates in the repos. There is also OS Vendor support for some Yocto EOL releases.<br />
<br />
¹ The 3.1 series was originally planned for two years but extended to four. No decision has been made about 4.0, it would be a decision by the project members who fund it. The project in unable to commit to funding the work multiple years in advance.<br />
<br />
== Releases Links==<br />
{| class="wikitable" border="2"<br />
| align="center" style="background:#f0f0f0;"|'''Yocto Project Release'''<br />
| align="center" style="background:#f0f0f0;"|'''Code Name'''<br />
| align="center" style="background:#f0f0f0;"|'''Poky version'''<br />
| align="center" style="background:#f0f0f0;"|'''Maintainer'''<br />
| align="center" style="background:#f0f0f0;"|'''Features'''<br />
| align="center" style="background:#f0f0f0;"|'''Schedule'''<br />
| align="center" style="background:#f0f0f0;"|'''Status'''<br />
| align="center" style="background:#f0f0f0;"|'''QA Test Plan'''<br />
| align="center" style="background:#f0f0f0;"|'''QA Test Report'''<br />
| align="center" style="background:#f0f0f0;"|'''Release notes'''<br />
<br />
|-valign="top"<br />
| Yocto Project 3.4<br />
| Honister<br />
| 26.0<br />
| Anuj Mittal<br />
| [[Yocto_3.4_Features]]<br />
| [[Yocto_3.4_Schedule]]<br />
| [[Yocto_Project_v3.4_Status]]<br />
| [[Yocto_Project_3.4_Release_Test_Plan | Yocto_3.4_Overall_Test_Plan]]<br />
| [[Yocto_Project_3.4_Release_Test_Plan#Execution_History | 3.4 qa run history]]<br />
| [https://lists.yoctoproject.org/g/yocto-announce/message/229 3.4 release notes]<br />
|-<br />
| Yocto Project 3.3<br />
| Hardknott<br />
| 25.0<br />
| Anuj Mittal<br />
| [[Yocto_3.3_Features]]<br />
| [[Yocto_3.3_Schedule]]<br />
| [[Yocto_Project_v3.3_Status]]<br />
| [[Yocto_Project_3.3_Release_Test_Plan | Yocto_3.3_Overall_Test_Plan]]<br />
| [[Yocto_Project_3.3_Release_Test_Plan#Execution_History | 3.3 qa run history]]<br />
| [https://lists.yoctoproject.org/g/yocto-announce/message/215 3.3 release notes]<br />
|-<br />
| Yocto Project 3.2<br />
| Gatesgarth<br />
| 24.0<br />
| Anuj Mittal<br />
| [[Yocto_3.2_Features]]<br />
| [[Yocto_3.2_Schedule]]<br />
| [[Yocto_Project_v3.2_Status]]<br />
| [[Yocto_Project_3.2_Release_Test_Plan | Yocto_3.2_Overall_Test_Plan]]<br />
| [[Yocto_Project_3.2_Release_Test_Plan#Execution_History | 3.2 qa run history]]<br />
| [https://lists.yoctoproject.org/g/yocto/message/51262 3.2 release notes]<br />
|-<br />
|-valign="top"<br />
| Yocto Project 3.1<br />
| Dunfell<br />
| 23.0<br />
| Steve Sakoman<br />
| [[Yocto_3.1_Features]]<br />
| [[Yocto_3.1_Schedule]]<br />
| [[Yocto_Project_v3.1_Status]]<br />
| [[Yocto_Project_3.1_Release_Test_Plan | Yocto_3.1_Overall_Test_Plan]]<br />
| [[Yocto_Project_3.1_Release_Test_Plan#Execution_History | 3.1 qa run history]]<br />
| [https://lists.yoctoproject.org/g/yocto/message/49201 3.1 release notes]<br />
|-<br />
<br />
|-valign="top"<br />
| Yocto Project 3.0<br />
| Zeus<br />
| 22.0<br />
| Armin Kuster/Anuj Mittal<br />
| [[Yocto_2.8_Features]]<br />
| [[Yocto_2.8_Schedule]]<br />
| [[Yocto_Project_v2.8_Status]]<br />
| [[Yocto_Project_2.8_Release_Test_Plan | Yocto_2.8_Overall_Test_Plan]]<br />
| [[Yocto_Project_2.8_Release_Test_Plan#Execution_History | 2.8 qa run history]]<br />
| [https://lists.yoctoproject.org/pipermail/yocto/2019-October/047111.html 3.0 release notes]<br />
|-<br />
|-valign="top"<br />
| Yocto Project 2.7<br />
| Warrior<br />
| 21.0<br />
| Community<br />
| [[Yocto_2.7_Features]]<br />
| [[Yocto_2.7_Schedule]]<br />
| [[Yocto_Project_v2.7_Status]]<br />
| [[Yocto_Project_2.7_Release_Test_Plan | Yocto_2.7_Overall_Test_Plan]]<br />
| [[Yocto_Project_2.7_Release_Test_Plan#Execution_History | 2.7 qa run history]]<br />
| [https://lists.yoctoproject.org/pipermail/yocto/2019-May/045028.html 2.7 release notes]<br />
|-<br />
|-valign="top"<br />
| Yocto Project 2.6<br />
| Thud<br />
| 20.0<br />
| Community<br />
| [[Yocto_2.6_Features]]<br />
| [[Yocto_2.6_Schedule]]<br />
| [[Yocto_Project_v2.6_Status]]<br />
| [[Yocto_Project_2.6_Release_Test_Plan | Yocto_2.6_Overall_Test_Plan]]<br />
| [[Yocto_Project_2.6_Release_Test_Plan#Execution_History | 2.6 qa run history]]<br />
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2018-November/000147.html 2.6 release notes]<br />
|-<br />
|-valign="top"<br />
| Yocto Project 2.5<br />
| Sumo<br />
| 19.0<br />
| Community<br />
| [[Yocto_2.5_Features]]<br />
| [[Yocto_2.5_Schedule]]<br />
| [[Yocto_Project_v2.5_Status]]<br />
| [[Yocto_Project_2.5_Release_Test_Plan | Yocto_2.5_Overall_Test_Plan]]<br />
| [[Yocto_Project_2.5_Release_Test_Plan#Execution_History | 2.5 qa run history]]<br />
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2018-May/000136.html 2.5 release notes]<br />
|-<br />
|-valign="top"<br />
| Yocto Project 2.4<br />
| Rocko<br />
| 18.0<br />
| Community<br />
| [[Yocto_2.4_Features]]<br />
| [[Yocto_2.4_Schedule]]<br />
| [[Yocto_Project_v2.4_Status]]<br />
| [[Yocto_Project_2.4_Release_Test_Plan | Yocto_2.4_Overall_Test_Plan]]<br />
| [[Yocto_Project_2.4_Release_Test_Plan#Execution_History | 2.4 qa run history]]<br />
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2017-October/000125.html 2.4 release notes]<br />
|-<br />
|-valign="top"<br />
| Yocto Project 2.3<br />
| Pyro<br />
| 17.0<br />
| Community<br />
| [[Yocto_2.3_Features]]<br />
| [[Yocto_2.3_Schedule]]<br />
| [[Yocto_Project_v2.3_Status]]<br />
| [[Yocto_Project_2.3_Release_Test_Plan | Yocto_2.3_Overall_Test_Plan]]<br />
| [[Yocto_Project_2.3_Release_Test_Plan#Execution_History | 2.3 qa run history]]<br />
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2017-May/000112.html 2.3 release notes]<br />
|-<br />
|-valign="top"<br />
| Yocto Project 2.2<br />
| Morty<br />
| 16.0<br />
| Community<br />
| [[Yocto_2.2_Features]]<br />
| [[Yocto_2.2_Schedule]]<br />
| [[Yocto_Project_v2.2_Status]]<br />
| [[Yocto_2.2_Overall_Test_Plan]]<br />
| [[Yocto_Project_2.2_Release_Test_Plan#Execution_History | 2.2 qa run history]]<br />
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2016-November/000101.html 2.2 release notes]<br />
|-<br />
|-valign="top"<br />
| Yocto Project 2.1<br />
| Krogoth<br />
| 15.0<br />
| Community<br />
| [[Yocto_2.1_Features]]<br />
| [[Yocto_2.1_Schedule]]<br />
| [[Yocto_Project_v2.1_Status]]<br />
| [[Yocto_2.1_Overall_Test_Plan]]<br />
| [[2.1 qa run history]] <br />
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2016-May/000089.html 2.1 release notes]<br />
|-<br />
|-valign="top"<br />
| Yocto Project 2.0<br />
| Jethro<br />
| 14.0<br />
| Community<br />
| [[Yocto_1.9_Features]]<br />
| [[Yocto_1.9_Schedule]]<br />
| [[Yocto_Project_v1.9_Status]]<br />
| <br />
| [[1.9 qa run history]] <br />
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2015-November/000076.html 2.0 release notes]<br />
|-valign="top"<br />
| Yocto Project 1.8<br />
| Fido<br />
| 13.0<br />
| Community<br />
| [[Yocto_1.8_Features]]<br />
| [[Yocto_1.8_Schedule]]<br />
| [[Yocto_Project_v1.8_Status]]<br />
| [[Yocto_1.8_Overall_Test_Plan]]<br />
| [[1.8 qa run history]] <br />
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2015-April/000062.html 1.8 release notes]<br />
|-<br />
| Yocto Project 1.7<br />
| Dizzy<br />
| 12.0<br />
| Community<br />
| [[Yocto_1.7_Features]]<br />
| [[Yocto_1.7_Schedule]]<br />
| [[Yocto_Project_v1.7_Status]]<br />
| [[Yocto_1.7_Overall_Test_Plan]]<br />
| [[1.7 qa run history]]<br />
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2014-October/000053.html 1.7 release notes]<br />
|-<br />
| Yocto Project 1.6<br />
| Daisy<br />
| 11.0<br />
| Community<br />
| [[Yocto_1.6_Features]]<br />
| [[Yocto_1.6_Schedule]]<br />
| [[Yocto_Project_v1.6_Status]]<br />
| [[Yocto_1.6_Overall_Test_Plan]]<br />
| [[1.6 qa run history]]<br />
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2014-April/000045.html 1.6 release notes]<br />
|-<br />
| Yocto Project 1.5<br />
| Dora<br />
| 10.0<br />
| Community<br />
| [[Yocto_1.5_Features]]<br />
| [[Yocto_1.5_Schedule]]<br />
| [[Yocto_Project_v1.5_Status]]<br />
| [[Yocto_1.5_Overall_Test_Plan]]<br />
| [[1.5 qa run history]]<br />
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2013-October/000037.html 1.5 release notes]<br />
|-<br />
| Yocto Project 1.4<br />
| Dylan<br />
| 9.0<br />
| Community<br />
| [[Yocto_1.4_Features]]<br />
| [[Yocto_1.4_Schedule]]<br />
| [[Yocto_Project_v1.4_Status]]<br />
| [[Yocto_1.4_Overall_Test_Plan]]<br />
| [[Yocto_1.4_Milestone_Test_Report]]<br />
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2013-April/000027.html 1.4 release notes]<br />
|-<br />
| Yocto Project 1.3<br />
| Danny<br />
| 8.0<br />
| Community<br />
| [[Yocto_1.3_Features]]<br />
| [[Yocto_1.3_Schedule]]<br />
| [[Yocto_Project_v1.3_Status]]<br />
| [[Yocto_1.3_Overall_Test_Plan]]<br />
| [[Yocto_1.3_Milestone_Test_Report]]<br />
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2012-October/000020.html 1.3 release notes]<br />
|-<br />
| Yocto Project 1.2<br />
| Denzil<br />
| 7.0<br />
| Community<br />
| [[Yocto_1.2_Features]]<br />
| [[Yocto_1.2_Schedule]]<br />
| [[Yocto_Project_v1.2_Status]]<br />
| [[Yocto_1.2_Overall_Test_Plan]]<br />
| [[Yocto_1.2_Milestone_Test_Report]]<br />
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2012-April/000009.html 1.2 release notes]<br />
|-<br />
| Yocto Project 1.1<br />
| Edison<br />
| 6.0<br />
| Community<br />
| [[Yocto_1.1_Features]]<br />
| [[Yocto_1.1_Schedule]]<br />
| [[Yocto_Project_v1.1_Release_Criteria]]<br />
| [[Yocto_1.1_Overall_Test_Plan]]<br />
| [[Yocto_1.1_Milestone_Test_Report]]<br />
|<br />
|-<br />
| Yocto Project 1.0<br />
| Bernard<br />
| 5.0<br />
| Community<br />
| [[Yocto_Features]]<br />
| [[Yocto_1.0_Schedule]]<br />
| [[Yocto_Project_v1.0_Release_Criteria]]<br />
| [[Yocto_1.0_Overall_Test_Plan]]<br />
| <br />
|<br />
|}</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User_talk:TheYoctoJester&diff=85766User talk:TheYoctoJester2023-04-26T16:02:46Z<p>MichaelHalstead: Welcome!</p>
<hr />
<div>'''Welcome to ''Yocto Project''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br />
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 16:02, 26 April 2023 (UTC)</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User:TheYoctoJester&diff=85765User:TheYoctoJester2023-04-26T16:02:46Z<p>MichaelHalstead: Creating user page for new user.</p>
<hr />
<div>Josef has been active for more than 15 years as a "Complete"-Stack developer for industrial controls by now. He's done everything from debugging hardware to writing drivers, from application development to web front ends.<br />
<br />
A passion for showing, telling, and teaching people in both entertaining and engaging ways led Josef to Mender.io. Here, he tries to make the world better and more secure by enabling OTA updates for as many devices as possible.<br />
Taking this passion, combining it with a keen interest in building systems and how they can be brought to the next generation of developers, Josef has been awarded Yocto Project Ambassador status.<br />
<br />
As such, Josef has also reached many thousands of aspiring developers not only through his presentations at various events and conferences but also by livecoding sessions and webinars.<br />
<br />
Josef holds a degree in Electrical Engineering / Computer Science from the University of Applied Sciences, Ingolstadt.</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=Project_Users&diff=85738Project Users2023-04-06T16:28:36Z<p>MichaelHalstead: /* Others */</p>
<hr />
<div>It's hard to know which companies or projects use the Yocto Project since there is no requirement to tell us. This list is here to informally collate the companies, projects and products that use the Yocto Project in some way. This helps the project since it means we can show at least some cross section of which companies are using it and how/where. There is more information about this here: https://lists.yoctoproject.org/g/yocto/topic/82722441<br />
<br />
= Companies using the Yocto Project =<br />
<br />
== Semiconductor Vendors ==<br />
* AMD (Silver Member)<br />
* ARM (Platinum Member)<br />
* Intel (Platinum Member)<br />
* Microchip<br />
* NXP (Silver Member)<br />
* Qualcomm<br />
* Renesas (Gold Member)<br />
* STMicroelectronics (Silver Member)<br />
* Texas Instruments (Gold Member)<br />
* Xilinx (Platinum Member)<br />
<br />
== Operating System Vendors ==<br />
* ENEA (Silver Member)<br />
* Linaro (Silver Member)<br />
* Lineo (Silver Member)<br />
* Mentor Graphics (Gold Member)<br />
* Microsoft (Platinum Member)<br />
* Montavista (Silver Member)<br />
* Wind River (Gold Member)<br />
<br />
== Others ==<br />
* [https://3mdeb.com/ 3mdeb]<br />
* [https://alladin.at/ alladin-IT GmbH]<br />
* [https://www.ambu.com/ Ambu] (Endoscope video devices)<br />
* [https://www.arthrex.co.uk/ Arthrex] (Surgical video products)<br />
* Atlas Copco<br />
* AWS (Platinum Member)<br />
* [https://www.axis.com/ Axis Communications] (Silver Member)<br />
* [https://www.balena.io/ Balena]<br />
* [https://www.brose.com/ Brose]<br />
* BMW<br />
* BMW Car IT<br />
* [https://www.brightsign.biz/ BrightSign]<br />
* [https://www.bruker.com/ Bruker BioSpin GmbH]<br />
* [https://bootlin.com/ Bootlin]<br />
* Cisco (Platinum Member)<br />
* CNH Industrial<br />
* Comcast (Platinum Member)<br />
* [https://www.cytera.bio/ Cytera] (via Belena)<br />
* Dell (Silver Member)<br />
* [https://www.denx.de/ DENX Software Engineering]<br />
* Dynamic Devices<br />
* [https://www.ericsson.com Ericsson]<br />
* Facebook (Platinum Member)<br />
* [https://formlabs.com/ Formlabs]<br />
* Fujitsu<br />
* [https://www.gardena.com/ GARDENA] (Husqvarna Group)<br />
* [https://www.garmin.com/ Garmin]<br />
* General Electric<br />
* [https://genielifesciences.com/ Genie Life Sciences]<br />
* Gigaset Communications GmbH <br />
* [https://hillrom.com Hillrom]<br />
* [https://www.hanoverdisplays.com/ Hanover]<br />
* Juniper<br />
* [https://koansoftware.com/ KOAN sas]<br />
* Kodak<br />
* [https://www.korg.com/ Korg]<br />
* [https://lawo.com/ LAWO]<br />
* Lexmark<br />
* LG (Silver Member)<br />
* [https://lightyear.one/ Lightyear]<br />
* National Instruments<br />
* [https://www.ovo.auto/ OVO Automotive]<br />
* [https://www.pengutronix.de/ Pengutronix]<br />
* reMarkable<br />
* [https://www.rethinkrobotics.com/ Rethink Robotics GmbH]<br />
* [https://www.siemens.com/ Siemens] (Gold Member)<br />
* [https://www.smile.eu/en/offers/embedded-iot Smile ECS]<br />
* StreamUnlimited Engineering GmbH<br />
* [https://www.taitradio.com Tait Communications]<br />
* [https://www.witekio.com/values-expertise/ Witekio]<br />
* [https://www.veobot.com/ Veo Robotics]<br />
<br />
= Products that use the Yocto Project =<br />
<br />
* Amazon Eero<br />
* Ambu aview2 and abox2 <br />
* BMW cars<br />
* [https://www.cambridgeaudio.com/ Cambridge Audio] network streamers<br />
* Comcast set top boxes<br />
* [https://dasharo.com/ Dasharo]<br />
* [https://www.gardena.com/int/products/smart/ GARDENA smart garden] (The smart garden gateway runs Yocto/OpenEmbedded. Open source parts can be found [https://github.com/husqvarnagroup/smart-garden-gateway-public on GitHub.])<br />
* Some Garmin [https://www.garmin.com/marine/ Marine] Products<br />
* Gigaset DSPG-SOCs based products (e.g N870, N870 Integrator, Marine 2/3/4)<br />
* Go Pro (https://gopro.com/content/dam/help/open-source/2020-09-28%20-%20HERO9%20Black%20-GoPro%20Open%20Source%20Software%20Notice.pdf)<br />
* Ikea Smart Hub<br />
* [https://www.korg.com/uk/products/synthesizers/wavestate/ Korg Wavestate Synthesizer]<br />
* LAWO [https://lawo.com/products/a__uhd-core/ A__UHD Core] [https://lawo.com/products/a__line/ A__ Line]<br />
* Lexmark Printers<br />
* LG webOS TVs<br />
* Lightyear 0 solar EV (Telematics Control Unit)<br />
* Mellanox Bluefield SmartNIC<br />
* [https://new.siemens.com/global/en/products/buildings.html Siemens Smart Infrastructure]: Products for sustainable, efficient and safe buildings<br />
* Sky Glass (clear from sources tarball [http://oss.sky.com/SkyHD/SkyGlass/skyglass_spk.tar.bz2])<br />
* [https://www.streamunlimited.com/hardware-modules/ StreamUnlimited hardware modules for voice assistants and connected speakers]<br />
* Vernier LabQuest<br />
<br />
= Projects that use the Yocto Project =<br />
<br />
* [https://asteroidos.org/ AsteroidOS]<br />
* [https://www.automotivelinux.org/ Automotive Grade Linux (AGL)]<br />
* [https://www.balena.io/ Balena]<br />
* Comcast RDK<br />
* [https://easyos.org/ EasyOS]<br />
* [https://github.com/oe-alliance Various Enigma2 based set-top boxes]<br />
* [https://www.webos-ports.org LuneOS]<br />
* Nvidia vibrante SDK [https://docs.nvidia.com/drive/archive/4.1.8.0L/nvoss_docs/index.html]<br />
* OpenBMC<br />
* [https://oryx-linux.org/ Oryx Linux]<br />
* [https://github.com/riscv/meta-riscv RISC-V]<br />
* [https://www.streamunlimited.com/stream-sdk/ StreamSDK for voice assistants and connected speakers]<br />
* Windows Subsystem Linux (v1+v2)<br />
* webOS<br />
* [https://www.webosose.org/ webOS OSE (Open Source Edition)]<br />
* [http://yoedistro.org The Yoe Distribution]</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=Project_Users&diff=85737Project Users2023-04-06T16:27:49Z<p>MichaelHalstead: /* Others */ adding hanoverdisplays to project users</p>
<hr />
<div>It's hard to know which companies or projects use the Yocto Project since there is no requirement to tell us. This list is here to informally collate the companies, projects and products that use the Yocto Project in some way. This helps the project since it means we can show at least some cross section of which companies are using it and how/where. There is more information about this here: https://lists.yoctoproject.org/g/yocto/topic/82722441<br />
<br />
= Companies using the Yocto Project =<br />
<br />
== Semiconductor Vendors ==<br />
* AMD (Silver Member)<br />
* ARM (Platinum Member)<br />
* Intel (Platinum Member)<br />
* Microchip<br />
* NXP (Silver Member)<br />
* Qualcomm<br />
* Renesas (Gold Member)<br />
* STMicroelectronics (Silver Member)<br />
* Texas Instruments (Gold Member)<br />
* Xilinx (Platinum Member)<br />
<br />
== Operating System Vendors ==<br />
* ENEA (Silver Member)<br />
* Linaro (Silver Member)<br />
* Lineo (Silver Member)<br />
* Mentor Graphics (Gold Member)<br />
* Microsoft (Platinum Member)<br />
* Montavista (Silver Member)<br />
* Wind River (Gold Member)<br />
<br />
== Others ==<br />
* [https://3mdeb.com/ 3mdeb]<br />
* [https://alladin.at/ alladin-IT GmbH]<br />
* [https://www.ambu.com/ Ambu] (Endoscope video devices)<br />
* [https://www.arthrex.co.uk/ Arthrex] (Surgical video products)<br />
* Atlas Copco<br />
* AWS (Platinum Member)<br />
* [https://www.axis.com/ Axis Communications] (Silver Member)<br />
* [https://www.balena.io/ Balena]<br />
* [https://www.brose.com/ Brose]<br />
* BMW<br />
* BMW Car IT<br />
* [https://www.brightsign.biz/ BrightSign]<br />
* [https://www.bruker.com/ Bruker BioSpin GmbH]<br />
* [https://bootlin.com/ Bootlin]<br />
* Cisco (Platinum Member)<br />
* CNH Industrial<br />
* Comcast (Platinum Member)<br />
* [https://www.cytera.bio/ Cytera] (via Belena)<br />
* Dell (Silver Member)<br />
* [https://www.denx.de/ DENX Software Engineering]<br />
* Dynamic Devices<br />
* [https://www.ericsson.com Ericsson]<br />
* Facebook (Platinum Member)<br />
* [https://formlabs.com/ Formlabs]<br />
* Fujitsu<br />
* [https://www.gardena.com/ GARDENA] (Husqvarna Group)<br />
* [https://www.garmin.com/ Garmin]<br />
* General Electric<br />
* [https://genielifesciences.com/ Genie Life Sciences]<br />
* Gigaset Communications GmbH <br />
* [https://hillrom.com Hillrom]<br />
* [https://www.hanoverdisplays.com/]<br />
* Juniper<br />
* [https://koansoftware.com/ KOAN sas]<br />
* Kodak<br />
* [https://www.korg.com/ Korg]<br />
* [https://lawo.com/ LAWO]<br />
* Lexmark<br />
* LG (Silver Member)<br />
* [https://lightyear.one/ Lightyear]<br />
* National Instruments<br />
* [https://www.ovo.auto/ OVO Automotive]<br />
* [https://www.pengutronix.de/ Pengutronix]<br />
* reMarkable<br />
* [https://www.rethinkrobotics.com/ Rethink Robotics GmbH]<br />
* [https://www.siemens.com/ Siemens] (Gold Member)<br />
* [https://www.smile.eu/en/offers/embedded-iot Smile ECS]<br />
* StreamUnlimited Engineering GmbH<br />
* [https://www.taitradio.com Tait Communications]<br />
* [https://www.witekio.com/values-expertise/ Witekio]<br />
* [https://www.veobot.com/ Veo Robotics]<br />
<br />
= Products that use the Yocto Project =<br />
<br />
* Amazon Eero<br />
* Ambu aview2 and abox2 <br />
* BMW cars<br />
* [https://www.cambridgeaudio.com/ Cambridge Audio] network streamers<br />
* Comcast set top boxes<br />
* [https://dasharo.com/ Dasharo]<br />
* [https://www.gardena.com/int/products/smart/ GARDENA smart garden] (The smart garden gateway runs Yocto/OpenEmbedded. Open source parts can be found [https://github.com/husqvarnagroup/smart-garden-gateway-public on GitHub.])<br />
* Some Garmin [https://www.garmin.com/marine/ Marine] Products<br />
* Gigaset DSPG-SOCs based products (e.g N870, N870 Integrator, Marine 2/3/4)<br />
* Go Pro (https://gopro.com/content/dam/help/open-source/2020-09-28%20-%20HERO9%20Black%20-GoPro%20Open%20Source%20Software%20Notice.pdf)<br />
* Ikea Smart Hub<br />
* [https://www.korg.com/uk/products/synthesizers/wavestate/ Korg Wavestate Synthesizer]<br />
* LAWO [https://lawo.com/products/a__uhd-core/ A__UHD Core] [https://lawo.com/products/a__line/ A__ Line]<br />
* Lexmark Printers<br />
* LG webOS TVs<br />
* Lightyear 0 solar EV (Telematics Control Unit)<br />
* Mellanox Bluefield SmartNIC<br />
* [https://new.siemens.com/global/en/products/buildings.html Siemens Smart Infrastructure]: Products for sustainable, efficient and safe buildings<br />
* Sky Glass (clear from sources tarball [http://oss.sky.com/SkyHD/SkyGlass/skyglass_spk.tar.bz2])<br />
* [https://www.streamunlimited.com/hardware-modules/ StreamUnlimited hardware modules for voice assistants and connected speakers]<br />
* Vernier LabQuest<br />
<br />
= Projects that use the Yocto Project =<br />
<br />
* [https://asteroidos.org/ AsteroidOS]<br />
* [https://www.automotivelinux.org/ Automotive Grade Linux (AGL)]<br />
* [https://www.balena.io/ Balena]<br />
* Comcast RDK<br />
* [https://easyos.org/ EasyOS]<br />
* [https://github.com/oe-alliance Various Enigma2 based set-top boxes]<br />
* [https://www.webos-ports.org LuneOS]<br />
* Nvidia vibrante SDK [https://docs.nvidia.com/drive/archive/4.1.8.0L/nvoss_docs/index.html]<br />
* OpenBMC<br />
* [https://oryx-linux.org/ Oryx Linux]<br />
* [https://github.com/riscv/meta-riscv RISC-V]<br />
* [https://www.streamunlimited.com/stream-sdk/ StreamSDK for voice assistants and connected speakers]<br />
* Windows Subsystem Linux (v1+v2)<br />
* webOS<br />
* [https://www.webosose.org/ webOS OSE (Open Source Edition)]<br />
* [http://yoedistro.org The Yoe Distribution]</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User_talk:Mathad&diff=85736User talk:Mathad2023-04-06T16:24:56Z<p>MichaelHalstead: Welcome!</p>
<hr />
<div>'''Welcome to ''Yocto Project''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br />
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 16:24, 6 April 2023 (UTC)</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User:Mathad&diff=85735User:Mathad2023-04-06T16:24:56Z<p>MichaelHalstead: Creating user page for new user.</p>
<hr />
<div>Hi there,<br />
<br />
I am an embedded system engineer, I started to work on embedded Linux in 2012, then I worked on Android products for 4 years and since 2016 I work on the Yocto Project.<br />
<br />
My company Hanover Displays uses the Yocto Project for several of our products, and we have a full Operating Systems environment like Comissiong OS, Recovery OS, and Main OS all based on embedded Linux kernel.</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=Accessing_Autobuilders&diff=85729Accessing Autobuilders2023-04-04T16:25:54Z<p>MichaelHalstead: Update to modern key lengths/types</p>
<hr />
<div>==Connecting to Autobuilders==<br />
We use an ssh jumphost called access.yoctoproject.org/access.yocto.io to connect to the autobuilders. Jumphosts enhance security by removing the threat of hijacked ssh-agents and limiting the services running on Internet exposed hosts.<br />
<br />
===Generate keys===<br />
In order to access any of the autobuilders your ssh public keys must first be installed. The preferred key type is ECC. RSA with 4096 bits is also acceptable. Please put your e-mail, the date of generation, and the host the key lives on in the comment. Please set a passphrase even if it's a simple one! Ideally your private key will never leave the host it is generated on - so if you have multiple machines please generate multiple keys. E-mail your '''public''' key named ~/.ssh/id_ed25519.pub or id_rsa.pub to helpdesk@yoctoproject.org. Keep id_ed25519 or id_rsa(the private key) super safe. Please never share it with anyone or copy it onto the Internet. Don't e-mail it to yourself either.<br />
<br />
ssh-keygen -t ed25519 -C "your_email@example.com_2012-05-30_localhostname"<br />
<br />
Substitute your own e-mail and your computer's hostname in the command above. Setting these helps with troubleshooting in the future.<br />
<br />
===Configure ssh===<br />
Edit ~/.ssh/config on your local machine and add:<br />
<br />
Host access.yoctoproject.org<br />
# Make sure your username matches your account on the autobuilder<br />
#User [username]<br />
# Give the full path to the proper public key if needed<br />
#IdentityFile /home/[username]/.ssh/id_rsa<br />
# If your network requires you to use a SOCKS proxy enable it here<br />
# ProxyCommand nc -X5 -x [proxyserver.address.company.com:1080] %h %p<br />
# If your system uses 'ncat', rather than 'netcat', use these options to enable a SOCKS proxy<br />
# ProxyCommand nc --proxy-type socks5 --proxy [proxyserver.address.company.com:1080] %h %p<br />
<br />
# *.yocto.io except for access is internal. Proxy through the bastion. <br />
Host !access.yocto.io *.yocto.io<br />
ProxyJump access.yoctoproject.org<br />
# Correct username and key repeated from above.<br />
#User [username]<br />
#IdentityFile /home/[username]/.ssh/id_rsa<br />
# We don't need strict checking on the private network.<br />
StrictHostKeyChecking no<br />
VisualHostKey no<br />
# Don't bother saving hostkeys we don't check<br />
UserKnownHostsFile /dev/null<br />
<br />
===Verify Fingerprints===<br />
Now actually ssh to access.yoctoproject.org and verify that the fingerprint you receive matches a fingerprint below.<br />
<br />
access.yocto.io<br />
256 SHA256:d3eQ8azExpEKfcJExpUSpgw9D7gZgVDZ6gl4Bt5r6cQ (ED25519)<br />
256 SHA256:jKW/rkm3+bNdtJ5CepVyHsxnbY8T78hk7lLwB0or0uA (ECDSA)<br />
2048 SHA256:Qpvu4aUBox4eaYTeneRx5zMjwKTsZrJnn5VS9N5w+Fo (RSA)<br />
<br />
===Connect!===<br />
Now that you've added access.yoctoproject.org to your known hosts you don't need to worry about fingerprints anymore. Time to connect to a builder. Run:<br />
ssh centos8-ty-1.yocto.io<br />
<br />
If all worked correctly you are now logged in. Build workers are [https://autobuilder.yoctoproject.org/typhoon/#/workers listed on the controller]. Append .yocto.io to the name to ssh.<br />
<br />
===Need to work on the build scripts?===<br />
If you are on the SWAT team you can access pokybuild using this sudo command:<br />
sudo -iu pokybuild<br />
<br />
<br />
keywords: ssh access auto builder accessing autobuilders</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User_talk:Jaekyu.lee&diff=85709User talk:Jaekyu.lee2023-03-17T16:55:23Z<p>MichaelHalstead: Welcome!</p>
<hr />
<div>'''Welcome to ''Yocto Project''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br />
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 16:55, 17 March 2023 (UTC)</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User:Jaekyu.lee&diff=85708User:Jaekyu.lee2023-03-17T16:55:23Z<p>MichaelHalstead: Creating user page for new user.</p>
<hr />
<div>SCM Engineer,Yocto newbie.<br />
Working in LGE</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User_talk:RedTentTest&diff=85690User talk:RedTentTest2023-03-15T09:25:17Z<p>MichaelHalstead: Welcome!</p>
<hr />
<div>'''Welcome to ''Yocto Project''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br />
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 09:25, 15 March 2023 (UTC)</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User:RedTentTest&diff=85689User:RedTentTest2023-03-15T09:25:17Z<p>MichaelHalstead: Creating user page for new user.</p>
<hr />
<div>Yocto Project test account. I need to check email.</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Release_Engineering&diff=85687Yocto Release Engineering2023-03-15T05:47:37Z<p>MichaelHalstead: </p>
<hr />
<div>== Yocto Project Release Engineering ==<br />
<br />
Welcome to Yocto Project Release Engineering.<br />
<br />
=== Processes ===<br />
<br />
* [[Yocto Project Release Process]]<br />
* [[Yocto Project Release Checklist]]<br />
* [[Uninative Release Process]]<br />
* [[Third_Party_BSP_Release_Process | Third Party BSP Release Guidelines]]<br />
<br />
=== Conventions ===<br />
<br />
* [[Yocto Project Tagging Conventions]]<br />
* [[Yocto Project Branch Conventions]]<br />
<br />
=== Resources ===<br />
<br />
* [[The Yocto Autobuilder]]<br />
* [[Frequently Asked Release Engineering Questions]]<br />
* [[Frequently Asked Yocto Autobuilder Questions]]<br />
<br />
=== Best Known Methods ===<br />
<br />
* [[BKM: Packaging a BSP for Release]]<br />
* [[BKM: Releasing a source archive]]<br />
<br />
=== Release Engineering Team ===<br />
<br />
The Yocto Project's Release Engineering Team is comprised of Chee Yang Lee and Michael Halstead.</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User_talk:Sriram_Giridharan&diff=85669User talk:Sriram Giridharan2023-02-27T15:14:09Z<p>MichaelHalstead: Welcome!</p>
<hr />
<div>'''Welcome to ''Yocto Project''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [[Help:Contents|help pages]].<br />
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 15:14, 27 February 2023 (UTC)</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User:Sriram_Giridharan&diff=85668User:Sriram Giridharan2023-02-27T15:14:09Z<p>MichaelHalstead: Creating user page for new user.</p>
<hr />
<div>Hi, <br />
<br />
I work with toaster in yocto project as part of my responsibilities. I would like to post an issue with toaster build, possibly discuss the issue.</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User_talk:Richard_Elberger&diff=85667User talk:Richard Elberger2023-02-27T15:13:56Z<p>MichaelHalstead: Welcome!</p>
<hr />
<div>'''Welcome to ''Yocto Project''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [[Help:Contents|help pages]].<br />
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 15:13, 27 February 2023 (UTC)</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User:Richard_Elberger&diff=85666User:Richard Elberger2023-02-27T15:13:56Z<p>MichaelHalstead: Creating user page for new user.</p>
<hr />
<div>https://www.linkedin.com/in/richardelberger/</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User_talk:Adrian_Freihofer&diff=85639User talk:Adrian Freihofer2023-02-03T17:19:04Z<p>MichaelHalstead: Welcome!</p>
<hr />
<div>'''Welcome to ''Yocto Project''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [[Help:Contents|help pages]].<br />
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 17:19, 3 February 2023 (UTC)</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User:Adrian_Freihofer&diff=85638User:Adrian Freihofer2023-02-03T17:19:04Z<p>MichaelHalstead: Creating user page for new user.</p>
<hr />
<div>E-Mail: adrian.freihofer@siemens.com</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User_talk:Jae_Yeong_Shim&diff=85637User talk:Jae Yeong Shim2023-02-03T17:18:46Z<p>MichaelHalstead: Welcome!</p>
<hr />
<div>'''Welcome to ''Yocto Project''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [[Help:Contents|help pages]].<br />
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 17:18, 3 February 2023 (UTC)</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User:Jae_Yeong_Shim&diff=85636User:Jae Yeong Shim2023-02-03T17:18:46Z<p>MichaelHalstead: Creating user page for new user.</p>
<hr />
<div>I'm now working on Embedded AI processor<br />
Don't know how to use Yocto or kernel building, so here for studying and getting in to projects</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User_talk:Giorgio_Duni&diff=85635User talk:Giorgio Duni2023-02-03T17:18:32Z<p>MichaelHalstead: Welcome!</p>
<hr />
<div>'''Welcome to ''Yocto Project''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [[Help:Contents|help pages]].<br />
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 17:18, 3 February 2023 (UTC)</div>MichaelHalsteadhttps://wiki.yoctoproject.org/wiki/index.php?title=User:Giorgio_Duni&diff=85634User:Giorgio Duni2023-02-03T17:18:32Z<p>MichaelHalstead: Creating user page for new user.</p>
<hr />
<div>Product Manager, HW, SW, FW developer</div>MichaelHalstead