aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/lantiq/xway/target.mk
Commit message (Collapse)AuthorAgeFilesLines
* lantiq: nand: drop ubifs imagesMathias Kresin2017-12-111-1/+1
| | | | | | | | | | | | | | | Users are confused which image type they should use and there are more drawbacks than adavantages in using a r/w ubifs rootfs in constrast to a read-only squashfs rootfs like: - less available free flash space due to better compression of squashfs images - no support for factory reset due to r/w filesystem - possibility to break failsafe due to r/w filesystem Therefore, drop support for r/w ubifs rootfs images. Signed-off-by: Mathias Kresin <dev@kresin.me>
* build: remove mips16 feature flag from target makefilesFelix Fietkau2017-01-241-1/+1
| | | | | | | It can be implicitly derived from the MIPS32 revision support in the kernel configuration Signed-off-by: Felix Fietkau <nbd@nbd.name>
* lantiq: add swconfig to the default packagesMathias Kresin2016-11-271-1/+1
| | | | | | | | | | | | The DEVICE_PACKAGES are not included in the initramfs image in case TARGET_PER_DEVICE_ROOTFS is set. This might produces initramfs images with a not working network configuration because of a missing swconfig. Workaround the issues by adding the essential swconfig package to the default packages selection and deselect swconfig for boards not having swconfig included before via device packages. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: switch from 34k to 24kJonas Gorski2016-08-231-1/+1
| | | | | | | GCC treats 24kc and 34kc exactly the same and will generate identical code, so there is no need to tune to 34kc instead of 24kc. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* build: remove MIPS dsp/dsp2 CPU_SUBTYPEFelix Fietkau2016-08-031-1/+0
| | | | | | | There does not seem to be any meaningful difference in generated code. This will save some time and space on snapshot builds Signed-off-by: Felix Fietkau <nbd@nbd.name>
* lantiq: move esi calls to dsl_cpe_control scripts to fix ordering wrt. ↵Felix Fietkau2015-12-041-1/+1
| | | | | | | | loading vr9 drivers Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 47764
* lantiq xway: generate ramdisk image by defaultJohn Crispin2014-10-141-1/+1
| | | | | | | | | | The installation process on nand-based boards using ubi like the BTHOMEHUBV2B makes use of a ramdisk image, so it makes sense to generate this by default. Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com> SVN-Revision: 42920
* lantiq: remove deprecated jffs2_nand configurationJohn Crispin2014-06-241-1/+1
| | | | | | | | | | | | | | | | | | | | | | As far as I am aware, amongst the lantiq boards, jffs2_nand was only used on the BTHOMEHUBV2B. Ubi-related modifications to the device tree for that board mean that the resulting jffs2 images no longer work, and are no longer required anyway. So I suggest removing the related configuration, which this patch does. If anyone else is using jffs2_nand on a lantiq target please speak up! Incidentally, for a jffs2 rootfs partition concatenated to the kernel image to be recognised and mounted correctly on nand this patch or something equivalent is required: http://patchwork.openwrt.org/patch/5110/ It is marked as accepted in patchwork but doesn't seem to have been committed. As far as I am concerned it too is deprecated. Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com> SVN-Revision: 41312
* kernel: add a NAND_SUPPORT symbolJohn Crispin2014-06-111-1/+1
| | | | | | Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 41122
* lantiq: BT Home Hub 2B - overlayfs on top of ubiJohn Crispin2014-04-221-1/+1
| | | | | | | | BT Home Hub 2B: use overlayfs on top of ubi. Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com> SVN-Revision: 40553
* lantiq: BT Home Hub 2B support - board supportJohn Crispin2014-04-031-1/+1
| | | | | | | | Board support patch for BT Home Hub 2B Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com> SVN-Revision: 40370
* lantiq: add esiJohn Crispin2014-03-301-1/+1
| | | | | | | | http://patchwork.openwrt.org/patch/3703/ Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 40326
* build: unify mips target cflagsFelix Fietkau2013-09-261-1/+2
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 38210
* lantiq: Tune the XWAY subtarget cflagsJohn Crispin2013-06-211-0/+1
| | | | | | | | | This patch sets the cflags -mtune=34kc -mdsp only in XWAY subtarget, while the others remain with mtune=mips32r2. Although the Danube has a Mips 24KEc core performs well with the above cflags. Signed-off-by: José Vázquez Fernández <ppvazquezfer@gmail.com> SVN-Revision: 37006
* lantiq: set mips16 support.John Crispin2013-06-211-1/+1
| | | | | | | | | | | Set mips16 support in XWAY subtarget. This patch is based in changeset #36600 Signed-off-by: José Vázquez Fernández <ppvazquezfer@gmail.com> Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 37005
* target: don't build jffs2 nor images by defaultJonas Gorski2013-06-051-1/+1
| | | | | | Signed-off-by: Jonas Gorski <jogo@openwrt.org> SVN-Revision: 36863
* dont use input layer for gpio buttonsJohn Crispin2012-12-211-1/+1
| | | | SVN-Revision: 34839
* add linux-v3.7John Crispin2012-12-151-1/+1
| | | | SVN-Revision: 34687
* add subtarget, as of 3.6 we dont seperate xway SoCJohn Crispin2012-11-021-0/+10
| | | | SVN-Revision: 34062
* rename xway profile to danube and remove ar9 specificsJohn Crispin2011-07-071-10/+0
| | | | SVN-Revision: 27535
* * backport 2.6.8 patches to .39 / .32.33John Crispin2011-05-291-2/+2
| | | | | | | | | * remove lqtapi * bump tapi/dsl to .39 * migrate to new ltq_ style api * add amazon_se support SVN-Revision: 27026
* * adds profiles to the kernel * fixes 2 compile errors in the usb driver * ↵John Crispin2011-02-011-3/+2
| | | | | | ioports were not allocated properly SVN-Revision: 25278
* adds new lantiq kernel. once the codebase is fully tested and know to be ↵John Crispin2010-12-121-0/+11
working on all the devices previously supported by ifxmips, we will drop ifxmips support. SVN-Revision: 24526
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-10 11:28:10 +0000