Hi,
While I applaud your achievement I'd don't see such projects viable in
terms of maintainability and longevity.
Pulling in Kodi will result in lots of external packages and
dependencies to make it usable in a reasonable way.
There are several issues with this:
* In general binary size >
On 03/15/2017 11:57 AM, Daniel Engberg wrote:
> Hi,
Huhu,
>
> While I applaud your achievement I'd don't see such projects viable in
> terms of maintainability and longevity.
Applauds from me as well! I started doing so with XBMC a couple of
years
ago and eventually gav
tive maintainers/moderators decide which to use, freeze the old
one and add a banner at the top of each page. Grace period ~1w or so
Best regads,
Daniel Engberg
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Hi,
Thanks for providing a patch, however it fails when applied to master
(83e4ed3497d40dc7da9d2d2c2febbf6272815c51) or maybe I'm doing something
wrong (tm). :-/
.
Applying
/home/diizzy/testme/source/target/linux/generic/patches-4.9/060-0004-mtd-bcm47xxpart-move-TRX-parsing-code-to-separ
On 2017-05-16 11:06, Koen Vandeputte wrote:
On 2017-05-16 10:06, Daniel Engberg wrote:
Hi,
Thanks for providing a patch, however it fails when applied to master
(83e4ed3497d40dc7da9d2d2c2febbf6272815c51) or maybe I'm doing
something wrong (tm). :-/
.
Applying
/home/diizzy/t
Long story short:
* Updated tools/sparse
* Compiles fine on my side (Debian 8)
* Blows up on buildbot (slave-lede-local) because it runs GCC 4.7 (lacks
bswap, 4.8+ works according to
https://sourceware.org/bugzilla/show_bug.cgi?id=20530)
Having a look at the buildbots, it shows that tictex-02
Hi,
I've been trying to fix ath10k (5Ghz) on my C59 (all in the same series
seems to share the same issue) but I'm struggling as I can't find any
documentation on how to debug.
dmesg (trunk), using stock non -CT firmware yields pretty much the same.
http://paste.ubuntu.com/24892442/
Looking
Hi,
This is exactly why I want to add
https://github.com/lede-project/source/pull/1133 so we don't need to
chase around for odd mirrors. :-)
Best regards,
Daniel
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mail
Hi Stefan,
Thanks for submitting a patch, I think however the preferred way is to
use GitHub (PR) as that's the main repo and it's still under the OpenWrt
project.
However, triggerhappy needs a bit more love than just adjusting what
version to pull.
PKG_SOURCE should be changed to xz inste
Hi,
Sorry for for not including the history (not subscribed).
Perhaps taking a peek at
https://github.com/buildroot/buildroot/tree/master/package/perl might
help as they seem to have it working?
Best regards,
Daniel
___
Lede-dev mailing list
Lede-
dated.
Best regards,
Daniel Engberg
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Hi,
I'm in favor of dropping it, don't see anything good in keeping outdated
and unsupported libraries.
As far as package status goes...
shadowsocks-libev --> https://github.com/openwrt/packages/pull/3729 +
https://github.com/lede-project/source/pull/657
pianod + shairport-sync* -->
https:/
Hi,
Thanks for submitting a patch but can you please outline why we would
want to switch from a tarball release to a git repo pull for iperf3?
Best regards,
Daniel Engberg
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http
On 2017-01-15 21:56, Christian Lamparter wrote:
On Sunday, January 15, 2017 9:25:28 PM CET Daniel Engberg wrote:
Thanks for submitting a patch but can you please outline why we would
want to switch from a tarball release to a git repo pull for iperf3?
Actually, it's in the commit. It sa
On 2017-01-15 22:06, Daniel Engberg wrote:
On 2017-01-15 21:56, Christian Lamparter wrote:
On Sunday, January 15, 2017 9:25:28 PM CET Daniel Engberg wrote:
Thanks for submitting a patch but can you please outline why we would
want to switch from a tarball release to a git repo pull for iperf3
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. Please benchmark the impact between 74kc and 24kc on 1004kc
and possibly on 74kc devices before blindly(?) switching.
http://code.metager.
to 4.7
network/utils/tcpdump - Update to 4.8.0
libs/elflibs - Update to 0.167
libs/gettext-full - Update to 0.19.8
libs/libiconv-full - Update to 1.14
libs/libpcap - Update to 1.8.0
libs/ncurses - Update to 6.0
libs/libbsd - Update to 0.8.3 (needs a.out.h, I got stuck on that)
libs/libtool - Update
request.
Best regards,
Daniel
On 2016-10-10 12:24, Daniel Engberg wrote:
Hi,
I've been trying with my limited set of skills to get most packages
and libraries up to date but I'm getting stuck on these below since
they have a lot patches and I can't adapt these for current versio
ing)
Many thanks for helping out!
Daniel
On 2016-10-13 10:08, Daniel Engberg wrote:
To follow up in order to prevent duplicate work,
Michael Richardson has offered to update libpcap in the beginning of
November
Dirk Neukirchen has submitted a patch for libs/gettext-full 0.19.8.1
which has b
19 matches
Mail list logo
