Overview This repository contains the port of Yocto Linux to Axxia.

Branches Some branches are duplicates of the branches with the same name from the Yocto Linux branch at git://git.yoctoproject.org/linux-yocto-3.10. Those branches are • • • • •

master standard/base standard/preemp-rt/base standard/axxia/base standard/preempt-rt/axxia/base

The following local development branches contain commits that have not yet been accepted by the Yocto project. • standard/axxia-dev/base • standard/preempt-rt/axxia-dev/base Note that prior to the 8.8.1.56 release, axxia-dev was lsi (standard/lsi/base etc.). Also, tags prior to the 8.8.1.56 release were of the form lsi_axxia_linux_A.B.C.D on standard/lsi/base and lsi_axxia_preempt-rt_A.B.C.D. Occasionally, some of the branches get renamed or recreated to clean up the commit history. This makes it impossible to update clones. When this happens, existing clones can no longer be used. An attempt is made to communicate this, but because there is no connection between clones and the repository, it is not possible to be sure everyone gets notified. If ‘git pull’ fails, try a fresh clone. The original branch is saved in case commit history etc. is needed. Here are the changes and the names of the saved branches. For releases through 8.8.1.3, use standard/lsi/base_8.8.1.3 or standard/preempt-rt/lsi/base_8.8.1.3 For releases after 8.8.1.3 through 8.8.1.5, use standard/lsi/base_8.8.1.5 or standard/preempt-rt/lsi/base_8.8.1.5 For releases after 8.8.1.5 through 8.8.1.7, use 1

standard/lsi/base_8.8.1.7 or standard/preempt-rt/lsi/base_8.8.1.7 For releases after 8.8.1.7 through 8.8.1.18, use standard/lsi/base_8.8.1.18 or standard/preempt-rt/lsi/base_8.8.1.18 For releases after 8.8.1.18 through 8.8.1.45, use standard/lsi/base_8.8.1.45 or standard/preempt-rt/lsi/base_8.8.1.45 For releases after 8.8.1.45 through 8.8.1.53, use standard/lsi/base_8.8.1.53 or standard/preempt-rt/lsi/base_8.8.1.53 For releases after 8.8.1.53 through 8.8.1.56, use standard/lsi/base_8.8.1.56 or standard/preempt-rt/lsi/base_8.8.1.56 For releases after 8.8.1.56 through 8.8.1.64, use standard/axxia-dev/base_8.8.1.64 or standard/preempt-rt/axxia-dev/base_8.8.1.64 After that, use standard/axxia-dev/base or standard/preempt-rt/axxia-dev/base

Versions Yocto does not allow tags. That being the case, here is how to git particular versions of the Yocto kernel (from the Yocto repository, or the Intel Github repositories on standard/axxia/base or standard/preempt-rt/axxia/base) using commit IDs. Note that not all tags get pushed to Yocto, so only some tagged versions are available. Axxia Tag

Commit ID

lsi_axxia_linux_8.8.1.53

9e57bfba80b2c5bf177e634b8f72ead4247b37da

lsi_axxia_linux_preempt-rt_8.8.1.53

c99491ecebc8c486ab10c518de495fa8d98f733b

lsi_axxia_linux_8.8.1.50

87c1d0a694a7670b54e6e0e72e2f3614509ad333

lsi_axxia_linux_preempt-rt_8.8.1.50 2 7511f4d2ce8049fcce67a76cb2cdc04edf4d8b72

Overview - GitHub

This makes it impossible to update clones. When this happens, ... versions of the Yocto kernel (from the Yocto repository, or the Intel Github repositories on ...

87KB Sizes 5 Downloads 152 Views

Recommend Documents

Overview Instruction - GitHub
IMAGE_FSTYPES += "ext2". PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-custom". Other optional settings for saving disk space and build time:.

Overview Instructions - GitHub
With U-Boot as the boot loader, the above need to be put into a format that U-Boot understands. The following describes using the FIT format (see doc/uImage.

BreedR Overview - GitHub
6 0 56. 72. 0. 55 1. 14 13. 4.775. 9 0 55. 73. 0. 22 1. 8. 13. 19.099 12 0 22. 74. 0 .... Predicted genetic values vs. ...... Plus some more specific metagene functions:.

Overview Instructions - GitHub
The build produces a kernel image, a root file system, and kernel header ... git1+973494766d7ca2401e3138f28b6257a5b899cf1d-r0/linux-lsisim-standard-build.

Overview Local Builds and Modifications - GitHub
restore "u-boot-spl.bin" binary S:0x20000000 set var $pc ... restore "parameters" binary S:0x2003f000 ... It is possible to use the data path instead of the FEMAC.

Makerspace RFID Lock Management Overview - GitHub
python manage.py loaddata rfid_lock_management/fixtures/initial.json. Run the Django development server. $ python manage.py runserver ... microcontroller (Arduino) that connects to the RFID scanner and operates the locking mechanism. Simulating authe

Overview for Axxia 5600 and Axxia 6700 Local Builds and ... - GitHub
cd axxia_u-boot. $ git checkout --track -b axxia-dev ... tools/mkimage -A arm64 -T firmware -C none -a 0 -e 0 -n XLOADER \. -d spl/u-boot-spl.bin spl/u-boot-spl.