Re: [LEDE-DEV] Kodi

2017-03-15 Thread Stijn Tintel
On 15-03-17 13:45, Mirko Vogt wrote: > 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

Re: [LEDE-DEV] Kodi

2017-03-15 Thread Stijn Tintel
On 15-03-17 11:57, Daniel Engberg wrote: > Hi, Hi Daniel, Can you please check why your mail client breaks up the mailing-list thread each time you reply? This is quite annoying as it breaks the flow of conversation. It's even worse than top-posting, please fix this. Thanks, Stijn __

[LEDE-DEV] OpenWrt/LEDE summit dates

2017-03-15 Thread Hauke Mehrtens
This year's OpenWrt/LEDE summit should take place in Prague in October around Embedded Linux Conference Europe (ELCE). OpenWrt/LEDE summit 2017 will not be collocated with ELCE and be free of charge as of the current planning. This event is in the early planning phase, see the website of last years

Re: [LEDE-DEV] [PATCH] ar71xx: change image version for ubiquiti devices

2017-03-15 Thread Mathias Kresin
03.03.2017 16:51, txt.file: changes the image version from hardcoded OpenWrt to $VERSION_DIST. AirOS shows a notification with the image version during a firmware upgrade. fixes #582 Signed-off-by: Matthias Fritzsche --- target/linux/ar71xx/image/ubnt.mk | 6 +++--- 1 file changed, 3 insertio

[LEDE-DEV] [lede] Patch notification: 1 patch updated

2017-03-15 Thread Patchwork
Hello, The following patch (submitted by you) has been updated in patchwork: * lede: [LEDE-DEV] SOC: Broadcom BCM6368 (2 * Broadcom BMIPS4350 V3.1 / 400 MHz) Flash size: 32MB (split 16/16 dual boot) RAM size: 64MB Wireless: BCM432x 802.11a/b/g/n(pci) Ethernet: Broadcom BCM53115 USB: 1 x USB 2.

Re: [LEDE-DEV] Kodi

2017-03-15 Thread Alberto Bursi
On 03/15/2017 11:57 AM, Daniel Engberg wrote: > Hi, > > * Will anyone properly maintain all packages? We're already now > struggling keeping the current repo somewhat up to date and > maintainable, adding very niche packages certainly won't help. > Maintainership depends from each maintainer's d

Re: [LEDE-DEV] Kodi

2017-03-15 Thread Daniel Engberg
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 gave up.. > > Pulling in

Re: [LEDE-DEV] Kodi

2017-03-15 Thread Mirko Vogt
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 gave up.. > > Pulling in K

Re: [LEDE-DEV] Kodi

2017-03-15 Thread Daniel Engberg
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 >

Re: [LEDE-DEV] Kodi

2017-03-15 Thread Alberto Bursi
On 03/15/2017 11:04 AM, Sorin Burjan wrote: > Since OpenWRT/LEDE is mostly destined to routers, which don't have a > HDMI or output port for display, how could someone use Kodi on a > OpenWRT/LEDE router ? > Correct, Kodi is useless if the device does not have a display controller/GPU and a scr

[LEDE-DEV] [PATCH] lantiq: Shortcut non-pppoa interfaces in dsl_notify

2017-03-15 Thread Oswald Buddenhagen
No need to query 'up' and 'auto' when they are not going to be used. Signed-off-by: Oswald Buddenhagen --- target/linux/lantiq/base-files/sbin/dsl_notify.sh | 14 -- 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/target/linux/lantiq/base-files/sbin/dsl_notify.sh b/tar

Re: [LEDE-DEV] Kodi

2017-03-15 Thread Sorin Burjan
I am a happy user of both OpenWRT/LEDE and Kodi/LibreELEC. OpenWRT is installed on my router of course, and for Kodi/LibreELEC I use a HDMI connected Rpi3 to the TV, which works perfectly. I am interested in such a package, but what I don't quite understand is how do you output the display from the

Re: [LEDE-DEV] Kodi

2017-03-15 Thread Stijn Tintel
On 15-03-17 10:20, Bastian Bittorf wrote: > * Stijn Tintel [15.03.2017 10:03]: >> work on Raspberry Pi. My main question now is: is there any interest in >> having Kodi for LEDE at all, or should I not bother preparing it for >> submission. > i like it...any repo where we can see your changes? > U

Re: [LEDE-DEV] Kodi

2017-03-15 Thread Bastian Bittorf
* Stijn Tintel [15.03.2017 10:03]: > work on Raspberry Pi. My main question now is: is there any interest in > having Kodi for LEDE at all, or should I not bother preparing it for > submission. i like it...any repo where we can see your changes? bye, bastian

Re: [LEDE-DEV] Kodi

2017-03-15 Thread Alexandru Ardelean
I'd just add an opinion here. Please take it as such. I think with Kodi [ specifically ] it's one of those sugar-features/packages that could be interesting for tinker-ers to try out when trying LEDE/OpenWrt. Not sure how intensive it would be on the build infrastructure. If you decide to package

[LEDE-DEV] Kodi

2017-03-15 Thread Stijn Tintel
Last week I managed to get Kodi to build for LEDE, and I am running it on my Raspberry Pi Zero W. It's mostly quick and dirty, definitely not ready to push to the repository, and in its current form it will only work on Raspberry Pi. My main question now is: is there any interest in having Kodi for

Re: [LEDE-DEV] [PATCH netifd 1/2] system-linux: parse gre specific settings as nested json data object

2017-03-15 Thread Hans Dedecker
On Tue, Mar 14, 2017 at 11:32 PM, Felix Fietkau wrote: > On 2017-03-14 21:36, Hans Dedecker wrote: >> Parse gre specific settings ikey, okey, icsum, ocsum, iseqno and oseqno >> as nested json data object >> >> Signed-off-by: Hans Dedecker > Are you sure this works? If I remember correctly, uci_to