- Aug 17, 2015
-
-
blogic authored
There is another Zbtlink board (ZBT-WA05) supported in ramips target, so use the same naming scheme for ZBT-WR8305RT board and its dts file. Signed-off-by:
Piotr Dymacz <pepe2k@gmail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@46614 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
blogic authored
The following patch fixes: * wrong indentations * doubled gpio-keys-polled nodes (DIR-300-B7, DIR-320-B1, DIR-610-A1) * duplicate spacings * empty lines at end of files and after last child nodes * trailing and leading whitespace * unnecessary and commented-out code * missing empty lines between nodes and between properties and nodes * unnecessary empty lines between nodes properties [1] in .dts{,i} files, for ramips target. [1] Some of empty lines in SOCs dtsi files were left untouched, because they seem to be there for a reason (readability?). Signed-off-by:
-
- Aug 15, 2015
-
-
hauke authored
In addition to the update this also fixes compile problems with kernel 4.1. This closes #20323. Signed-off-by:
Hauke Mehrtens <hauke@hauke-m.de> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@46609 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
wigyori authored
Signed-off-by:
Matthias Schiffer <mschiffer@universe-factory.net> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@46608 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
wigyori authored
It's nice to have a distinction between files which are built during the normal OpenWrt build process and ones that are created by the ImageBuilder (like it already exists on some other targets). This also gives boot.img a profile-specific prefix as it contains profile- specific data. KDIR_TMP does not need to be specified since include/image.mk already sets it. Signed-off-by:
Zoltan HERPAI <wigyori@uid0.hu> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@46607 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
wigyori authored
Install uboot files to KERNEL_BUILD_DIR instead of BIN_DIR to fix ImageBuilder. Similar fixes are necessary for many (all?) other uboot targets. Signed-off-by:
-
wigyori authored
The DTS files aren't useful (other targets don't copy them either) and clutter BIN_DIR with files unrelated to the chosen profile. Signed-off-by:
-
- Aug 14, 2015
-
-
jogo authored
Switch ipq806x to the new image build system. Image files might change slightly their names, but the generated files should not change. Signed-off-by:
Jonas Gorski <jogo@openwrt.org> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@46602 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
jogo authored
Allow other targets to make use of it. Signed-off-by:
-
jogo authored
Linux 4.1 is also affected from the dma issue, so remove the dma proprties there as well. Signed-off-by:
-
jogo authored
Changelog: * https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.1.5 Signed-off-by:
-
jogo authored
Make the device name accessible for any build commands instead of forcing targets to define it themselves. Signed-off-by:
-
jogo authored
Instead of letting each target define it themselves, create on in include/image.mk and let the targets use it. Signed-off-by:
-
jogo authored
Rename BOARD_ID to NETGEAR_BOARD_ID. Signed-off-by:
-
jogo authored
Rename BOARD_ID to NETGEAR_BOARD_ID and REGION to NETGEAR_REGION. Signed-off-by:
-
jogo authored
Rename BOARD_ID to NETGEAR_BOARD_ID and REGION to NETGEAR_REGION. Signed-off-by:
-
jogo authored
Instead of each target defining it the same, move the KDIR_TMP definition to include/image.mk. In addition Image/Build/SysupgradeNAND already requires KDIR_TMP to be set, so it makes sense to have it globally defined. Signed-off-by:
-
- Aug 13, 2015
-
-
nbd authored
Previous patch 6f2905ee enabled ADM in the kernel, which causes a kernel panic when accessing the SPI flash. As a workaround, We'll disable DMA for the flash for now. It was not enabled previously anyway so we'll just leave it as is. Reported-by:
Mathieu Olivari <mathieu@codeaurora.org> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@46587 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
- Aug 12, 2015
-
-
rmilecki authored
We got check for nvram_len placed too early and the code never tried reading CFE variables used on WGT634U. This is a regression introduced in r45942 and reported in #20291. Signed-off-by:
Rafał Miłecki <zajec5@gmail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@46584 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
- Aug 09, 2015
-
-
wigyori authored
Signed-off-by:
-
hauke authored
This fixes this linking problem: ERROR: "clk_set_rate" [drivers/usb/phy/phy-generic.ko] undefined! ERROR: "clk_round_rate" [drivers/media/v4l2-core/videodev.ko] undefined! ERROR: "clk_set_rate" [drivers/media/v4l2-core/videodev.ko] undefined! In the upstream kernel it is fixed here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=411520af8ec9456886359b42628e583ac58e7e44 This closes: #20162, #20172, #20196, #20197, #20202 and #20308 Signed-off-by:
-
wigyori authored
Signed-off-by:
-
hauke authored
Changelog: * https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.20 Signed-off-by:
-
- Aug 07, 2015
-
-
nbd authored
Previous patch set backported the recently posted NAND flash driver to 3.18 and 4.1 kernel. This patch now enables it in the kernel config. There is no change to the partition layout and init yet. But the NAND flash can be seen in the mtd list on an AP148: root@OpenWrt:/# cat /proc/mtd dev: size erasesize name mtd0: 10000000 00020000 "qcom-nandc" ... Signed-off-by:
-
nbd authored
These patches add support for ipq806x NAND flash controller. Most of these are cherry-picked & backported from LKML: *https://lkml.org/lkml/2015/8/3/16 This patch just modifies the kernel code, but doesn't change the config. It should be harmless. Signed-off-by:
-
nbd authored
These are cherry-picked & backported from LKML: *https://lkml.org/lkml/2015/3/17/19 They are enabled on both 3.18 and 4.1 kernel. Patches 150 to 154 are applying changes merged since 3.18; they enable mechanisms used by the ADM driver. ADM engine is used by the NAND controller, so it is necessary to bring-up NAND flash support. Signed-off-by:
-
- Aug 05, 2015
-
-
jogo authored
Without it the wifi isn't really usable. Signed-off-by:
-
jogo authored
Variables dependend on JFFS2_BLOCKSIZE and NANDBLOCK_SIZE are used for template generation, so need to be present before inclusion of image.mk in target image Makefiles. So move all declarations to before any includes. Fixes: r42878 ("image.mk: clean up and parallelize mkfs calls") Signed-off-by: -
jogo authored
It looks like RAC flushes cause random corruption(?) when the second thread is set as default. Fixes #20160. Signed-off-by:
-
jogo authored
BCM6318: add support for Plusnet / Sagem 2704N (V1) Signed-off-by:
Matt Goring <matt.goring@googlemail.com> Signed-off-by:
-
jogo authored
It boots fine, so no reason to not build it. Signed-off-by:
-
jogo authored
Changelog: * https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.1.4 Signed-off-by:
Daniel Golle <daniel@makrotopia.org> [jogo: fix brcm2708 patches, refresh target patches] Signed-off-by:
-
nbd authored
We forgot to enable the stmmac driver for 4.1 kernel, so ethernet interfaces don't show-up on this kernel. Signed-off-by:
-
nbd authored
Remove options which have been moved into the generic config ever since. Signed-off-by:
-
nbd authored
Old bootloader (same ones which have DT disabled) don't perform any PCIe initialization. The consequence is a freeze during PCIe bring-up on these old u-boot. Same kernel with a newer bootloaders works fine as they contain the corresponding PCIe init code. In this change, we'll add the missing init and make sure the kernel doesn't rely on some preexisting init to get PCIe to work. That includes the following changes: *GPIOs: set function & drive strength *Clocks: add init code for aux & ref clocks *PCIe driver: additional init of the hardware controller Tested 3.18 and 4.1 on an AP148 with bootloader branch 0.0.1 Signed-off-by:
-
nbd authored
PCIe controller nodes are numbers 0/1/2 in the chipset dtsi file, but the pinmux nodes are numbers 1/2/3. We'll make it consistent by changing the pinmux numbering to match the controller's one. Signed-off-by:
-
nbd authored
Certain AP148 platforms (and derivative) use bootloaders which did not have DT enabled. In order to support these old platforms, we'll now make the following modifications: *explicitely add the memory node in the AP148 DT: this used to be added by new u-boot through a run-time patch mechanism. We'll now add it explicitely so it works on boots which don't support that feature. New boots will have the node twice, the second one will be ignored. *add the zImage generation next to the FIT image for AP148. Other platforms using non-DT enabled bootloaders may want to leverage this zImage code to generate their own firmare as well. Signed-off-by:
-
nbd authored
Default kernel doesn't change and stays on 3.18 for now. Signed-off-by:
-
nbd authored
Signed-off-by:
Felix Fietkau <nbd@openwrt.org> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@46553 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
- Aug 02, 2015
-
-
nbd authored
Reported-by:
Steve Brown <sbrown@cortland.com> Signed-off-by:
Sven Eckelmann <sven@open-mesh.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@46547 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
