[OpenWrt-Devel] [PATCH 1/4] brcm2708-gpu-fw: update to latest version

2015-10-25 Thread Álvaro Fernández Rojas 
Signed-off-by: Álvaro Fernández Rojas <nolt...@gmail.com>
---
 package/kernel/brcm2708-gpu-fw/Makefile | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/package/kernel/brcm2708-gpu-fw/Makefile 
b/package/kernel/brcm2708-gpu-fw/Makefile
index dd53bce..2686cf0 100644
--- a/package/kernel/brcm2708-gpu-fw/Makefile
+++ b/package/kernel/brcm2708-gpu-fw/Makefile
@@ -8,13 +8,13 @@ include $(TOPDIR)/rules.mk
 include $(INCLUDE_DIR)/kernel.mk
 
 PKG_NAME:=brcm2708-gpu-fw
-PKG_REV:=f9d0138ee8e2805299724addf85d03e851569291
-PKG_VERSION:=20150904
+PKG_REV:=9d268f00de7c13afa315fe2d303265d535c4bdf0
+PKG_VERSION:=20151025
 PKG_RELEASE:=1
 
 PKG_SOURCE:=$(PKG_REV).tar.gz
 PKG_SOURCE_URL:=https://github.com/Hexxeh/rpi-firmware/archive/
-PKG_MD5SUM:=7e645dc54bf4175ca358aeb4b3406d7c
+PKG_MD5SUM:=21ac2ba64ef045655b4d4677b3fdf6cd
 
 PKG_BUILD_DIR:=$(BUILD_DIR)/$(PKG_NAME)/rpi-firmware-$(PKG_REV)
 
-- 
1.9.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH 3/4] brcm2708: update modules

2015-10-25 Thread Álvaro Fernández Rojas 
- Add support for DAC+ Pro.
- Add kmod-smi-bcm2835 and kmod-smi-bcm2835-dev modules.

Signed-off-by: Álvaro Fernández Rojas 
---
 target/linux/brcm2708/modules.mk | 41 +---
 1 file changed, 38 insertions(+), 3 deletions(-)

diff --git a/target/linux/brcm2708/modules.mk b/target/linux/brcm2708/modules.mk
index 36d26c6..3bc592c 100644
--- a/target/linux/brcm2708/modules.mk
+++ b/target/linux/brcm2708/modules.mk
@@ -66,20 +66,21 @@ endef
 $(eval $(call KernelPackage,sound-soc-hifiberry-dac))
 
 define KernelPackage/sound-soc-hifiberry-dacplus
-  TITLE:=Support for HifiBerry DAC+
+  TITLE:=Support for HifiBerry DAC+ / DAC+ Pro
   KCONFIG:= \
CONFIG_SND_BCM2708_SOC_HIFIBERRY_DACPLUS \
CONFIG_SND_SOC_PCM512x
   FILES:= \
+   $(LINUX_DIR)/drivers/clk/clk-hifiberry-dacpro.ko \
$(LINUX_DIR)/sound/soc/bcm/snd-soc-hifiberry-dacplus.ko \
$(LINUX_DIR)/sound/soc/codecs/snd-soc-pcm512x.ko
-  AUTOLOAD:=$(call AutoLoad,68,snd-soc-pcm512x snd-soc-hifiberry-dacplus)
+  AUTOLOAD:=$(call AutoLoad,68,clk-hifiberry-dacpro snd-soc-pcm512x 
snd-soc-hifiberry-dacplus)
   DEPENDS:=kmod-sound-soc-bcm2708-i2s +kmod-i2c-bcm2708
   $(call AddDepends/sound)
 endef
 
 define KernelPackage/sound-soc-hifiberry-dacplus/description
-  This package contains support for HifiBerry DAC+
+  This package contains support for HifiBerry DAC+ / DAC+ Pro
 endef
 
 $(eval $(call KernelPackage,sound-soc-hifiberry-dacplus))
@@ -236,6 +237,40 @@ endef
 $(eval $(call KernelPackage,random-bcm2835))
 
 
+define KernelPackage/smi-bcm2835
+  SUBMENU:=$(OTHER_MENU)
+  TITLE:=BCM2835 SMI driver
+  KCONFIG:=CONFIG_BCM2835_SMI
+  FILES:=$(LINUX_DIR)/drivers/misc/bcm2835_smi.ko
+  AUTOLOAD:=$(call AutoLoad,20,bcm2835_smi)
+  DEPENDS:=@TARGET_brcm2708
+endef
+
+define KernelPackage/smi-bcm2835/description
+  This package contains the Character device driver for Broadcom Secondary
+  Memory Interface
+endef
+
+$(eval $(call KernelPackage,smi-bcm2835))
+
+define KernelPackage/smi-bcm2835-dev
+  SUBMENU:=$(OTHER_MENU)
+  TITLE:=BCM2835 SMI device driver
+  KCONFIG:=CONFIG_BCM2835_SMI_DEV
+  FILES:=$(LINUX_DIR)/drivers/char/broadcom/bcm2835_smi_dev.ko
+  AUTOLOAD:=$(call AutoLoad,21,bcm2835_smi_dev)
+  DEPENDS:=@TARGET_brcm2708 +kmod-smi-bcm2835
+endef
+
+define KernelPackage/smi-bcm2835-dev/description
+  This driver provides a character device interface (ioctl + read/write) to
+  Broadcom's Secondary Memory interface. The low-level functionality is 
provided
+  by the SMI driver itself.
+endef
+
+$(eval $(call KernelPackage,smi-bcm2835-dev))
+
+
 define KernelPackage/spi-bcm2708
   SUBMENU:=$(SPI_MENU)
   TITLE:=BCM2708 SPI controller driver
-- 
1.9.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] buildbot: gb15 fails to upload due to host keys and wyrding timeouts largest firmwares

2015-10-25 Thread Zoltan HERPAI 

Hannu Nyman wrote:
Buildbot needs some maintenance, as some of the buildslaves are 
behaving badly :-(


1)
gb15 has a wrong host key and silently fails all uploads. It just 
completed 4 builds successfully, but did not upload them. That has 
been going on for some time now.
It is rather sad that the buildbot script silently fails the binary 
uploads, because that makes the error hard to notice. The build shows 
green on the status screen, so unless you wonder about the missing 
binaries of a successful build and really check the upload step's log 
file, you won't notice the error. It would be great if the buildbot 
upload script could be modified to show the upload error more clearly.


2)
wyrding timeouts the imagebuilder/SDK tar file creation step for the 
largest firmwares. I have noticed that as ar71xx has suffered from 
that several times in the last few weeks. The 20 minutes given for 
waiting for any output from the process is sometimes too short for the 
tar file creation step and the buildbot breaks the build. Apparently 
"tar" does not produce any intermediate output.  (When that timeout 
happens, the file cleanup step may also take hours, so there may be 
something wrong with the buildslave's disk or I/O in general.)

[snip]

We're checking these, hopefully both will resolve with the next round of 
builds.


Thanks,
-w-
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] buildbot: gb15 fails to upload due to host keys and wyrding timeouts largest firmwares

2015-10-25 Thread Hannu Nyman 

On 25.10.2015 13:14, Zoltan HERPAI wrote:

Hannu Nyman wrote:
wyrding timeouts the imagebuilder/SDK tar file creation step for the 
largest firmwares. I have noticed that as ar71xx has suffered from that 
several times in the last few weeks. The 20 minutes given for waiting for 
any output from the process is sometimes too short for the tar file 
creation step and the buildbot breaks the build. Apparently "tar" does not 
produce any intermediate output.  (When that timeout happens, the file 
cleanup step may also take hours, so there may be something wrong with the 
buildslave's disk or I/O in general.)


We're checking these, hopefully both will resolve with the next round of 
builds.


Thanks,
-w-



Good to hear.

One piece of additional information:
I noticed today that also buildslave2 may timeout the SDK tar generation 
phase, so it might be that Openwrt has grown so large that the 20 min timeout 
is generally too short.


http://buildbot.openwrt.org:8010/builders/ath25/builds/107
http://buildbot.openwrt.org:8010/builders/ath25/builds/107/steps/compile_8/logs/stdio

*

make[2]: Entering directory `/home/openwrt/slave/ath25/build/target/sdk'
...
tar -xf - -C 
/home/openwrt/slave/ath25/build/build_dir/target-mips_mips32_musl-1.1.11/OpenWrt-SDK-ath25_gcc-4.8-linaro_musl-1.1.11.Linux-x86_64


command timed out: 1200 seconds without output, attempting to kill
process killed by signal 9
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH 4/4] brcm2708: copy overlays README to boot partition

2015-10-25 Thread Álvaro Fernández Rojas 
Signed-off-by: Álvaro Fernández Rojas 
---
 target/linux/brcm2708/image/Makefile | 1 +
 1 file changed, 1 insertion(+)

diff --git a/target/linux/brcm2708/image/Makefile 
b/target/linux/brcm2708/image/Makefile
index cc0bfb0..cf263bd 100644
--- a/target/linux/brcm2708/image/Makefile
+++ b/target/linux/brcm2708/image/Makefile
@@ -43,6 +43,7 @@ define Build/boot-img
mcopy -i $@.boot $(DTS_DIR)/$(DEVICE_DTS).dtb ::$(DEVICE_DTS).dtb
mmd -i $@.boot ::/overlays
mcopy -i $@.boot $(DTS_DIR)/overlays/*.dtb ::/overlays/
+   mcopy -i $@.boot $(DTS_DIR)/overlays/README ::/overlays/
 endef
 
 define Build/sdcard-img
-- 
1.9.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH 2/2] ar71xx: add support for TP-LINK TL-WR841N/ND v10

2015-10-25 Thread Alexander Couzens 
Hi Matthias,

as long you can not flash the exact same image as v9,
you have to create a mips machine, but you can use the same setup
function as v9.

Many parts of openwrt use the mips machine to detect the board, like
sysupgrade.

Add your machine id to
target/linux/ar71xx/patches-4.1/700-MIPS-ath79-openwrt-machines.patch
and use the MIPS_MACHINE macro in 
target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wr841n-v9.c

Best
lynxis

PS. Nice catch on the revision/version fix for ar9533. The problem why
v9 didn't work in the first time was quite similiar.

On Thu, 22 Oct 2015 14:01:40 +0200
Matthias Schiffer  wrote:

> The TL-WR841N/ND v10 is mostly identical to the v9. Apart from some
> minor changes, it contains a newer revision of the QCA9533 SoC and
> the CPU clock is significantly higher.
> 
> Signed-off-by: Matthias Schiffer 
> ---
>  target/linux/ar71xx/image/Makefile | 9 -
>  1 file changed, 8 insertions(+), 1 deletion(-)
> 
> diff --git a/target/linux/ar71xx/image/Makefile
> b/target/linux/ar71xx/image/Makefile index 7759a0d..a659af9 100644
> --- a/target/linux/ar71xx/image/Makefile
> +++ b/target/linux/ar71xx/image/Makefile
> @@ -704,6 +704,13 @@ define Device/tl-wr841n-v9
>  TPLINK_HWID := 0x08410009
>  endef
>  
> +define Device/tl-wr841n-v10
> +$(Device/tplink-4mlzma)
> +BOARDNAME := TL-WR841N-v9
> +DEVICE_PROFILE := TLWR841
> +TPLINK_HWID := 0x08410010
> +endef
> +
-- 
Alexander Couzens

mail: lyn...@fe80.eu
jabber: lyn...@fe80.eu
mobile: +4915123277221
gpg: 390D CF78 8BF9 AA50 4F8F  F1E2 C29E 9DA6 A0DF 8604


pgpgHUvyqxe1a.pgp
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH 2/2] ar71xx: add support for TP-LINK TL-WR841N/ND v10

2015-10-25 Thread Matthias Schiffer 
Thanks, but I know what I'm doing. The hardware is similar enough to
boot with the exact same initialization routines as the v9, thus reusing
the BOARDNAME is fine (it is done like this for other hardware as well -
OpenWrt has a distinction between "board" and "model", where multiple
models can have the same board, but still each model has its own images)

On TP-LINK devices, sysupgrade checks the TPLINK_HWID of the image
against the one in the flash, the BOARDNAME doesn't matter (except to
determine that it is a TP-LINK device).

Matthias


On 10/25/2015 11:47 PM, Alexander Couzens wrote:
> Hi Matthias,
> 
> as long you can not flash the exact same image as v9,
> you have to create a mips machine, but you can use the same setup
> function as v9.
> 
> Many parts of openwrt use the mips machine to detect the board, like
> sysupgrade.
> 
> Add your machine id to
> target/linux/ar71xx/patches-4.1/700-MIPS-ath79-openwrt-machines.patch
> and use the MIPS_MACHINE macro in 
> target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wr841n-v9.c
> 
> Best
> lynxis
> 
> PS. Nice catch on the revision/version fix for ar9533. The problem why
> v9 didn't work in the first time was quite similiar.
> 
> On Thu, 22 Oct 2015 14:01:40 +0200
> Matthias Schiffer  wrote:
> 
>> The TL-WR841N/ND v10 is mostly identical to the v9. Apart from some
>> minor changes, it contains a newer revision of the QCA9533 SoC and
>> the CPU clock is significantly higher.
>>
>> Signed-off-by: Matthias Schiffer 
>> ---
>>  target/linux/ar71xx/image/Makefile | 9 -
>>  1 file changed, 8 insertions(+), 1 deletion(-)
>>
>> diff --git a/target/linux/ar71xx/image/Makefile
>> b/target/linux/ar71xx/image/Makefile index 7759a0d..a659af9 100644
>> --- a/target/linux/ar71xx/image/Makefile
>> +++ b/target/linux/ar71xx/image/Makefile
>> @@ -704,6 +704,13 @@ define Device/tl-wr841n-v9
>>  TPLINK_HWID := 0x08410009
>>  endef
>>  
>> +define Device/tl-wr841n-v10
>> +$(Device/tplink-4mlzma)
>> +BOARDNAME := TL-WR841N-v9
>> +DEVICE_PROFILE := TLWR841
>> +TPLINK_HWID := 0x08410010
>> +endef
>> +




signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Site needs GPG signing

2015-10-25 Thread Luke 
Hello OpenWRT Team,
Per #openwrt IRC it was suggested that I post here to get everyone's
attention. I would like to request that the OpenWRT site begin using GPG
/ SHA256 for it's packages and official releases.

A home router is way too important to leave into the hands of an
attacker. I see there's a few bug reports already filed on this issue,
but they've gone unnoticed for years:

https://dev.openwrt.org/ticket/13346
https://dev.openwrt.org/ticket/20592

Thanks.


Luke



signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel