John,
just checked with master build f500799 as initrd-kernel. Looks fine as
I can see from bootlog.
Anything special to test?
[1.71] MediaTek Nand driver init, version v2.1 Fix AHB virt2phys error
[1.72] Allocate 16 byte aligned buffer: 80592f90
[1.73] Enable NFI Clock
[
Signed-off-by: Sergey Ryazanov
---
target/linux/ath25/config-4.4 | 156 --
.../linux/ath25/patches-4.4/107-ar5312_gpio.patch | 212 ---
.../linux/ath25/patches-4.4/108-ar2315_gpio.patch | 363
.../ath25/patches-4.4/110-ar2313_ethernet.patch| 1828 ---
Signed-off-by: Sergey Ryazanov
---
target/linux/ath25/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/ath25/Makefile b/target/linux/ath25/Makefile
index 86db43f..27c2639 100644
--- a/target/linux/ath25/Makefile
+++ b/target/linux/ath25/Makefile
@@ -12,7 +
Few tiny fixes for issues caused by changes in the upstream:
- do not touch PHY IRQ array (core code initializes it itself now)
- add missed SET_NETDEV_DEV() invocation (causes segfault during phy
connection)
- use phy API inside the MDIO probe function instead of direct field
access (cons
Drop the own PHY polling function and switch to using the kernel PHY
state machine. This change allows driver to work correctly with devices
that do not support PHY behaviour but whose driver could emulate
autonegotiation completion (e.g. MV88E6060 and IP17xx switches).
NB: earlier this driver rel
Consider renaming the dev field to parent in the upstream.
Signed-off-by: Sergey Ryazanov
---
target/linux/ath25/patches-4.9/107-ar5312_gpio.patch | 2 +-
target/linux/ath25/patches-4.9/108-ar2315_gpio.patch | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/target/linux/ath2
Hello,
This series adds support for 4.9 kernel and then switches the default
kernel version to it. Almost copy'n'refresh. The only exception is the
reworked PHY handling inside the Ethernet controller driver caused by
upstream changes.
This series depends on earlier submitted fixes for kernel con
Copy and refresh patches and config from 4.4
Signed-off-by: Sergey Ryazanov
---
target/linux/ath25/{config-4.4 => config-4.9} | 15 +-
.../107-ar5312_gpio.patch | 34 +++---
.../108-ar2315_gpio.patch | 10 +++
...
PHY core treats any positive return value as the auto-negotiation done
indication. Since we do not actually check any device register in this
callback then update it to return positive value with a neutral meaning
instead of the register flag to avoid confusing for future readers.
Signed-off-by:
The Marvel 88E6060 switch has an MDIO interface, but does not emulate
regular PHY behavior for the host. The network core can not detect using
the generic code, whether the connection via the attached PHY can be
used or not. The PHY's state machine is stuck in a state of
auto-negotiation and does n
Hello,
this series contains couple of patches for issues spotted during the
ath25 kernel update. The first patch is a fix for real issue with
autonegotiation. The second one is a cosmetic change for the function
return value, which confused me during the driver code studying.
Sergey Ryazanov (2):
Merged into my staging tree with
http://git.lede-project.org/?p=lede/jow/staging.git;a=commitdiff;h=3f3d68c6f2.
Thank you!
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Citeren Giuseppe Lippolis :
100.64.0.0/10 is shared address space under RFC6598. IETF seems to point
to significant restrictions on its use. Customer connectivity issues are
clear in the RFC. Chasing mobile load and avoiding rerouting global IP
space is likely fair. Enumerating users fixed wire
> 100.64.0.0/10 is shared address space under RFC6598. IETF seems to point
> to significant restrictions on its use. Customer connectivity issues are
> clear in the RFC. Chasing mobile load and avoiding rerouting global IP
> space is likely fair. Enumerating users fixed wire line end points is
> li
Hi,
John Crispin wrote:
Hi,
here is a V3 of the remerge proposal, I tried to fold all the comments
people made into it, if anything is missing let me know. Please
remeber that post remerge anything can be voted on, so cluttering the
proposal with many details will delay the remerge even mor
On Montag, 5. Juni 2017 11:29:59 CEST Torbjorn Jansson wrote:
>
> so i don't know if i want to swap over to lede/openwrt permanently (more
> or less) and it would have been really nice if you could have one of the
> two running firmware as lede/openwrt and the other one as the built in
> edgeos an
Signed-off-by: Sven Roederer
---
target/linux/ath25/base-files/lib/preinit/15_preinit_iface_atheros | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/target/linux/ath25/base-files/lib/preinit/15_preinit_iface_atheros
b/target/linux/ath25/base-files/lib/preinit/15_preinit_
On 29 May 2017 at 13:45, Imre Kaloz wrote:
> On 2017-05-29 13:10, Jamie Stuart wrote:
>>
>> See another iteration, with:
>>
>> - correct capitalisation
>> - antenna to the side (will not work with lowercase ’n’)
>> - open sans typeface (open source)
>> - mockups of website header
>> - accent colou
On 05/06/17 18:45, Ben Greear wrote:
On 06/04/2017 03:40 AM, Kevin Darbyshire-Bryant wrote:
FAO that nice Mr Greer,
I'm getting (for free) a nice selection of ath10 debug messages when
using the Ath10K-ct firmware & driver in LEDE. A small collection
reproduced below. Are
they of any inte
19 matches
Mail list logo
