Hi,
I was curious if there are some GPIOs exposed on the Linksys WRT3200ACM, so
I started exporting them in /sys/class/gpio. I realized, that some are
locked against exporting (those claimed by gpio-leds and gpio-keys, power
regulator), while others exposed more or less problematic side effects.
Le
Signed-off-by: Yousong Zhou
---
include/download.mk | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/include/download.mk b/include/download.mk
index 3634e777c9..5cfc542042 100644
--- a/include/download.mk
+++ b/include/download.mk
@@ -59,7 +59,7 @@ check_escape=$(subst '
- Make the code more GitHub-specific
- Requires mirror hash to work with .gitattributes
- Use different API depending on whether PKG_SOURCE_VERSION is a
complete commit id or other ref types like tags
- Fix removing symbolic link
- pre-clean dir_untar for possible leftovers from previous ru
Signed-off-by: Yousong Zhou
---
scripts/fixup-makefile.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/fixup-makefile.pl b/scripts/fixup-makefile.pl
index 9026ddcce4..b6f1c74738 100755
--- a/scripts/fixup-makefile.pl
+++ b/scripts/fixup-makefile.pl
@@ -26,7 +26,7 @@
Signed-off-by: Yousong Zhou
---
include/download.mk | 22 ++
1 file changed, 14 insertions(+), 8 deletions(-)
diff --git a/include/download.mk b/include/download.mk
index 3851f6c98a..d09ffab579 100644
--- a/include/download.mk
+++ b/include/download.mk
@@ -19,17 +19,23 @@ end
Hi Jo,
Since this morning, there seems to be a recursive dependency present.
Judging by the output and the changes in Luci repo, I suspect the source
is one of your latest commits?
tmp/.config-package.in:57794:error: recursive dependency detected!
For a resolution refer to Documentation/kbuil
+ NL80211_STA_INFO_SIGNAL_AVG
+ NL80211_STA_INFO_RX_DROP_MISC
+ NL80211_STA_INFO_CONNECTED_TIME
Signed-off-by: Daniel Danzberger
---
include/iwinfo.h | 3 +++
iwinfo_nl80211.c | 12
2 files changed, 15 insertions(+)
diff --git a/include/iwinfo.h b/include/iwinfo.h
index 929f697..4
The following 2 patches add some more stats to libiwinfo.
There is another patch for the rpcd iwinfo module that uses them.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Signed-off-by: Daniel Danzberger
---
include/iwinfo.h | 11
iwinfo_nl80211.c | 69
2 files changed, 80 insertions(+)
diff --git a/include/iwinfo.h b/include/iwinfo.h
index 4111205..49ee7f0 100644
--- a/include/iwinfo.h
+++ b/include/iwinf
Aren’t all inbound SYNs unsolicited by definition? Is there a danger of
reflection attacks?
Sent from my iPhone
> On Jul 2, 2018, at 9:29 AM, Alin Nastac wrote:
>
> From: Alin Nastac
>
> RFC 6092 recommends in section 3.3.1 that an IPv6 CPE must respond to
> unsolicited inbound SYNs with an
Curious: what purposes or use-cases are intended to be served with this event ?
> Op 29 jun. 2018, om 16:14 heeft Hans Dedecker het
> volgende geschreven:
>
> On Fri, Jun 29, 2018 at 5:23 AM Alexander Couzens wrote:
>>
>> "create" will be called before the proto handlers initialised.
> Acked
On Tue, Jul 3, 2018 at 7:26 PM Paul Oranje wrote:
>
> Curious: what purposes or use-cases are intended to be served with this event
> ?
Please don't top post
The interface event IFEV_CREATE can be used by external applications
or netifd internal subsystems to trigger specific logic when an
inter
Anyone got any insight into this one?
One of the characteristics of Perl versus other OpenWrt projects is each new
version is guaranteed to break in an entirely different way you’ve never seen
before.
I’ve reached out to the Storable author but haven’t heard back yet.
Maybe someone in the comm
On Tue, Jul 3, 2018 at 6:39 PM Philip Prindeville
wrote:
>
> Aren’t all inbound SYNs unsolicited by definition? Is there a danger of
> reflection attacks?
Not all inbound SYNs are unsolicited. Take for instance active mode
FTP transfers where the client resides on the LAN . In this case the
FTP
> On Jul 3, 2018, at 3:22 PM, Alin Năstac wrote:
>
> On Tue, Jul 3, 2018 at 6:39 PM Philip Prindeville
> wrote:
>>
>> Aren’t all inbound SYNs unsolicited by definition? Is there a danger of
>> reflection attacks?
>
> Not all inbound SYNs are unsolicited. Take for instance active mode
> FTP
From: Linus Walleij
Date: Sat, 30 Jun 2018 13:17:29 +0200
> This adds the device tree bindings for the Vitesse VSC73xx
> switches. We also add the vendor name for Vitesse.
>
> Cc: devicet...@vger.kernel.org
> Reviewed-by: Florian Fainelli
> Signed-off-by: Linus Walleij
> ---
> ChangeLog v1->v2
From: Linus Walleij
Date: Sat, 30 Jun 2018 13:17:30 +0200
> The VSC7385, VSC7388, VSC7395 and VSC7398 are integrated
> switch/router chips for 5+1 or 8-port switches/routers. When
> managed directly by Linux using DSA we need to do a special
> set-up "dance" on the PHY. Unfortunately these sequen
From: Linus Walleij
Date: Sat, 30 Jun 2018 13:17:31 +0200
> This adds a DSA driver for:
>
> Vitesse VSC7385 SparX-G5 5-port Integrated Gigabit Ethernet Switch
> Vitesse VSC7388 SparX-G8 8-port Integrated Gigabit Ethernet Switch
> Vitesse VSC7395 SparX-G5e 5+1-port Integrated Gigabit Ethernet Swi
On Tue, Jul 3, 2018 at 11:32 PM Philip Prindeville
wrote:
> > On Jul 3, 2018, at 3:22 PM, Alin Năstac wrote:
> >
> > On Tue, Jul 3, 2018 at 6:39 PM Philip Prindeville
> > wrote:
> >>
> >> Aren’t all inbound SYNs unsolicited by definition? Is there a danger of
> >> reflection attacks?
> >
> > No
On 07/04/2018 01:39 AM, Alin Năstac wrote:
On Tue, Jul 3, 2018 at 11:32 PM Philip Prindeville
wrote:
On Jul 3, 2018, at 3:22 PM, Alin Năstac wrote:
On Tue, Jul 3, 2018 at 6:39 PM Philip Prindeville
wrote:
Aren’t all inbound SYNs unsolicited by definition? Is there a danger of
reflection a
20 matches
Mail list logo
