Merged into my staging tree with
http://git.openwrt.org/?p=openwrt/staging/jow.git;a=commitdiff;h=bb22c988ce.
Thank you!
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Merged into my staging tree with
http://git.openwrt.org/?p=openwrt/staging/jow.git;a=commitdiff;h=eed9614af2.
Thank you!
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Merged into my staging tree with
http://git.openwrt.org/?p=openwrt/staging/jow.git;a=commitdiff;h=e7d9da323f.
Thank you!
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Merged into my staging tree with
http://git.openwrt.org/?p=openwrt/staging/jow.git;a=commitdiff;h=f9ae253c3e.
Thank you!
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Merged into my staging tree with
http://git.openwrt.org/?p=openwrt/staging/jow.git;a=commitdiff;h=b21a7e5349.
Thank you!
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
The kernel configuration of the mikrotik subtarget enables
several kernel options that are not required by the supported
MikroTik boards.
The patches in this series are disabling some of them to get
rid of the unused code and to reduce the size of the compiled
kernel.
The size of the compress
Reduces the compressed kernel size by ~2.5KB.
Signed-off-by: Gabor Juhos
---
target/linux/ar71xx/mikrotik/config-default | 6 ++
1 file changed, 6 insertions(+)
diff --git a/target/linux/ar71xx/mikrotik/config-default
b/target/linux/ar71xx/mikrotik/config-default
index 815ac60e68..da0c9dac
Disable the drivers for the following ethernet switches:
Realtek RTL8306
Realtek RTL8366/8367
Marvell 88E6060 (DSA)
Marvell 88E6063 (DSA)
Also disable the phy driver for Marvell PHYs.
None of the supported RouterBOARDs are using any device
which needs these drivers.
Disable the DSA frame
It does not belongs to the MikroTik boards.
Signed-off-by: Gabor Juhos
---
target/linux/ar71xx/mikrotik/config-default | 1 +
1 file changed, 1 insertion(+)
diff --git a/target/linux/ar71xx/mikrotik/config-default
b/target/linux/ar71xx/mikrotik/config-default
index da0c9dacc9..a77813d23d 10064
Sorry, now the non-HTML version...
Hi guys,
I remember there was quite a bit of gnashing of teeth, when targets in
master dropped 4.4 support so quickly after 17.01 had been released
(which made it very cumbersome to backport 4.4 kernel bumps from master
to the stable branch). Wouldn't it be
1. Add support for SAMA5D27 SOM1 EK board
2. version update to v3.8.9
Signed-off-by: Sandeep Sheriker Mallikarjun
---
package/boot/at91bootstrap/Makefile | 20 +---
1 file changed, 17 insertions(+), 3 deletions(-)
diff --git a/package/boot/at91bootstrap/Makefile
b/package/boot
Add support for SAMA5D27 with target device as at91-sama5d27_som1_ek
in SAMA5 subtarget and build images for SAMA5D27 SOM1 EK board.
Signed-off-by: Sandeep Sheriker Mallikarjun
---
target/linux/at91/base-files/lib/at91.sh | 3 +++
target/linux/at91/image/sama5.mk | 8
2 files c
This patch series includes adding support of SAMA5D27 SOM1 Ek board
Sandeep Sheriker Mallikarjun (3):
at91:Add SAMA5D27 SOM1 EK device
at91bootstrap: Add support for SAMA5D27 SOM1 EK board
uboot-at91: Add support for SAMA5D27 SOM1 EK board
package/boot/at91bootstrap/Makefile | 20
Add support for SAMA5D27 SOM1 EK board.
Signed-off-by: Sandeep Sheriker Mallikarjun
---
package/boot/uboot-at91/Makefile | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/package/boot/uboot-at91/Makefile b/package/boot/uboot-at91/Makefile
index ae2e888..c1d5cac
Hi Hauke,
I have already fixed this and submitted this patch. below is the
patch link for references.
https://patchwork.ozlabs.org/patch/855788/
Regards,
Sandeep Sheriker M
On 01/08/2018 03:58 PM, Hauke Mehrtens wrote:
These packages are needed to generate the image, better mark them hid
These packages are needed to generate the image, better mark them hidden
so we will activate them based on which boards gets build and they will
be activated always when the board which needs then gets build.
Signed-off-by: Hauke Mehrtens
---
package/boot/uboot-at91/Makefile | 1 +
1 file change
It is sufficient to define this in AT91Bootstrap/Default as this is not
used for all.
Signed-off-by: Hauke Mehrtens
---
package/boot/at91bootstrap/Makefile | 8
1 file changed, 8 deletions(-)
diff --git a/package/boot/at91bootstrap/Makefile
b/package/boot/at91bootstrap/Makefile
index
The packages should start with AT91Bootstrap and not at91bootstrap to use the
default definition.
Without this patch the packages are not getting selected automatically
when the board gets selected, but this is needed to successfully create
the image.
Fixes: 670448a002 ("at91bootstrap: New packa
The default configuration file for sama5d4_xplainednf_uboot does not
exist, but a default configuration file for
sama5d4_xplainednf_uboot_secure exists, fix the name.
Fixes: 670448a002 ("at91bootstrap: New package at91bootstrap")
Signed-off-by: Hauke Mehrtens
---
package/boot/at91bootstrap/Makef
Without this patch one sdcard image with the following name is created
for all devices:
openwrt-at91-sama5--sdcard.img.gz
This makes the build system create device specific versions like:
openwrt-at91-sama5-at91-sama5d2_xplained-sdcard.img.gz
Signed-off-by: Hauke Mehrtens
---
target/linux/at91/i
These packages are needed to generate the image, better mark them hidden
so we will activate them based on which boards gets build and they will
be activated always when the board which needs then gets build.
Signed-off-by: Hauke Mehrtens
---
package/boot/at91bootstrap/Makefile | 1 +
1 file cha
The common option on an interface that disables/enables it is named "disabled".
Just corrected wiki entry accordingly.
Regards,
Paul
> Op 8 jan. 2018, om 20:06 heeft yanosz het volgende
> geschreven:
>
> Hallo,
>
>
> Am 2018-01-08 um 16:41 schrieb Jo-Philipp Wich:
>> Hi yanosz,
>>
>> "optio
update at91 kernel 4.9.73 to 4.14.11
Signed-off-by: Sandeep Sheriker Mallikarjun
---
target/linux/at91/Makefile | 2 +-
target/linux/at91/{config-4.9 => config-4.14} | 6 ++
.../100-ARM-at91-build-dtb-for-LMU5000.patch
Thank you. I think we ought to demand a product recall for everything Intel.
signature.asc
Description: PGP signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Hallo,
Am 2018-01-08 um 16:41 schrieb Jo-Philipp Wich:
> Hi yanosz,
>
> "option enabled" is not defined for /etc/config/network, config
> interface as far as I know. Maybe you meant "option auto 0" instead?
Interesting. Looking at the docs it is supported:
https://lede-project.org/docs/user-gui
On 01/08/2018 03:52 PM, Matthias Schiffer wrote:
> When attempting to fix FS#837, I decided to treat our metadata generator to
> a greater refactoring, which resulted in this patchset. FS#837 is fixed in
> patch 13.
>
> I also removed two seemingly obsolete features, "preconfig" and "package
> fea
Hi,
2018-01-06 12:12 GMT+01:00, Nishant Sharma :
> Hi Hauke,
>
> On Friday 05 January 2018 11:33 PM, Hauke Mehrtens wrote:
>> I have never looked at the OpenWrt fork provided by Marvell, but I got
>> OpenWrt master working on the espressobin with kernel 4.14. It only has
>> a low number of patches
Hi,
[...]
> diff --git a/scripts/package-metadata.pl b/scripts/package-metadata.pl
> index 980ad24dc0..41e7108322 100755
> --- a/scripts/package-metadata.pl
> +++ b/scripts/package-metadata.pl
> @@ -101,14 +101,16 @@ my %dep_check;
> sub __find_package_dep($$) {
> my $pkg = shift;
>
Hi yanosz,
"option enabled" is not defined for /etc/config/network, config
interface as far as I know. Maybe you meant "option auto 0" instead?
Regards,
Jo
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listin
The Marvell 88E6063 ethernet switch driver depends on the DSA
framework. Add a 'depends on NET_DSA' statement to its Kconfig
entry to state that explicitly.
Fixes the following Kconfig warning:
warning: (NET_DSA_MV88E6060 && NET_DSA_MV88E6063) selects NET_DSA_TAG_TRAILER
which has unmet direct
The symbols in some kernel configurations of the target are in
wrong order. Sort them with kconfig.pl.
Signed-off-by: Gabor Juhos
---
target/linux/ar71xx/config-4.4 | 4 ++--
target/linux/ar71xx/config-4.9 | 4 ++--
target/linux/ar71xx/mikrotik/config-default | 2 +-
ta
Hello,
I discovered an issue with disabled interfaces propagating routes to
sepcified tables.
Given:
config interface 'internet_share'
option ifname '@wan'
option proto 'dhcp'
option ip4table '65'
config interface 'internet_share6'
option ifname '@wan'
op
Signed-off-by: Matthias Schiffer
---
scripts/feeds | 20 +++-
scripts/metadata.pm | 6 +++---
scripts/package-metadata.pl | 16 +++-
3 files changed, 21 insertions(+), 21 deletions(-)
diff --git a/scripts/feeds b/scripts/feeds
index 42f7b3b116..
Instead of adding virtual packages to the normal package list, keep a
separate list for provides, make each package provide itself, and resolve
all dependencies through this list. This allows to use PROVIDES to replace
existing packages.
Fixes FS#837.
Signed-off-by: Matthias Schiffer
---
script
This feature has been unused for years, and its scope is too limited to be
actually useful.
Signed-off-by: Matthias Schiffer
---
include/package-dumpinfo.mk | 16 +---
package/Makefile| 3 ---
scripts/metadata.pm | 20 +---
scripts/package-metadat
Package "features" seem to be unused for some time. In any case, custom
Config.in snippets and package PROVIDES are a much more flexible way to
express similar options.
Signed-off-by: Matthias Schiffer
---
include/package-dumpinfo.mk | 25 -
scripts/metadata.pm |
Target build depends are similar to host build depends in that they refer
to source packages rather than binary packages. Therefore, it makes sense
to handle them together, rather than putting them in a list together with
runtime depends and trying to figure out if the entries refer to source or
to
Runtime depends cannot have a buildtype suffix, and they never refer to
source package names. In addition, this adds warnings about unsatisfiable
dependencies.
Furthermore, this change fixes the generation of conditional build
dependencies for virtual packages provided by different source packages
Build depends must refer to source packages rather than binary package
names.
Signed-off-by: Matthias Schiffer
---
include/autotools.mk | 4 ++--
include/nls.mk | 2 +-
package/network/config/ltq-adsl-app/Makefile | 2 +-
package/network/conf
Turn the srcpackage values into hashes to allow storing more information
than just binary package names.
Signed-off-by: Matthias Schiffer
---
scripts/feeds | 2 +-
scripts/metadata.pm | 6 --
scripts/package-metadata.pl | 2 +-
3 files changed, 6 insertions(+), 4 deleti
When attempting to fix FS#837, I decided to treat our metadata generator to
a greater refactoring, which resulted in this patchset. FS#837 is fixed in
patch 13.
I also removed two seemingly obsolete features, "preconfig" and "package
features", which are not used by any package in the OpenWrt/LEDE
Eventually the BUILDONLY package flag could be replaced by simply creating
a package Makefile without any BuildPackage calls. This will fail for now,
as BuildPackage also causes the Makefile's compile target etc. to do
something useful at all.
Signed-off-by: Matthias Schiffer
---
include/package
Nothing explicitly depends on base-files, and even if it would, it would
not cause any problems. Remove the unused special case.
Signed-off-by: Matthias Schiffer
---
scripts/package-metadata.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/package-metadata.pl b/scri
All build dependencies are between source packages. Interating over source
rather than binary packages simplifies parts of the code and prepares
further improvement.
As a side effect, this changes the implicit default variant of a few
packages (the first defined is used now instead of the lexicogr
We often want to access fields of a source packages through pkg->{src}.
Allow accessing them directly instead of resolving the source hash through
srcpackages.
Signed-off-by: Matthias Schiffer
---
scripts/feeds | 4 ++--
scripts/metadata.pm | 51 ++-
Build types are a property of source rather than binary packages. This is a
preparation for followup cleanup.
Signed-off-by: Matthias Schiffer
---
scripts/metadata.pm | 4 ++--
scripts/package-metadata.pl | 13 +++--
2 files changed, 9 insertions(+), 8 deletions(-)
diff --git a
Every single reference to subdir was concatenated with the source package
name, so it makes sense to store the concatenated value instead.
Signed-off-by: Matthias Schiffer
---
scripts/metadata.pm | 12 +++-
scripts/package-metadata.pl | 25 -
2 files chang
Signed-off-by: Matthias Schiffer
---
scripts/metadata.pm | 3 ---
scripts/package-metadata.pl | 8
2 files changed, 4 insertions(+), 7 deletions(-)
diff --git a/scripts/metadata.pm b/scripts/metadata.pm
index e636a45a33..50f91407d6 100644
--- a/scripts/metadata.pm
+++ b/scripts/
Alberto,
Despite the disinformation Intel initially spread, it looks like AMD processors
are not vulnerable to Meltdown (which these patches should address).
Spectre is a different thing altogether, and affects AMD and Intel as well, but
these are other CVEs.
Stijn
More important bug fix:
402f05c Use full-rate mtu_time in all tins. Fixes an issue where some
cake tins experienced excessive latency since 49776da (dynamically
adjust target)
Minor bug fixes:
31277c2 Avoid unsigned comparison against zero. Fix compiler warning,
no known impact.
8cf5278 ack_fi
More important bug fix:
402f05c Use full-rate mtu_time in all tins. Fixes an issue where some
cake tins experienced excessive latency since 49776da (dynamically
adjust target)
Minor bug fixes:
31277c2 Avoid unsigned comparison against zero. Fix compiler warning,
no known impact.
8cf5278 ack_fi
AFAIK AMD processors that don't need that are from Zen onwards. Older
ones are impacted.
-Alberto
On 08/01/2018 12:27, Nick Lowe wrote:
Hi Kevin,
I am not following :-) For AMD, there should not be a tradeoff as
there is no need for the page table isolation.
Regards,
Nick
On Mon, Jan 8, 2
Sorry, it was back ported to 4.9.75 :-)
On Mon, Jan 8, 2018 at 12:34 PM, Nick Lowe wrote:
> It looks like PCID and INVPCID support is likely to be back ported to
> the 4.9.76 Linux Kernel: https://patchwork.kernel.org/patch/10143225/
___
Lede-dev maili
It looks like PCID and INVPCID support is likely to be back ported to
the 4.9.76 Linux Kernel: https://patchwork.kernel.org/patch/10143225/
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Hi all,
I am a moron, I missed:
+skip:
+ if (boot_cpu_data.x86_vendor == X86_VENDOR_AMD)
+ goto disable;
It uses a different path...
Regards,
NIck
On Mon, Jan 8, 2018 at 11:27 AM, Nick Lowe wrote:
> Hi Kevin,
>
> I am not following :-) For AMD, there should not be a tradeoff as
> there is no
Hi Kevin,
I am not following :-) For AMD, there should not be a tradeoff as
there is no need for the page table isolation.
Regards,
Nick
On Mon, Jan 8, 2018 at 11:21 AM, Kevin Darbyshire-Bryant
wrote:
>
>
>> On 8 Jan 2018, at 11:12, Nick Lowe wrote:
>>
>> Agreed. So this will seemingly regres
> On 8 Jan 2018, at 11:12, Nick Lowe wrote:
>
> Agreed. So this will seemingly regress something like an APU2 and
> therefore probably should not be merged to LEDE as-is?
I’ll let an adult decide the performance/security tradeoff.
signature.asc
Description: Message signed with OpenPGP
__
Citeren Kevin Darbyshire-Bryant :
On 8 Jan 2018, at 11:04, Nick Lowe wrote:
Hi,
Where in 4.9.75 does it avoid the page table isolation mitigation for AMD?
Committed to the 4.14 and 4.15 branch is:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.15-rc7&id=694d
Agreed. So this will seemingly regress something like an APU2 and
therefore probably should not be merged to LEDE as-is?
Nick
On Mon, Jan 8, 2018 at 11:08 AM, Kevin Darbyshire-Bryant
wrote:
>
>
>> On 8 Jan 2018, at 11:04, Nick Lowe wrote:
>>
>> Hi,
>>
>> Where in 4.9.75 does it avoid the page t
> On 8 Jan 2018, at 11:04, Nick Lowe wrote:
>
> Hi,
>
> Where in 4.9.75 does it avoid the page table isolation mitigation for AMD?
>
> Committed to the 4.14 and 4.15 branch is:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.15-rc7&id=694d99d40972f12e59a36
Hi,
Where in 4.9.75 does it avoid the page table isolation mitigation for AMD?
Committed to the 4.14 and 4.15 branch is:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.15-rc7&id=694d99d40972f12e59a3696effee8a376b79d7c8
X86_BUG_CPU_INSECURE becomes X86_BUG_CPU_ME
Tested-by: Koen Vandeputte
Targets: cns3xxx, imx6
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
The ATM subsystem is different from the generic ethernet NICs. The ATM
subsystem requires a callback when a packet has been sent. It means a
tx skb_buff need to be used after it has sent. While the generic NIC
can fill up the TX ring and free skb_buffs if it encounter a ring buffer slot
with an alr
From: Martin Schiller
Signed-off-by: Martin Schiller
---
package/kernel/lantiq/ltq-atm/src/ltq_atm.c | 41 -
1 file changed, 41 deletions(-)
diff --git a/package/kernel/lantiq/ltq-atm/src/ltq_atm.c
b/package/kernel/lantiq/ltq-atm/src/ltq_atm.c
index f306d19364fd..0
64 matches
Mail list logo
