summaryrefslogtreecommitdiff
path: root/target/linux/ar71xx/patches-4.1/799-MIPS-ath79-add-minibox-v1-support.patch
Commit message (Collapse)AuthorAgeFilesLines
* ar71xx: reorganize target patches/files to make it possible to add boards ↵Felix Fietkau2015-12-111-39/+0
| | | | | | | | without adding patch files Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 47874
* kernel: update m25p80 in 4.1 to the latest version from 4.4-rc1Felix Fietkau2015-11-241-3/+3
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 47624
* kernel: update kernel 4.1 to version 4.1.11Hauke Mehrtens2015-10-251-14/+14
| | | | | | | | https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.1.11 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 47252
* ar71xx: Add Gainstrong MiniBox v1.0 support to trunkJohn Crispin2015-10-191-0/+39
This patch supersedes the v1 from September 17th. Bumping the patch version - the MiniBox profile showed up under M, but since it's called 'Gainstrong MiniBox v1.0' now it looks out of place. Renamed the profile to gs-minibox-v1.mk to fix that. The following patch adds support for the Gainstrong MiniBox into trunk (or 'Designated Driver' :D ). Fixed items: - Inverted LED polarity (OOLITE seems to suffer from the same problem). - Changed uppercase MINIBOX_V1_ prefix as requested. - Prefixes are now gs_minibox_ similar to gs_oolite_ (same vendor). - Mention the vendor (Gainstrong) in code headers. Compiles fine, has been confirmed working by owners on 15.05. Question: I've seen some boards use tools/firmware-utils/src/mktplinkfw.c, the MiniBox images build fine without, so I'm wondering: do I need to add it in there as well? Any added benefit? Thank you Signed-off by: Stijn Segers <francesco.borromini@inventati.org> SVN-Revision: 47234