[OpenWrt-Devel] [PATCH] bcm53xx: drop Copyright header from two of my bash scripts

2016-05-09 Thread Rafał Miłecki
Both scripts modified by this patch were added by me. First of all I incorrectly added OpenWrt as Copyright holder. It was wrong because: 1) I simply can't transfer my moral rights according to the Polish law 2) Transfering copyrights (economic rights) requires an agreement which I didn't sign

Re: [OpenWrt-Devel] mt76 wifi module on mt7688 board, no interface

2016-05-09 Thread John Crispin
Hi Baptiste, on my list for this week John On 09/05/2016 18:56, Baptiste Clenet wrote: > Lazar, > Have you managed to make mt76 work on mt7688? > > Thanks > > 2016-05-03 1:52 GMT+02:00 Lazar Demin : >> Marc, >> Can you expand on what you did to get the AP to work? I'm

Re: [OpenWrt-Devel] mt76 wifi module on mt7688 board, no interface

2016-05-09 Thread Baptiste Clenet
Lazar, Have you managed to make mt76 work on mt7688? Thanks 2016-05-03 1:52 GMT+02:00 Lazar Demin : > Marc, > Can you expand on what you did to get the AP to work? I'm completely > stumped... > > Any luck on the STA? > > > Thanks > > On Thu, Apr 21, 2016 at 3:00 PM, Marc Nicholas

[OpenWrt-Devel] hostapd-wpad-mesh fails to build.

2016-05-09 Thread Carlos Ferreira
The output of "make ./package/network/services/hostapd/{clean,compile} V=s -j1" can be seen here: http://pastebin.com/KpcbNzmy hostapd-wpad-mesh is failing to build. -- Carlos Miguel Ferreira Researcher at Telecommunications Institute Aveiro - Portugal Work E-mail - c...@av.it.pt Skype &

[OpenWrt-Devel] [PATCH 1/1] [CC]: openssl: Update to version 1.0.2h

2016-05-09 Thread Mohammed Berdai
openssl: Update to version 1.0.2h Bump to the latest version, fixes several security issues: * CVE-2016-2107, CVE-2016-2105, CVE-2016-2106, CVE-2016-2109, CVE-2016-2176 More details at https://www.openssl.org/news/openssl-1.0.2-notes.html Signed-off-by: Mohammed Berdai

Re: [OpenWrt-Devel] [PATCHv2 001/001] [brcm63xx] Display the correct detected CPU ID

2016-05-09 Thread Graham Fairweather
Thanks. I'm looking into that, but currently my system doesn't support 'git send-email' and I'm researching why. My apologies for the noob spam, I still have much to learn and mistakes to make. John has just pointed me toward 'git am', which I also didn't know about. Thank you. On 9 May 2016 at

Re: [OpenWrt-Devel] [PATCHv2 001/001] [brcm63xx] Display the correct detected CPU ID

2016-05-09 Thread Felix Fietkau
On 2016-05-09 13:19, Graham Fairweather wrote: > It wasn't my intention to spam the list. I asked for help on the > forum, I asked for help on IRC and I was told to try things. The > documents say if unsuccessful then try again. As a noob, it is not the > easiest process to follow, especially when

Re: [OpenWrt-Devel] [PATCHv2 001/001] [brcm63xx] Display the correct detected CPU ID

2016-05-09 Thread John Crispin
On 09/05/2016 13:19, Graham Fairweather wrote: > It wasn't my intention to spam the list. I asked for help on the > forum, I asked for help on IRC and I was told to try things. The > documents say if unsuccessful then try again. As a noob, it is not the > easiest process to follow, especially

Re: [OpenWrt-Devel] [PATCHv2 001/001] [brcm63xx] Display the correct detected CPU ID

2016-05-09 Thread Graham Fairweather
It wasn't my intention to spam the list. I asked for help on the forum, I asked for help on IRC and I was told to try things. The documents say if unsuccessful then try again. As a noob, it is not the easiest process to follow, especially when something doesn't work. How would sending the mail to

Re: [OpenWrt-Devel] [PATCH v2 2/3] ext4_part_match: fix bug that prevented matching names

2016-05-09 Thread Ram Chandra Jangir
Hi Josua Mayer, Partname is nothing but respective partition name of emmc card. It reads partition name from GPT partition table. I think fdisk may not be able to write partition name in GPT table, but you should be able to create the partition name with GPT fdisk (consisting of the gdisk,

Re: [OpenWrt-Devel] [PATCHv2 001/001] [brcm63xx] Display the correct detected CPU ID

2016-05-09 Thread Felix Fietkau
On 2016-05-09 12:50, Graham Fairweather wrote: > From: Graham Fairweather > > This patch fixes the logged detected CPU ID when an equivalent is used, > like in the case where we have a bcm6369 and configuration for a > bcm6368 is used. > So, it will display 'Detected Broadcom

[OpenWrt-Devel] [PATCHv2 001/001] [brcm63xx] Display the correct detected CPU ID

2016-05-09 Thread Graham Fairweather
From: Graham Fairweather This patch fixes the logged detected CPU ID when an equivalent is used, like in the case where we have a bcm6369 and configuration for a bcm6368 is used. So, it will display 'Detected Broadcom 0x6369 CPU revision b2' instead of 'Detected Broadcom

[OpenWrt-Devel] [PATCH 1/1] [brcm63xx] Fix the CPU ID logged when detecting bcm63xx variants.

2016-05-09 Thread Graham Fairweather
From: Graham Fairweather This patch fixes the logged detected CPU ID when an equivalent is used, like in the case where we have a bcm6369 and configuration for a bcm6368 is used. So, it will display 'Detected Broadcom 0x6369 CPU revision b2' instead of 'Detected Broadcom

[OpenWrt-Devel] [PATCHv2 001/001] [brcm63xx] Display the correct detected CPU ID

2016-05-09 Thread Graham Fairweather
From: Graham Fairweather This patch fixes the logged detected CPU ID when an equivalent is used, like in the case where we have a bcm6369 and configuration for a bcm6368 is used. So, it will display 'Detected Broadcom 0x6369 CPU revision b2' instead of 'Detected Broadcom

[OpenWrt-Devel] [PATCH 1/1] [brcm63xx] Display the correct CPU ID when alternative used.

2016-05-09 Thread Graham Fairweather
From: Graham Fairweather This patch fixes the logged detected CPU ID when an equivalent is used, like in the case where we have a bcm6369 and configuration for a bcm6368 is used. So, it will 'Detected Broadcom 0x6369 CPU revision b2' display instead of 'Detected Broadcom

[OpenWrt-Devel] [PATCHv2 001/001] [brcm63xx] Display the correct detected CPU ID

2016-05-09 Thread Graham Fairweather
From: Graham Fairweather This patch fixes the logged detected CPU ID when an equivalent is used, like in the case where we have a bcm6369 and configuration for a bcm6368 is used. More info can be found at: https://forum.openwrt.org/viewtopic.php?id=64621

[OpenWrt-Devel] [PATCH, v2 001/001] [brcm63xx] Display the correct detected CPU ID

2016-05-09 Thread Graham Fairweather
From: Graham Fairweather This patch fixes the logged detected CPU ID when an equivalent is used, like in the case where we have a bcm6369 and configuration for a bcm6368 is used. More info can be found at: https://forum.openwrt.org/viewtopic.php?id=64621

[OpenWrt-Devel] [PATCH v2] [brcm63xx] Display the correct detected CPU ID

2016-05-09 Thread Graham Fairweather
From: Graham Fairweather This patch fixes the logged detected CPU ID when an equivalent is used, like in the case where we have a bcm6369 and configuration for a bcm6368 is used. More info can be found at: https://forum.openwrt.org/viewtopic.php?id=64621

[OpenWrt-Devel] [PATCH v2 001/001] [brcm63xx] Display the correct detected CPU ID

2016-05-09 Thread Graham Fairweather
From: Graham Fairweather This patch fixes the logged detected CPU ID when an equivalent is used, like in the case where we have a bcm6369 and configuration for a bcm6368 is used. More info can be found at: https://forum.openwrt.org/viewtopic.php?id=64621

[OpenWrt-Devel] [PATCHv2 001/001] [brcm63xx] Display the correct detected CPU ID

2016-05-09 Thread Graham Fairweather
From: Graham Fairweather This patch fixes the logged detected CPU ID when an equivalent is used, like in the case where we have a bcm6369 and configuration for a bcm6368 is used. More info can be found at: https://forum.openwrt.org/viewtopic.php?id=64621

[OpenWrt-Devel] [PATCHv2 001/001] [brcm63xx] Display the correct detected CPU ID

2016-05-09 Thread Graham Fairweather
From: Graham Fairweather This patch fixes the logged detected CPU ID when an equivalent is used, like in the case where we have a bcm6369 and configuration for a bcm6368 is used. More info can be found at: https://forum.openwrt.org/viewtopic.php?id=64621

[OpenWrt-Devel] [PATCH 001/001] [brcm63xx] v2:Display the correct detected CPU ID

2016-05-09 Thread Graham Fairweather
From: Graham Fairweather This patch fixes the logged detected CPU ID when an equivalent is used, like in the case where we have a bcm6369 and configuration for a bcm6368 is used. More info can be found at: https://forum.openwrt.org/viewtopic.php?id=64621

[OpenWrt-Devel] [PATCH 001/001] [kernel] Bump linux LTS kernel from 4.4.7 to 4.4.9

2016-05-09 Thread Graham Fairweather
From: Graham Fairweather Increment PATCH number, added MD5 sum for release. Patches were refreshed. *https://www.kernel.org/ * Signed-off-by: Graham Fairweather --- include/kernel-version.mk | 4 ++--

[OpenWrt-Devel] [PATCHv2 001/001] [brcm63xx] Display the correct detected CPU ID

2016-05-09 Thread Graham Fairweather
From: Graham Fairweather This patch fixes the logged detected CPU ID when an equivalent is used, like in the case where we have a bcm6369 and configuration for a bcm6368 is used. More info can be found at: https://forum.openwrt.org/viewtopic.php?id=64621

[OpenWrt-Devel] [PATCH 001/001] [brcm63xx] [v2] Display the correct detected CPU ID

2016-05-09 Thread Graham Fairweather
From: Graham Fairweather This patch fixes the logged detected CPU ID when an equivalent is used, like in the case where we have a bcm6369 and configuration for a bcm6368 is used. More info can be found at: https://forum.openwrt.org/viewtopic.php?id=64621