summaryrefslogtreecommitdiff
path: root/target/config
AgeCommit message (Collapse)Author
2016-05-18hide kernel configuration if no arch is choosenWaldemar Brodkorb
2016-05-18llvm is experimentalWaldemar Brodkorb
2016-05-18add experimental musl xtensa supportWaldemar Brodkorb
2016-05-16bump linux kernel versionsWaldemar Brodkorb
2016-05-15add support for qemu xilinx zynq emulationWaldemar Brodkorb
2016-05-14some basic qemu nios2 supportWaldemar Brodkorb
2016-05-12add support to play with LLVM/clangWaldemar Brodkorb
2016-05-11Linux kernel for ppc64 does not like to be built with -mcpu=power7, getting ↵Waldemar Brodkorb
SIGILL for busybox
2016-05-10add basic ppc64 musl supportWaldemar Brodkorb
2016-05-09kernel: update to 4.5.3Waldemar Brodkorb
2016-05-08gawk is required on Darwin for Linux compileWaldemar Brodkorb
2016-05-05rpi: add patch for 4.4.x kernelWaldemar Brodkorb
2016-05-05rpi: enable default kernel build from githubWaldemar Brodkorb
2016-05-03update rpi kernel patch, add mkknlimg back, more fixesWaldemar Brodkorb
2016-05-02kernel: add 4.5.2Waldemar Brodkorb
2016-05-01for udev device node management we need depmod on host, reported by BalatonWaldemar Brodkorb
2016-05-01Revert "bfin does not compile with gcc 6.1.0"Waldemar Brodkorb
This reverts commit f03053c18301e7353236f7f0114cc6499eec3e02.
2016-04-30bfin does not compile with gcc 6.1.0Waldemar Brodkorb
2016-04-29fixup c++ compiler issues the right wayWaldemar Brodkorb
2016-04-28disable C++ for alpha, static build seems problematicWaldemar Brodkorb
2016-04-28rename symbol name for toolchain onlyWaldemar Brodkorb
2016-04-28linux: bump all kernelsWaldemar Brodkorb
2016-04-28add gcc6 supportWaldemar Brodkorb
2016-04-26allow to experiment with gcc goWaldemar Brodkorb
2016-04-24bfin: msep-data can be usedWaldemar Brodkorb
2016-04-23disable DOPIC for coldfire flatWaldemar Brodkorb
2016-04-21add suffix definition for microblazeWaldemar Brodkorb
2016-04-21m68k: default to binutils 2.26Waldemar Brodkorb
2016-04-19mergeWaldemar Brodkorb
2016-04-18uclibc-ng: update to latest releaseWaldemar Brodkorb
2016-04-17some minor fixes for NSLU2Waldemar Brodkorb
2016-04-16use better suffix for lemote yeelongWaldemar Brodkorb
2016-04-08ed: update to 1.13, add lzip as decompressorWaldemar Brodkorb
2016-04-06add basic raspberry pi3 support (ARM 32Bit)Waldemar Brodkorb
2016-04-05disable 4.4.x for bcm28xx for nowWaldemar Brodkorb
2016-04-05don't try t obuild C++ for h8300Waldemar Brodkorb
2016-04-05add better gcc language support, allow to build objc/fortranWaldemar Brodkorb
2016-04-04add binfmt suffix for bfinWaldemar Brodkorb
2016-04-04new bcm28xx-bootloader does not work with mknlimg, fix 4.1.20 rpi2 bootupWaldemar Brodkorb
2016-04-03add mn10300 newlib toolchain supportWaldemar Brodkorb
2016-04-03add msp430 newlib toolchain supportWaldemar Brodkorb
2016-04-02use bzImage for generic x86/x86_64Waldemar Brodkorb
2016-04-02add m32r newlib toolchainWaldemar Brodkorb
2016-04-02add support for epiphany bare-metal toolchain buildingWaldemar 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-03-31xtensa: use latest binutils/gccWaldemar Brodkorb
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: update kernel and gccWaldemar Brodkorb
2016-03-27newlib: update to latest 2.2.x/2.3.x versionsWaldemar Brodkorb
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-16 23:23:05 +0000