Re: [LEDE-DEV] [PATCH 2/2] prism54-firmware: add also other p54 firmware to own package

2016-06-30 Thread Hauke Mehrtens
On 06/30/2016 09:07 PM, John Crispin wrote:
> i have already added this to my staging tree, feel free to send a ptch
> that i can fold into haukes patch
> 
>   John

I already pushed this, but send a patch to improve this please.

Hauke
> 
> On 30/06/2016 20:53, Christian Lamparter wrote:
>> On Wednesday, June 29, 2016 11:13:01 PM Hauke Mehrtens wrote:
>>> From: Hauke Mehrtens 
>>>
>>> Extract the other p54 firmware files into the prism54-firmware package.
>>>
>>> Signed-off-by: Hauke Mehrtens 
>> Hey, that's really nice of you.
>>
>> Would it be possible to set PKG_VERSION to like 1.0 and add a variable
>> for PRISM54FW:=1.0.4.3.arm and set the PKG_SOURCE:=$(PRISM54FW) instead?
>>
>> Regards,
>> Christian
>>
>>> ---
>>>  package/firmware/prism54-firmware/Makefile | 75 
>>> --
>>>  package/kernel/mac80211/Makefile   | 48 ++-
>>>  2 files changed, 75 insertions(+), 48 deletions(-)
>>>
>>> diff --git a/package/firmware/prism54-firmware/Makefile 
>>> b/package/firmware/prism54-firmware/Makefile
>>> index 759e6b0..2f39dc9 100644
>>> --- a/package/firmware/prism54-firmware/Makefile
>>> +++ b/package/firmware/prism54-firmware/Makefile
>>> @@ -9,20 +9,70 @@ PKG_NAME:=prism54-firmware
>>>  PKG_VERSION:=1.0.4.3
>>>  PKG_RELEASE:=1
>>>  
>>> +PRG_URL:=https://daemonizer.de/prism54/prism54-fw/
>>> +
>>>  # Prism54 FullMAC firmware (jbnore.free.fr seems to be rather slow, so we 
>>> use daemonizer.de)
>>>  PKG_SOURCE:=$(PKG_VERSION).arm
>>> -PKG_SOURCE_URL:=https://daemonizer.de/prism54/prism54-fw/fw-fullmac/
>>> +PKG_SOURCE_URL:=$(PRG_URL)/fw-fullmac/
>>>  PKG_MD5SUM:=8bd4310971772a486b9784c77f8a6df9
>>>  
>>>  include $(INCLUDE_DIR)/package.mk
>>>  
>>> -define Package/prism54-firmware
>>> +
>>> +# Prism54 drivers
>>> +P54USBFW:=2.13.24.0.lm87.arm
>>> +P54PCIFW:=2.13.12.0.arm
>>> +P54SPIFW:=2.13.0.0.a.13.14.arm
>>> +
>>> +define Download/p54-usb-firmware
>>> +  FILE:=$(P54USBFW)
>>> +  URL:=$(PRG_URL)/fw-usb
>>> +  MD5SUM:=8e8ab005a4f8f0123bcdc51bc25b47f6
>>> +endef
>>> +$(eval $(call Download,p54-usb-firmware))
>>> +
>>> +define Download/p54-pci-firmware
>>> +  FILE:=$(P54PCIFW)
>>> +  URL:=$(PRG_URL)/fw-softmac
>>> +  MD5SUM:=ff7536af2092b1c4b21315bd103ef4c4
>>> +endef
>>> +$(eval $(call Download,p54-pci-firmware))
>>> +
>>> +define Download/p54-spi-firmware
>>> +  FILE:=$(P54SPIFW)
>>> +  URL:=$(PRG_URL)/stlc4560
>>> +  MD5SUM:=42661f8ecbadd88012807493f596081d
>>> +endef
>>> +$(eval $(call Download,p54-spi-firmware))
>>> +
>>> +
>>> +define Package/prism54-firmware-default
>>>SECTION:=firmware
>>>CATEGORY:=Firmware
>>> -  URL:=https://daemonizer.de/prism54/prism54-fw
>>> +  URL:=https://daemonizer.de/prism54/prism54-fw/
>>> +endef
>>> +
>>> +define Package/prism54-firmware
>>> +$(Package/prism54-firmware-default)
>>>TITLE:=prism54 firmware
>>>  endef
>>>  
>>> +define Package/p54-usb-firmware
>>> +$(Package/prism54-firmware-default)
>>> +  TITLE:=p54-usb firmware
>>> +endef
>>> +
>>> +define Package/p54-pci-firmware
>>> +$(Package/prism54-firmware-default)
>>> +  TITLE:=p54-pci firmware
>>> +endef
>>> +
>>> +define Package/p54-spi-firmware
>>> +$(Package/prism54-firmware-default)
>>> +  TITLE:=p54-spi firmware
>>> +endef
>>> +
>>> +
>>>  define Build/Prepare
>>> mkdir -p $(PKG_BUILD_DIR)
>>>  endef
>>> @@ -36,4 +86,23 @@ define Package/prism54-firmware/install
>>> $(INSTALL_DATA) $(DL_DIR)/$(PKG_SOURCE) $(1)/lib/firmware/isl3890
>>>  endef
>>>  
>>> +define Package/p54-usb-firmware/install
>>> +   $(INSTALL_DIR) $(1)/lib/firmware
>>> +   $(INSTALL_DATA) $(DL_DIR)/$(P54USBFW) $(1)/lib/firmware/isl3887usb
>>> +endef
>>> +
>>> +define Package/p54-pci-firmware/install
>>> +   $(INSTALL_DIR) $(1)/lib/firmware
>>> +   $(INSTALL_DATA) $(DL_DIR)/$(P54PCIFW) $(1)/lib/firmware/isl3886pci
>>> +endef
>>> +
>>> +define Package/p54-spi-firmware/install
>>> +   $(INSTALL_DIR) $(1)/lib/firmware
>>> +   $(INSTALL_DATA) $(DL_DIR)/$(P54SPIFW) $(1)/lib/firmware/3826.arm
>>> +endef
>>> +
>>> +
>>>  $(eval $(call BuildPackage,prism54-firmware))
>>> +$(eval $(call BuildPackage,p54-usb-firmware))
>>> +$(eval $(call BuildPackage,p54-pci-firmware))
>>> +$(eval $(call BuildPackage,p54-spi-firmware))
>>> diff --git a/package/kernel/mac80211/Makefile 
>>> b/package/kernel/mac80211/Makefile
>>> index bee0723..38eb4af 100644
>>> --- a/package/kernel/mac80211/Makefile
>>> +++ b/package/kernel/mac80211/Makefile
>>> @@ -1061,33 +1061,6 @@ define KernelPackage/mwifiex-pcie/description
>>>   Kernel modules for Marvell 802.11n/802.11ac PCIe Wireless cards
>>>  endef
>>>  
>>> -
>>> -# Prism54 drivers
>>> -P54PCIFW:=2.13.12.0.arm
>>> -P54USBFW:=2.13.24.0.lm87.arm
>>> -P54SPIFW:=2.13.0.0.a.13.14.arm
>>> -
>>> -define Download/p54usb
>>> -  FILE:=$(P54USBFW)
>>> -  URL:=http://daemonizer.de/prism54/prism54-fw/fw-usb
>>> -  MD5SUM:=8e8ab005a4f8f0123bcdc51bc25b47f6
>>> -endef
>>> -$(eval $(call Download,p54usb))
>>> -
>>> 

Re: [LEDE-DEV] [PATCH 2/2] prism54-firmware: add also other p54 firmware to own package

2016-06-30 Thread John Crispin
i have already added this to my staging tree, feel free to send a ptch
that i can fold into haukes patch

John

On 30/06/2016 20:53, Christian Lamparter wrote:
> On Wednesday, June 29, 2016 11:13:01 PM Hauke Mehrtens wrote:
>> From: Hauke Mehrtens 
>>
>> Extract the other p54 firmware files into the prism54-firmware package.
>>
>> Signed-off-by: Hauke Mehrtens 
> Hey, that's really nice of you.
> 
> Would it be possible to set PKG_VERSION to like 1.0 and add a variable
> for PRISM54FW:=1.0.4.3.arm and set the PKG_SOURCE:=$(PRISM54FW) instead?
> 
> Regards,
> Christian
> 
>> ---
>>  package/firmware/prism54-firmware/Makefile | 75 
>> --
>>  package/kernel/mac80211/Makefile   | 48 ++-
>>  2 files changed, 75 insertions(+), 48 deletions(-)
>>
>> diff --git a/package/firmware/prism54-firmware/Makefile 
>> b/package/firmware/prism54-firmware/Makefile
>> index 759e6b0..2f39dc9 100644
>> --- a/package/firmware/prism54-firmware/Makefile
>> +++ b/package/firmware/prism54-firmware/Makefile
>> @@ -9,20 +9,70 @@ PKG_NAME:=prism54-firmware
>>  PKG_VERSION:=1.0.4.3
>>  PKG_RELEASE:=1
>>  
>> +PRG_URL:=https://daemonizer.de/prism54/prism54-fw/
>> +
>>  # Prism54 FullMAC firmware (jbnore.free.fr seems to be rather slow, so we 
>> use daemonizer.de)
>>  PKG_SOURCE:=$(PKG_VERSION).arm
>> -PKG_SOURCE_URL:=https://daemonizer.de/prism54/prism54-fw/fw-fullmac/
>> +PKG_SOURCE_URL:=$(PRG_URL)/fw-fullmac/
>>  PKG_MD5SUM:=8bd4310971772a486b9784c77f8a6df9
>>  
>>  include $(INCLUDE_DIR)/package.mk
>>  
>> -define Package/prism54-firmware
>> +
>> +# Prism54 drivers
>> +P54USBFW:=2.13.24.0.lm87.arm
>> +P54PCIFW:=2.13.12.0.arm
>> +P54SPIFW:=2.13.0.0.a.13.14.arm
>> +
>> +define Download/p54-usb-firmware
>> +  FILE:=$(P54USBFW)
>> +  URL:=$(PRG_URL)/fw-usb
>> +  MD5SUM:=8e8ab005a4f8f0123bcdc51bc25b47f6
>> +endef
>> +$(eval $(call Download,p54-usb-firmware))
>> +
>> +define Download/p54-pci-firmware
>> +  FILE:=$(P54PCIFW)
>> +  URL:=$(PRG_URL)/fw-softmac
>> +  MD5SUM:=ff7536af2092b1c4b21315bd103ef4c4
>> +endef
>> +$(eval $(call Download,p54-pci-firmware))
>> +
>> +define Download/p54-spi-firmware
>> +  FILE:=$(P54SPIFW)
>> +  URL:=$(PRG_URL)/stlc4560
>> +  MD5SUM:=42661f8ecbadd88012807493f596081d
>> +endef
>> +$(eval $(call Download,p54-spi-firmware))
>> +
>> +
>> +define Package/prism54-firmware-default
>>SECTION:=firmware
>>CATEGORY:=Firmware
>> -  URL:=https://daemonizer.de/prism54/prism54-fw
>> +  URL:=https://daemonizer.de/prism54/prism54-fw/
>> +endef
>> +
>> +define Package/prism54-firmware
>> +$(Package/prism54-firmware-default)
>>TITLE:=prism54 firmware
>>  endef
>>  
>> +define Package/p54-usb-firmware
>> +$(Package/prism54-firmware-default)
>> +  TITLE:=p54-usb firmware
>> +endef
>> +
>> +define Package/p54-pci-firmware
>> +$(Package/prism54-firmware-default)
>> +  TITLE:=p54-pci firmware
>> +endef
>> +
>> +define Package/p54-spi-firmware
>> +$(Package/prism54-firmware-default)
>> +  TITLE:=p54-spi firmware
>> +endef
>> +
>> +
>>  define Build/Prepare
>>  mkdir -p $(PKG_BUILD_DIR)
>>  endef
>> @@ -36,4 +86,23 @@ define Package/prism54-firmware/install
>>  $(INSTALL_DATA) $(DL_DIR)/$(PKG_SOURCE) $(1)/lib/firmware/isl3890
>>  endef
>>  
>> +define Package/p54-usb-firmware/install
>> +$(INSTALL_DIR) $(1)/lib/firmware
>> +$(INSTALL_DATA) $(DL_DIR)/$(P54USBFW) $(1)/lib/firmware/isl3887usb
>> +endef
>> +
>> +define Package/p54-pci-firmware/install
>> +$(INSTALL_DIR) $(1)/lib/firmware
>> +$(INSTALL_DATA) $(DL_DIR)/$(P54PCIFW) $(1)/lib/firmware/isl3886pci
>> +endef
>> +
>> +define Package/p54-spi-firmware/install
>> +$(INSTALL_DIR) $(1)/lib/firmware
>> +$(INSTALL_DATA) $(DL_DIR)/$(P54SPIFW) $(1)/lib/firmware/3826.arm
>> +endef
>> +
>> +
>>  $(eval $(call BuildPackage,prism54-firmware))
>> +$(eval $(call BuildPackage,p54-usb-firmware))
>> +$(eval $(call BuildPackage,p54-pci-firmware))
>> +$(eval $(call BuildPackage,p54-spi-firmware))
>> diff --git a/package/kernel/mac80211/Makefile 
>> b/package/kernel/mac80211/Makefile
>> index bee0723..38eb4af 100644
>> --- a/package/kernel/mac80211/Makefile
>> +++ b/package/kernel/mac80211/Makefile
>> @@ -1061,33 +1061,6 @@ define KernelPackage/mwifiex-pcie/description
>>   Kernel modules for Marvell 802.11n/802.11ac PCIe Wireless cards
>>  endef
>>  
>> -
>> -# Prism54 drivers
>> -P54PCIFW:=2.13.12.0.arm
>> -P54USBFW:=2.13.24.0.lm87.arm
>> -P54SPIFW:=2.13.0.0.a.13.14.arm
>> -
>> -define Download/p54usb
>> -  FILE:=$(P54USBFW)
>> -  URL:=http://daemonizer.de/prism54/prism54-fw/fw-usb
>> -  MD5SUM:=8e8ab005a4f8f0123bcdc51bc25b47f6
>> -endef
>> -$(eval $(call Download,p54usb))
>> -
>> -define Download/p54pci
>> -  FILE:=$(P54PCIFW)
>> -  URL:=http://daemonizer.de/prism54/prism54-fw/fw-softmac
>> -  MD5SUM:=ff7536af2092b1c4b21315bd103ef4c4
>> -endef
>> -$(eval $(call Download,p54pci))
>> -
>> -define Download/p54spi
>> -  FILE:=$(P54SPIFW)
>> -  

[LEDE-DEV] Need /dev/mtd4 from TPLink TL-WR941ND v6

2016-06-30 Thread Dennis Schneck
Hello,
has anybody a TPLink TL-WR941ND Ver. 6.0.
Can you please export with dd the Partition: /dev/mtd4 an offer me a Download ?
Thanks
Dennis

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


[LEDE-DEV] [PATCH] Bridge: Fix ipv6 mc snooping if bridge has no ipv6 address

2016-06-30 Thread Daniel Danzberger
This patch is a backport for current LEDE 4.4 Kernels.
It is already upstream, for linux-next and stable.
The initial commit message is below:

The bridge is falsly dropping ipv6 mulitcast packets if there is:
 1. No ipv6 address assigned on the brigde.
 2. No external mld querier present.
 3. The internal querier enabled.

When the bridge fails to build mld queries, because it has no
ipv6 address, it slilently returns, but keeps the local querier enabled.
This specific case causes confusing packet loss.

Ipv6 multicast snooping can only work if:
 a) An external querier is present
 OR
 b) The bridge has an ipv6 address an is capable of sending own queries

Otherwise it has to forward/flood the ipv6 multicast traffic,
because snooping cannot work.

This patch fixes the issue by adding a flag to the bridge struct that
indicates that there is currently no ipv6 address assinged to the bridge
and returns a false state for the local querier in
__br_multicast_querier_exists().

Special thanks to Linus Lüssing.

Signed-off-by: Daniel Danzberger 
---
 ...mc_snooping_if_bridge_has_no_ipv6_address.patch | 76 ++
 1 file changed, 76 insertions(+)
 create mode 100644 
target/linux/generic/patches-4.4/646-bridge_fix_ipv6_mc_snooping_if_bridge_has_no_ipv6_address.patch

diff --git 
a/target/linux/generic/patches-4.4/646-bridge_fix_ipv6_mc_snooping_if_bridge_has_no_ipv6_address.patch
 
b/target/linux/generic/patches-4.4/646-bridge_fix_ipv6_mc_snooping_if_bridge_has_no_ipv6_address.patch
new file mode 100644
index 000..e0bdbae
--- /dev/null
+++ 
b/target/linux/generic/patches-4.4/646-bridge_fix_ipv6_mc_snooping_if_bridge_has_no_ipv6_address.patch
@@ -0,0 +1,76 @@
+diff --git a/net/bridge/br_multicast.c b/net/bridge/br_multicast.c
+index c8c2a8a..d063a10 100644
+--- a/net/bridge/br_multicast.c
 b/net/bridge/br_multicast.c
+@@ -465,8 +465,11 @@ static struct sk_buff 
*br_ip6_multicast_alloc_query(struct net_bridge *br,
+   if (ipv6_dev_get_saddr(dev_net(br->dev), br->dev, >daddr, 0,
+  >saddr)) {
+   kfree_skb(skb);
++  br->has_ipv6_addr = 0;
+   return NULL;
+   }
++
++  br->has_ipv6_addr = 1;
+   ipv6_eth_mc_map(>daddr, eth->h_dest);
+ 
+   hopopt = (u8 *)(ip6h + 1);
+@@ -1768,6 +1771,7 @@ void br_multicast_init(struct net_bridge *br)
+   br->ip6_other_query.delay_time = 0;
+   br->ip6_querier.port = NULL;
+ #endif
++  br->has_ipv6_addr = 1;
+ 
+   spin_lock_init(>multicast_lock);
+   setup_timer(>multicast_router_timer,
+diff --git a/net/bridge/br_private.h b/net/bridge/br_private.h
+index e24abfd..3dd7e2c 100644
+--- a/net/bridge/br_private.h
 b/net/bridge/br_private.h
+@@ -303,6 +303,7 @@ struct net_bridge
+   u8  multicast_disabled:1;
+   u8  multicast_querier:1;
+   u8  multicast_query_use_ifaddr:1;
++  u8  has_ipv6_addr:1;
+ 
+   u32 hash_elasticity;
+   u32 hash_max;
+@@ -577,10 +578,22 @@ static inline bool br_multicast_is_router(struct 
net_bridge *br)
+ 
+ static inline bool
+ __br_multicast_querier_exists(struct net_bridge *br,
+-struct bridge_mcast_other_query *querier)
++  struct bridge_mcast_other_query *querier,
++  const bool is_ipv6)
+ {
++  bool own_querier_enabled;
++
++  if (br->multicast_querier) {
++  if (is_ipv6 && !br->has_ipv6_addr)
++  own_querier_enabled = false;
++  else
++  own_querier_enabled = true;
++  } else {
++  own_querier_enabled = false;
++  }
++
+   return time_is_before_jiffies(querier->delay_time) &&
+- (br->multicast_querier || timer_pending(>timer));
++ (own_querier_enabled || timer_pending(>timer));
+ }
+ 
+ static inline bool br_multicast_querier_exists(struct net_bridge *br,
+@@ -588,10 +601,12 @@ static inline bool br_multicast_querier_exists(struct 
net_bridge *br,
+ {
+   switch (eth->h_proto) {
+   case (htons(ETH_P_IP)):
+-  return __br_multicast_querier_exists(br, >ip4_other_query);
++  return __br_multicast_querier_exists(br,
++  >ip4_other_query, false);
+ #if IS_ENABLED(CONFIG_IPV6)
+   case (htons(ETH_P_IPV6)):
+-  return __br_multicast_querier_exists(br, >ip6_other_query);
++  return __br_multicast_querier_exists(br,
++  >ip6_other_query, true);
+ #endif
+   default:
+   return false;
-- 
2.8.1


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


[LEDE-DEV] [PATCH] netifd: remove wireless device when device fails to setup

2016-06-30 Thread Eduardo Abinader
Ensure wireless device struct is removed, when it fails to be set up,
due to a invalid configuration, hence enabling the wireless dev
to be set up again, when a new valid configuration is set.

Signed-off-by: Eduardo Abinader 
---
 wireless.c | 4 
 1 file changed, 4 insertions(+)

diff --git a/wireless.c b/wireless.c
index 34dd328..bc31d4a 100644
--- a/wireless.c
+++ b/wireless.c
@@ -336,6 +336,10 @@ wireless_device_mark_down(struct wireless_device *wdev)
 
wireless_process_kill_all(wdev, SIGTERM, true);
 
+   if (wdev->state == IFS_SETUP && !wdev->autostart) {
+   wdev->config_state = IFC_REMOVE;
+   }
+
wdev->cancel = false;
wdev->state = IFS_DOWN;
wireless_device_free_state(wdev);
-- 
2.5.0

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] adding luci to snapshot images

2016-06-30 Thread John Crispin


On 29/06/2016 16:54, Jo-Philipp Wich wrote:
> Hi,
> 
> it would certainly help to bridge the gap until the #1 release and it
> would give more testing exposure to the ui...
> 
> My observation on the matter is this:
> People who do *not* want to have the ui included are either building
> from source or using the IB anyway and those users *requiring* a ui tend
> to be unable to spin their own builds (no Linux os at hand, too hard, ...)
> 
> So personally I'd lean toward adding LuCI to the snapshots but would
> await further feedback on it.
> 
> ~ Jo
> 

Hi Jo,

if you add this then please make it depend on !SMALL_FLASH

John

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] Add Synopsys brand to Wiki

2016-06-30 Thread Alexey Brodkin
Hi Thomas,

Thanks for that.

Now looks like "target" has to be added as well.

I'll need 2 targets:
 1) arc770
 2) archs38

Thanks in advance,
Alexey

On Wed, 2016-06-29 at 20:57 +0200, Thomas Endt wrote:
> Done.
> 
> Regards, Thomas
> 
> > 
> > -Ursprüngliche Nachricht-
> > Von: Alexey Brodkin [mailto:alexey.brod...@synopsys.com]
> > Gesendet: Mittwoch, 29. Juni 2016 19:18
> > An: t...@gmx.de
> > Cc: lede-dev@lists.infradead.org; j...@mein.io
> > Betreff: Re: Add Synopsys brand to Wiki
> > 
> > Hi Thomas,
> > 
> > Could you please assist me in adding new brand (Synopsys) to OpenWRT
> > Wiki ToH?
> > 
> > That's my original request sent to Lede dev mailing list:
> > http://lists.infradead.org/pipermail/lede-dev/2016-June/001551.html
> > 
> > -Alexey
> > 
> > On Wed, 2016-06-29 at 15:42 +0200, Jo-Philipp Wich wrote:
> > > 
> > > Hi Alexey,
> > > 
> > > please contact Thomas Endt  for assistance on adding
> > > brands to the OpenWrt Wiki ToH.
> > > 
> > > ~ Jo=
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] fstools testing help

2016-06-30 Thread Álvaro Fernández Rojas
I will try to test it on RPi tonight.

Regards,
Álvaro.

El 30/6/16 a las 9:21, John Crispin escribió:
> Hi,
> 
> i have just merged to fstools patches into my staging tree that address
> a double mount issue and add back ext4 support. the ext4 patch
> previously broke rPi and other ext4 targets, but i thini with josua's
> patch applied it should work. i have done some basic testing already my
> end but would like further etst coverage to make sure there are no
> hidden regressions
> 
> things that should be tested are
> 
> * does ext4 mount work on eMMC
> * does rootfs mount work on rPi
> * does extroot still work with flat mounts
> * does extroot still work with flat overlay mounts
> 
> i have only tested the last one so far.
> 
>   John
> 

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] [PATCH] e2fsprogs: fix build problem with very old libmagic

2016-06-30 Thread Dirk Neukirchen
On 29.06.2016 23:14, Hauke Mehrtens wrote:
> From: Hauke Mehrtens 
> 
> The libmagic shipped with RedHat 5 does not define

As a reference - RHEL4: Mar/2017, RHEL5:Nov/2020 
src: https://access.redhat.com/support/policy/updates/errata

I have recommended/tested build OS on my todo list 


> MAGIC_NO_CHECK_COMPRESS and MAGIC_NO_CHECK_COMPRESS.

c/p error ?

e2fsprogs should
> check for that otherwise the build will fail.
> 
> Signed-off-by: Hauke Mehrtens 
> ---
>  tools/e2fsprogs/patches/010-old-libmagic.patch | 11 +++
>  1 file changed, 11 insertions(+)
>  create mode 100644 tools/e2fsprogs/patches/010-old-libmagic.patch
> 
> diff --git a/tools/e2fsprogs/patches/010-old-libmagic.patch 
> b/tools/e2fsprogs/patches/010-old-libmagic.patch
> new file mode 100644
> index 000..5ba8a54
> --- /dev/null
> +++ b/tools/e2fsprogs/patches/010-old-libmagic.patch
> @@ -0,0 +1,11 @@
> +--- a/lib/support/plausible.c
>  b/lib/support/plausible.c
> +@@ -247,7 +247,7 @@ int check_plausibility(const char *devic
> + return 0;
> + }
> + 
> +-#ifdef HAVE_MAGIC_H
> ++#if defined(HAVE_MAGIC_H) && defined(MAGIC_NO_CHECK_COMPRESS) && 
> defined(MAGIC_NO_CHECK_COMPRESS)

c/p error ?

> + if ((flags & CHECK_FS_EXIST) &&
> + !getenv("E2FSPROGS_LIBMAGIC_SUPPRESS") &&
> + magic_library_available()) {
> 


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev