summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2016-04-04bcm28xx-bootloader: git checkout take ages, just add the required files, ↵Waldemar Brodkorb
update to latest
2016-04-03add mn10300 newlib toolchain supportWaldemar Brodkorb
2016-04-03add msp430 newlib toolchain supportWaldemar Brodkorb
2016-04-03enable ACPI for generic x86/x86_64 reported by OliverWaldemar Brodkorb
2016-04-02use bzImage for generic x86/x86_64Waldemar Brodkorb
2016-04-02allow to choose audio drivers for genericWaldemar Brodkorb
2016-04-02fix download link for lvmOliver Schib
Signed-off-by: Oliver Schib <lich000king@yahoo.de>
2016-04-02cherrypy: update to 5.1.0Waldemar Brodkorb
2016-04-02fix lm32 toolchain buildingWaldemar Brodkorb
2016-04-02add m32r newlib toolchainWaldemar Brodkorb
2016-04-02dovecot: update to 2.2.23Waldemar Brodkorb
2016-04-02backport patch from upstream gitWaldemar Brodkorb
Commit: 82df3e70ac191a2a3cabf3574839e7561e00e370
2016-04-02openswan: update to 2.6.47Waldemar Brodkorb
2016-04-02strongswan: update to 5.4.0Waldemar Brodkorb
2016-04-02postgresql: update to 9.5.2Waldemar Brodkorb
2016-04-02php: update to 5.6.20Waldemar Brodkorb
2016-04-02openldap: update to 2.4.44Waldemar Brodkorb
2016-04-02nginx: update to 1.9.13Waldemar Brodkorb
2016-04-02busybox: update to 1.24.2Waldemar Brodkorb
2016-04-02mksh: update to 52cWaldemar Brodkorb
2016-04-02add support for epiphany bare-metal toolchain buildingWaldemar Brodkorb
2016-04-01add newlib patchWaldemar Brodkorb
2016-04-01lua: update to 5.3.2Waldemar Brodkorb
2016-04-01sqlite: update to 3.12.0Waldemar Brodkorb
2016-04-01nmap: update to 7.12Waldemar Brodkorb
2016-04-01libressl: update to 2.3.3Waldemar Brodkorb
2016-04-01gzip: update to 1.7Waldemar Brodkorb
2016-04-01git: update to 2.8.0Waldemar Brodkorb
2016-04-01ffmpeg: update to 3.0.1Waldemar Brodkorb
2016-04-01curl: update to 7.48.0Waldemar Brodkorb
2016-04-01linux: update to 4.1.20, add solidrun patch for 4.4.6Waldemar Brodkorb
2016-04-01newlib: add 2.4.0 releaseWaldemar Brodkorb
2016-04-01pixman: update to 0.34.0Waldemar Brodkorb
2016-04-01pango: update to 1.40.0Waldemar Brodkorb
2016-04-01create parent dirWaldemar Brodkorb
2016-04-01mesa: update to 11.1.2Waldemar Brodkorb
2016-04-01libgtk2: update to 2.24.30Waldemar Brodkorb
2016-04-01cairo: update to 1.14.6Waldemar Brodkorb
2016-04-01atk: update to 2.20.0Waldemar Brodkorb
2016-03-31xtensa: use latest binutils/gccWaldemar Brodkorb
2016-03-31binutils: remove upstreamed patchWaldemar Brodkorb
2016-03-31h8300: use correct branch for gdb simulatorWaldemar Brodkorb
2016-03-31add required patch for sh2Waldemar Brodkorb
2016-03-27Fix for unavailable dev-help and pkg-help targetsPhil Sutter
Fixes: a94d74d9c875b ("rework prereq check") Signed-off-by: Phil Sutter <phil@nwl.cc>
2016-03-27reimplement package patching and update-patches logicPhil Sutter
This works by using git as backend for all the dirty work. This means that patches are not just applied, but committed separately on top of the base sources (which are put into an initial commit). A final empty commit marks the end of the applied patch series, which allows to have multiple sets of patches to apply on top of each other. So a git history might look like this: - OpenADK patch marker: 0000 (this is the initial commit, containing the unpatched sources) - patch 1 of series 1 - patch 2 of series 1 - patch 3 of series 1 - OpenADK patch marker: 0001 - patch 1 of series 2 - patch 2 of series 2 - OpenADK patch marker: 0002 In addition to the separating empty commits, for every patch series metadata files are added (which are used for update-patches): __patchfiles__: A list of the patches' file names __patchdir__: The directory containing the applied patches Since patches might have to be unzipped first and in order to allow calling git-am just once for each patch series, the patches (along with above metadata files) are cached in dedicated directories: .git/patch_tmp/NNNN (where NNNN is the series number with leading zeroes [so shell globbing returns them in the right order]). In case update-patches is called later, update_patches.sh works it's way reverse through the git history, searching for commits named 'OpenADK patch marker: NNNN'. For each one it finds, it uses the metadata info to first remove all source patch files, then export the history in between using git-format-patch. To change patches or add new ones, the user has to use git-rebase in order to get things where they need to be for update_patches.sh to put stuff at the right place. For an example, here is how to change patch 3 of series 1 in the sample history above: - make desired code changes - commit them, ideally using --fixup option - call 'git rebase -i --autosquash <hash of OpenADK patch marker: 0000>' Using --fixup and --autosquash is convenient, since it automatically edits the rebase todo as intended. It's optional though, editing the todo manually will do just fine as well. Signed-off-by: Phil Sutter <phil@nwl.cc>
2016-03-27or1k: sync kernel configWaldemar Brodkorb
2016-03-27linux: add OpenADK startup patchWaldemar Brodkorb
2016-03-27or1k: update kernel and gccWaldemar Brodkorb
2016-03-27newlib: update to latest 2.2.x/2.3.x versionsWaldemar Brodkorb
2016-03-26frv: resolve remaining issues to check toolchain compileWaldemar Brodkorb