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_N
On 29/06/2016 23:14, Hauke Mehrtens wrote:
> From: Hauke Mehrtens
>
> The libmagic shipped with RedHat 5 does not define
> MAGIC_NO_CHECK_COMPRESS and MAGIC_NO_CHECK_COMPRESS. e2fsprogs should
> check for that otherwise the build will fail.
>
can you send this upstream aswell please ?
On 30/06/2016 04:20, L. D. Pinney wrote:
> The NixCore X1 is a Ralink/MediaTek rt5350 WiFi Module.
>
> http://nixcores.com/
>
> Signed-off-by: L. D. Pinney
> Acked-by: Drew Gaylo
>
this is a different patch to drew's version 5. please incorporate all
the feedback we already gave to drew.
On 29 June 2016 at 16:54, Jo-Philipp Wich wrote:
> 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, t
The NixCore X1 is a Ralink/MediaTek rt5350 WiFi Module.
http://nixcores.com/
Signed-off-by: L. D. Pinney
Acked-by: Drew Gaylo
---
target/linux/ramips/base-files/etc/board.d/02_network | 1 +
target/linux/ramips/base-files/lib/ramips.sh | 3 +++
target/linux/ramips/base-files/lib/
rootfs part needs to be aligned to erase block size which is passed as
the 6th argument to Image/Build/Seama and is now 65536 since commit
commit 5119ee9 "ar71xx: fix bogus hardcoded kernel image size for Seama
images (fixes #20585)", but $(($(6) - 64)) still assumes that the
argument is a limit o
Signed-off-by: Yousong Zhou
---
target/linux/ar71xx/image/generic.mk | 224 +--
1 file changed, 112 insertions(+), 112 deletions(-)
diff --git a/target/linux/ar71xx/image/generic.mk
b/target/linux/ar71xx/image/generic.mk
index 6802501..3e3dc69 100644
--- a/target
Remove kmod-crypto-deflate and kmod-ledtrig-gpio as the device works the
same by default without them
Signed-off-by: Yousong Zhou
---
target/linux/ar71xx/image/generic.mk| 15 +--
target/linux/ar71xx/image/legacy-devices.mk | 8
2 files changed, 9 insertions(+), 14
The patch on HiWiFi HC6361 has been run-tested.
The patch on seama image build has only been compile-tested and inspected
manually. I'd like to wait for some acks before it get merged.
v1 -> v2:
- Fix making making sysupgrade image: the .seama ext of output file seama
utility was previously
Signed-off-by: Yousong Zhou
---
target/linux/ar71xx/image/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/target/linux/ar71xx/image/Makefile
b/target/linux/ar71xx/image/Makefile
index 2380a62..ced1610 100644
--- a/target/linux/ar71xx/image/Makefile
+++ b/target/linux/ar71xx/image/Mak
This folds 550-ath9k_add_ar9280_gpio_chip.patch into
548-ath9k_enable_gpio_chip.patch because the former patch only extends
code which is introduced in the latter.
Signed-off-by: Martin Blumenstingl
---
.../patches/548-ath9k_enable_gpio_chip.patch | 14 ++-
.../patches/549-ath9k_en
This re-uses the "number of GPIOs" which are already configured per
ath9k chip/revision during chip initialization in hw.c's
ath9k_hw_fill_cap_info().
It also sets the parent device of the GPIO controller which is not only
good practice, but it will also allow using the ath9k device as GPIO
control
This allows gpiolib to re-use ath9k's devicetree node as GPIO
controller.
Example:
ath9k: ath9k@0 {
#gpio-cells = <2>;
gpio-controller;
}
Now the ath9k node can be used just like any other GPIO controller:
gpios = <&ath9k 1 GPIO_ACTIVE_HIGH>;
Signed-off-by: Martin Blumens
This enables ath9k's built-in GPIO controller for all chip versions
(instead of an explicit whitelist). This also allows us to get rid of
some duplicate code between hw.c and gpio.c because hw.c already
determines the number of GPIOs.
Signed-off-by: Martin Blumenstingl
---
.../patches/548-ath9k_
From: Mathias Kresin
Signed-off-by: Mathias Kresin
---
.../100-remove-cryptoapi-dependencies.patch| 90 --
.../mac80211/patches/530-ath9k_extra_leds.patch| 12 +--
.../patches/541-ath9k_rx_dma_stop_check.patch | 4 +-
.../patches/910-01-add-support-for-mt76
From: Hauke Mehrtens
This adds this commit from normal libnl to libnl-tiny:
https://github.com/tgraf/libnl/commit/2dbc1ca76c5b82c40749e609eb83877418abb006
commit 2dbc1ca76c5b82c40749e609eb83877418abb006
Author: dima
Date: Wed Oct 13 17:53:34 2010 +0300
Generic Netlink multicast groups su
From: Hauke Mehrtens
The libmagic shipped with RedHat 5 does not define
MAGIC_NO_CHECK_COMPRESS and MAGIC_NO_CHECK_COMPRESS. 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
From: Hauke Mehrtens
Instead of downloading the firmware for prism54 devices in the
wireless.mk do it in an extra package Makefile. To ship the complete
source code Intel ships our modified OpenWrt/LEDE + the content of the
dl directory. We do not want to have any files in the dl/ directory
which
From: Hauke Mehrtens
Extract the other p54 firmware files into the prism54-firmware package.
Signed-off-by: Hauke Mehrtens
---
package/firmware/prism54-firmware/Makefile | 75 --
package/kernel/mac80211/Makefile | 48 ++-
2 files changed, 7
hi,
the webserver will see an update to F24 tonight and get more disk space.
there will be several reboots over the next few hours. if all goes well
we will be back to normal operational mode in a few hours.
John
___
Lede-dev mailing list
Lede-
On Wed, Jun 29, 2016 at 2:43 PM, David Lang wrote:
> I agree. There may be some devices with extremely small flash that can't fit
> luci, but otherwise I think it should be on the default images that people
> are pointed at.
> Having a second set of images without luci isn't a bad idea, but if for
I agree. There may be some devices with extremely small flash that can't fit
luci, but otherwise I think it should be on the default images that people are
pointed at.
Having a second set of images without luci isn't a bad idea, but if forced to
choose, I would say they should have luci
Davi
On 29/06/16 15: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
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,
Remove kmod-crypto-deflate and kmod-ledtrig-gpio as the device works the
same by default without them
Signed-off-by: Yousong Zhou
---
target/linux/ar71xx/image/generic.mk| 15 +--
target/linux/ar71xx/image/legacy-devices.mk | 8
2 files changed, 9 insertions(+), 14
rootfs part needs to be aligned to erase block size which is passed as
the 6th argument to Image/Build/Seama and is now 65536 since commit
commit 5119ee9 "ar71xx: fix bogus hardcoded kernel image size for Seama
images (fixes #20585)", but $(($(6) - 64)) still assumes that the
argument is a limit o
Signed-off-by: Yousong Zhou
---
target/linux/ar71xx/image/generic.mk | 224 +--
1 file changed, 112 insertions(+), 112 deletions(-)
diff --git a/target/linux/ar71xx/image/generic.mk
b/target/linux/ar71xx/image/generic.mk
index 6802501..3e3dc69 100644
--- a/target
Signed-off-by: Yousong Zhou
---
target/linux/ar71xx/image/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/target/linux/ar71xx/image/Makefile
b/target/linux/ar71xx/image/Makefile
index 2380a62..ced1610 100644
--- a/target/linux/ar71xx/image/Makefile
+++ b/target/linux/ar71xx/image/Mak
The patch on HiWiFi HC6361 has been run-tested.
The patch on seama image build has only been compile-tested and inspected
manually. I'd like to wait for some acks before it get merged.
Yousong Zhou (4):
ar71xx: hiwifi-hc6361: move packages selection to generic.mk
ar71xx: image: remove duplic
While I think adding luci will be convenient for many users.
I feel that the initial release is the paramount issue and that builds
containing luci could be added later.
A nice solution would be to offer downloads built w/wo lucias well
as adding 'luci' to the filename if built with luci.
On
Totally agree with the observation.
+1 for including LuCI as default.
-Original Message-
From: Lede-dev [mailto:lede-dev-boun...@lists.infradead.org] On Behalf Of
Jo-Philipp Wich
Sent: miércoles, 29 de junio de 2016 09:54 a.m.
To: lede-dev@lists.infradead.org
Subject: Re: [LEDE-DEV] adding
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 te
Hi Jo,
can we add luci to snapshot images until the first release is out ?
people are using the images and seem to be confused by there being no luci.
personally i would prefer to not include luci in snapshots to keep them
as minimal as possible but until we have a first release it would make
sen
Hi Hans,
pushed to netifd.git - thank you!
~ Jo
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
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
Fixes missing link state event propagation for an aliased device in case a new
device is added
as the link state has the last known status of the old device possible
resulting into
no link state change detection.
Signed-off-by: Hans Dedecker
---
alias.c | 4 +++-
1 file changed, 3 insertions(+
Hi!
I got an interesting bug on a quite ancient ath9k system which used
to run stable on BB.
Can anyone with more insight of ath9k tell me what's going on?
DISTRIB_RELEASE='Chaos Calmer'
DISTRIB_REVISION='r49378'
system type : Atheros AR9132 rev 2
machine : TP-LINK T
From: Ram Chandra Jangir
This change will enables eMMC (ext4 fs) boot support, when we try to boot
from eMMC card then it will read partition names from
/sys/block/mmcblkX/mmcblkXY/uevent
file and will mount the rootfs_data partition as ext4fs overlay.
Signed-off-by: Ram Chandra Jangir
---
CMa
From: Josua Mayer
When there is a) no rootfs_data overlay partition,
and b) /dev/root points to an ext4 partition
the partition would be mounted twice, once as / and then as /overlay.
The essence of this change is to return before mounting /overlay,
if /dev/root has been mounted as /.
Signed-off
On 29/06/2016 12:34, Josua Mayer wrote:
>
>
> Am 29.06.2016 um 12:21 schrieb John Crispin:
>>
>>
>> On 29/06/2016 12:11, Josua Mayer wrote:
>>> Hi John,
>>>
>>> thansk for taking a look. I actually sent it this way by intention,
>>> looking to get in touch with someone who had the original bug.
Am 29.06.2016 um 12:21 schrieb John Crispin:
>
>
> On 29/06/2016 12:11, Josua Mayer wrote:
>> Hi John,
>>
>> thansk for taking a look. I actually sent it this way by intention,
>> looking to get in touch with someone who had the original bug.
>>
>> Am 29.06.2016 um 08:30 schrieb John Crispin:
>
On 29/06/2016 12:11, Josua Mayer wrote:
> Hi John,
>
> thansk for taking a look. I actually sent it this way by intention,
> looking to get in touch with someone who had the original bug.
>
> Am 29.06.2016 um 08:30 schrieb John Crispin:
>> Hi,
>>
>> the patch is an attachement making inline com
Hi John,
thansk for taking a look. I actually sent it this way by intention,
looking to get in touch with someone who had the original bug.
Am 29.06.2016 um 08:30 schrieb John Crispin:
> Hi,
>
> the patch is an attachement making inline commenting impossible. please
> send patches inline
>From 5
43 matches
Mail list logo
