From: Rafał Miłecki
If something goes wrong and script can't find upstream revision it will
return something like:
r2220
which looks like a valid upstream revision 2220. We cant' distinguish it
from e.g. 2200 upstream commits and 20 local ones.
The new format still provides
From: Rafał Miłecki
It should be faster than printing them and piping to the wc.
Signed-off-by: Rafał Miłecki
---
scripts/getver.sh | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/scripts/getver.sh b/scripts/getver.sh
index
Hi, Mathias Kresin.
It seems its Ethernet LEDs are directly hooked into switch chip. It
flashes without defining them in DTB. I dunno about where WLAN LEDs are
hooked. I failed to drive them with sysfs gpio driver.
I tried LED blinker script in
https://wiki.openwrt.org/doc/hardware/port.gpio
Hi David,
On Tuesday, November 15, 2016 4:49:40 PM CET David Lang wrote:
> > Well, we are. We can't change the fact that the devices need to be locked
> > to be sold in the US. But if you google a little, you will find a lot of
> > patches for various Open Source projects signed by @open-mesh.com
On Wed, Nov 16, 2016 at 8:35 PM, Felix Fietkau wrote:
> It's in my staging tree and will make it to the main repo soon.
Good to hear. Thanks.
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
Hi Felix,
Patchwork was changed to "accepted" --
http://patchwork.ozlabs.org/patch/694517/ -- but this hasn't shown up
in the actual LEDE repo. What's up?
Jason
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
On 2016-11-16 20:35, Jason A. Donenfeld wrote:
> Hi Felix,
>
> Patchwork was changed to "accepted" --
> http://patchwork.ozlabs.org/patch/694517/ -- but this hasn't shown up
> in the actual LEDE repo. What's up?
It's in my staging tree and will make it to the main repo soon.
- Felix
> If someone stumbles upon the solution for this problem, please let me
> know.
Since I havn't found any open issue that could cause this, I opened a
ticket:
https://github.com/LotarProject/dokuwiki-template-bootstrap3/issues/268
Thomas
___
Lede-dev
Hi,
find my comments inline.
2016-11-16 12:47 GMT+01:00 perillamint :
> From: "Yong-hyu, Ban"
>
> Signed-off-by: Yong-hyu, Ban
> ---
> .../linux/ramips/base-files/etc/board.d/02_network | 1 +
>
> There is a small usability issue with the wiki: there is no easy way to
> get a permalink to a page section (i.e. a link that includes an
> anchor).
>
> First, it would be nice to have a small clickable permalink just beside
> a section title.
Done.
> Also, there is a bug in the table of
This patch fixes switch initial config on Mikrotik RB450/G
Signed-off-by: João Chaínho
---
diff --git a/target/linux/ar71xx/base-files/etc/board.d/02_network
b/target/linux/ar71xx/base-files/etc/board.d/02_network
index df87c96..daf9495 100755
---
On 16/11/2016 16:35, Rafał Miłecki wrote:
> On 16 November 2016 at 12:41, wrote:
>>> patch fails to apply to current HEAD. could you check/resend it please
>>
>> Just checked again on a new git clone - everything is fine here.
>
> I can confirm it applies cleanly
> $ curl
* Koen Vandeputte [16.11.2016 17:45]:
> 3)
> - When a kernel update patch is posted, it requires at least 2
> additional "tested-by"'s on different targets before it can be
> considered for merging. (Covering 5 .. 6 targets in total
thanks for these insights.
i
This patch enables the serial console on some Mikrotik devices (RB450, RB450G,
RB493G, RB750UP).
Signed-off-by: João Chaínho
diff --git
a/target/linux/ar71xx/patches-4.4/701-MIPS-ath79-add-routerboard-detection.patch
This patch adds support for the Cisco Meraki MX60/MX60W Security
Appliance. Flashing information can be found at
https://github.com/riptidewave93/LEDE-MX60
Specs are as follows:
AppliedMicro APM82181 SoC at 800MHz
1GiB NAND - Samsung K9K8G08U0D
512MB DDR RAM - 4x Nanya NT5TU128M8GE-AC
Atheros
On 16 November 2016 at 12:41, wrote:
>> patch fails to apply to current HEAD. could you check/resend it please
>
> Just checked again on a new git clone - everything is fine here.
I can confirm it applies cleanly
$ curl https://patchwork.ozlabs.org/patch/695452/mbox/ | git am
These patches add support for the Cisco Meraki MX60 & MX60W Security Appliance.
Cc: Christian Lamparter
Chris Blake (2):
firmware-utils: Add support for the Cisco Meraki MX60/MX60W
apm821xx: Add support for the Cisco Meraki MX60/MX60W
This patch adds header support for the Cisco Meraki MX60/MX60W, which
are a part of the apm821xx target. Some structure changes were needed
due to the fact this device uses U-Boot (unlike other devices in
mkmerakifw.c) which uses a different header structure to define the load
offsets for the
This patch adds support for the Cisco Meraki MX60/MX60W Security
Appliance. Flashing information can be found at
https://github.com/riptidewave93/LEDE-MX60
Specs are as follows:
AppliedMicro APM82181 SoC at 800MHz
1GiB NAND - Samsung K9K8G08U0D
512MB DDR RAM - 4x Nanya NT5TU128M8GE-AC
Atheros
From: "Yong-hyu, Ban"
Signed-off-by: Yong-hyu, Ban
---
.../linux/ramips/base-files/etc/board.d/02_network | 1 +
target/linux/ramips/base-files/lib/ramips.sh | 3 +
.../ramips/base-files/lib/upgrade/platform.sh | 1 +
> patch fails to apply to current HEAD. could you check/resend it please
Just checked again on a new git clone - everything is fine here.
Regards,
P. Wassi
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
Hi,
patch fails to apply to current HEAD. could you check/resend it please
John
On 16/11/2016 07:25, p.wa...@gmx.at wrote:
> From: Paul Wassi
>
> Fix the incorrect usage of ar934x_nfc_write_page and
> ar934x_nfc_write_page_raw.
> Add *page* in the argument list and
I started the script to do this for 4.4.31, and I already have more
changes than you, so NAK. While I appreciate the effort, I would like to
ask you to not send these kind of patches anymore until you are sure you
completely understand what you are doing.
Ok, noted.
I just started playing
On 16-11-16 07:43, p.wa...@gmx.at wrote:
> From: Paul Wassi
>
> Refresh patches for all targets that support kernel 4.4.
> compile/run-tested on kirkwood, ar71xx, brcm47xx.
>
> Signed-off-by: Paul Wassi
> ---
> This patch is meant to be applied upon 4.4.31!
>
On 11/16/2016 08:01 AM, Baptiste Jonglez wrote:
> Hi,
>
> I discovered that tons of packages now have their own page in the wiki,
> which is nice. It looks automated, what is the source of the data?
>
> Here are a few observations:
>
> - I'm not sure the list of architectures is very relevant,
> On 16-11-16 09:54, Koen Vandeputte wrote:
> - From each seperate build, copy all pathes from
> target/linux/"target"/patches-4.4 to the unused git source clone
> ("target" being cns3xxx or imx6)
Ah, ok. So that's why the things for apm821xx and brcm2708 were not refreshed.
I thought a patch
On 16-11-16 09:54, Koen Vandeputte wrote:
> Hi Paul,
>
> First of all, thank you for reviewing and testing the patch.
>
>
> Let me share in detail how I prepare the kernel update patch:
>
> - Pull the latest git state 3 times
> - On two of them, I apply my custom .config and feeds for the hardware
Small correction below
On 2016-11-16 09:54, Koen Vandeputte wrote:
Hi Paul,
First of all, thank you for reviewing and testing the patch.
Let me share in detail how I prepare the kernel update patch:
- Pull the latest git state 3 times
- On two of them, I apply my custom .config and feeds
Hi Paul,
First of all, thank you for reviewing and testing the patch.
Let me share in detail how I prepare the kernel update patch:
- Pull the latest git state 3 times
- On two of them, I apply my custom .config and feeds for the hardware
targets I use (1 for cns3xxx, 1 for imx6)
- On each
Hi,
There is a small usability issue with the wiki: there is no easy way to
get a permalink to a page section (i.e. a link that includes an anchor).
First, it would be nice to have a small clickable permalink just beside a
section title.
Also, there is a bug in the table of contents of a page.
30 matches
Mail list logo