Hi,
On 14 June 2017 at 14:28, Yousong Zhou wrote:
> Signed-off-by: Yousong Zhou
> ---
> package/base-files/Makefile | 2 +-
> package/base-files/files/lib/functions.sh | 54
> +++
> 2 files changed, 28 insertions(+), 28 deletions(-)
>
> diff --git a/p
On 29 May 2017 at 09:03, John Crispin wrote:
> (resend, this time as plain text)
>
>
> Hi,
>
> here is a V3 of the remerge proposal, I tried to fold all the comments
> people made into it, if anything is missing let me know. Please remeber that
> post remerge anything can be voted on, so clutterin
Hi John,
On 2 August 2017 at 06:36, John Crispin wrote:
>
>
> On 31/07/17 18:11, John Crispin wrote:
>>
>> Hi,
>>
>> I rebased my ages old kernel patch cleanup series. It can be found here
>> [1].
>>
>> the series annotates all patches and splits them up into 3 folders
>> backports/pending/hacks.
On 3 August 2017 at 18:03, Rafał Miłecki wrote:
> I have router with internal switch with 6 ports. The default config is:
> 0: LAN1
> 1: LAN2
> 2: LAN3
> 3: LAN4
> 4: WAN
> 5: CPU
>
> I want to use port 3 (LAN4) for something different. Another network,
> mwan, whatever. For that purpose I edited
Hi,
On 17 August 2017 at 15:05, Karl Palsson wrote:
> xz has supported multithreaded compression since 5.2 in 2014. Enable
> it's automatic support for this via the "-T 0" flag.
its ;p
>
> Previously: (xz -7e)
> real3m13.631s
>
> Now: (xz -T 0 -7e)
> real1m23.051s
After playing around
Hi,
On 20 August 2017 at 17:32, Daniel Gonzalez Cabanelas wrote:
> Add support for the Sercomm AD1018 router
>
> This a BCM6328 based board, 128 MB RAM, 128 MiB NAND flash,
> with an onboard BCM43217 wifi, 4 ethernet ports and 1 USB
> host port (not soldered).
>
> Since NAND flash chips aren't st
On 18 August 2017 at 15:06, Karl Palsson wrote:
>
> Bjørn Mork wrote:
>> This looks yucky. Experimenting a bit, I see that the result
>> with
>>
>> a) -T 0 depends on multi-core vs single-core
>> b) -T 1 is always different from the output of -T x where x > 1
>> c) -T x where x > 1 is indepen
On 17 November 2017 at 01:41, wrote:
> From: Luiz Angelo Daros de Luca
>
> Only backup /aaa/bbb/ccc if /rom/aaa/bbb/ccc does not exist
> or /aaa/bbb/ccc is different from /rom/aaa/bbb/ccc.
>
> Signed-off-by: Luiz Angelo Daros de Luca
> ---
> package/base-files/files/sbin/sysupgrade | 6 --
On 17 November 2017 at 11:35, Matthias Schiffer
wrote:
> On 11/17/2017 10:14 AM, Jonas Gorski wrote:
>> On 17 November 2017 at 01:41, wrote:
>>> From: Luiz Angelo Daros de Luca
>>>
>>> Only backup /aaa/bbb/ccc if /rom/aaa/bbb/ccc does not exist
>>&g
6.[ch] Sorry forgot adding them. Thanks for
Graham Gower ")
Signed-off-by: Jonas Gorski
---
libopkg/sha256.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libopkg/sha256.c b/libopkg/sha256.c
index e0c4e3e0d423..5848799c0260 100644
--- a/libopkg/sha256.c
+++ b/libopk
On 17 November 2017 at 13:23, Jonas Gorski wrote:
> On 17 November 2017 at 11:35, Matthias Schiffer
> wrote:
>> On 11/17/2017 10:14 AM, Jonas Gorski wrote:
>>> On 17 November 2017 at 01:41, wrote:
>>>> From: Luiz Angelo Daros de Luca
>>>>
>>&
On 11 December 2017 at 10:04, Rosen Penev wrote:
> Mainly plugging memory leaks. Size reduction as well. The calloc change
> accounts for 272 bytes on this machine for some reason...
Please state the exact errors found by cppcheck so we don't have to
guess what it found.
Regards
Jonas
___
On 12 December 2017 at 21:03, Jo-Philipp Wich wrote:
> Hi Piotr,
>
> my rough idea was to somehow tie the manifest generation to the "define
> Device/*" macros present in the image building code because there you
> have all required information in a central place:
>
> - unique board identifier
>
Hi,
On 12 December 2017 at 23:05, Jo-Philipp Wich wrote:
> Hi Rafał,
>
> in principle fine with me - but I guess all restrictions will be in the
> form { : true } so I'd rather make it an array.
>
> Also since a restriction implies something not possible, I'd drop the
> "no_" prefix too. So in th
On 12 December 2017 at 23:13, Jo-Philipp Wich wrote:
> Hi,
>
>> I'd argue the no_ prefix makes it more clear that these restrictions
>> say what is prohibited, not what is allowed.
>
> What about calling it "prohibit" instead of "restrictions" then? That
> would make it both terse and unambiguous.
Hi Nishant,
On 5 January 2018 at 09:16, Nishant Sharma wrote:
> Hi,
>
> First of all, congratulations on re-merge of OpenWrt and LEDE.
>
> Now to the problem being faced. I am trying to build OpenWrt for Espressobin
> (http://espressobin.net) as described in their wiki at
> http://wiki.espressobi
Hi Nishant,
On 5 January 2018 at 10:48, Nishant Sharma wrote:
> Hi Jonas,
>
> On Friday 05 January 2018 02:24 PM, Jonas Gorski wrote:
> (http://espressobin.net) as described in their wiki at
>>>
>>>
>>> http://wiki.espressobin.net/tiki-ind
On 5 January 2018 at 10:53, Jo-Philipp Wich wrote:
> Introduce a name-agnostic PROJECT_GIT variable poiting to
> https://git.openwrt.org/ and declare LEDE_GIT and OPENWRT_GIT
> as aliases to it.
>
> After some transition time we can drop this alias variables.
>
> Signed-off-by: Jo-Philipp Wich
G
Hi,
On 18 January 2018 at 10:50, Koen Vandeputte
wrote:
> A lot of targets have more than sufficient space to allow
> building the kernel for speed iso size.
>
> Export this performance option to the main config:
>
> - Making it easy accessable for users
> - Discarding the need to adjust it in th
On 22 January 2018 at 10:20, Koen Vandeputte
wrote:
>
>
> On 2018-01-21 13:37, Jonas Gorski wrote:
>>
>> Hi,
>>
>> On 18 January 2018 at 10:50, Koen Vandeputte
>> wrote:
>>>
>>> A lot of targets have more than sufficient space to allow
&
Hi,
On 22 January 2018 at 07:16, perillamint wrote:
> Hello,
>
> I'm currently porting LEDE(wait, OpenWRT now?) on Intel Galileo.
>
> Since not every Intel Quark board has GPIO multiplexer chips like
> Galileo, I think I have to separate board specific components into
> separate Kconfig and keep
On 30 January 2018 at 21:04, Andrey Jr. Melnikov wrote:
> Hauke Mehrtens wrote:
>
>
>> On 01/30/2018 04:32 PM, Andrey Jr. Melnikov wrote:
>> > Evgeniy Didin wrote:
>> >
>> >> While building mpi.ko module with stable Linux v4.14.14 an error occured:
>> >>> ERROR: "abort" [lib/mpi/mpi.ko] undefine
On 10 February 2018 at 13:41, wrote:
> I'm using extroot on SD card in 4G dongle attached to USB of my TP-Link
> Archer C2. For reasons unknown to me it started to take more than 10 seconds
> to show among devices, this patch adds 2 more detection attempts/delays to
> already existing 5s.
Jus
Hi,
On 13 February 2018 at 13:03, wrote:
> Hi Jonas,
>
> thanks for bringing kernel 4.9 and 4.14 to the brcm63xx target and therefore
> keeping
> them as 'active' devices (regarding development).
> I just tried 4.9 and 4.14 on my AV4202 and can't fully boot the thing due to
> JFFS2 errors.
> A
Hi,
On 15 October 2016 at 17:32, Rafał Miłecki wrote:
> Hi,
>
> After Holger & Alexander talk at OpenWrt Summit I started thinking
> about handling feeds in LEDE. Right now we simply point to external
> repositories within feeds.conf(.default):
> src-git packages https://git.lede-project.org/feed
Hi,
On 21 October 2016 at 13:15, Eddi De Pieri wrote:
> Hi,
>
> Here to raise your attention to https://github.com/pgid69/bcm63xx-phone
> projet.
For this one I'd like to see the receipts, i.e. to know these aren't
based on (leaked) sources, or if derived through reverse engineering
as a white
Hi,
On 17 November 2016 at 10:10, Rafał Miłecki wrote:
> On 17 November 2016 at 10:05, Rafał Miłecki wrote:
>> On 17 November 2016 at 09:57, Jo-Philipp Wich wrote:
>>> do you happen to know whether rev-list --count is available in all Git
>>> versions?
>>
>> I found it mentioned in various post
Hi,
On 16 November 2016 at 08:21, wrote:
> Hi,
>
> as I've been working on changes for kirkwood/board.d/01_leds:
>
> Previously, for ar71xx or ramips, I've been told to name LEDs like
> :: (1)
> before that, they were
> :: (2)
> (And we also renamed those of (2) in order to fit (1))
>
> On targe
Hi,
On 18 December 2016 at 02:19, Daniel Gonzalez Cabanelas
wrote:
> The internal phy is using wrong registers for the config interrupt function,
> causing incorrect behavior when detecting the link activity. Fix it.
>
> We cannot use the bcm_phy_config_intr function from the bcm-phy-lib.c
> beca
Hi,
On 21 December 2016 at 09:21, John Crispin wrote:
> This patch makes 3 symbols default, that get selected by the according code.
>
> arch/mips/bcm47xx/Kconfig: select SSB_B43_PCI_BRIDGE if PCI
> drivers/net/wireless/broadcom/b43legacy/Kconfig:select
> SSB_B43_PCI_BRIDGE
> driver
On 21 December 2016 at 09:34, John Crispin wrote:
>
>
> On 21/12/2016 09:31, Jonas Gorski wrote:
>> Hi,
>>
>> On 21 December 2016 at 09:21, John Crispin wrote:
>>> This patch makes 3 symbols default, that get selected by the according code.
>>&g
On 21 December 2016 at 10:42, John Crispin wrote:
>
>
> On 21/12/2016 09:39, Jonas Gorski wrote:
>> On 21 December 2016 at 09:34, John Crispin wrote:
>>>
>>>
>>> On 21/12/2016 09:31, Jonas Gorski wrote:
>>>> Hi,
>>>>
>>>
Hi,
On 14 February 2017 at 16:36, Daniel Gonzalez Cabanelas
wrote:
> Leds are wrong and a button is missing, fix them.
>
> Signed-off-by: Daniel Gonzalez Cabanelas
> diff --git a/target/linux/brcm63xx/dts/cpva502plus.dts
> b/target/linux/brcm63xx/dts/cpva502plus.dts
> index 6d9b5d3..3ddc459 100
Hi,
Please Cc me for brcm63xx patches, this makes it easier for me to
apply them (especially if they get mangled by patchwork).
On 12 February 2017 at 14:48, Anthony Sepa via Lede-dev
wrote:
> The sender domain has a DMARC Reject/Quarantine policy which disallows
> sending mailing list messages
Hi,
On 17 February 2017 at 14:53, Rafał Miłecki wrote:
> I was doing some fun experiments with ssb/bcma/b43 as a research based on:
> [PATCH RFC] kernel: allow selecting kmod-ssb on TARGET_brcm47xx_mips74k
>
> I was trying to build 2 variants of ssb package and 2 variants of b43
> package.
> It d
Hi,
On 16 February 2017 at 02:14, Daniel Danzberger wrote:
> Calling opkg with --no-configure prevents opkg
> from running the configuration of the package (postinstall scripts ..etc)
>
> This way opkg will only install the package, without restarting the service
> for example.
What's the use
On 17 February 2017 at 15:20, Daniel wrote:
> 2017-02-17 15:06 GMT+01:00 Jonas Gorski :
>> Hi,
>>
>> On 14 February 2017 at 16:36, Daniel Gonzalez Cabanelas
>> wrote:
>>> Leds are wrong and a button is missing, fix them.
>>>
>>> Signed-off-
On 8 February 2017 at 04:56, Florian Fainelli wrote:
> 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.
>
On 17 February 2017 at 15:38, Rafał Miłecki wrote:
> On 17 February 2017 at 15:14, Jonas Gorski wrote:
>> On 17 February 2017 at 14:53, Rafał Miłecki wrote:
>>> I was doing some fun experiments with ssb/bcma/b43 as a research based on:
>>> [PATCH RFC] kernel:
On 17 February 2017 at 17:56, Rafał Miłecki wrote:
> On 17 February 2017 at 16:06, Jonas Gorski wrote:
>> On 17 February 2017 at 15:38, Rafał Miłecki wrote:
>>> On 17 February 2017 at 15:14, Jonas Gorski wrote:
>>>> If that isn't enough you could also creat
Hi,
please don't drop the mailing list.
On 18 February 2017 at 21:41, Anthony Sepa wrote:
>
>
> On Fri, Feb 17, 2017 at 10:07 AM Jonas Gorski
> wrote:
>>
>> Hi,
>>
>> Please Cc me for brcm63xx patches, this makes it easier for me to
>> apply th
On 19 February 2017 at 12:50, Mauro Mozzarelli wrote:
> Thanks to those who provided directions.
>
> I will settle with checking on LINUX_3_18.
>
> I am not sure who manages build variables, but in future it would be useful
> to be able to identify which kernel major version we are building for.
On 19 February 2017 at 13:01, Mauro Mozzarelli wrote:
> Author: Mauro Mozzarelli
> Date: Sun Feb 19 11:33:23 2017 +
>
> IPVS (IP Virtual Server) implements transport-layer load balancing
> inside the Linux kernel, so called Layer-4 switching. IPVS running on a host
> acts as a load bala
Hi,
please don't top-post.
On 20 February 2017 at 20:03, Mauro Mozzarelli wrote:
> Jonas,
>
>
> There is in some cases where kernel drivers have changed. As you might see
> in the ip_vs patch I posted, kernel drivers differ in Kernel 3 and 4 and
> thus it is necessary to know which kernel I am b
On 20 February 2017 at 10:47, Jonas Gorski wrote:
> On 19 February 2017 at 13:01, Mauro Mozzarelli wrote:
>> Author: Mauro Mozzarelli
>> Date: Sun Feb 19 11:33:23 2017 +
>>
>> IPVS (IP Virtual Server) implements transport-layer load balancing
>> i
o updater while it is updating
> itself.
Please don't top post, it makes the discussion hard to follow.
Anyway this tidbit was all I was after, so LGTM.
Regards
Jonas
>
>
> On 02/17/2017 06:17 AM, Jonas Gorski wrote:
>> Hi,
>>
>> On 16 February 2017 at 02:1
On 2 June 2016 at 19:18, John Crispin wrote:
>
>
> On 02/06/2016 19:02, Ted Hess wrote:
>> Check it out now...
>>
>
> the funk soul brothers
Hm, it now advertises git protocol, but it isn't actually usable:
$ git clone git://git.lede-project.org/source.git
Cloning into 'source'...
fatal: un
Hi,
On 5 June 2016 at 15:13, Graham Fairweather wrote:
> It would great if someone with the knowledge could take at look and
> see if they know why the 53115 switch is not detected so that this is
> a fully working device.
MDIO connected switches aren't currently supported for bcm6368 and
newer,
Hi,
On 14 June 2016 at 12:55, Rafał Miłecki wrote:
> In kernel 4.7 there is upstreamed b53 driver using (mostly?) the same
> symbols as our b53 does. Change our symbols so both drivers can coexist
> in kernel tree.
>
> Signed-off-by: Rafał Miłecki
Makes sense, so
Acked-b
Hi,
On 22 June 2016 at 09:57, John Crispin wrote:
> Hi,
>
> the issue tracker now announces bug reports on this list
>
> https://lists.infradead.org/mailman/listinfo/lede-bugs
Yay! Thanks a lot.
I wonder if we could change the subject to just "[#] ",
that way gmail and other crappy email client
Hi John,
On 13 July 2016 at 09:39, John Crispin wrote:
> Hi Jonas,
> Hi Felix,
>
> your recent changes to getver.sh are causing a regression when not
> building inside trunk but inside a staging tree
>
> blogic@debian:/lede/staging$ ./scripts/getver.sh
> warning: refname 'origin/master' is ambigu
On 13 July 2016 at 11:13, John Crispin wrote:
>
>
> On 13/07/2016 11:11, Jonas Gorski wrote:
>> Hi John,
>>
>> On 13 July 2016 at 09:39, John Crispin wrote:
>>> Hi Jonas,
>>> Hi Felix,
>>>
>>> your recent changes to getver.sh are cau
On 13 July 2016 at 11:16, Álvaro Fernández Rojas wrote:
> Appart from that, if there's no remote named origin it will also spam some
> errors about having no reference to origin/master.
> My current setup includes lede, staging and github remotes, so there's no
> origin remote at all.
Can you g
On 13 July 2016 at 11:52, Álvaro Fernández Rojas wrote:
> That one is working fine after a small fix:
> https://gist.github.com/Noltari/0c395c57b94598bdf96e6a292c7b5888
> (You're missing one "|").
That's what I get for manually fixing up an older WIP patch ;p.
I added another commit on top, drop
Hi,
On 22 July 2016 at 12:18, Alexey Brodkin wrote:
> With that patch in place for initramfs no additional options are
> reported for "/" partition. What's really important is missing
> info about sizes. Which in its turn makes opkg think that there's
> no space on "/" partition to install softwa
re pushing yourself).
> - sw_dev->ports = sw_dev->cpu_port + 1;
> dev->enabled_ports |= BIT(sw_dev->cpu_port);
> + sw_dev->ports = fls(dev->enabled_ports);
>
> dev->ports = devm_kzalloc(dev->dev,
>
Hi Daniel,
On 28 July 2016 at 22:33, dani wrote:
Please use your full name as From, or ensure you have From: ... as the
first line in your patches. I fixed this up locally, but it would be
nice if I don't have to do that in the future.
I added the patch to my staging tree.
Regards
Jonas
_
contains
"ubi.mtd=rootfs" in its commandline, triggering the misbehaviour.
Fixes: 0ddcbee26151 ("ipq806x: activate ATAG DTB mangle and EA8500 rootblock in
dts")
Signed-off-by: Jonas Gorski
---
This patch is also available in my staging tree at
https://git.lede-project.org/?p=led
Make use of the existing board.d to autodetect lan ifname in a generic way.
Signed-off-by: Jonas Gorski
---
.../files/lib/preinit/10_indicate_preinit | 45 --
1 file changed, 41 insertions(+), 4 deletions(-)
diff --git a/package/base-files/files/lib/preinit
at my staging git at
https://git.lede-project.org/?p=lede/jogo/staging.git;a=shortlog;h=refs/heads/generic-failsafe-networking
Jonas Gorski (7):
base-files: split config generation out of board_detect
base-files: add preinit ifname detection based on board.json
base-files: allow failsaf
Move config generation out of board_detect and allow overriding the
generated json's filename.
Signed-off-by: Jonas Gorski
---
package/base-files/files/bin/board_detect | 10 ++
package/base-files/files/etc/init.d/boot | 2 +-
package/base-files/file
In preparation of properly setting up vlans and switches, add
support for configuring failsafe on a vlan tagged interface.
Signed-off-by: Jonas Gorski
---
.../base-files/files/lib/preinit/10_indicate_preinit| 17 +++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git
Any required vlan setup should be taken care of the generic code, so we
can drop the ramips iface setup.
Signed-off-by: Jonas Gorski
---
.../lib/preinit/07_set_preinit_iface_ramips| 29 --
1 file changed, 29 deletions(-)
delete mode 100644
target/linux/ramips/base
We don't ship vconfig anymore and board.d sets up the lan interfaces
accordingly, so just drop the local version.
Signed-off-by: Jonas Gorski
---
.../lib/preinit/15_preinit_iface_atheros | 35 --
1 file changed, 35 deletions(-)
delete mode 100644
target/
Remove all trivial set_preinit_iface implementation which just set ethX
based on the board name.
Signed-off-by: Jonas Gorski
---
.../lib/preinit/05_set_preinit_iface_adm5120 | 9
.../lib/preinit/05_set_preinit_iface_apm821xx | 9
.../lib/preinit
Also configure the switch based on the failsafe config, and create the
failsafe interface as tagged if necessary.
Signed-off-by: Jonas Gorski
---
.../files/lib/preinit/10_indicate_preinit | 48 +-
1 file changed, 46 insertions(+), 2 deletions(-)
diff --git a
Hi,
On 1 August 2016 at 17:06, Daniel Gonzalez Cabanelas wrote:
No idea why it doesn't appear in patchwork. I checked with the email
from my inbox it applies properly.
> Livebox firmware is totally broken, fix it.
>
> - Fix Image generation: missing "relocate-kernel", wrong "LOADADDR", fix it
>
Hi,
On 16 August 2016 at 16:47, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> On all devices suppored so far BCM53125 got port 8 connected to the SoC
> interface and ports 0-4 to physical ports. On BCM53573 there is slightly
> more comlex setup. We have 2 SoC interfaces: one (eth0) connected to
On 16 August 2016 at 15:40, Rafał Miłecki wrote:
> On 16 August 2016 at 11:55, Rafał Miłecki wrote:
>> I got used to doing some small target modifications, calling "make
>> V=s" and getting new image quickly build.
>>
>> From some time (less than a month I think) modifying e.g.
>> target/linux/bc
iminate two more
package feeds, mips_34kc and mipsel_1004kc.
Only compile tested, due to lack of devices.
Jonas Gorski (4):
ar71xx: switch to 24kc
lantiq: switch from 34k to 24k
include: remove 34k distinction
ramips: mt7621: switch to 24kc
include/target.mk | 2 --
GCC treats 24kc and 34kc exactly the same and will generate identical
code, so there is no need to tune to 34kc instead of 24kc.
Signed-off-by: Jonas Gorski
---
target/linux/ar71xx/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/ar71xx/Makefile b/target
1004kc is just a SMP capable 34kc, and GCC treats 24kc and 34kc exactly
the same and will generate identical code, so there is no need to tune
to 1004kc instead of 24kc.
Signed-off-by: Jonas Gorski
---
include/target.mk| 1 -
target/linux/ramips/mt7621/target.mk | 2 +-
2
GCC treats 24kc and 34kc exactly the same and will generate identical
code, so there is no need to tune to 34kc instead of 24kc.
Signed-off-by: Jonas Gorski
---
target/linux/lantiq/xrx200/target.mk | 2 +-
target/linux/lantiq/xway/target.mk| 2 +-
target/linux/lantiq/xway_legacy
Now that there are no users anymore, drop the 34kc CPU_FLAGS.
Signed-off-by: Jonas Gorski
---
include/target.mk | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/target.mk b/include/target.mk
index 8b94959..ed15d04 100644
--- a/include/target.mk
+++ b/include/target.mk
@@ -167,7 +167,6
Hi Daniel,
On 22 August 2016 at 08:34, Daniel Engberg
wrote:
> Hi,
>
> Before going all in switching to 24kc, 74kc seems to use a different code
> path and looking at datasheets 1004kc seems more similar to 74kc than 24kc.
I'm not sure how you came to this conclusion:
24kc has a 8-stage pipelin
Hi Hauke,
On 25 August 2016 at 23:20, Hauke Mehrtens wrote:
> backport a patch from upstream Linux kernel which stores the appended
> dtb not in the same resisters as defined in the UHI specification, use
> a separate variable on MIPS.
>
> Signed-off-by: Hauke Mehrtens
You will also need to upd
On 20 August 2016 at 21:21, Florian Fainelli wrote:
> Le 17/08/2016 à 23:06, Rafał Miłecki a écrit :
>> On 17 August 2016 at 12:28, Jonas Gorski wrote:
>>> On 16 August 2016 at 16:47, Rafał Miłecki wrote:
>>>> From: Rafał Miłecki
>>>>
>>>&
On 22 August 2016 at 08:48, Rafał Miłecki wrote:
> On 16 August 2016 at 13:47, Daniel Gonzalez Cabanelas
> wrote:
>> Fix the DTS file for the Livebox 1 routers:
>> - leds are totally wrong, fix them.
>> - no failsafe button, use button 1 for this purpose
>> - part probe wrong, it should be RedBo
Hi Daniel,
On 16 August 2016 at 13:47, Daniel Gonzalez Cabanelas wrote:
> Fix the DTS file for the Livebox 1 routers:
> - leds are totally wrong, fix them.
> - no failsafe button, use button 1 for this purpose
> - part probe wrong, it should be RedBoot (uppercase matters)
These are still three d
Hi,
On 30 August 2016 at 19:42, Christian Lamparter wrote:
> The insertion or removal of the sd-card cannot be detected
> by the hardware itself. This is by design. To workaround this,
> for the WNDR4700 unload/load the dwc2 module in case the
> the special SD CARD GPIO line is low/high.
is this
Hi,
On 11 October 2016 at 13:37, Christian Lamparter
wrote:
> Currently, the wifi detection script is executed as part of
> the (early) boot process. Pluggable wifi USB devices, which
> are inserted at a later time are not automatically
> detected and therefore they don't show up in LuCI.
>
> A u
On 11 October 2016 at 13:37, Christian Lamparter
wrote:
> Previously, wifi detect simply dumped its generated wireless
> configuration out to STDOUT. A second step was needed to
> append the configuration to /etc/config/wireless (or create
> it, if it didn't exist).
>
> With this patch, The wifi d
On 12 October 2016 at 20:13, Christian Lamparter
wrote:
> Hello,
>
> On Wednesday, October 12, 2016 1:32:38 PM CEST Jonas Gorski wrote:
>> On 11 October 2016 at 13:37, Christian Lamparter
>> wrote:
(snip)
>> > diff --git a/package/kernel/mac80211/Makefile
83 matches
Mail list logo
