Citeren André Valentin :
Signed-off-by: André Valentin
---
.../patches-4.4/477-mtd-add-spi-nor-add-mx25u3235f.patch | 10
++
1 file changed, 10 insertions(+)
create mode 100644
target/linux/generic/patches-4.4/477-mtd-add-spi-nor-add-mx25u3235f.patch
diff --git
a/target
Hi,
Am 25.10.2016 um 08:58 schrieb Arjen de Korte:> Citeren André Valentin
:
>
>> Signed-off-by: André Valentin
>> ---
>> .../patches-4.4/477-mtd-add-spi-nor-add-mx25u3235f.patch | 10
>> ++
>> 1 file changed, 10 insertions(+)
>> create mode 100644
>> target/linux/generic/patch
On Mon, 24 Oct 2016, Jo-Philipp Wich wrote:
I would be interested in a more contributor oriented insight at this
point. For example it took me a while to realize that being on Github
suddenly means that people edit C code via the web interface without any
means to syntax / compile / run test the
Citeren André Valentin :
Hi,
Am 25.10.2016 um 08:58 schrieb Arjen de Korte:> Citeren André
Valentin :
Signed-off-by: André Valentin
---
.../patches-4.4/477-mtd-add-spi-nor-add-mx25u3235f.patch |
10 ++
1 file changed, 10 insertions(+)
create mode 100644
target/linux/g
From: Paul Wassi
Bump U-Boot for Kirkwood to upstream 2016.09.01. Local patches
cleaned up and reworked. Rename OpenWrt/LEDE occurrences.
Signed-off-by: Paul Wassi
---
This patch bumps uboot-kirkwood to 2016.09.01, some of the local patches
can be dropped then (since already integrated upstream
On 25.10.2016 9:13, p.wa...@gmx.at wrote:
It seems I'm experiencing the same crazy problem. Local builds work
for me (as explained in commit message), but image from buildbot
doesn't boot. This is some totally crazy thing :|
I opt for staying at 4.4 and not reverting, since the issue already occ
From: Paul Wassi
Fix the default value for the 'bootcmd' environment variable.
Therefore make the default bootcmd work for buildbot's images.
Signed-off-by: Paul Wassi
---
The images generated for Dockstar (and probably other devices as well)
have an _uncompressed_ uImage. The bootcmd is 'bootz
Hi Rafal,
did you ever test local builds with all additional kmods (including all
kmods from feeds) enabled as ? I guess this will bump the kernel
size somewhat due to additional subsystems which are getting enabled.
~ Jo
___
Lede-dev mailing list
Led
Hi,
I just discovered why I was getting some crazy results during my various kernel
tests. It seems that LEDE doesn't rebuild images as expected with make -j N.
I think that some/all images may be generated before Image/Prepare step.
// I did initial build with CONFIG_KERNEL_KALLSYMS=y
$ ls -l
On 25 October 2016 at 08:13, wrote:
>> It seems I'm experiencing the same crazy problem. Local builds work
>> for me (as explained in commit message), but image from buildbot
>> doesn't boot. This is some totally crazy thing :|
>
> I opt for staying at 4.4 and not reverting, since the issue alrea
On 25 October 2016 at 09:55, Hannu Nyman wrote:
> On 25.10.2016 9:13, p.wa...@gmx.at wrote:
>>>
>>> It seems I'm experiencing the same crazy problem. Local builds work
>>> for me (as explained in commit message), but image from buildbot
>>> doesn't boot. This is some totally crazy thing :|
>>
>> I
On 25 October 2016 at 10:00, Jo-Philipp Wich wrote:
> did you ever test local builds with all additional kmods (including all
> kmods from feeds) enabled as ? I guess this will bump the kernel
> size somewhat due to additional subsystems which are getting enabled.
No, I never expected extra kmod
Hi,
On Wed, Oct 19, 2016 at 1:10 PM, Florian Larysch wrote:
> Currently, libubox uses json_object_get_int when converting a JSON
> document into a blobmsg. However, json-c stores integers as int64_t
> values and may clamp the value when asked to return it as an int32_t.
>
> Always use json_object
> Anyway I finally debugged this local vs. buildbot difference to the
> CONFIG_KERNEL_KALLSYMS. Images from buildbot have this symbol enabled
> which slightly increases kernel size. Enough to stop it from booting
> on WRT300N v1.
There must be something more...
What I had on WRT54GL:
http://lists.
The bridge name is a copy of the device name; but the device name can
change which is the case when an aliased interface is used as bridge member.
This will result into unwanted side effects like bridge reload triggering
a topology change effect after doing network reload; therefore use the
configu
Similar as when updating a vif; call wireless_interface_handle_link removing
the vif from
the network when deleting a vif
Signed-off-by: Hans Dedecker
---
wireless.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/wireless.c b/wireless.c
index 9109ce1..387f4ba 100644
--- a/wireless.c
+++ b/
Various packages in the feeds and within the base repository provide multiple
build variants with slightly varying feature sets and in some cases packages
rely on functionality that can be supported by entirely different packages,
like using either openssl-util or px5g to generate an RSA certificat
Currently the code emitting dependencies for provide candidates is overwriting
the specification calculated by the previous conditional dependency handling
code, rendering dependencies on virtual PROVIDES packages in conjunction with
conditional dependencies unusable.
Instead of overwriting, appen
Right now the $(PKG_INSTALL_STAMP) files are only written if a package is
selected as <*> but never deleted or emptied if the corresponding package
is getting deselected.
For ordinary packages this usually is no problem as the package/install
recipe performs its own check for enabled packages when
Rename the "ip" package declaration to "ip-tiny" and let both "ip-tiny" and
"ip-full" provide the virtual "ip" package. This allows users to freely choose
the "ip" command variant while other packages can continue to depend on "ip"
without needing to enforce a specific variant.
Note that this comm
Allow CONFIG_TARGET_EXT4_RESERVED_PCT to be empty as make_ext4fs is usually
able to figure out a suitable default.
Signed-off-by: Jo-Philipp Wich
---
include/image.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/image.mk b/include/image.mk
index 8b7d91d..59dd66f 10
There is very little practical use to limit the number of available inodes on
an ext4 filesystem and the make_ext4fs utility is able to calculate useful
defaults by itself.
Drop the option to make resulting ext4 filesystems more flexible by default.
Signed-off-by: Jo-Philipp Wich
---
config/Con
This patch series tunes the ext4 default parameters in order to support
online resize and to make resulting filesystem images more flexible.
The changes should also fix the issue reported at
http://lists.infradead.org/pipermail/lede-dev/2016-September/002518.html
at least for x86 systems.
Change
The current default rootfs size of 256MB in conjunction with 4K blocks
produces an ext4 filesystem which lacks the appropriate amount of backup GDT
entries to support online-resizing.
For x86 targets, increase the default rootfs size to 2048MB which allows
online resizing the filesystem to up to 2
Hi,
> IIUC, your change makes the type of fields vary upon their values.
> I'm wondering how you suggest applications parse the resulting blob messages?
you're right, this doesn't make sense. In my case, the only consumer was
using blobmsg_format_json(), which handles element types dynamically.
From: Paul Wassi
The pogo_e02's dts file has its LEDs named "pogo_e02:(...)"
Fix the status-LED's name for this device.
Signed-off-by: Paul Wassi
---
linux/kirkwood/base-files/etc/diag.sh |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/target/linux/kirkwood/base-fi
Hi all -
First off, thanks for all the feedback, suggestions and volunteers. For
starters, and perhaps to become permanent, we have set up a copy of Discourse
(http://discourse.org) for testing and evaluation. It is a very popular package
for new organizations and it has a pretty active community
Hello all, am having a similar problem with a boot loop. After an
attempted flash of a LEDE build, my router is in a 5-6 second loop.
Am 20.08.2016 um 23:35 schrieb Jochen Demmer:
> yesterday I bricked an Archer C7 v2 by installing some homebrew
(buildroot) lede firmware. > It got stuck i
Hi Felix,
it seems like that this autoconnect feature is causing some regressions and a
headaches to few people :-) I'm talking about this commit in particular:
Author: Felix Fietkau
Date: Thu Sep 22 20:07:45 2016 +0200
uqmi: re-enable autoconnect which was dropped
Hi - a few "armchair" comments from a complete outsider, repeating things that
you probably already know:
> There are large PRs (think the Mikrotik changes) which are unsuitable for
> inclusion as-is, yet too worthwhile to be left rotting.
One of my favorite lines from the first chapter of ESR's
Just my humble opinion.
That piece of software looks great.
Isn't there any other free (as in beer) alternative?
--
Vincenzo Romano - NotOrAnd.IT
Information Technologies
--
NON QVIETIS MARIBVS NAVTA PERITVS
2016-10-25 17:03 GMT+02:00 Ted Hess :
> Hi all -
>
> First off, thanks for all the feedba
Ok, here's some news on this topic.
I've built some images for WRT54GL to test, here come the results:
-) Builtbot's image: does NOT boot (as expected)
-) Local image without KALLSYMS: works fine
-) Local image with KALLSYMS: does NOT boot (which is unexpected,
as such an image booted witho
On Tue, 2016-10-25 at 17:26 +0200, Vincenzo Romano wrote:
> Just my humble opinion.
> That piece of software looks great.
> Isn't there any other free (as in beer) alternative?
> --
> Vincenzo Romano - NotOrAnd.IT
> Information Technologies
> --
> NON QVIETIS MARIBVS NAVTA PERITVS
>
>
The other
From: Rafał Miłecki
This release fixes bugs introduced in 1.4.40 and 1.4.41.
Signed-off-by: Rafał Miłecki
---
Hi Michael,
Since we use the same version in for-15.05 branch, could you backport
this patch there as well, please?
---
net/lighttpd/Makefile | 4 ++--
1 file changed, 2 insertions(+)
Sorry for the incomplete error description.
It can be reproduced if setting up a default x86 generic and add
"kmod-fs-isofs".
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
On 10/25/2016 01:02 PM, Jo-Philipp Wich wrote:
>
> For x86 targets, increase the default rootfs size to 2048MB which allows
> online resizing the filesystem to up to 2TB which is the current theoretical
> maximum for LEDE, due to missing GPT support on the root block device.
>
FYI: in the packag
Hello again,
I have been working on adding support for this router with the
help of SCApi and we got it to the point that Ethernet ports works,
leds and buttons works and wifi card 0xa8d6 43222 works.
The wifi card don't have sprom and I had to write a patch to add
fallback sprom support for t
From: Ben Greear
This should fix problems with latest backports, and also adds
driver support for QCA9888 chipset.
Signed-off-by: Ben Greear
---
package/kernel/ath10k-ct/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/kernel/ath10k-ct/Makefile
b/packag
Adding helpers for virtual interfaces generic options in ncm, qmi, mbim
and directip protocols as suggested by Felix in
https://lists.openwrt.org/pipermail/openwrt-devel/2016-February/039794.html
Signed-off-by: Marcin Jurkowski
---
scripts/netifd-proto.sh | 13 +
1 file changed, 13 i
39 matches
Mail list logo
