Le 02/07/17 à 12:36, Daniel Gonzalez Cabanelas a écrit :
> Fix the register for configuring rising/falling edge
>
> Rising should be sense=1, and falling sense=0.
> The old driver used these values, but the new one have
> them flipped.
This should probably be sent upstream as well, right?
>
>
Hi,
This series has been resubmitted as PR #800.
HTH,
T.
> Le 7 févr. 2017 à 11:10, Thibaut a écrit :
>
> Hi,
>
> Please ignore this series for now: since there are SPI-NOR devices which are
> not wireless APs that could be supported with the same code base, I’m going
> to resubmit these pa
Fix the register for configuring rising/falling edge
Rising should be sense=1, and falling sense=0.
The old driver used these values, but the new one have
them flipped.
Signed-off-by: Daniel Gonzalez Cabanelas
diff --git
a/target/linux/brcm63xx/patches-4.4/321-irqchip-add-support-for-bcm6345-s
Hi,
Am Tue, 7 Feb 2017 08:39:53 -0800
schrieb Etienne Champetier :
> [..]
> Haven't looked how debian and others are doing telemetry
Debian uses the package "popularity contest". It submits the ist of installed
(and based on file timestamps: used) packages along with a unique host ID
(AFAIK). T
Hi Felix,
On Tue, 2017-02-07 at 10:43 +0100, Felix Fietkau wrote:
> Hi Alexey,
>
> I will soon push a change to switch to binutils 2.27 by default. It
> seems that since 2.26, binutils has gained support for ARC.
> Can we get rid of the ARC specific binutils version then, or does it
> still have
On 07.02.2017 16.40, Bastian Bittorf wrote:
* Etienne Champetier [07.02.2017 16:27]:
not a fan of leaking revision number on public network by default (if
you are connected to public wifi or ...)
This is a valid point somehow, but:
because model and revision number can/must be encoded with e.
2017-02-07 7:40 GMT-08:00 Bastian Bittorf :
> * Etienne Champetier [07.02.2017 16:27]:
>> not a fan of leaking revision number on public network by default (if
>> you are connected to public wifi or ...)
>
> This is a valid point somehow, but:
> because model and revision number can/must be encode
* Etienne Champetier [07.02.2017 16:27]:
> not a fan of leaking revision number on public network by default (if
> you are connected to public wifi or ...)
This is a valid point somehow, but:
because model and revision number can/must be encoded with e.g. base64
it is at least not plaintext, but
Adds preliminary kernel 4.9 support for this target.
- Refreshed/Updated all patches
Added 3 new patches:
- 093 --> Add virtual PCI MMIO mapping
- 230 --> Remove deprecated code
- 240 --> Rework AT24 eeprom code to use the new NVMEM API
Compiled & tested on cns3xxx (gw2388)
Signed-off-by: Koen
Hi All,
2017-02-07 1:27 GMT-08:00 Bastian Bittorf :
> * Giuseppe Lippolis [07.02.2017 10:00]:
>> My proposal for the anonymous datacollection is to send
>> 1) an UDP telegram with sysupgraded.$boardname at the end of the sysupgrade
>> 2) an UDP telegram with firstboot.$boardname at the end of the
On 2017-02-07 15:55, Felix Fietkau wrote:
On 2017-02-07 15:52, Koen Vandeputte wrote:
Adds preliminary kernel 4.9 support for this target.
What's missing?
Nothing except the actual switch in the makefile.
(Just being cautious)
- Felix
Koen
___
L
On 2017-02-07 15:52, Koen Vandeputte wrote:
> Adds preliminary kernel 4.9 support for this target.
What's missing?
- Felix
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Adds preliminary kernel 4.9 support for this target.
- Refreshed/Updated all patches
Added 2 new patches:
- 230 --> Remove deprecated code
- 240 --> Rework AT24 eeprom code to use the new NVMEM API
Compiled & tested on cns3xxx (gw2388)
Signed-off-by: Koen Vandeputte
---
Builds & boots without
* Jo-Philipp Wich [07.02.2017 15:20]:
> Check "git log scripts/config/" and compare the complexity & size of
> "./scripts/metadata.pl config tmp/.packageinfo" in OpenWrt with
> "./scripts/package-metadata.pl config tmp/.packageinfo" on LEDE.
>
> Also compare the runtimes of "make prepare-tmpinfo"
After doing some more tests it looks like these problems only come out when
bridging WiFi & ethernet on the Raspberry Pi.
https://github.com/raspberrypi/firmware/issues/673
I'm currently running wifi and eth on separate interfaces and so far so good :).
~ Álvaro.
El 07/02/2017 a las 10:53, Álva
Hi,
> I'am not sure, what is internally done and how,
> can somebody point me to the program.c so maybe i
> get an idea whats "wrong".
Check "git log scripts/config/" and compare the complexity & size of
"./scripts/metadata.pl config tmp/.packageinfo" in OpenWrt with
"./scripts/package-metadata.p
in our build-process we make intensive use of
'make defconfig' and registrated a massive speed-loss
in building comparing with OpenWrt r49276 on the
same machine with nearly the same .config:
r49276: ~1.2sec
LEDE: ~10 sec
everything is in a tmpfs, it's a Xeon 5680@3.33GHz
I'am not sure, what is
Hi,
Please ignore this series for now: since there are SPI-NOR devices which are
not wireless APs that could be supported with the same code base, I’m going to
resubmit these patches with « rbspi » as the namespace for the new file and
attached bits.
T.
> Le 5 févr. 2017 à 13:31, ha...@slashd
Hi Rafał,
El 02/02/2017 a las 12:32, Rafał Miłecki escribió:
> Hi,
>
> There are few changes that recently went into master and I'd like to
> see in lede-17.01. Let me what do you think, if backporting any of
> these is a bad idea.
>
> 1) bgmac support for external PHYs
> 6a853776a502 ("kernel:
On 2017-02-07 09:15, Rafał Miłecki wrote:
> I think various targets handle it in different ways. E.g. brcm47xx has
> modules for b44, tg3 and bgmac while bcm53xx has bgmac built-in.
>
> Is there any preference for this?
>
> I was thinking about supporting more Ethernet-related stuff like
> switch
Hi Alexey,
I will soon push a change to switch to binutils 2.27 by default. It
seems that since 2.26, binutils has gained support for ARC.
Can we get rid of the ARC specific binutils version then, or does it
still have some important changes that are not upstream yet?
- Felix
___
* Giuseppe Lippolis [07.02.2017 10:00]:
> My proposal for the anonymous datacollection is to send
> 1) an UDP telegram with sysupgraded.$boardname at the end of the sysupgrade
> 2) an UDP telegram with firstboot.$boardname at the end of the firstboot
sorry, i just forgot: the revision number mus
On 2017-02-07 09:10, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> It's needed to get proper bridging support with DSA drivers.
>
> Signed-off-by: Rafał Miłecki
> ---
> package/kernel/linux/modules/netsupport.mk | 14 ++
> 1 file changed, 14 insertions(+)
>
> diff --git a/package
Add missing parentheses.
Fixes kernel build issue when using this driver.
Signed-off-by: Koen Vandeputte
---
target/linux/generic/files/drivers/mtd/mtdsplit/mtdsplit_uimage.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/generic/files/drivers/mtd/mtdsplit/mtdsp
I think various targets handle it in different ways. E.g. brcm47xx has
modules for b44, tg3 and bgmac while bcm53xx has bgmac built-in.
Is there any preference for this?
I was thinking about supporting more Ethernet-related stuff like
switchdev, DSA, b53. It would be nice to have a clear guidance
From: Rafał Miłecki
It's needed to get proper bridging support with DSA drivers.
Signed-off-by: Rafał Miłecki
---
package/kernel/linux/modules/netsupport.mk | 14 ++
1 file changed, 14 insertions(+)
diff --git a/package/kernel/linux/modules/netsupport.mk
b/package/kernel/linux/mo
26 matches
Mail list logo
