Hi,
as I've been working on changes for kirkwood/board.d/01_leds:
Previously, for ar71xx or ramips, I've been told to name LEDs like
:: (1)
before that, they were
:: (2)
(And we also renamed those of (2) in order to fit (1))
On target kirkwood, some LEDs are named by upstream kernel DTS files.
E
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, and it clutters
the page a lot. See for instance
https://wik
As I've just sent in 4.4.32, I came across other changes from which
I think they should have already been done in 4.4.31:
/apm821xx/patches-4.4/801-usb-xhci-add-firmware-loader-for-uPD720201-and-uPD72.patch
/apm821xx/patches-4.4/802-usb-xhci-force-msi-renesas-xhci.patch
Changes to xhci-pci.c were
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!
Apply https://patchwork.ozlabs.org/patch/694032/ first.
include/kernel-version.mk
From: Paul Wassi
Bump U-Boot for Kirkwood to upstream 2016.11. Local patches refreshed.
Signed-off-by: Paul Wassi
---
This patch bumps uboot-kirkwood to 2016.11.
Compile-tested, run-tested on Seagate Dockstar.
package/boot/uboot-kirkwood/Makefile
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 remove the local variable.
Signed-off-by: Paul Wassi
---
In the buildlogs of ar71xx-nand [1] you can see a warning
> drivers/mtd/nand/ar934x_nfc.c: In function 'a
Hello, I'm currently porting LEDE on Digitalzone(Korean company) WeVO
W2914NS v2 and its variants.
However, their variant naming scheme is just "insane". Their variant has
different model name with same spec (HI1200AC, It seems they just used
different color housing. Also, comment from their CS in
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 mail addresses
(LEDE, Linux, hostapd, etc) ... Feel free to compare that with other
Hi Koen,
as you might have noticed, I'm trying to learn how patch refreshing is done.
(And I had quite a trouble, which lead to some discussion this month)
Currently I'm preparing a bump to 4.4.32 (actually, the patches are already
prepared,
I'll send them in soon, it's just still compiling for
From: Rafał Miłecki
We already count amount of local git commits. This allows realizing if
user did any local changes based on his boot log or openwrt_release.
Signed-off-by: Rafał Miłecki
---
scripts/getver.sh | 4
1 file changed, 4 insertions(+)
diff --git a/scripts/getver.sh b/scripts
* Bastian Bittorf [21.10.2016 23:02]:
> we use the signal reported from 'iw' for some actions
> and I can see them beeing inconsistent or maybe even
> wrong calculated (strange values are marked)
I tried LEDE r2167 and it's still the
same: at *** the signal value is just wrong.
should i report th
This will include the latest firmware for the QCA4019:
firmware-5.bin_10.4-3.2.1-00044.
Signed-off-by: Christian Lamparter
---
package/firmware/ath10k-firmware/Makefile | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/package/firmware/ath10k-firmware/Makefile
b/package/
On 2016-11-08 22:39, Benjamin Berg wrote:
Also sending the eject command to LUN 1 is required for some D-Link devices.
Signed-off-by: Benjamin Berg
Signed-off-by: René van Weert
---
switch.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/switch.c b/switch.c
index b283561..587a2af 1
This patch adds a new firmware package to ath10k-firmware
called ath10k-firmware-qca4019.
Signed-off-by: Christian Lamparter
---
package/firmware/ath10k-firmware/Makefile | 18 ++
1 file changed, 18 insertions(+)
diff --git a/package/firmware/ath10k-firmware/Makefile
b/package/
Simon Wunderlich [2016-11-15 11:51:54]:
> Hey Petr,
Hi!
> We don't have any influence on the production decisions, though.
sure, I'm not blaming any of you, I understand this, it's very hard :-)
> But as Sven said, please contact customer support. I'm sure they will find a
> solution for you
Hey Petr,
On Tuesday, November 15, 2016 11:29:40 AM CET Petr Štetiar wrote:
> Sven Eckelmann [2016-11-15 09:32:18]:
>
> Hi,
>
> > I was told that OpenMesh is also shipping an already unlocked version of
> > it in regions which don't requires closed down versions. They called it
> > "(Internatio
Sven Eckelmann [2016-11-15 09:32:18]:
Hi,
> I was told that OpenMesh is also shipping an already unlocked version of it in
> regions which don't requires closed down versions. They called it
> "(International Version)".
quoting from Cloudtrax help portal[1]:
"For international customers, pleas
On 3 November 2016 at 17:51, Rafał Miłecki wrote:
> I'm trying to understand how REVISION variable and getver.sh work. There is
> this
> nice feature: whenever a new git commit appears, getver.sh is used to
> calculate
> new revision and it's used for /etc/openwrt_version. LEDE never misses an
[this is a rather odd change of topic]
On Montag, 14. November 2016 14:24:48 CET Petr Štetiar wrote:
[...]
> But on the other hand I'm wondering how should I upload my custom LEDE image
> to my recently purchased OM5P-AC device as the U-Boot there is locked down and
> accepts only signed OS im
19 matches
Mail list logo
